Product Testing & Review
See your product from the outside.
An independent assessment of what your product does, how people experience it and the assumptions it rests on. A clear basis for deciding what comes next.
Scoped per product.
01 // Perspective
We also tell you what not to change.
Good judgment includes recognising what already works. We identify strengths worth preserving alongside friction, gaps and risks, so improvement does not become change for its own sake.
This goes beyond generic QA or bug testing. A Product Review may combine journey and edge-case testing, UX and product analysis, assumption testing and competitive context. The scope follows the product and the decisions you need to make.
02 // Six lenses
One product. More than one way to look.
We examine six connected lenses, with the depth of each agreed for your product.
- 01Experience
Can people find their way?
Journeys, clarity, friction and recovery: how the product feels to someone who does not already know how it works.
- 02Function
Does it do what it promises?
Core flows, states and edge cases, including what happens when inputs, permissions or expectations change.
- 03Product
Is the right problem being solved?
The value, scope and coherence of the product. What earns its place, what is missing and what adds unnecessary complexity.
- 04Market
How does it stand in context?
Positioning, alternatives and competitive expectations, considered against the audience the product is intended to serve.
- 05Intelligence
Where does judgment belong?
Where AI, automation or decision logic helps, where it falls short, and whether people can understand, verify or override its outputs.
- 06Assumptions
What are we taking for granted?
Beliefs about users, behaviour and demand. Which have support, which need testing and what evidence would change the decision.
03 // The deliverable
The Product Review
A decision document rather than a bug report. It connects evidence-backed findings to their implications, with prioritised recommendations and a clear account of what to preserve.
Context & boundaries
The product, intended audience, review questions, access and limits of the assessment.
Findings & evidence
What we found, how we reached it, why it matters and how certain we can be.
Decisions & priorities
What to keep, what to change, what to test next and what can wait, with the reasoning behind each recommendation.
Optional developer handover
A walkthrough and actionable implementation notes to help your team carry agreed recommendations into the work.
The evidence has a label.
Findings distinguish what we know from what still needs checking. Uncertainty stays visible.
- Observed
- Directly encountered during the review, within the access and conditions available.
- Reproduced
- Repeated under documented conditions, with steps and supporting evidence.
- Inferred
- An interpretation supported by the available evidence, with the reasoning made explicit.
- Requires verification
- An open question that needs further access, data or testing before a conclusion can be drawn.
04 // Scope & fit
For products at a point of decision.
Before launch, after a first release or when deciding where to invest next. Suitable for web and mobile apps, SaaS, portals, internal systems, marketplaces and prototypes.
We begin with the product, its audience and the questions you need answered. Together we agree the journeys, environments, access, review depth and timing before the assessment begins.
Specialist work is separately scoped.
A Product Review does not include formal penetration testing, security or regulatory certification, exhaustive accessibility or load testing, or compliance auditing unless separately scoped.