Product Lab

Explore a need, question an idea and plan a test

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.

Start here · Interactive thinking journey

Opportunity Explorer

Work through a question-led journey: reframe the need, develop alternatives, pressure-test the assumptions and identify the next experiment.

Think before you build1 of 7

Questions provide guidance, not independent validation. Responses stay in this browser tab unless exported; do not enter confidential information.

Optional worksheet · Capture your thinking

Opportunity Discovery Canvas

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.

Tool 02 · Idea validation

Experiment Planner

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.

Concept · In development

Product Value Compass

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.

Questions worth asking

  • What problem is worth solving?
  • Who benefits, and how will we know?
  • What assumptions could invalidate the plan?
  • What are the critical dependencies?
  • Who owns the benefits after delivery?
Tool 03 · Investment and delivery decisions

Product & Technology Decision Brief

Structure the options, constraints and evidence before making a decision.

Worked example · Entirely hypothetical

From a dashboard request to a testable opportunity

A service team requests a new dashboard. Instead of immediately designing charts, begin with the decision they struggle to make.

Signal

“We need a dashboard.”

The requested feature is not proof of the real need.

Investigate

Which decision is slow?

Observe the workflow and interview the people involved.

Hypothesis

Information arrives too late

This might be a data-access problem rather than a visualisation problem.

Test

Run a manual weekly summary

Measure whether decisions improve before funding a dashboard.

Fictional example for learning only; not an actual client engagement or proven product outcome.

Illustrative example

A fictional SaaS investment decision

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.

Option A

Upgrade now

Potential functionality gains; requires evidence on adoption, integration effort and total cost.

Option B

Targeted improvement first

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.