goga-define-problem

goga-define-problem

Purpose

Define the actual product problem that needs to be solved.

Transform the initial product idea into a clear problem statement that explains:

• what is wrong or missing;
• who is affected;
• in what context the problem occurs;
• why the problem matters;
• what outcome is currently prevented.

The result must describe the problem, not the proposed solution.

---

Contract

consume:
  - product
  - input

produce:
  - problem

---

Core Principle

Do not accept the user's proposed solution as the problem.

A request such as:

"Add export to Excel."

is not a problem statement.

Determine what problem the requested capability is intended to solve.

For example:

Users need to share operational data with colleagues, but the current product does not provide a convenient way to transfer the relevant information outside the product.

The proposed Excel export may or may not be the right solution.

Do not decide that at this stage.

---

Product Interview

The problem must be established with the user, not inferred from the requested feature alone.

Treat the initial request as a hypothesis about the problem.

Before producing the problem definition, identify the decisions that materially affect the problem statement and interview the user about them.

In particular, clarify when necessary:

• who actually experiences the problem;
• what situation triggers it;
• what the user is trying to achieve;
• what prevents the desired outcome;
• whether the request describes a problem or already assumes a solution;
• what makes the problem important.

Do not silently convert a feature request into a problem statement based on assumptions.

Do not stop interviewing merely because one interpretation appears plausible.

Continue until all materially different interpretations of the problem have been resolved.

---

Process

1. Understand the initial request

Analyze the user's original input.

Identify:

• the requested outcome;
• any explicitly stated problem;
• any proposed solution;
• affected users;
• relevant product area;
• known constraints.