goga-define-experience

goga-define-experience

Purpose

Define the user experience required to achieve the established product goals and solve the identified problem.

Transform the understanding of the product, problem, users, and goals into a complete description of how users interact with the product and what they should experience throughout the relevant scenarios.

The result must describe observable product behaviour from the user's perspective.

---

Contract

consume:
  - product
  - problem
  - users
  - goals

produce:
  - user_experience

---

Core Principle

Describe the experience, not the implementation.

The central question is:

What does the user do, what does the product show or allow, and what happens next?

The experience must be understandable without knowing how the product is implemented.

Do not prescribe:

• APIs;
• databases;
• services;
• frameworks;
• internal architecture;
• technical workflows.

---

Product Interview

The user experience must be discovered through interaction with the user.

Do not invent UX decisions merely because one flow appears conventional or obvious.

Identify the product decisions that materially affect the experience and interview the user about them.

Clarify when necessary:

• how the user enters the workflow;
• what the user expects to happen;
• what the primary successful path is;
• which alternative paths matter;
• what should happen when the operation cannot be completed;
• what the user should see after important actions;
• which actions should remain available in different states;
• what recovery behaviour is expected;
• which parts of the experience are intentionally excluded.

When several UX behaviours are reasonable, do not silently select one.

---

Decision Branches

For each important user scenario, identify materially different behavioural branches.

Examples:

success
failure
retry
cancel
partial completion
already completed
not available

Do not enumerate theoretical edge cases.