After the creation of a Needs Matrix, the NeedRank™ algorithm will have computed values for the x and y axes for each job-to-be-done. The x-axis is the importance to the people you care about most and the y-axis is the importance to the organisation.

These weightings are then carried through into the scorecards automatically as x*y.

Weightings for scorecard dimensions may be set and changed manually as a score from 1 to 100. The default is 25 to represent a mid-range value.

Why isn't the default 50? Well, if you look at the weighting table below, you'll see that the value in the centre of the Needs Matrix is 5*5, which is 25.

The simplest way to select a weighting for a dimension

Decide how important it is to your organisation on a scale of 0-10 (with 10 being absolutely critical). Then square that number (multiply it by itself). So if you decide the dimension of "cost", say, is a 7 on that scale, the number to enter in the dimension weight is 49 (7x7).

If you're unsure which dimension is more important than another, you can use this quick trick to identify the relative importance of all the dimensions.


Geeks only beyond this point

Weightings are calculated using a 2-dimensional non-linear array.

If you think of a ruler, with the numbers 1 to 10 on it, equally spaced, that’s a linear scale. However, the digits on our N2D ruler are actually squares of themselves. So, even though we might see 1 to 10, evenly speed on a ruler, the values of those digits are actually 1, 4, 9, 16, 25, 36, 49, 64, 81, 100. Their spacing increases as you go along the ruler.

What makes Method weighting more complicated still is that it’s a 2-dimensional non-linear array: it’s not a single ruler with non-linear values, it’s two of them forming a right angle. One for the importance of JTBD to the people and the other for the importance of JTBD to the organisation. This creates a plane.

This is what the weighting table looks like visualised in a 3D plot. You’ll notice that it gets much steeper toward the top right.

Plot courtesy of WolframAlpha.

For a JTBD to achieve a weighting of 100 all of the following would have to be true:

  • every single segment has this JTBD

  • the JTBD is absolutely critical to every segment

  • helping people achieve the JTBD would accomplish every single objective the organisation has

Very low probability that this will ever be the case. This is why the weighting table gets steeper. It's much harder to achieve scores on the steeper part of the slope.

Did this answer your question?