A working session that validates the few decisions your business is actually rooted in, and leaves your leadership team with a shared language for every decision that follows.
Is this the right thing for this business to do, measured against what we have already decided we are?
Do we have the evidence, the capability, and the standing to actually do it?
Will the people who have to live with this decision carry it, or merely comply with it?
Most organizations answer the second one. Some answer the first. Almost none answer the third before committing, which is where execution quietly goes wrong.
The point at which an organization's ability to create, execute, and scale new value consistently exceeds the rate at which disruption erodes its existing value.
Below that line, you consume best practices, copy competitors, and work harder every year to stay level. Above it, you create markets and competitors react to you. The formula is a product, not a sum. That is the part that matters.
Try raising Execution. The verdict doesn't move. When your competitors have the same tools, execution speed cancels out of the inequality. It raises the rate of disruption at exactly the rate it raises your output. Only Innovation and Adoption change where you sit.
Execution got cheap. Judgment did not.
For thirty years capability was the constraint, so capability is what companies bought, and it worked, because a team that could execute better than its competitors was genuinely ahead. AI has collapsed the cost of execution. The two factors that never came from tools are now the ones that decide the outcome.
Still necessary. No longer where the advantage is. Reskilling moves a person to different work; upskilling makes them better at the same work. Both are real investments and both should continue.
But they raise the factor your competitors are raising in the same quarter, with the same tools, from the same vendors. Capability that everyone acquires simultaneously does not separate anyone.
Upthink changes what gets asked before anyone acts: a better question, earlier, from a team that shares a standard for what counts as validated.
Rethink turns that standard on the decisions you already made and never revisited. The anchor decisions everything else inherits from, tested against today's evidence rather than the case that was true when you made them.
This is not an argument against training. It is an argument about which factor your training is aimed at, and about the one nobody can buy off a shelf, because it is specific to the decisions your business is actually rooted in.
Automation does not fix a decision. It scales one, and makes it permanent before anyone catches the flaw. The faster you can execute, the more the quality of the decision underneath determines what execution is worth.
Underneath those three questions sit five validation channels, running in parallel on every consequential decision: evidence, social confirmation, lived pattern, institutional standing, and desire. They compete for primacy, and most of the time a leader feels only the loudest one.
One channel fired. That is what certainty feels like from the inside.
That single channel firing produces the felt sense of having validated. It is not the same thing as having validated. We call the difference the dominance-sufficiency error, and it explains why confident decisions quietly go wrong, and why post-mortems so often find reasoning that was never actually there.
This is the layer beneath strategy and execution. It is also the layer nobody audits.
Five channels are a diagnostic. Three questions are what a leadership team still uses in a Tuesday meeting six months later, which is the difference between a workshop people enjoyed and a workshop that changed something.
Mission. Values. Goals. The commitments the business is rooted in. If a team answers should we from scratch in every meeting, they are re-litigating their own strategy implicitly, and usually settling it by whoever is most senior or most certain in the room. A verified reference frame makes this question answerable in two minutes instead of two hours.
The question most organizations are good at, and the one most often asked first. Asked first, it produces capability-led strategy: the business does what it is already good at, or what a vendor demonstrated, and constructs the rationale afterward. Every AI pilot that started with a tool rather than a decision is this failure.
Most organizations ask this during rollout, framed as "how do we get buy-in." By then the decision is made and the resources are committed, and the question has been demoted to a communications problem.
Asked before you commit, "will people?" is a validation input. Asked after, it is a change management cost.
Teams leave with a one-page protocol they run themselves, without a facilitator present. It ends with the only instruction that really matters: whichever question you answered fastest is the one to check twice.
Every business rests on a small number of anchor decisions: which market, which model, which capability you are betting on, who you are for. Downstream decisions rarely fail on their own merits. They fail because they are executing an anchor that was never validated, or because different leaders are executing different anchors.
Those anchors are usually the least validated decisions in a business. They were made early, under pressure, by fewer people, then retroactively justified by everything built on top of them since.
So the day ends by turning the method on the anchor itself. Your team spends the session learning to validate ordinary decisions. Then they apply it to the one everything else inherits from.
Every channel fills on current evidence. Your anchor is sound and the constraint sits somewhere downstream. This is a real outcome and we have delivered it.
One channel cannot be filled, and we name which. Usually evidence: the case that was true when the decision was made and has never been re-tested since.
The anchor cannot be defended on current evidence, or your leaders do not agree what it is. You leave with the specific gap, the evidence that would close it, who gathers it, and by when.
All three outcomes are stated to the room before the pass is run, so nobody spends the afternoon wondering whether the result was decided in advance.
Your leadership team already knows how to decide. That is why they hold the roles they hold. The day examines the reasoning they are already running, in a room where it can be looked at directly. The framework is never taught first.
The team works a decision under real constraint. Nobody is told what is being observed, because knowing changes it.
Not what was concluded, but what caused the room to converge. New evidence, or the moment someone senior spoke. The distinction is uncomfortable and instructive in equal measure.
Taught first, a framework is a claim to be evaluated. Taught here, it names something that just happened to the people in the room.
Real questions the business currently faces, worked through every channel under time pressure. The channel a team cannot stay inside is the finding.
Not intentions. A specific change to how this team validates before it commits, and the decisions it applies to, written down.
Three things, taught together because they only work together: strategic alignment on what the business has already decided, a method for validating decisions against it, and the judgment to tell which decisions are safe to hand to a machine.
Most of what reaches a leader looks like work and is actually a decision wearing work's clothes. Recognizing the difference is what makes the rest of the day possible.
Evidence, social confirmation, lived pattern, institutional standing, and desire. What each one is good for, and where each one turns on you.
Which one fires first for you, what it feels like from the inside, and why that feeling is not the same as having validated anything.
Name the moment one channel's activation gets mistaken for a complete answer. In your own reasoning, on a decision you actually made.
Should we, can we, will people. Why the order matters, and what it costs when the third one gets asked during rollout instead of before commitment.
Mission, values, and goals as a working reference frame rather than a wall poster. Teams that skip this re-argue their own strategy in every meeting without noticing.
When a decision keeps coming back, something the person it went to was never given. Learn to name which of the five it was, precisely enough to build it.
Automation does not improve a decision, it scales one. Learn to tell which decisions are validated enough to hand to a system, and which would simply propagate a flaw faster than anyone can catch it.
Apply the method to an anchor decision the business has been executing for years, against today's evidence rather than the case that was true when it was made.
The point is not that your team can do this with us in the room. It is that they can do it in a Tuesday meeting three months later, on their own.
A one-page standard the team runs itself, in its own meetings, without a facilitator present. The artifact most likely to still be in use a year from now.
A scored reading of how you believe you validate, anchored to one real decision you brought with you. Returned to you individually, never to your manager or your team.
The distance between how you believe you validate and what you demonstrably did during the day. This is the finding, not the score, and it is the only thing here you could not have arrived at on your own.
The result of the Anchor Pass in writing: what held, what did not, the specific gap, the evidence that would close it, who gathers it, and by when.
A written executive review follows within five business days, covering the team pattern and the dominant channels in the room. No individual results appear in it. The full day includes a 30/60/90-day reinforcement sequence, because vocabulary acquired in a day is not the same as behavior changed over a quarter.
Decision maps, authority maps, and architecture build plans are outputs of the Decision Intelligence Workshop, which is a separate engagement. They are described further down.
The method is the same in every room. What changes is which decisions get worked, and that comes from the people who walk in, not from a different curriculum.
An executive team attending together, working the decisions they are actually facing. Strongest at six to twelve, where every person can be heard on every decision and disagreement has nowhere to hide.
Owners and CEOs of growing businesses, with their leadership team or alongside other owners. In a cohort, the comparison across companies does work that no single-company session can.
The people who carry decisions they did not make, and who make plenty of their own. Same framework, same three questions, applied to the decisions in front of them.
Eight participants are required to run a session and ten are billed. Up to twenty-five in a room; above sixteen a second facilitator is included. Groups drawn from one intact team produce a sharper team pattern than a mixed group, but the workshop works either way.
Both are the Decision Validation Workshop. Same framework, same three questions, same instrument. The longer format does not cover more ground; it stays on the same ground longer, with more of your own decisions in play.
The framework, the assessment, breakouts, and the pattern named. Your team leaves seeing how they decide, where it costs them, and holding the three-question protocol.
Adds the diagnostic passes, the cost simulation, the design work, and the Anchor Pass, where the method gets turned on a decision the business is already rooted in.
Cohorts running across several sites or business units, sessions delivered to more than one team in sequence, groups larger than twenty-five, and internal facilitator licensing are all scoped individually.
Eight participants are required to run a session and ten are billed. Materials are included for every attendee. Most clients fund this from leadership development, alignment, or AI-readiness budget rather than consulting spend.
Two things can follow the workshop. Neither is a prerequisite for the other, and neither is assumed. Plenty of teams do the workshop and nothing else, which is a legitimate outcome and sometimes the right one.
A working session on one to three anchor decisions, with only the people who can actually commit to them in the room. The workshop teaches the method and tests one anchor. This applies it in full to the decisions everything else inherits from, and does not end until each one has a verdict, an owner, and a date.
Moves from judgment to architecture: how decisions actually travel through the business, who decides what, and what has to exist before a decision can safely leave someone's desk.
Produces a decision map, an authority map, and an architecture build plan.
Scoping and investment for both depend entirely on what the workshop finds, so we do not quote them in advance. If your anchors hold and your decisions are moving, we will say so and recommend neither.
The team pattern is shared with everyone in the room, including you. Individual results go to individuals only and appear in no report. That agreement is signed before anyone is assessed, and it is the single thing that makes honest answers possible.
Your profile is yours alone, on exactly the same terms as everyone else's. You appear in the aggregate, unattributed, which means the pattern the room sees includes you, and nothing about your individual results reaches the written review. This is the question most leaders are actually asking, and it deserves a direct answer.
The Anchor Pass can conclude that your anchors hold, and when it does we say so and recommend the build rather than more diagnosis. A facilitator who has never delivered that outcome is steering, and we treat that as a certification failure. All three outcomes are stated to the room before the pass begins.
That is the real cost, and it is considerably larger than the fee. It is also why the day is built the way it is: no lecture, no icebreakers, no content that could have been an email. Every hour is your team working your decisions. If you can only spare half a day, take the half day. It is a real product, and we will tell you plainly what it does not include.
Those assign roles. They tell you who holds the decision. They do not tell you whether the person holding it can actually validate it: whether they have the data, the standing, the pattern, the backing, or the safety to be wrong. That is the layer underneath, and it is why decisions with clean charts still do not move. If you already run one, we test whether the roles you assigned are executable.
A thirty-minute scoping conversation. We take one live decision, run it through the three questions together, and determine whether the full session is the right fit for your team.
Book a Decision Clarity CallIt is not a sales call. You leave with the decision examined either way, and if the answer is that you do not need this, we will say so.