The Application Learning Path: Running Real Decisions

The Application path is a curated six-step sequence that turns decision-making concepts into runnable practice, mirroring the applied arc of our long-form curriculum — decision analysis and structured deliberation in real organizations. It is built for people who facilitate or own real decisions: team leads, product managers, engineering leads, and facilitators who finished the Foundations path or already hold its concepts. The sequence and its reasoning: first, the business decision frameworks chooser — because the most common applied mistake is grabbing the wrong tool, and the router (which situation calls for which framework) prevents it; second, SWOT analysis run properly — the most-used framework in business, taught with the disciplines (a decision anchor, evidence per entry, forced ranking) that separate working sessions from wall art; third, the pre-mortem facilitation tutorial — the highest-value-per-hour ritual in the applied toolbox, and the first full facilitation script in the path; fourth, the design sprint tutorial — a complete multi-day decision process showing every method element operating across a week; fifth, decision records and ADRs — because a decision that isn't recorded gets relitigated, and capture-as-you-decide beats write-up-afterwards; sixth, stakeholder buy-in — the step that makes the other five land in organizations, reframing buy-in as showing inspectable reasoning rather than selling conclusions. After the path you should be able to choose a framework by situation, facilitate a pre-mortem end to end, and leave every consequential decision with a record that survives staff turnover.

All learning paths
Learning path · Application

Application: Running Real Decisions

Six readings from chooser to practice: pick the right framework, run the session, keep the reasoning, win the room. For the person who actually facilitates.

Who this path is for

This path assumes you own real decisions — as a team lead, product or engineering manager, or facilitator — and either finished the Foundations path or already carry its concepts (the method's five elements, the named traps, the crowd-wisdom conditions). The output here isn't understanding; it's runnable procedure: sessions you can facilitate this month.

The sequence mirrors the applied arc of the long-form curriculum behind our content — decision analysis and structured deliberation applied inside organizations — compressed to the six readings with the highest practice-per-page ratio.

Why this order

Applied decision-making fails in a characteristic way: teams learn one framework and apply it everywhere. So this path starts with the chooser — matching tool to situation — before any single tool. Then it deepens one framework properly (SWOT, because you'll meet it everywhere), adds the two highest-leverage rituals (pre-mortem, then the full sprint), and closes with the two steps that make everything durable: recording decisions, and getting organizations to actually commit to them.

The path, step by step

  1. 1
    Business decision frameworks: the chooser's guide

    The router: which decision situation calls for which framework — and why frameworks are input generators, not decision makers.

    First on purpose: the most common applied mistake is reaching for the familiar tool instead of the fitting one. The chooser's situation-groups give you the map before the territory — and its framework-theater warning (a framework without the reasoning step is four lists) sets the standard every later step meets.

  2. 2
    SWOT analysis, run properly

    One framework in full depth: decision anchoring, evidence per entry, forced ranking, and the argument-tree mapping.

    SWOT is the framework you'll encounter most, and the one most often wasted — which makes it the ideal deep-dive: the disciplines that rescue it (anchor, evidence, ranking, pairing) transfer to every other framework in the library. The worked example doubles as a facilitation template.

  3. 3
    The pre-mortem, facilitated

    A complete 60–90 minute facilitation script for the highest-value ritual in the toolbox.

    Your first full session script. The pre-mortem earns its place by ratio — one hour, and the risks your team already knows but won't say become plan inputs. Its silent-independent-writing mechanic is also the purest live demonstration of the independence condition from Foundations.

  4. 4
    Design sprints that survive Monday

    A multi-day structured decision process — every method element operating across one week.

    The scale-up: where the pre-mortem is one session, the sprint is a whole decision arc — framing Monday, surfacing and challenge midweek, weighted choice Wednesday, evidence Friday. Running (or even just reading) one shows how the five elements chain in practice, and its Friday-findings-to-Monday-hypotheses link is the record discipline the next step generalizes.

  5. 5
    From RFC to ADR: keeping the reasoning

    Decision records that fall out of the process instead of being written up afterwards.

    The durability step. An unrecorded decision gets relitigated every quarter and dies with staff turnover; this tutorial's core move — run the debate as structure so the record is a by-product, not homework — is what makes everything earlier in the path compound instead of evaporate.

  6. 6
    How to get stakeholder buy-in

    Buy-in as inspectable reasoning: showing the case instead of selling the conclusion.

    Last because it's the multiplier. The best-run session fails if the organization won't commit; this reading reframes buy-in from persuasion to transparency — stakeholders commit to decisions whose reasoning they can inspect — which is exactly what the recorded, structured decisions of steps 2–5 make possible.

Frequently Asked Questions

Do I need the Foundations path first?

It helps considerably but isn't mandatory. The Application readings are self-contained enough to run sessions from — the tutorials carry full facilitation scripts. What Foundations adds is the diagnostic layer: knowing the five method elements and the seven traps means that when a session goes sideways, you can name which element failed and which trap fired, instead of just improvising. Facilitators without that vocabulary tend to fix symptoms; with it, they fix causes.

Which step should I actually run first with my team?

The pre-mortem, almost always. It has the best ratio in the applied toolbox — 60 to 90 minutes, a full facilitation script, and a mechanism (silent independent writing about imagined failure) that makes the risks people already know sayable. It also requires no prior team training and produces immediately usable output: risks attached to the plan they threaten. Success there builds the credibility to run the longer rituals — a structured SWOT session next, then a sprint when a decision deserves a week.

What comes after the Application path?

The Mastery path — the organizational layer. Application makes you effective within single decisions; Mastery addresses the system around them: the decision-quality standard for judging process, enterprise decision excellence, governance (who decides), decision-rights frameworks like RAPID, and decision intelligence. The transition question is the tell: when you stop asking 'how do I run this session well?' and start asking 'why does this organization keep deciding badly between my sessions?', you're ready for Mastery.

Run your first structured session this week

Pick the smallest real decision on your desk, open a tree, and walk it through the method — the path's readings work best next to live practice.

Start Free — No Credit Card

Free forever for individuals