What We Believe
Four positions, in the order they depend on each other
These are not slogans. Each one rules something out, and together they decide what BlackRidge will and will not build.
These are not slogans. Each one rules something out, and together they decide what BlackRidge will and will not build.
The role a leader is moving into decides what development should be. Development only counts if it survives the work. Whether it survived is a question only evidence answers.
The role defines the development. The evidence tells us whether it worked.
The responsibilities change. The decisions change. The relationships change. Development should change with them.
Development budgets are usually organized by level: a program for managers, another for directors. Level is a practical way to schedule a cohort. It is a poor way to decide what a particular leader needs, because two people at the same level can be standing in front of entirely different moves.
A promotion is not a larger version of the last job. It is a different job that happens to carry a related title.
Putting everyone at a level through the same program because they share a title.
We do not start with a course catalog. We start with what the leader will be responsible for next, then build development around those demands.
Naming the receiving role first changes every decision after it. It shows which conversations the leader has not had to have yet, which decisions will arrive without precedent, and which relationships are about to change character.
A competency model describes leadership in general. A named role describes the leadership one person is about to be accountable for.
Choosing the content first and finding an audience for it afterward.
Learning has to survive the real environment, real teams, real workloads, real decisions, and real organizational conditions.
A workshop can create language. Practice creates behavior. Whether that behavior survives depends on what the leader returns to: decision rights, a manager who reinforces the change, and room to try something and get it partly wrong.
When development does not hold, the cause often sits in the conditions rather than in the person. That is a different problem with a different answer, and it is worth telling the two apart before recommending anything.
Treating the classroom as where development happens and the workplace as where it is tested.
Organizations deserve to know what changed, what is developing, and what still needs attention, not simply who attended.
Attendance is easy to count and tells a sponsor almost nothing. Satisfaction scores describe the experience of the session rather than the change in the work.
Useful evidence connects four things: what the transition demanded, where development focused, what was actually done, and what changed afterward. That line is harder to produce, and it is the one worth holding.
Reporting completion rates as though they were outcomes.
A belief you cannot argue against is decoration. Each of these rules something out.
