Read the signal
How to use this diagnostic
This page is a triage tool, not a checklist. Start by mapping the behavior you see (what keeps happening, where it happens, who repeats it) and then use the short decision prompts below to pick the next reading. Each linked guide on the site focuses on a different pattern: some problems come from overload and process friction, others from emotional or reputational commitments. Use this diagnostic to narrow the cause quickly, then follow the recommended guide or implement the local fixes listed here. The goal is to reduce wasted meetings and better calibrate who decides what, when, and with which data.
Map where the pattern happens (meetings, hiring, scoping)
Pick the most similar problem pattern before applying fixes
Use one guide at a time-test one change across a few decisions
Part 2
Distinguishing similar patterns: what to watch for
Different biases look alike in practice: stalled options, repeated approvals, or escalation of effort can arise from distinct causes. Choice overload shows up as lots of late-stage comparisons, new options introduced at approval, or defaulting to status quo. Sunk cost shows as defenders citing past spend, emotional ownership, or repeated scope additions to justify continuation. Anchoring and first-proposal effects occur when the initial number or timeline largely determines the rest of the conversation. Confirmation and availability biases favor familiar vendors, metrics, or anecdotes. Planning fallacy appears when teams repeatedly underestimate time and resources despite past misses. Use short tests-ask whether the argument references past investment, whether fresh options are blocked, or whether the initial proposal drives the outcome-to separate these patterns.
If the debate cites past spend, consider sunk-cost fixes
If many options appear late, consider choice-overload tactics
If the first number sticks, assess anchoring and reset framing
Part 3
Quick checks leaders can run in meetings and panels
Run three quick checks during a review to triage bias risk. First, timebox the rationale: ask each advocate to state the top decision criteria in one sentence; if people struggle, the meeting will drift. Second, scan for commitment language-phrases like 'we've always' or 'we've invested' signal sunk-cost dynamics. Third, inspect option flow: are new alternatives appearing late or are reviewers reverting to defaults? These checks cost a minute each and reveal whether you need structured options, a reframe, or governance intervention. If the checks implicate process rather than preferences, pause and set a follow-up with a defined evaluation template rather than extending the same meeting.
Timebox a 30-60 second criteria statement from each stakeholder
Listen for 'we've already' or 'we can't stop' as sunk-cost flags
Note whether options are added late-if so, use a scored rubric
Part 4
When to open the deeper guides on the site
Use the site guides when the quick checks point to a specific pattern. Open the Choice Overload guide when decisions stall with too many plausible options, frequent last-minute additions, or a cycle of extra reviews. Read the Sunk Cost Fallacy guide when defenders justify continuation by past effort, budget, or prestige rather than forward-looking value. If anchoring, confirmation, or planning fallacy are central, choose diagnostics and playbooks that focus on framing, evidence standards, and retrospective learning. Each guide includes meeting scripts and governance templates; pick one primary guide to pilot for a month and collect outcome metrics before layering additional fixes.
Choose Choice Overload when options multiply or reviews repeat
Choose Sunk Cost when arguments rely on past investment
Pick framing or planning guides for anchors and repeated underestimates
Part 5
Immediate fixes and governance moves to try first
If you need quick improvement, apply lightweight governance: require a one-paragraph decision memo before reviews, limit the active option set to three, and assign a decision owner with a timeline. Introduce an explicit stop rule for projects showing no forward-looking value for two consecutive reviews. For hiring panels, anonymize early screening and use scored rubrics to prevent availability and confirmation biases. Run a short post-decision review after three months to capture learning on estimates and assumptions. These moves reduce repeated errors with minimal overhead and create data you can use to decide whether deeper process redesign is necessary.
Require a short decision memo and a named decision owner
Limit active options to three and use a scored rubric
Add a two-review stop rule for projects lacking forward value