Identify the moment of use
Consider where and why a person opens the experience. They may need to find information quickly, complete a repeated task or resume an activity from another device. That context helps determine what belongs in the primary journey.
Prioritise the essential task
List the actions needed to complete the goal. Remove steps that ask for information the system already has or distract from the immediate task. Make the next action and its result clear at each point.
Choose the platform around the requirements
The appropriate approach depends on device capabilities, distribution, offline needs, integration constraints and the team maintaining the product. A responsive website and a mobile application support different operating models. Review those needs before committing to a platform.
Design the interrupted state
People leave and return to mobile tasks. Consider partial input, changing connectivity and the need to recover an activity. Define what is saved, what is confirmed and how a user knows the current state.
Review with representative content
Check long names, detailed messages, different screen sizes and keyboard interactions. Use realistic scenarios to assess the experience. The interface should remain understandable when the content and the conditions vary.
Bring your business question.
Share the goal, the constraints and what a better outcome would look like.
Start a Project ↗
