The Bearing Framework
A map I use when the terrain will not hold still.
Framework · 18 pages
Most planning assumes the ground stays still.
Most strategy work I have seen inherits the same quiet assumption: define the goal, draw a line from here to there, execute the plan. That works when the ground is stable. It rarely is.
Funding landscapes shift. Community needs evolve. Partners restructure. Technology ages. The terrain changes before execution begins, and the plan that looked honest in the room looks naive by the time it reaches Monday.
I built The Bearing Framework for the reality I actually see. Not as a prescription. As a map. Five stages I come back to when a leader I am sitting with needs a way to read where they are standing before they choose the next move.
The question underneath is navigational, not strategic.
Strategy asks where we want to go. Navigation asks where we actually are and what the ground in front of us will allow. Leaders who confuse the two end up with beautiful plans and brittle execution.
Every time I walk an organization through this, the first stage takes the longest. Not because the data is hard to gather. Because the stories people have been telling themselves about the organization turn out to be half a generation old.
Five stages. One cycle. Higher ground each time.
Clarity
Stop pretending to know where you are.
Every organization I work with enters fog naturally. The calendar fills, the team adapts, the founder or ED stays close to the fires, and nobody stops long enough to draw a map of the actual ground. Clarity is the discipline of stopping. We look at where capacity truly lives, which programs are generating leverage and which are consuming it, what the funding base really depends on, and which stories about the organization stopped being true two years ago.
The move for the leader
Name what you are seeing but cannot yet articulate. Write it down in one sentence. If that sentence scares you slightly, it is probably closer to the truth than the narrative you have been presenting.
The trap
Racing to solutions before the map exists. Most of what feels like strategy failure is actually map failure. The plan was honest about a terrain that did not exist.
Leverage
Find the fulcrum. Stop building from scratch.
Once the map is real, I look for the structural advantage already in the building. Every organization I have worked with has underutilized assets, relationships, programs, or positioning that could change the arithmetic. Leverage is the act of finding the point where small, deliberate effort produces disproportionate result. It is the opposite of founding every initiative fresh.
The move for the leader
List three assets nobody is talking about. A relationship, a dataset, a reputation, a building, a capability you developed for one program and never reused. Ask what would happen if you treated one of them as the center of gravity instead of the sideline.
The trap
Over-investing in new initiatives when the answer was already on the roster. Exhaustion from building from zero, over and over.
Direction
Choose, sequence, and make the tradeoffs explicit.
Direction is not a to-do list. It is a set of prioritized, sequenced decisions with clear ownership, tradeoffs made explicit, and the structural reinforcement that lets the direction hold. A plan that cannot name what it is saying no to is not a plan. It is a wish list. I push hard here, because this is where most strategy work quietly fails: the document leaves the retreat with five priorities, which is another way of saying none.
The move for the leader
Write the three decisions this quarter actually depends on. For each one, name the tradeoff you are accepting and the signal that would tell you the decision was wrong. If you cannot name the disqualifying signal, you have not made a decision yet.
The trap
Mistaking a list of intentions for a set of decisions. The plan reads well and survives no contact with reality.
Execution
Stay close while strategy meets reality.
Reality pushes back on every plan. Execution is the stage where the organization discovers which of its assumptions were load-bearing and which were decoration. I stay embedded here when I can, because the decisions that matter most happen in the tensions no plan anticipated: a funder moving a deadline, a key hire leaving, a program producing unexpected demand, a partner changing direction. The job is not to defend the plan. It is to help the leader read what the terrain is now saying.
The move for the leader
Run a short weekly rhythm that separates what the plan predicted from what the terrain is now showing. Treat divergence as information, not as failure.
The trap
Defending the plan against the evidence. The meeting becomes about status, not reality. The organization misses the signal until the signal has become a crisis.
Momentum
Enter the next cycle from higher ground.
Momentum is not speed. It is the compounding effect of the first four stages working together. The organization stops starting over every quarter. The systems that were built in the last cycle carry weight in the next one. Leaders notice that the work is producing evidence of itself, not just activity. That is the signal that the cycle is ready to repeat, one level higher than it started.
The move for the leader
Before the next planning cycle, ask what compounded. Name the systems, relationships, or capabilities that are stronger than they were twelve months ago. Protect those. Start the next cycle from that higher ground.
The trap
Declaring momentum because the calendar rolled over. Restarting from zero each year because the compounding work was never named, never protected, and quietly eroded by the next round of initiatives.
Not a consulting methodology. A way of seeing.
I am not offering this as a service. I am offering it as the map I actually use when I sit with a leader whose plan has stopped working and whose board is asking for certainty the terrain will not provide.
If this names something you are already feeling, take it. Apply it to the hardest room on your calendar this quarter. If it does not, it is not the right tool, and that is also useful information.
Either way, I would rather this be a useful artifact in your thinking than a frame you adopt because someone handed it to you.
Get the PDF.
Enter your details and I will send it to your inbox. You will also get the occasional piece of writing. Unsubscribe anytime.
I did not invent this. I synthesized it from the thinkers I come back to most.
Ronald Heifetz — Adaptive Leadership
The distinction between technical problems and adaptive challenges. Most strategy failure is an adaptive challenge misread as a technical one.
Jim Collins — Flywheel and Doom Loop
The mechanics of compounding. Why momentum matters more than speed, and how organizations lose it without noticing.
Robert Kegan — Immunity to Change
Why competent leaders sincerely commit to change and then produce the opposite. The stories underneath the stated goal.
Eliyahu Goldratt — Theory of Constraints
Leverage lives at the constraint. Improving everywhere else is motion disguised as progress.
Edgar Schein — Organizational Culture
The terrain beneath the org chart. The underlying assumptions that decide which strategies actually hold.
Marvin Weisbord — Six-Box Model
A diagnostic instinct for seeing the whole system at once: purpose, structure, relationships, rewards, leadership, helpful mechanisms.