Design Validation

Design Validation is not a rebrand engagement. It’s the opposite: we’re hired to look at what you already have and give you a written account of where intent diverges from execution. That distinction matters. Most design work we get asked to audit is fundamentally fine — it needs pruning, not replacement — and clients who came to us expecting a redesign recommendation usually leave with a shorter, cheaper list of things that will have more impact.

The work proceeds in three passes. First, a heuristic audit of the key flows — onboarding, the critical path through the product, settings, whatever matters commercially. Second, a review of the design system as it actually lives in code, not as it’s drawn in Figma. The gap between those two is where most design debt hides. Third, if the brief includes real users, we run a handful of sessions and synthesise what we see into observations you can act on.

What you get back is a written critique — ordered by impact, not by alphabet — with specific screens called out, specific patterns flagged, and a prioritised fix list that distinguishes “ship this sprint” from “put on the backlog” from “honestly, leave alone.” We’re deliberately honest about that last category. Most audits over-recommend; ours doesn’t.

This is a diagnostic engagement, not an execution engagement. If the audit surfaces work that needs doing, we’ll quote it separately or hand the findings to your team. We won’t use the audit as a funnel for a larger contract — if the right answer is “fix three things and leave the rest,” that’s what we’ll say.