Unclear paths
Important actions are difficult to find, terminology is inconsistent, or users have to understand the organisation behind the product before they can use it.
01 · Technology layer
Experience Layer
Plan clear, accessible interfaces around the tasks people need to complete across web and mobile experiences.
The context
Why this layer deserves deliberate decisions.
The experience layer is where product intent becomes something people can understand and use. Its quality depends on more than visual polish: content, navigation, system feedback, accessibility, and technical behaviour all need to support the same journey.
Disconnected states
Loading, validation, empty, error, and success states have grown separately, leaving the interface unpredictable when a journey moves away from its ideal path.
Uneven device support
The primary flow works in one viewport or input method but becomes harder to complete on smaller screens, keyboards, or assistive technology.
Areas of attention
Connect product needs to technical responsibilities.
The appropriate depth depends on the current system, the decision in front of the team, and the consequence of getting it wrong.
01
Journey and content structure
Map tasks, information, decisions, and supporting content into a sequence that reflects the user's context.
02
Interface system
Define reusable patterns, states, language, and visual rules so related experiences feel coherent.
03
Responsive behaviour
Decide how hierarchy, navigation, data, and controls adapt across devices rather than simply shrinking a desktop layout.
04
Accessible interaction
Consider semantics, focus order, keyboard use, contrast, motion, and understandable feedback as design and engineering concerns.
Potential artefacts
Make the technical direction usable by the team.
The exact artefacts follow the question and available evidence. Their purpose is to support implementation, review, and future ownership.
- 01Prioritised user journeys and task flows
- 02Page, screen, or navigation structure
- 03Interface states and interaction notes
- 04Reusable component and content guidance
- 05Responsive and accessibility acceptance criteria
Decision framing
Use context and evidence before adding complexity.
A useful direction explains the inputs, how it can be evaluated, and where its boundaries remain.
What we need to understand
- The people and roles using the product
- The tasks and decisions the interface supports
- Existing research, analytics, feedback, or support themes
- Brand, platform, content, and technical constraints
Evidence of a useful direction
- A critical journey can be understood without hidden knowledge
- Important states and edge cases have been represented
- The interface can be reviewed at relevant viewport sizes
- Acceptance criteria connect design intent to implementation
Important boundary
Interface work does not replace user research, content ownership, or accessibility testing with people who use assistive technology. The appropriate validation approach depends on the product, audience, and risk.
Working path
Move from current reality to an owned direction.
These stages are adapted to the size of the decision. Each should leave the next choice clearer than it was before.
Understand the journey
Clarify the audience, task, current friction, content, and operational context behind the interface.
Structure the experience
Organise flows, information, navigation, and states before committing to detailed presentation.
Design and validate
Create proportionate interface detail and review important behaviours with stakeholders or representative users where possible.
Support implementation
Translate intent into reusable patterns, acceptance notes, and design review during engineering.
Technology questions
Useful details to clarify.
Does experience-layer work include visual design?+
It can. The appropriate work may include journey mapping, wireframes, content hierarchy, interaction design, interface styling, or implementation review depending on what is already known.
Can you improve one part of an existing product?+
Yes. A focused journey can be assessed in its wider product context, then improved without requiring an immediate redesign of every screen.
How is accessibility considered?+
Accessibility considerations are included in structure, interaction, content, and engineering decisions. The level of formal evaluation should match the product's audience, obligations, and risk.
Do we need completed requirements first?+
No. Early experience work can help expose missing decisions and turn a broad objective into clearer journeys and acceptance criteria.
Start a conversation
Need clarity around the experience layer?
Share the product, current system, constraints, and decision in front of your team. We can help frame a practical next step.