Strategy Deep-Dive
Find the right problem before you commit.
A single day to sharpen who you are serving, the problem worth solving for them, and the directions worth testing next.
Why this exists
Most teams don't suffer from a shortage of ideas. They suffer from a shortage of clarity about which ideas matter, and a backlog of assumptions that no one has named out loud.
Building before you have named the right problem is the most expensive way to find out you didn't. The Strategy Deep-Dive does that work in one session: who you are serving, the problem worth solving for them, and the assumptions still being treated as facts.
It will not tell you the answer. It will leave you with a sharper bet, the assumptions worth testing first, and a much smaller chance of building the wrong thing.
How it works
One day on the calendar, three movements before and after.
Pre-session intake
A short call to surface the situation, the people in the room, and the question we are actually trying to answer.
Facilitated session
A focused 3 to 4 hours: who you are serving, the problem worth solving for them, and the assumptions still being treated as facts.
Synthesis and follow-up
Annotated impact map, prioritized assumptions, and a 30-minute call to decide the next move.
What you walk away with
Three concrete artifacts. Not a deck, not slides, not a Notion page that gets archived next week.
Annotated impact map
Goal, the actors who get you there, and the leverage between them, captured in one artifact.
Prioritized assumption list
Ordered by risk to the goal. The ones that, if wrong, change the answer.
Recommended next move
The assumption worth testing first, and how to test it before the budget moves.
Pricing and scope
Fixed price. The smallest engagement I offer, by design. The point is to use it, not negotiate it.
Includes
Pre-session intake call
Facilitated 3 to 4 hour session: user, problem, assumptions
Annotated impact map and prioritized assumption list
30-minute follow-up to decide the next move
Excludes
Prototype or design artifacts
User testing or research sessions
Implementation or build support
If you're not sure you're solving the right problem yet, get in touch.
A short note is enough: what you're trying to figure out, who'd be in the room, and roughly when. I'll come back within a day.
Send a note