Decision Making Framework

A VP at a technology company who is widely regarded as a strategic thinker but has a pattern of initiating decisions, soliciting input extensively, and then delaying commitment. His team has learned to wait rather than act. He describes himself as 'weighing all the factors' but the delays are now affecting delivery timelines.

Frame this as a sequencing tool, not a decision-making lesson. 'You already generate options well. This structure is about what comes after the options.' The Issue-Options-Choice-Pros/Cons-Decision sequence forces him to close the loop explicitly. Expect resistance around the Pros/Cons step: clients who delay decisions often believe they're still gathering information. Name the difference: 'There's a point where more information changes the decision and a point where it doesn't. This tool helps locate that threshold.'

Watch whether the client populates the Choice field before completing the Pros/Cons section. Leaders who are genuine decision-avoiders will often arrive at the Pros/Cons step with an empty Choice field - they're still in options mode. Also watch for a Pros/Cons table where every Pro has a corresponding Con - this symmetry usually signals that the client is managing anxiety through false equivalence rather than genuine analysis.

Start with the Choice field. 'What did you write here, and how did it feel to write it?' If it's blank, that's the conversation. Then move to the Decision field: 'If you had written the same Choice three weeks ago, what would have changed?' That question usually surfaces the actual obstacle - which is rarely lack of information. The debrief question that creates movement: 'What's the cost of leaving this in Options mode for another month?'

A team manager, 18 months in the role, who refers every decision beyond routine operations to her director. Her director has flagged this pattern and asked her to 'take more ownership.' She describes herself as 'not confident making the wrong call' and often waits until she can get her director's input before moving.

Frame this as a decision architecture tool rather than a confidence-building exercise. 'The goal isn't to decide faster. It's to see what a decision actually looks like when you decompose it - because most of the time, the hard part is naming the issue clearly, not choosing.' Expect resistance in the form of 'but I don't have enough information' - which is the deferral pattern wearing a rational costume. Name it: 'Let's map what information you'd need and see whether you already have most of it.'

Watch whether she can populate the Issue field specifically. Clients who defer decisions often have difficulty naming the decision itself in concrete terms - they describe a situation but not a choice. If her Issue field is vague or reads as a situation description rather than a decision question, she hasn't yet isolated what she's deciding. Also watch whether her Pros/Cons list populates freely or stalls - stalling at this step usually signals that the real obstacle is risk aversion, not information deficit.

Start with the Issue field. 'Read what you wrote here. Is this a decision you could make with the information you currently have?' Then move to Decision: 'What would you tell your director you've decided if you had to send that message right now?' The discomfort of imagining the message usually reveals what the actual blocker is. The question that creates movement: 'What's the worst outcome if you decide wrong - and how reversible is it?'

A founder, five years in business, who has operated on instinct and speed and built a successful small company on it. He is now facing a hiring decision for a COO role - the first senior hire - that would meaningfully change the company's trajectory. He is uncomfortable with the slower pace this decision seems to require.

Don't suggest his instinct is wrong. 'This tool isn't replacing your pattern recognition. It's capturing your reasoning so you can examine it.' Founders who have built on instinct can be skeptical of structured analysis - it feels like bureaucracy. Frame the Issue-Options-Choice sequence as documentation of what he's already doing mentally, not a substitute for it. 'You've already been running this analysis. Let's see what it looks like written down.'

Watch whether his Pros/Cons list contains items that are genuinely different or whether they're all variations of 'she's a strong operator' versus 'she's expensive.' If the analysis is thin, the intuition hasn't actually been examined yet - it's been asserted. Also watch the Timeline field in the Decision section: founders who move fast often set unrealistically short timelines for high-stakes decisions and then experience a confidence crisis when they miss them.

Start with the Options field. 'Walk me through the three options. How did you arrive at them?' This surfaces whether he's actually considered multiple options or has already decided and is now building a rationale. Then ask about the Pros list: 'Which of these would matter in year three, and which only matter now?' That time-horizon shift usually reveals what the decision is really optimizing for. The question that creates movement: 'If you had to defend this hire to your board in 18 months, what would you want to be able to say you analyzed?'