Product thinking
The ability to see the product as a way to solve the customer's task and create business value: choose what to do and what not to do, balancing value, cost and risk.
Definition
BT360 v2.0.0The ability to see the product as a way to solve the customer's task and create business value: choose what to do and what not to do, balancing value, cost and risk.
What is it made up of?
3 INDICATORS- 01Understanding the customer's task and value
- 02Choosing priorities and saying no
- 03Balancing value, cost and risk
Behavior levels 0–5
MANAGER'S GOAL - 3| Lv. | Label | Descriptor |
|---|---|---|
| 0 | Absent | The product is a set of features; the customer's task is unclear; priorities are random; features are added instead of solving the task; value is not measured. |
| 1 | Poorly developed | Understands the product but not the task; picks features by how loudly they are requested; cannot say no; does not connect decisions to metrics. |
| 2 | Underdeveloped | Articulates value for part of the customers; prioritizes by obvious criteria; finds refusals difficult; uses metrics partially. |
| 3 | Normally developed leader's goal | Understands the task and the value; sets priorities by contribution; says no; balances benefit, cost and risk; tests hypotheses with metrics. |
| 4 | Highly developed | Builds product logic on insights; manages a portfolio of bets; finds non-obvious value; makes decisions to say no; connects the product to strategy. |
| 5 | Overdeveloped | Product thinking turns into perfectionism: endless improvements, constant scope creep, growing complexity; the product loses focus; time to market grows. |
How is it measured?
coating BSJT - BT360 situational test: provides a hypothesis about judgments in work situations and does not replace observation, 360 and interviews.
There is no direct test of product thinking; BFI-44 (openness) provides only a weak hypothesis. The level is confirmed by the product case and solutions.
Development Actions
5 CATEGORIESCase 'what we do and what we do not do'; audit of product decisions: value, cost, metrics, refusals.
Course 'Product thinking': customer tasks, value, prioritization, metrics, saying no.
Prioritize the backlog by value, cost and risk and defend three refusals.
Review with the product lead: where you added a feature instead of solving the task.
Introduce the team rule 'every feature has a customer task and a metric'.