Decision Velocity for Leadership Teams
Decision Velocity for Leadership Teams is the compression of a leadership team's decision cycle when the team reasons with AI as a thinking partner. It is the ROI anchor of the Havruta Methodology. A decision cycle is the time from a question being raised to a decision being made and owned. Most leadership teams run that cycle slow, because the work between the meeting and the decision is preparation, narration, and the same analysis circulated three times. The Havruta Methodology compresses it, often threefold to fivefold, by changing what AI does inside the cycle: the 4-Lines opening turns AI from a vending machine into a partner that questions the team's reasoning before it hardens into a decision. Velocity here is not speed for its own sake. It is decisions made and owned sooner, with the weak assumption caught before the meeting rather than after the mistake. It is the methodology turned into a number a board will accept.
Why leadership decisions are slow
A leadership team's decision cycle is rarely slow because the leaders are slow. It is slow because of the work that sits between the meeting and the decision, and almost none of that work is the deciding.
It is the pre-read nobody quite finished. It is the analysis that gets re-run because the first version answered the wrong question. It is the half-day spent narrating context to people who already have it, the deck rebuilt to land better, the same three numbers circulated in four formats. By the time the team is in the room, the cycle has already eaten days, and the meeting itself is spent catching up rather than choosing.
The methodology has names for the two thieves. Hidden Headcount is the 20 to 30 per cent of senior capacity consumed by narrating and reformatting work rather than reasoning about it, capacity that never reaches the decision. High-Speed Waste is the plausible commodity output that feels like progress and moves nothing, the faster deck that still opens the meeting on the briefing rather than the choice. Most AI adoption makes the second one worse, because a vending machine is very good at producing more to narrate. MIT NANDA, in The GenAI Divide, found that about 95 per cent of organisations report no measurable profit impact from generative AI, the financial signature of all that motion changing nothing. The cycle does not get shorter. It gets busier.
Without the methodology
Several working days
With the Havruta Methodology
A fraction of the cycle
How leadership teams actually use AI for decision making
Ask how executives use AI for decisions and the common answer is: as a faster analyst. Feed it the data, get the summary, decide. That is the picture most coverage paints, and it is the picture most teams live. Deloitte, surveying thousands of leaders, found that a clear majority now use AI to support their decisions, while only a small minority believe they manage it well (Deloitte, 2026). The usage is near-universal. The discipline is not.
The reason the faster-analyst pattern does not compress the cycle is simple: the slow part was never the analysis. Speeding up the part that was already fast leaves the cycle roughly where it was. You get the summary sooner and still spend the days on preparation, narration, and re-running the work that answered the wrong question.
What does compress the cycle is using AI on the part that was actually slow: the framing of the decision. A thinking partner that questions the team's reasoning before the meeting collapses the days that used to be spent discovering, in the room, that the recommendation rested on an assumption nobody had tested. The decision still gets made by the leaders. It just gets made without the detour. That is the difference between AI as a faster analyst and AI as a thinking partner, and it is the difference between activity and velocity.
The 4-Lines as the mechanism
The mechanism that produces Decision Velocity is the methodology's canonical opening, the 4-Lines: Persona, Goal, the Flip, Sequence. It is the four-line opening that turns an AI exchange from a request into paired reasoning. Of the four, the line that does the velocity work is the Flip, the instruction that makes the AI question the team's thinking before the team commits to it.
Here is how that compresses a cycle. A leadership team at a Fortune 50 pharmaceutical company had been using AI the ordinary way, to format the pre-read and tidy the deck. The decision still arrived at the meeting half-formed, and the meeting was spent stress-testing it live, which is the most expensive place to discover a weak assumption. The change was not a faster model. It was a different job for the machine: before the meeting, the team ran the recommendation through the Flip, instructing the AI to find the assumption the plan could not survive and to question them until it had what it needed. The weak point surfaced in the preparation, where it is cheap to fix, instead of in the room, where it is not. The meeting opened on the decision rather than on the briefing, and the cycle that used to span several working days closed in a fraction of that.
Michael Schrage of MIT names the same posture from the research side: do not treat AI outputs as answers, treat them as hypotheses to test and stress-test, asking for the strongest case against each one before you accept it (MIT Sloan Management Review, 2026). That is the Flip in a sentence, and it is why the velocity is real rather than reckless. The cycle gets shorter because the questioning happens earlier, not because the thinking is skipped.
Velocity without the Flip is just deciding faster, and being wrong faster.
What faster decisions are worth
Decision Velocity is the methodology's ROI anchor because it converts a way of reasoning into a number a board will accept. A leadership team that closes its consequential decisions in a fraction of the previous cycle, without losing quality, has freed the scarcest resource in the company: senior judgement, returned to the decisions that need it.
There is one honest caveat, and it is the whole argument. Velocity is only a gain if the decision quality holds. Deciding faster and being wrong faster is not Decision Velocity, it is High-Speed Waste with a stopwatch. The reason the methodology holds quality while compressing the cycle is the Flip: the assumption is forced to be tested before the decision is made, not after. Take the Flip out and you are left with speed alone, which is the failure mode, not the goal. Keep it in and the compression is safe, because the thing that got faster is the discovery of the weak point, and the thing that got slower, by design, is the moment of accepting an answer without challenging it.
If you want to install Decision Velocity in your own leadership team, working a live decision through the method with me alongside you, that is what the 1:1 Executive AI Enablement Coaching Programme is built for.
Frequently asked questions
What is Decision Velocity for Leadership Teams?
Decision Velocity for Leadership Teams is the compression of a team's decision cycle when it reasons with AI as a thinking partner rather than a vending machine. A decision cycle is the time from a question being raised to a decision being made and owned. The Havruta Methodology compresses it, often threefold to fivefold, by using AI to question the team's framing before the meeting rather than to format the pre-read. It is the ROI anchor of the Havruta Methodology: a way of reasoning turned into a number a board accepts.
How do CEOs use AI for decision making?
Most use AI as a faster analyst: feed it the data, take the summary, decide. That speeds up the part that was already fast and leaves the cycle roughly where it was, because the slow part was never the analysis. The move that compresses the cycle is using AI to question the framing of the decision before the team commits, which is the thinking-partner pattern named in Vending Machine vs Thinking Partner. The decision stays with the leaders; the detour disappears.
What slows down a leadership team's decisions?
Not the deciding. The cycle is slowed by the work between the meeting and the decision: the unfinished pre-read, the analysis re-run because it answered the wrong question, the context narrated to people who already have it. The methodology names two causes, Hidden Headcount and High-Speed Waste, and most AI adoption makes the second worse. The cycle does not shorten, it gets busier. Compression comes from changing what AI does inside the cycle.
Does using AI for decisions improve quality or just speed?
Both, but only if the move is right. Used as a vending machine, AI raises speed and can lower quality, because an agreeable model hands back a confident version of the answer you already had. Used as a thinking partner through the Flip, it raises quality and compresses the cycle, because the weak assumption is caught in preparation rather than in the room. Velocity without quality is just being wrong faster. The Flip is what keeps the compression safe.
What is the difference between Decision Velocity and just deciding faster?
Deciding faster can mean skipping the thinking, which produces fast mistakes. Decision Velocity is the opposite: the cycle gets shorter because the questioning happens earlier, not because it is skipped. The Flip forces the assumption to be tested before the decision, so the part that compresses is the discovery of the weak point, and the part that is protected is the judgement. It is faster and sounder at once, which is why it survives as the Havruta Methodology's ROI anchor.
How does the 4-Lines speed up decisions?
The 4-Lines is the canonical opening that turns AI into a thinking partner: Persona, Goal, the Flip, Sequence. The Flip is the line that does the velocity work, instructing the AI to question the team's reasoning before the meeting. That moves the stress-testing from the room, where it is slow and expensive, to the preparation, where it is fast and cheap. The meeting opens on the decision rather than the briefing, and the cycle closes sooner.
Is Decision Velocity an ROI metric a board will accept?
Yes, which is the point of it. Decision Velocity converts a reasoning discipline into a measure a board already understands: the time a leadership team takes to make and own a consequential decision, and how far that compresses. Because the gain comes from removing the detour rather than skipping the work, it holds up to scrutiny. It is the number that translates the Havruta Methodology from a way of working into a return.
Can any leadership team get Decision Velocity, or only some?
Any leadership team can, because the thing that has to change is not the technology or the talent, it is the move the team makes when it brings AI into a decision. The 4-Lines works with any model and any team willing to let the machine question them before it answers. What separates the teams that get it from the teams that do not is not capability. It is whether they run the Flip, which is what the Eye-Opener Workshop installs.
References
- MIT Project NANDA. "The GenAI Divide: State of AI in Business 2025." July 2025.
- Deloitte. "Decision-making with AI" (2026 Global Human Capital Trends). 2026.
- Schrage, M. "The AI Atrophy Problem: How CIOs Fight It." MIT Sloan Management Review, 2026.