Design audit can change everything and, as one scene in The Accountant (2016), could begin with something surprisingly small.
An employee notices that a few numbers don’t add up.
What starts as a simple discrepancy eventually becomes a much larger investigation, revealing patterns that had been hidden for years.
Good design audits begin in much the same way.
A recurring customer complaint.
A drop in conversion.
A checkout flow generating excessive support tickets.
A component recreated by multiple teams.
Individually, these may look like isolated problems.
Together, they often point to something much deeper.
The instinctive response is usually to fix the symptom.
Move the button.
Rewrite the error message.
Add another confirmation step.
Improve the navigation.
A design audit asks a different question:
Why is this happening in the first place?
That shift transforms design audits from interface reviews into strategic product tools.
What is a design audit?
A design audit is a structured evaluation of the current state of a product, service, or design organization.
Its purpose is not simply to identify inconsistencies.
The design audit goal is to connect evidence, root causes, customer impact, business outcomes, and opportunities for improvement.
Depending on the question being investigated, a design audit may evaluate:
- Interface consistency
- Usability and accessibility
- Content and information architecture
- Cross-channel customer journeys
- Design systems
- Research and discovery practices
- Collaboration between Design, Product, and Engineering
- Metrics and measurement
- Design’s role in strategic decision-making
Every audit starts with a different question.
A checkout audit is different from a design system audit.
A product audit is different from an organizational design maturity assessment.
But they all share one goal:
Supporting better decisions.
If your work ends with a list of problems, you’ve created an inventory.
If it connects evidence, causes, business impact, priorities, and recommendations, you’ve created a design audit.
When should you conduct one?
Design audits require time.
They involve multiple stakeholders.
Sometimes they uncover more problems than an organization can realistically address.
That is why they shouldn’t happen simply because they sound like good practice.
They are particularly valuable when:
- Customer complaints increase or become repetitive.
- Critical business metrics decline without a clear explanation.
- A redesign is being planned.
- Multiple products need to become more consistent.
- The design system has drifted over time.
- Product and Engineering experience significant rework.
- Critical journeys accumulate quick fixes instead of systemic improvements.
- The product has grown faster than its foundations.
- New leadership needs a clear understanding of the current state.
- Annual planning is approaching.
- There are signs of revenue loss or unnecessary operational costs.
- Significant market, business, or technology changes occur.
Before starting an audit, three conditions should exist:
- There is a clear decision the audit should support.
- The necessary evidence and stakeholders are accessible.
- Someone has the authority to prioritize and act on the findings.
A design audit doesn’t need to promise that every issue will be fixed, but it should guarantee that every important finding informs future decisions.
Continuous observation versus deep audits
Not every audit needs to become a massive project.
The healthiest organizations combine two different rhythms.
Continuous monitoring
Lightweight monitoring tracks signals such as:
- App Store reviews
- Customer support conversations
- Product analytics
- Accessibility issues
- Design system inconsistencies
- Research findings
- Technical incidents
- Customer feedback
- Sales and customer success insights
These signals create an ongoing backlog of opportunities and risks.
Focused audits
At strategic moments, organizations perform deeper investigations with defined scope, timeline, stakeholders, and expected outcomes.
Examples include:
- Quarterly audits of a critical customer journey
- Semiannual design system reviews
- Annual design maturity assessments
- Product performance audits
- Pre-redesign evaluations
This balance allows teams to keep building new capabilities without waiting for problems to become crises.
A practical design audit process
1. Start with a question
Avoid beginning with:
“Let’s find everything that’s wrong.”
Instead, ask something specific:
- Why are users abandoning activation?
- Why is support receiving so many delivery-related requests?
- Where does inconsistency create the most rework?
- Is our design system increasing team efficiency?
- Which problems have the greatest impact on customer trust?
- Where are the biggest financial bottlenecks?
A focused question defines the scope, participants, timeframe, and expected outcome.
2. Collect evidence from multiple sources
Don’t start with interfaces alone.
Many of the strongest signals appear after the experience has already happened.
Useful sources include:
- Customer support conversations
- App reviews
- Satisfaction surveys
- User interviews
- Behavioral analytics
- Usability testing
- Technical incidents
- Cancellation reasons
- Refund requests
- Previous product decisions
- Existing design patterns
- Internal stakeholder interviews
Each source answers different questions.
Support reveals frustration.
Analytics reveals scale.
Research reveals motivation.
None should work in isolation.
3. Compare time periods
Context matters.
Some problems emerge after a release.
Others have existed for years.
Looking across different time windows helps distinguish:
- Temporary incidents
- Long-term patterns
- Growth trends
- Seasonality
- Reoccurring issues
- Fixes that solved symptoms but not causes
Time should become part of the investigation—not just a reporting period.
4. Organize evidence before drawing conclusions
When information comes from multiple sources, resist the temptation to jump directly to recommendations.
Instead, create small diagnostic summaries.
For example:
- Top customer support themes
- Most common usability issues
- Funnel breakdowns
- Research insights
- Design system inconsistencies
Each finding should connect:
- Observation
- Evidence
- Likely cause
- Customer impact
- Business impact
- Confidence level
The audit should tell a coherent story—not become a collection of screenshots and opinions.
Prioritize by impact, not by noise
The loudest problem isn’t always the most important.
The most frequent problem isn’t always the most expensive.
Consider evaluating findings across dimensions such as:
- Frequency
- Reach
- Severity
- Persistence
- Business impact
- Confidence
- Implementation effort
Whenever possible, translate percentages into something tangible.
“2% of users” sounds abstract.
“Forty thousand customers every month” changes the conversation.
Business impact isn’t limited to revenue.
It may involve:
- Conversion
- Adoption
- Retention
- Customer support costs
- Task completion time
- Rework
- Legal risk
- Accessibility
- Brand trust
- Customer satisfaction
Don’t let audits trap you in the past
One risk of auditing is becoming obsessed with fixing existing problems.
Eventually, the roadmap turns into an endless repair queue.
I like separating audits into two complementary movements.
Movement one: Understand today’s product
Investigate:
- What patterns keep repeating?
- Which fixes were only temporary?
- What decisions created these outcomes?
- Which capabilities are missing?
The goal isn’t assigning blame.
It’s understanding the system producing the results.
Movement two: Imagine tomorrow’s product
Once the diagnosis is complete, temporarily ignore today’s constraints.
AJ, Head of Product Design and founder of Design Circuit, calls this Blue Sky thinking.
Ask questions like:
- What if this step didn’t exist?
- What if customers never needed to create an account?
- What if support and product became one seamless experience?
- What if we started from scratch?
- What if our product needed to support ten times more customers?
The first movement explains today’s reality.
The second prevents teams from limiting innovation to fixing existing problems.
Balancing improvements and innovation
Audit findings shouldn’t automatically consume the entire roadmap.
A useful approach is organizing initiatives into three horizons.
Now
Protect the current experience.
Critical usability problems.
Accessibility.
Major risks.
Broken journeys.
Next
Strengthen the foundation.
Design systems.
Research capabilities.
Content strategy.
Architecture.
Instrumentation.
Cross-functional processes.
Future
Create new possibilities.
New products.
New services.
New business models.
New customer experiences.
The right balance depends on the maturity of the product.
Products in crisis should invest heavily in stabilization.
Healthy products can invest more aggressively in future opportunities.
Strategy is deciding how to sustain both.
Turning findings into strategy
A useful audit report doesn’t need hundreds of pages.
It should answer five questions:
- What is happening today?
- Where do we want to go?
- What deserves priority?
- What happens now, next, and later?
- How will we measure success?
Notice that none of these questions begin with features.
To support these questions, a design audit could also present 10 key points:
- Traceable evidence;
- Key patterns;
- Probable causes;
- Impact on customers/users and the business;
- Priorities;
- Future opportunities;
- Initiatives by horizon;
- Owners;
- Metrics and potential gains, losses, or impacts associated with resolving—or not resolving—the issues;
Questions requiring further investigation.
They begin with outcomes.
The real purpose of a design audit
A design audit isn’t about proving that a product is broken.
It’s about making visible what daily operations have made invisible.
It connects scattered signals.
Explains their causes.
Measures their impact.
And helps organizations choose—consciously—what to fix, what to strengthen, and what to invent next.
For this is crucial an action:
In a design audit, involve everyone from the start to learn from them, align, and adjust—avoiding a scenario where the final report comes as an unexpected revelation; therefore, share findings throughout the process and be genuinely open to feedback.
Ultimately, the most important question isn’t:
“How many problems did we find?”
It’s this:
What did we learn about our product, and what better decisions can we make because of it?
References
Moultrie, J.; Clarkson, P. J.; Probert, D. (2007). Development of a Design Audit Tool for SMEs. Journal of Product Innovation Management, 24(4), 335–368. The paper presents an audit tool that combines product, process, and management.
Topaloğlu, F.; Er, Ö. (2017). Discussing a New Direction for Design Management through a New Design Management Audit Framework. The Design Journal, 20(sup1), S502–S521. Expands the audit to include strategy, integration, research, culture, and organizational development.
Hands, D.; Ingram, J.; Jerrard, R. (2002). Design Management Case Studies. Routledge. It presents procedures, methods, and audit cases regarding design management.
Jerrard, R.; Hands, D. (eds.) (2008). Design Management: Exploring Fieldwork and Applications. Routledge. It discusses the assessment of design value by combining qualitative and quantitative methods.
Borja de Mozota, B. (2003). Design Management: Using Design to Build Brand Value and Corporate Innovation. Allworth Press. Offers a foundation for linking design, management, innovation, and business value.
Sheppard, B. et al. (2018). The Business Value of Design. McKinsey & Company. It links practices regarding design, leadership, metrics, holistic experience, and business performance.
Apparicio Junior — AJ. Canal DC 2.0, da Design Circuit. The open class on product design auditing presents the investigation, temporal comparison, Big Thinking, and Blue Sky exercises mentioned in this article.
Faberhaus Play – Terms in business. Explains important business terms that can cause confusion.
