When this format fits
- You need a shared evidence base before a redesign or roadmap reset
- Leadership asks what is wrong but internal teams disagree
- You want to see the depth of work before committing to a full engagement
Screenshots
Homepage, dashboard, core workflow, or other key product screens.
Drop screenshots here or browse files
PNG, JPG, WEBP — up to 10 MB each. One is enough; 3–5 is ideal.
Evidence depth scales with screenshots — one unlocks the base assessment; more screens deepen coverage.
Product Friction Assessment
Analyzing your product
Turning your screenshots and context into an evidence-led assessment.
- Reviewing screenshots
- Mapping workflows
- Identifying friction
- Synthesizing findings
Summary
Product Assessment
Find what blocks growth before your next roadmap commit
When adoption, conversion or retention stall and internal teams disagree on why, this deliverable turns usage evidence into one prioritized plan leadership can act on.
Applied across complex B2B and operational software, including product workfor Route One and Omio.
02 · Deliverable
What you receive
One written assessment, not a slide deck of opinions. Product, UX and workflow analysis in a single prioritized view your team can share.
- Findings tied to adoption, conversion or retention metrics
- Recommendations ranked by impact, confidence and effort
- 90-day roadmap sequenced for delivery, not a flat backlog
Customized to your product and constraints. Consistent section structure so every stakeholder knows where to find context, findings and next steps.
Is this the right deliverable?
Three checks, timing, evidence base and boundaries.
What the assessment is built from
Findings in the document reflect real usage evidence, the mix depends on access and product complexity:
- Product analytics and funnel data
- Support themes and recurring friction patterns
- Workflow walkthroughs across key roles
- Stakeholder and user interviews where scope includes them
- Review of existing documentation and in-product flows
When another format fits
- You only need a quick UX review of one screen, scope may be narrower
- You already have a validated roadmap and need implementation support instead
Product Audit, Assessment, or Implementation Support?
Three related formats with different depth, timing and deliverables. Most diagnostic work flows from audit to assessment; implementation follows once direction is validated.
| Product Audit | Product Assessment | Implementation Support | |
|---|---|---|---|
| What it is | A structured diagnostic engagement - research, analysis and recommendations delivered hands-on. | The decision-ready document - executive summary, findings, prioritized recommendations and 90-day roadmap. | Post-diagnosis support - specifications, team collaboration and delivery validation with your engineering team. |
| Primary output | Findings, stakeholder alignment and a path forward - often culminating in a written assessment. | One shareable written report for product, design, engineering and leadership. | Shipped improvements, specs and validated UX changes in your codebase or design system. |
| Typical duration | 5–7 working days | 5–7 working days (standalone or as audit deliverable) | Flexible - sprints or ongoing support after direction is validated |
| Best when | Metrics are off, teams disagree on the cause, or you need an independent view before committing budget. | You need a shared evidence base and prioritized plan before a roadmap reset or redesign. | Direction is validated and you need senior support to ship with confidence - not outsourcing. |
Many Product Audits culminate in a Product Assessment document. Implementation Support is the natural next step when recommendations are approved. Product Audit · Implementation Support
03 · Structure
Ten sections.
One decision-ready document.
Depth adapts to your product, sections are included when relevant to scope.
Read the example assessmentContext
- 01
Executive Summary
Leadership-ready overview of the situation, top findings and recommended focus areas.
- 02
Product Overview
Scope of what was reviewed, product surface, primary users, and key flows included in the assessment.
- 03
Business Context
Goals, constraints, metrics and stakeholder priorities that frame the findings.
Findings
- 04
Product Findings
Evidence-based issues in product logic, feature adoption and gaps between intent and usage.
- 05
UX Findings
Interface friction, usability problems and interaction patterns that block progress.
- 06
Workflow Analysis
How people complete critical tasks end-to-end, including workarounds and handoffs between roles.
- 07
Information Architecture
Structure, navigation and findability, where users lose orientation or duplicate effort.
Action plan
- 08
Prioritized Recommendations
Ranked improvements with rationale tied to business impact, confidence and implementation effort.
- 09
90-Day Roadmap
Phased plan for the highest-leverage fixes, sequenced for delivery, not a flat backlog.
- 10
Executive Conclusions
Decision-ready summary: what to do next, what to defer, and what success should look like.
04 · Example
Read an example assessment
The linked document is a complete Product Assessment. It shows the structure, tone and level of detail you can expect, not a generic template filled with placeholder text.
About the example. The sample is in English. Your deliverable language follows the engagement. Structure and rigor reflect actual client work.
Related content
05 · Questions
Before you book
- Is the example document exactly what I would receive?
- The structure and rigor are representative. Your assessment is customized, sections deepen or slim based on product complexity, access to data and business questions.
- How do Product Audit, Product Assessment and Implementation Support differ?
- Product Audit is the engagement - hands-on diagnostic work. Product Assessment is the deliverable - the written report with findings and roadmap. Implementation Support follows when your team is ready to ship validated changes. See the comparison table on this page for timing and fit.
- How is this different from a Product Audit?
- The Product Audit page describes the engagement. This page describes the deliverable - the document your team receives. Many audits culminate in a Product Assessment.
- How long does it take to produce?
- Most focused assessments run 5–7 working days depending on product scope, stakeholder availability and data access.
- Can I share the assessment internally?
- Yes. It is written for product, design, engineering and leadership, with an executive layer for decision-makers who will not read every finding.
Discuss a Product Assessment for your product
Tell me what is not working. I will confirm whether this deliverable format fits your situation and timeline.