Notes on shaping early-stage products — what to fix first, what to leave rough, and the conversations that move a v1 forward faster than another round of polish.

Most early product work fails for the same reason: the team agrees on what the product should do but not on what it should refuse to do. The first cut is therefore less about features and more about clarifying what is out of scope, what is provisional, and what we already know we will throw away.

A useful exercise: write a paragraph about the user the day after they sign up. Not a persona, not a journey — a paragraph. Whatever you can't say specifically is the part of the product that needs more thinking, not more design.

Design quality at v1 is not the same as design quality at v3. Early flows benefit from rhythm — predictable layouts, predictable typography, predictable interaction patterns — far more than they benefit from a beautifully styled empty state. Polish is what you add when the structure is settled. Adding it earlier locks in decisions that are still cheap to change.

A common signal: when a designer is choosing between two icons for a button that doesn't have a confirmed label, the team has skipped a step.

The fastest way to unblock a v1 is to ask the questions that nobody on the team wants to be the one to ask. Whose job is it when this fails? What happens if the user closes the tab here? What does the second-week experience look like for this feature?

These aren't design questions. They're product questions disguised as design questions. Naming them in a design review tends to do more for the release than another iteration of the screen they came up around.