Template: Design Scoping

Context

In what context did this topic come up? Does it answer a need expressed by users, by Product Owners? Are there figures or percentages that illustrate the situation?

Two or three sentences are enough. The goal is that someone who joins the topic a month later understands where it comes from.

Problem

The need and the question it raises

What is the need, and what problem does it raise? State the question in one sentence, with no solution inside it.

What exists today

How is this problem answered today, in the product or outside it? Screenshots, current journey, workarounds observed among users.

Benchmark

Do services already answer this problem? What are their strengths and weaknesses? Two or three well-chosen examples are worth more than a list.

Goals

State the goals of the topic: what are we trying to reach, and what would the benefit be? Three goals at most, written so that it is possible to say later whether they were reached.

• Goal 1
• Goal 2
• Goal 3

Exploring solutions

Concepts

One table per concept explored, with the same grid for all of them: a short description, the strengths, the weaknesses. Three concepts is a good number for a discussion; with only one, the conversation moves to details instead of the approach.

Prototypes

One prototype per concept kept, embedded or linked from Figma. The level of fidelity depends on what is being tested: a flow is tested in low fidelity, a fine interaction needs high fidelity.

Next steps

List the steps to follow, tag the people involved, write down what the user research team needs in order to test the hypotheses. Each step has an owner and a date, otherwise it does not exist.

Additional notes

Notes or comments that fit nowhere else: technical constraints learned along the way, decisions taken in meetings, questions still open.