1
What is the problem you’re trying to solve?
This is the question people skip — and the most expensive mistake they make. Teams jump straight to buying tools or reorganizing before they’ve named the underlying problem, then wonder six months later why nothing got better. Name the real, specific problem first; without that anchor, even the most sophisticated tool becomes noise.
2
What are the pieces of the puzzle?
Once the problem is named, lay out the context around it: the people, data, systems, constraints, resources, and skills that actually bear on it. Lay all the pieces on the table before you start the puzzle. Most won’t matter — and that’s the point. Naming them earns you the right to set them aside, so the few that count become visible.
3
What does success look like?
Where are we trying to get to? Most people spend more time cataloging what they don’t like than naming what they want. Define a concrete, time-bound outcome — “by [date], we have [specific result]” — and that becomes your anchor. Effort gets measured by what it produces, not the hours it takes, and every distraction gets held against the target.
4
What are the options for getting there?
How are we going to get there? With the problem named, the pieces laid out, and a time-bound target in place, the options surface — options, not a solution. There are always multiple ways to get from where you are to where you’re going, and the people who jump to one solution first almost always choose the wrong one. Weigh each by impact, not emotion or urgency.
Problem, pieces, success, options. From paralysis to a plan.