Framework
A diagnostic for finding which layer is producing the results you have, which one must change for the results you want, and what way of being underneath has to shift for the change to hold.
Four layers produce results. Being is the through-line that connects them.
Four layers
Being
Execution
Action that delivers.
Decision-making
Choices that produce real decisions.
Alignment
Same problem, plain language.
Trust
The foundation underneath.
Through-line
Being
Who you are while the work is happening.
When results stall, one layer is usually broken — often the one no one will name.
Read from the foundation up. When a layer is broken, everything above it compensates — until the system exhausts itself.
The foundation everything else rests on.
Without trust, alignment is performance. Decisions get re-litigated after the meeting. Execution becomes compliance. Most stalls that look like strategy problems are trust problems no one will name.
Can this group absorb honest truth — and act on it?
Agreement on what we're actually solving for.
Teams can agree on a slide and still be solving different problems. Alignment is whether the work in the room matches the outcome the leader is accountable for — not whether everyone nodded.
Are we solving the same problem — in plain language?
Choices that produce real decisions.
Many organizations confuse discussion with decision. Real decision-making names who decides, by when, with what input — and what will be different in the world afterward. Equally important — how do we resolve differences at pace?
What is actually decided — and who owns it?
Action that delivers.
Execution is whether the system produces the result without the leader personally pushing every ball uphill. When all layers are sound, execution stops depending on heroics.
Is the result happening proactively without you in the middle?
The through-line that holds the four layers together — what it means in practice.
Through-line
Who you are while the work is happening.
Being is the through-line that holds all four layers together. When who you are being does not match the change you are asking for, the layers leak — especially under pressure.
Engagements usually have to name this, even when the presenting problem sits higher in the stack.
Not a template — a map we return to when results stall or a transition has to hold.
Start with outcomes as they are — not the story about why. The engine maps backward from results to the layer producing them.
Usually one layer is under-running. Teams often over-invest in execution when trust or alignment is the actual constraint.
Being is who you are while the work is happening. When it does not match the change you are asking for, the layers leak — especially under pressure.
Interventions at the top layer without working underneath regress. Engagements stay until the new way of operating survives pressure and time.
Next step
A conversation is usually enough to name the layer — and whether being underneath is the constraint.