Skip to main content

Product Manifesto

“Product Speak” — A Learning Path
  1. Product Personas — Understanding people
  2. Jobs-To-Be-Done — Understanding progress
  3. Product Manifesto — Shared product ethos
  4. Product Discovery — Validating hypothesis
  5. Product Rhythm — Sustaining learning loop
  6. The 3-Factor Score - Prioritization, What matters?
  7. Playbook Extreme - The bare minimum
Today’s Agenda
  • A 10 Step Program For Engineers, providing a shared product ethos
#1 — Start with Real Problems, Not Assumptions

Everything begins with understanding the context and pressures in which people operate.

Practice
Keep discovery honest and design intentional, ask:

  • “Who is this for?”
  • “What progress are they trying to make?”
  • “What’s blocking that progress right now?”

Relation
Personas help us visualize real-world roles, environments, and behaviors — they give the work a human anchor. JTBD defines the progress someone is trying to make, rather than the task they’re doing.

#2 — Measure Progress Through Outcomes, Not Output

Every product exists to help someone move from a current state (struggle, inefficiency, uncertainty) to a desired state (confidence, control, simplicity).

Shipping a feature isn’t success — enabling progress is.

Practice
Define success through outcomes, such as:

  • Faster reconciliation
  • Fewer manual steps
  • Better decisions
  • Greater trust

Measure those — not lines of code or story points.

Relation
Use personas to predict how different people define “better,” and test whether your product truly delivers that improvement.

#3 — Keep Motivation at the Center

People don’t just use products — they choose them, often for emotional or social reasons as much as functional ones.

Practice
In design ask: “Why would someone choose this?” If the answer isn’t tied to a clear motivation, you’re likely solving the wrong problem.

Relation
Personas highlight motivators such as ambition, confidence, recognition, trust, or safety. JTBD helps you articulate them:

When [situation], I want to [motivation], so I can [expected outcome].

#4 — Seek Progress, Not Perfection

Progress happens in loops — learn, build, test, refine.

Practice
Iterate fast. Validate early. Let learning shape your roadmap more than assumptions.

Relation
JTBD frames product work as a continuous journey; people struggle, explore, adopt, evaluate, and sometimes switch.

#5 — Find and Fix Friction

Every moment of friction, confusion, delay, workarounds, or resistance signals unmet needs.

Practice
Instrument, observe, and ask:

“Where are people struggling? What is this friction telling us about their deeper goal?”

Relation
Personas help us spot where struggles appear. JTBD clarifies why they happen and what progress people are failing to make.

#6 — Build Shared Understanding

Great products emerge when everyone shares the same mental model — of who the product is for, what they’re trying to do, and why it matters.

Practice
Use personas and job statements as shorthand in standups, planning, and retros — not as documentation, but as language for alignment.

Relation
Personas provide a human reference point; JTBD provides a purpose-driven structure. Together, they align everyone on what “value” truly means.

#7 — Balance Innovation with Trust

Innovation only matters if it earns trust.

Practice
Design for both innovation and assurance. If you change behavior, show that it’s reliable and verifiable.

Relation
Personas remind us that reliability, compliance, and predictability aren’t “boring” — they enable confidence. JTBD frames this as part of the job to be done: people want progress that feels safe.

#8 — Simplify Relentlessly

The clearer we are about what someone is trying to accomplish, the simpler the product becomes.

Simplicity is not minimalism — it’s clarity.

Practice
When evaluating a design or architecture, ask:

“Does this make the core job easier, or just add more to manage?”

Relation
JTBD helps strip away everything that doesn’t serve the job. Personas remind us which complexities are real — and which are self-inflicted.

#9 — Stay Curious, Stay Close

Stay close to users, customers, and data to keep your understanding fresh and grounded.

Practice
Observe. Interview. Shadow. Use feedback cycles to challenge what you think you know.

Relation
Personas and jobs are not artifacts to be filed away — they evolve as real people and the business domain evolve.

#10 — Validate with Evidence

The final test of product work is whether it helps someone make progress better than before.

Practice
Validate early and often. Ask: “Did this help them do their job faster, safer, or with more confidence?” If not — learn and adjust.

Relation
Personas and JTBD both demand validation — qualitative (stories, feedback) and quantitative (metrics, adoption).

In Closing — Our Ethos

A great product doesn’t just work — it helps someone move forward with less friction, more clarity, and deeper trust. Our craft is not just engineering; it’s enabling progress.

Practice
We build for people who are trying to make progress — not for ourselves.

Relation
We use Personas to stay human, and JTBD to stay purposeful.