01. The problem is sacred
Never assume you understand the problem. The real problem is rarely the one presented in the first conversation.
Never assume you understand the problem. The real problem is rarely the one presented in the first conversation.
Don't ask the client what solution they need. Ask them what hurts, what slows them down, what costs them.
You can't write precise context for AI if there's disagreement within your organization about the problem or solution.
Writing context for AI is not summarizing what you know. It's making deliberate decisions about what to include, exclude, and how to structure.
Building is the natural consequence of having thought well. It's not an achievement in itself.
The speed AI offers is the result of having done the prior work well, not the goal of doing it.
No discovery, however deep, replaces real contact with the market.
Each iteration must incorporate new information. If you return to the same point without learning something new, you're not iterating.
The context you build for AI is not a static document. It evolves with each iteration, market signal, and new learning.
In every phase of this methodology, clarity is the scarcest and most valuable resource.