Use case · Human-centered Product Development

Product decisions that rest on users, not on opinions

rygg connects roadmaps, requirements and designs with the evidence about users and contexts of use. Teams focus on outcomes that matter to users and therefore to the business, and every decision shows what it rests on.

REQ-114Braking distanceDriver in raincontext of useFMEA chassishighest risk: wetFinding P-22test was missingTC-31suggested test
Traceability: from requirement via context of use and evidence to a suggested test. Sample data.

Situation

  • Roadmaps are decided in meetings. Which user requirement a feature serves, and how certain that is, often stays open.
  • Research is commissioned per project and filed afterwards. The next project starts again from zero.
  • Use errors and wrong assumptions surface late, in the field or shortly before series launch, where changes are expensive.

Questions the graph answers

Every answer shows its source and whether it is evidence or assumption.

  1. Which user requirement does this feature serve, and how certain are we?
  2. Which contexts of use does our portfolio cover, and which are missing?
  3. Which roadmap items rest on evidence, which on assumption?
  4. Which outcome for users do we expect, and how do we measure it?
  5. What did earlier studies find about this task or this user group?
  6. Which use errors were found before launch, and which were fixed?
  7. What does it take to show conformity with HCRD standards for this product?

What rygg provides

  • A domain model of users, tasks, contexts of use and requirements, linked to roadmap items and designs
  • Traceability from research finding to requirement to design decision to test result
  • Coverage reports per product, variant or market
  • Research & Design Engineers who close gaps in the field and feed the results back
  • Validation against HCRD standards with every release

Who works with it

  • Product management
  • UX and research
  • Engineering leads
  • Quality and approval
  • Portfolio management

What you can measure

Examples. We agree on metrics we can influence, not on your revenue.

  • Coverage of contexts of use across the portfolio
  • Share of requirements traceable to research
  • Use errors found in usability tests before series launch
  • Time to evidence of conformity with HCRD standards

How it starts

We start with one product line: existing research is brought into the graph, gaps are closed with a short study, and the roadmap is checked against the evidence.

Package: Pilot · 4 to 8 weeks

The same graph serves