A collection of polished screens is not yet a complete product experience. People encounter a product as a sequence: they arrive with a goal, make choices, wait for something to happen and decide what to do next.

The moments between the main screens deserve the same attention as the screens themselves. They explain the rules of the experience and help people understand whether their action worked.

Start with a task, then follow it through

Choose one meaningful task and describe it without interface language. “Find a suitable plan and understand the commitment” is more useful than “click the pricing button.” It keeps attention on the person’s goal rather than the controls already in the design.

Walk through that task from the first entry point to the final confirmation. Note what someone needs to know at each step, what information the product asks for and what could make them hesitate. Include the return journey: what happens if they leave and come back later?

Write the uncertain moments

Uncertainty often appears in small places. A vague button label does not explain what comes next. A confirmation may say “Success” without explaining what has happened. An error may identify a problem but offer no route forward.

Draft this language while the flow is still being designed. A button might say “Review your request” when it leads to a review stage. A confirmation can name the completed action and explain the next step. An error should help the person understand what they can change, using terms that fit the task.

Writing these states can expose gaps in the underlying flow. If the team cannot explain what happens next, the design decision may not be finished.

Design for an incomplete world

Real content is not always neat. A name can be long. A list can be empty. A connection can fail. A person may have access to one part of an account and not another.

Choose the states that are relevant to the product and make them part of the design review. Show an empty list alongside a populated one. Consider what the interface communicates while a task is in progress. Explain when someone needs to act and when they simply need to wait.

These details should follow a shared visual and verbal system so the product remains understandable across different situations.

Review the journey together

Bring content, design and development into the same conversation before treating the screens as final. Review the sequence using realistic material, including awkward examples. Ask where the person is, what they know and what action is available.

A prototype can make these questions easier to discuss because it connects the decisions into a sequence. Keep the review anchored to the original task rather than the number of screens completed.

At NEXT, product thinking connects structure, language and interaction. The aim is a useful experience that continues to make sense when the content changes, the path branches or someone needs a little more help.