Diagnosis
Best on laptop or desktop
Start a brief

What’s the decision in front of you?

Bring it as it stands — messy is fine. You’ll get a committed read, the reasoning behind it, and a plan you can run.

The situation
Add to the brief
Try:
Confidential — your text is used to build your brief, never to train. Attachments are read for the run and never stored.
Read an example brief →
Reading the problem
The Problem

1Classify: What kind of problem, and what decision actually needs to be made
2Hypothesize: What's most likely broken, and what would change that view
3Probe: The issue tree, built to test the diagnosis
4Validate: What to prove and how to prove it
Appears on the PDF's cover — never on the LinkedIn card.
One brief, one file — it grows as you go. Build the strategy and the plan, and this same download becomes the full brief.
What's next
The diagnosis is done.
Build a recommended strategy with three evaluated options and a 90-day execution plan — specific to this problem, not a generic template.
Structuring the problem
Compiling diagnostic into a machine-operable blueprint
Typically 10–15 seconds
Stage 05
Strategy: Three paths. One call it stands behind.
Primary leverage point
Recommendation pre-selected. Select a different option to change it, then build the execution plan.
Stage 06
Execution Plan: 90 days.
Account