“We need a dashboard.”
The requested feature is not proof of the real need.
For product managers, product owners, business analysts and technology professionals. Start with a signal, a problem or an idea; leave with alternative approaches, uncertainties and a practical next investigation.
Work through a question-led journey: reframe the need, develop alternatives, pressure-test the assumptions and identify the next experiment.
Questions provide guidance, not independent validation. Responses stay in this browser tab unless exported; do not enter confidential information.
Start with a real signal—not your favourite feature. Capture who experiences the friction, what evidence exists and where to look next.
Use as a thinking aid, not proof of demand.
Turn a promising idea into a small test. Define what you need to learn before investing in a full solution.
Set success criteria before testing; evidence may support, change or disprove the idea.
An exploratory way to assess whether a product or technology decision is likely to create meaningful value across customer or user outcomes, operational benefits, cost, risk and the ability to deliver and sustain the change.
This is a working idea, not a validated or proprietary framework.
Structure the options, constraints and evidence before making a decision.
A service team requests a new dashboard. Instead of immediately designing charts, begin with the decision they struggle to make.
The requested feature is not proof of the real need.
Observe the workflow and interview the people involved.
This might be a data-access problem rather than a visualisation problem.
Measure whether decisions improve before funding a dashboard.
Fictional example for learning only; not an actual client engagement or proven product outcome.
A hypothetical company is considering a SaaS upgrade. The question is not simply whether the new feature list is attractive, but whether the investment addresses a meaningful problem and whether integration, adoption and operational costs are understood.
Potential functionality gains; requires evidence on adoption, integration effort and total cost.
Lower immediate commitment; may delay benefits that depend on broader platform change.
Entirely hypothetical. Not a representation of a real employer, client or completed consulting engagement.