Method
Good digital product experiences start before the interface.
This is the full method, in eight stages — not a sales sequence. Each stage answers a specific question, and no stage is skipped to reach a predetermined deliverable.
The Home page shows a high-level summary of this process.
00
System overview
Eight stages, one dependency chain.
Each stage takes the previous stage's output as its input. Judgment happens inside each stage — not at the end. If an early stage is skipped, everything after it inherits unverified assumptions.
- 01Commercial Context
→ the current commercial reality
- 02Product Truth
→ verified product facts
- 03Product Architecture
→ families, hierarchy, differentiation
- 04Customer Decision Truth
→ the decisions customers must make
- 05Decision Experience
→ where the experience fails the decision
- 06System Design
→ what should be built — and what not
- 07Implementation
→ a working digital experience
- 08Verification
→ a verified release
01
Commercial Context
Diagnosis starts from commercial reality, not from the sitemap.
The business as it is today — what is sold, how it reaches customers, and where education, selection and transaction actually occur.
What is commercially current — and what is already obsolete.
The current commercial reality the work must serve.
Obsolete or irrelevant product structures are not diagnosed — the current business is.
02
Product Truth
You cannot build a clear decision experience on uncertain product truth.
Current products, specifications and technical material.
Which attributes are meaningful, verifiable and material to customers.
Verified product facts — the Product Truth layer.
03
Product Architecture
Separating real decision complexity from superficial SKU complexity.
Verified product facts.
Real decision complexity versus superficial SKU complexity.
Product families, relationships, differentiation and hierarchy.
04
Customer Decision Truth
A Finder is a conclusion, not an assumption.
The product system and how customers actually buy.
Which decisions customers must make before they can buy with confidence — and which variables separate appropriate choices.
The decision set the experience must support.
A catalog being large does not by itself mean customers need a product finder. That determination follows the evidence.
05
Decision Experience
The test is not "is this good design?" but "does this support the decision?"
The decision set and the current digital experience.
Where the current experience supports those decisions — and where it fails.
An evidence-based picture of the gaps.
The current experience is evaluated against the verified decisions — including:
- navigation;
- category pages;
- product cards;
- product detail pages;
- comparison;
- selection paths;
- technical information;
- channel paths;
- purchase handoffs.
06
System Design
Features follow the problem.
The evidence-based gap picture.
What should be built — and what should not.
The system design: hierarchy, comparison, selection support, technical education, PDP structure — where justified.
07
Implementation
Beyond recommendations, into implementation.
The system design.
How it translates into interface structure, product content structure and frontend implementation — with responsive behavior and appropriate integrations.
A working digital experience.
This practice is capable of moving beyond recommendations into implementation. It does not assume every diagnosis becomes an implementation engagement.
08
Verification
No unverified performance claims.
The implemented work.
Content consistency, product logic, decision paths, responsive and functional behavior, regression risk.
A verified release — or a bounded punch list.
The method is deliberately bounded.
Internal research frameworks, screening systems and qualification thresholds remain private and are not published.
If you want to see how the first stages apply to your product line, the Product Decision Review is the low-friction entry point.