Day 229 of the Daily · Operations

The Product-Process Matrix

5 min read · 4 principles · apply it by lunch

Nobody in your business ever chose the way work moves through it. It accumulated.

The question

How many jobs did your operation deliver last quarter, and how many of those needed a step your standard path doesn’t have — and was the way your work is organised designed for that pair of numbers, or for the pair you had the day you set it up? Whenever the honest answer is the second one, the gap between those two pairs is coming out of your margin every week, in a line nobody can quite locate.

The idea

Almost everything that matters about how work moves through a business comes down to a diagonal line on a single grid. The grid appeared in the Harvard Business Review in 1979, when Robert Hayes and Steven Wheelwright published ‘Link Manufacturing Process and Product Life Cycles’ — a piece that has outlasted most of what was written about factories that decade. Down one side sit four ways of organising work: the job shop, where every order takes its own route; the batch, where similar jobs are grouped and run in lots; the line, where a fixed sequence handles a few high-volume products; and continuous flow, where the thing never stops. Across the other sits the product itself — one-off and bespoke at one end, standardised and high-volume at the other. What matters is the diagonal. Low volume with high variety belongs in a job shop; high volume with low variety belongs on a line. Businesses in trouble are rarely bad at the work; they’ve drifted off the diagonal and are running one structure while selling the other. The trap is that the drift is invisible from inside it: there’s no meeting where it gets decided, no line in the accounts where it shows up, and it usually becomes obvious only when somebody else prices you out of your own category.

In the Daily · 4 principles and a template

The Product-Process Matrix is Day 229 of 365.

In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.

$29 a month · cancel any time · 7-day money-back guarantee

More from Operations

The next four in the course.

All 24 Operations frameworks
Day 239 · Operations

Takt Time

Ask whoever runs your busiest repeated process how often a finished one has to come off the end for the business to keep the promises it’s already made — could they give you a number, or would they tell you they’re going as fast as they can? One of those is a rate you can staff to. The other is an apology.

See the framework →
Day 248 · Operations

The Level Schedule

Look at what your team actually started in each of the last four weeks — not what was sold, what was released into the work — and how far apart are the biggest and the smallest of those weeks? If you don’t have the numbers to hand, the shape is almost certainly your order book’s, because that’s the default: whatever arrives gets released, and the swing gets paid for by everyone standing behind you.

See the framework →
Day 257 · Operations

Batch Size and Changeover

Pick the thing your operation does in batches — the Thursday invoice run, the fortnightly release, the print run, the monthly board pack — and ask why it’s that size rather than half of it: can you give a reason that isn’t simply that switching over is a nuisance nobody wants to do twice? If not, you’ve been paying for that nuisance in flow time every week since, and never once priced it.

See the framework →
Day 266 · Operations

Pull and the WIP Limit

Count the pieces of work your team has open right now — the half-drafted, the in-review, the waiting-on-a-client, the one you’d have to check the board to remember — then count the people, and ask whether the first number is more than double the second. If it is, you already know why everything takes so long. The queue isn’t in front of your team; it’s inside it.

See the framework →