I’ve seen this screen before.I know how it ends.
A structured review of your product by someone who has designed, specified and shipped more than 1,200 of them. You get a ranked list of what is costing you customers, and what to do about each one.
- Conversion or adoption is flat and nobody agrees why
- You’re about to redesign and want to keep what works
- A new leader needs an honest baseline, fast
- An investor or acquirer asked how good the product really is
- Every key flow reviewed against eight questions a screen has to pass
- Findings ranked by severity and by cost to fix
- Annotated screens your team can act on the same day
- Quick wins separated from structural problems
- One worst flow redesigned as a worked example
- A readout for executives, and one for the team
Eight questions every screen has to pass.
A screen exists to support one decision. If I can’t say which, neither can your customer.
Errors, declines and confirmations get the most scrutiny.
People act on the first number they see.
Placeholder copy hides real problems.
What happened, why, and the way out.
The primary action, on the smallest screen you support.
And with a screen reader, and at 200% zoom.
And on a slow connection, and with a keyboard only.
Every finding is a small brief.
- Checkout → Review order
- The total only appears after tapping “Details”. People confirm without seeing it.
- The first number people see is the one they act on. Here it’s the subtotal.
- Total first and largest. Fees itemised directly under it.
- Small. About two days, no backend change.
- Opinions about colours
- Two hundred nitpicks in no order
- “Best practice” with no reason attached
- A redesign you didn’t ask for
Isn’t this just one person’s opinion?
It’s one person’s pattern recognition, from more than 1,200 products, checked against eight explicit questions. Where a finding needs proof, I’ll say so and recommend a quick test.
Do you need access to our data?
It helps. Analytics and support tickets tell me where to look hardest. I can also work from the product alone.
What happens after the readout?
Your team owns a ranked list with owners and dates. I can stay on to pair with designers on the hardest fixes.
Four steps.
- Brief
We agree the flows, the audience and the business number that matters.
- Review
I work through the product as your customer, then as your expert user, then as your engineer.
- Rank
Findings are scored by severity, reach and effort, so the order of work is obvious.
- Readout
A working session. We leave with owners and dates, not a PDF.