From ambiguity to direction: the seven steps I use

The short version

• Most product work starts as noise: competing asks, unclear owners, messy data.
• Seven steps take it from there to something adopted: opportunity, evidence, direction, alignment, execution, adoption, impact.
• Each step has a question to answer, something to produce, and a trap to avoid.

Across media, SaaS, travel and AI, the situation I'm asked to help with looks similar: there is a real opportunity, but the path is tangled, technically or organizationally. This is the sequence I use to untangle it. (There is an interactive version in the Approach section of the home page.)

1. Opportunity

The question: What problem is worth solving, and for whom? What I produce: A short problem statement that someone outside the team can understand. The trap: Starting with a solution. "We need AI" is not an opportunity; "editors spend hours on a repetitive task" is.

2. Evidence

The question: What do users, data and operations actually tell us? What I produce: A baseline: a few numbers from analytics and SQL, plus what customer conversations reveal. The trap: Collecting evidence to confirm a plan you've already made. Look for what would change your mind.

3. Direction

The question: What is the thesis, and what is the first bet? What I produce: A product thesis, a short list of priorities, and, just as important, what we are not doing. The trap: A roadmap that is only a list of features. Direction explains why these things, in this order.

4. Alignment

The question: Who needs to agree for this to work, and on what? What I produce: A shared definition of success, named owners and the decisions that are still open. The trap: Consensus theater. Alignment is not everyone liking the plan; it is everyone knowing what they are doing and why.

5. Execution

The question: What is the smallest coherent version that can create value? What I produce: A scoped release, with experiments or A/B tests where the answer isn't obvious. The trap: Scope that grows because nobody wants to say no. Small and coherent beats big and late.

6. Adoption

The question: Will people actually use it, and trust it? What I produce: A rollout plan: training, champions inside the teams, and a feedback loop that works. The trap: Declaring victory at launch. If it isn't embedded in real work, it hasn't shipped.

7. Impact

The question: Did the outcome change? What I produce: Honest measurement against the baseline from step 2, and a decision: reinforce or rethink. The trap: Vanity metrics. Choose the one that would convince a skeptic.

Why a sequence helps

Skipping steps is where most initiatives get into trouble. Teams jump from opportunity to execution and discover, late, that nobody agreed on success, or that the people who need to use the product were never part of the plan.

The sequence also makes ambiguity less frightening. You don't need certainty to begin. You need the next question, and the next thing to produce.