Name the user job

An app idea often begins with screens: a dashboard, profile, settings, reports. A user begins with a job. They need to request a quote, approve a design, record an inspection, place an order or see what happens next.

Write the job as a sentence with a beginning and an outcome. “A venue manager can review an event enquiry and send a confirmed response” gives the team a tighter starting point than “build an events dashboard”.

Follow the whole path

The useful journey includes the entry point, the information needed to act, validation, an outcome and a way to recover when something goes wrong. A button that produces a success animation before the data is actually saved is not a completed journey.

Map the handoffs too. If an app creates a request for a staff team, decide where it lands, who owns it and what the customer sees while they wait. Product design and operations meet at that handoff.

Make the state visible

Users do not experience features as a clean flowchart. They experience loading, empty results, a failed payment, an expired link, an unavailable time slot and a return visit after several days away.

Make each state legible. Tell the user what is happening, what has been saved and what they can do next. This reduces support work as much as it improves the interface.

Keep the first release small

A smaller release makes the real constraints visible sooner. It can show whether the team needs an approval step, a better data model, a notification or a different payment flow before those decisions spread across ten screens.

That does not mean releasing carelessly. The first journey still needs accessibility, input validation, account boundaries, clear error handling and a support route. Small scope should make quality easier to achieve.

Choose the next step from evidence

A dashboard can come later, once it helps a defined user make a better decision. First, make sure there is something real to decide.

  • Watch a user complete the journey without narrating every click.
  • Record where they hesitate, abandon or request help.
  • Check whether the operational handoff completes reliably.
  • Measure completion and time to outcome before adding broad engagement metrics.
  • Prioritise the next improvement by user impact and delivery risk.
Written by Pressine

Our studio combines design, software development and search. These guides document our approach and link to primary references where platform behaviour matters.

About our method