Day 245 of the Daily · Product Management

The House of Quality

5 min read · 4 principles · apply it by lunch

Good morning. A customer says it should feel solid. Somebody now has to turn that into a number.

The question

Your customers keep asking for the same vague thing — that it feel faster, or simpler, or more solid — and delivering it means moving one measurable characteristic inside the product: can you say which one, and in what unit? Most teams can’t. So the unit gets chosen by whoever writes the code, at the moment they write it.

The idea

In the Harvard Business Review of May-June 1988, John Hauser of MIT’s Sloan School and Don Clausing, an engineering professor at the same institution, published ‘The House of Quality’ — the article that set out quality function deployment’s basic design tool for Western managers. The method was Yoji Akao’s, and the house itself originated in 1972 at Mitsubishi Heavy Industries’ Kobe shipyard, after which Toyota and its suppliers developed it further; by the time the article ran, Ford alone had more than fifty applications of it. The house is a grid. Down the left side go customer attributes in the customer’s own words. Across the top go the engineering characteristics you can measure and move. The body records which characteristic affects which attribute, and how strongly. Their worked example is a car door: ‘easy to close’ carried an importance of 7, and translated into the engineering characteristic ‘energy needed to close the door’, with a target of reducing that to 7.5 foot-pounds. Then comes the roof — the triangular matrix sitting on top — which records which engineering characteristics fight each other. Lower the energy needed to close the door and you weaken the seal and let in road noise. You can’t have both, and the roof is what makes you choose rather than discover it late.

In the Daily · 4 principles and a template

The House of Quality is Day 245 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 Product Management

The next four in the course.

All 22 Product Management frameworks
Day 255 · Product Management

RICE

When your team last settled what to build next, could anyone in that room have said out loud how sure they were — not whether the idea was good, but how much of the case rested on a figure somebody had actually gone and looked up? I’ll give you the answer: nobody was asked, because nothing on the list carried a number anyone could argue with.

See the framework →
Day 264 · Product Management

Working Backwards

Your team is building something right now that nobody outside the building has heard of yet — so on the day it ships, when the announcement goes out with the customer named, the problem stated and the reason anyone should care in two plain sentences, will a stranger read that and want the thing, or read a list of capabilities and feel nothing at all?

See the framework →
Day 274 · Product Management

User Story Mapping

Your team has committed to a release next: could one real customer start at the very beginning and get all the way through to the thing they actually came for using only what’s above the line — or does it stop somewhere in the middle, polished at step one and missing entirely at step four? A backlog sorted by priority almost always slices the wrong way.

See the framework →
Day 283 · Product Management

Brooks’s Law

Think about the last project that ran late on you: when the extra people arrived, who stopped doing their own work in order to bring them up to speed, how many weeks went by before the newcomers were producing more than they were consuming, and did anyone put either of those two costs on paper before the decision got made?

See the framework →