Five decisions to make before the first pixel

Most teams do not have a design problem when they open Figma. They have a decision problem. The canvas simply makes that ambiguity visible.

The fastest route to a coherent product is to make a few uncomfortable choices before polished screens create false confidence.

1. Name the change you create

What becomes meaningfully different for a customer after using the product? Avoid category language. “A platform for modern operations” describes a shelf, not an outcome.

Use a plain before-and-after sentence. If the team cannot agree on it, visual exploration is premature.

2. Choose the first believer

“Teams” is not an audience. Choose the person who feels the problem most acutely, has the authority to act, and can recognize value quickly.

3. Define the smallest convincing proof

An MVP is not the product with most features removed. It is the smallest experience capable of proving the most important assumption.

Ask what a customer must see, feel, or accomplish to believe the larger promise.

4. Decide what not to compete on

Strong products are opinionated. List the conventions you will follow without debate so you can invest creative energy where distinction matters.

5. Agree on the evidence

Before launch, define what you expect to learn and the signals that would change the plan. This keeps a test from becoming a referendum on whoever speaks loudest.

Direction is a deliverable

These decisions will evolve. That is healthy. Their purpose is not to predict the future; it is to give the next week of work a coherent direction.