Process

Reduce ambiguity
before teams
spend heavily.

The process is not a fixed ceremony. It is a sequence of questions that turns ambition into a credible product direction.

What operational reality makes this worth solving?

Find the real problem

Start from user friction, business constraints, existing tools, incentives, and observable behavior—not a feature wishlist.

Who acts, what changes, and where does value move?

Define users, roles, permissions, journeys, workflows, value exchange, and product boundaries before interface detail.

What must the product prove first?

Separate the MVP from future ambition. Delay expensive ecosystems until the core behavior can be tested honestly.

What must be true for this experience to work?

Translate decisions into UX flows, requirements, data paths, architecture options, capacity assumptions, risks, and phases.

How will the team know what happens next?

Clarify ownership, decision logs, review cycles, quality checks, stakeholder communication, and measurable next actions.