Define core motivation and intention
The first decision isn't a feature — it's the answer to why you're building at all. Here's how we help founders find their honest answer.
Before any feature list, before any Figma file, before any code — the first decision a product team makes is why they're building. Most teams skip this step because it feels soft. The ones who don't skip it ship clearer products faster.
Motivation is not strategy
Strategy is the set of moves you'll make. Motivation is the answer to the question "why me, why now, why this?" — and it tends to survive pivots that strategy doesn't. When a roadmap is dying, the team that can still articulate its motivation tends to find the next shape.
- Motivation is personal. A team's motivation is the intersection of what each founder cares about.
- Motivation is usually pre-verbal. Surface it with structured interviews, not a slide template.
- Motivation is stable. If it keeps changing, it's probably strategy dressed up as purpose.
What intention adds
Intention is the shape of the outcome you want in the world. A motivation can be private; an intention has to be testable. "I want to help people live longer" is a motivation. "I want to build the tool GPs in Europe use to coach patients through behaviour change" is an intention.
"If you can't state the intention in one sentence a stranger would repeat back correctly, it isn't clear enough to build against."