Method
Good digital product experiences start before the interface.
Recognize the problem. See what you can receive.
The work starts with the product, the business, and what customers need to know before choosing. The areas below pair problems you may recognize with specific results you receive. A project includes only the work agreed for your needs; these are not eight mandatory steps.
Service overview
Eight areas of work. One evidence-led approach.
Find the concerns closest to yours, then see the results available within an agreed scope. Some projects need a focused review; others also include content, design, or implementation.
- 01Business & website context
review findings and priorities
- 02Product information
reviewed product information
- 03Product range & differences
product grouping and comparisons
- 04Customer questions
answers to customer questions
- 05Current website experience
specific website findings and limits
- 06Website improvements
agreed website changes and page designs
- 07Implementation
completed website changes
- 08Verification
check results and remaining issues
01
Business & website context
Know where to start.
See the problem and what you receive
You're ready to improve the website, but it's unclear which problems deserve attention first or how much work is needed.
A clear summary of the website concerns supported by the review, what already works, and priorities for further work. The review also identifies questions that need more information.
Results cover the pages and information agreed for the review, not every part of the business.
02
Product information
Give customers information they can rely on.
See the problem and what you receive
Specifications and descriptions are spread across pages or documents. Customers encounter different wording, missing explanations, or details that need confirmation.
A product-information review identifying confirmed details, inconsistencies, and unanswered questions. Where content work is agreed, you receive clearer descriptions and specifications based on approved facts.
Unconfirmed details remain marked for clarification; they are not replaced with assumptions.
03
Product range & differences
Make the differences between products clear.
See the problem and what you receive
Customers see several models but struggle to understand the differences or which ones are relevant to their needs.
Product grouping, key differences, and comparison content that explain where models differ in use, fit, and specifications. Deliverables may include recommendations or finished page content, as agreed.
A larger catalog does not automatically require a product-selection tool.
04
Customer questions
Answer the questions that keep coming back.
See the problem and what you receive
The website lists features and specifications, yet customers still ask the same questions about size, intended use, compatibility, or how to buy.
Content addressing the recurring questions you share, with clearer explanations of suitability, limitations, and next steps. Depending on the agreed scope, this can include product-page text, answers to common customer questions, or buying guidance.
Customer questions and product claims need supporting information from your team or identifiable sources.
05
Current website experience
Show what may be getting in the way.
See the problem and what you receive
Customers can find a product, but the website may leave them unsure whether it fits their needs or what to do next. You want to know whether there is a real issue before spending on changes.
A review showing where the checked pages support choosing and where a specific obstacle or unanswered question was observed, with page examples and limits. If no clear issue is established, the result says so.
A website observation alone does not prove lost sales or explain why a customer did not buy.
06
Website improvements
Agree the changes before committing to a rebuild.
See the problem and what you receive
You know something needs attention, but you're concerned that improving it will mean replacing the whole website.
A clear description of the proposed changes and reasons for each recommendation. It may include revised page layouts, comparison content, or selection guidance; it also identifies what can stay. A rebuild is recommended only when the findings and constraints justify it.
Before changes begin, we agree on the work included, what is needed to carry it out, and the checks used to accept the finished work.
07
Implementation
Get agreed improvements built.
See the problem and what you receive
You have recommendations or a design, but need the content and website changes carried through to a usable result.
Completed content, page designs, or website changes within the agreed scope. When access to make website changes is unavailable, you receive instructions and materials your team can use to carry out the work.
Making website changes requires your permission, access to the website, and agreement on the technical requirements. Recommendations are not described as completed website changes.
08
Verification
Know what is complete—and what remains.
See the problem and what you receive
The changes are finished, but you need to know whether the pages, content, and agreed functions work as intended before accepting the work.
A record of the checks performed, completed items, remaining issues, and any unverified areas. Depending on scope, checks cover product content, links, customer paths, and desktop and mobile behavior.
Claims that more visitors inquire or buy, or that sales improve, require separate customer or business data; checking the finished website alone cannot establish those results.
The method is deliberately bounded.
The work is limited to the agreed scope. Client information is treated as confidential by default.
A free Product Decision Review is one optional, simple way to begin. If you already have a defined website need, you can start a direct conversation instead.