Information architecture
Observe how people group information before designing navigation. Use page and screen labels that match real customer questions, then test whether they support a realistic task.
Avoid relying exclusively on internal department names. A customer reading on mobile should understand where to go without opening every menu.
When mapping choosing a digital partner, choose a boundary that the team recognises. Describe what enters the work, what leaves it and who receives the result. Note any existing agreement, published information or timed dependency that still requires confirmation.
What to prepare · Page tree and task-based navigation checks
Mobile starting point
Sketch the smallest supported view first. Review when primary actions are visible, whether content wraps correctly and whether controls are easy to reach.
Check long names, magnified text and keyboards on actual devices. Desktop designs that scale down well can still hide an important prompt below the fold.
Add this item to the project plan as an observable step. Record the person or team who supplies the input, the way you will verify it and any other milestone that must finish first. If work is split across teams, decide what information can be shared early and document the decision that is still outstanding.
What to prepare · Responsive layouts and small-screen acceptance checks
Form design
Request the minimum information needed to direct or complete the task. Set clear labels, indicate required fields and explain how an unsuccessful submission can be corrected.
Use input types and keyboard suggestions that suit the field. Preserve entered information where appropriate when a connection or validation check fails.
A useful test includes the condition that starts the work, a single action and an outcome that a reviewer can actually observe. Note whether the result is visible to a customer, an administrator or both. Keep an example that support can repeat after a release so an unexpected change can be compared with the original acceptance result.
What to prepare · Field list, validation rules and confirmation copy
Accessible UI
Review keyboard order, visible focus, plain labels, contrast and text resizing. Check important tasks with assistive technology where your project supports it.
Account for disabled, loading, expired, failed and completed states. Users need a way to recognise each result without depending on colour or position alone.
Invite the people who will use or maintain this part of the service to the review. Give them a realistic brief, ask them to complete the intended task and note the point where they ask a question. Decide whether the answer belongs in the interface, the operating procedure or a separate support note, and name who owns that change.
What to prepare · Accessibility review and testable component states
Design systems
Define typography, spacing, colour, content hierarchy and interaction patterns alongside variants of common parts. Explain when exceptions are appropriate.
A component has to support longer text, unfamiliar data and a narrow device. Write design notes around the choices a developer or editor will repeat.
Write down the assumption that would be most expensive if it turned out to be wrong. Consider how you could verify it in a small sample before the full scope is approved. Set a deadline for resolving the assumption and explain what happens to work that is already under way if the dependency cannot be confirmed.
What to prepare · Style tokens, component examples and implementation notes
Editorial ownership
Assign responsibility for product copy, navigation labels, translation and imagery. Record what an editor can update safely after launch.
Use a checklist when publishing important pages. Require a clear main heading, useful alternative text, a relevant next step and a named reviewer.
Review how a failure or delay will be detected. Decide who is responsible for the first response, which record captures the decision and what happens if a customer needs help before a fix is available. Give the receiving person a brief explanation of why the state occurred and which actions they can take safely.
What to prepare · Content matrix, review workflow and editor training
Brand and image preparation
Gather approved logos, original assets, usage rights, output sizes and a concise set of visual rules. Choose crops based on where images appear and what they explain.
Use realistic replacement material if the client cannot share an internal screen. Mark recommendations and concept examples clearly when showing them as work.
At handover, ask the owner to repeat an ordinary update while another reviewer observes. This exposes permissions, missing context and steps that depend on a specific person or private account. Retain the example in the project notes. Check that a new team member can identify the source of the existing decision and request a change.
What to prepare · Asset inventory with permissions and export specifications
International experience
Write down which language, contact, currency and delivery details change by market. Decide which values can be configured and which require dedicated copy.
A translation should survive real text lengths and reading direction. Test an actual translated example before setting fixed sizes or approving a single mockup.
For a release with several markets, branches or customer groups, check which parts of this decision apply to everyone and which require a local choice. Document the rule and a representative example where possible. Ask the appropriate regional or operational reviewer to confirm whether the result can still be used in their normal working conditions.
What to prepare · Language and market matrix with review owners