Day 227 of the Daily · Product Management

Versioning

5 min read · 4 principles · apply it by lunch

Good morning. One product, one price, and a market full of people who’d happily have paid something else.

The question

Look at the cheapest thing you sell and the dearest one, then say what actually differs between them — not the price, the product itself: is that difference a dimension your best customers would genuinely pay to escape, or a handful of things somebody switched off on a Thursday so the tiers wouldn’t look identical?

The idea

Carl Shapiro and Hal Varian were both economists at the University of California, Berkeley — Shapiro at the Haas School of Business, Varian the founding dean of the School of Information Management and Systems — when they published Information Rules in 1998. Their starting point is that an information good costs a fortune to make once and almost nothing to make again, so cost tells you nothing useful about price. Value does, and value differs person to person. Since you can’t read willingness to pay off a buyer’s forehead, you ship the same underlying thing in several editions and let people sort themselves. What Shapiro and Varian supply is the list of axes you can version along — delay, speed, resolution, capability, comprehensiveness, support and, memorably, annoyance — not one of which is the price. The harder half of the argument belongs to Raymond Deneckere and Preston McAfee, in the Journal of Economics and Management Strategy in 1996, under the title ‘Damaged Goods’. They open with Intel’s 486SX, a 486DX with the maths coprocessor switched off, and go on to IBM’s LaserPrinter E, which printed at half the speed of the LaserPrinter because IBM had added parts that held it back. The cheap edition cost more to build. Their finding is that the damage can leave both sides better off — the firm earns more, and buyers who would otherwise be priced out get served at all.

In the Daily · 4 principles and a template

Versioning is Day 227 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 236 · Product Management

The Opportunity Solution Tree

Pick any item on the roadmap you’re working to right now and say out loud which outcome it’s meant to move and which customer need it addresses — then work down the list item by item, and how far do you get before the honest answer becomes ‘because it was already on the roadmap’?

See the framework →
Day 245 · Product Management

The House of Quality

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.

See the framework →
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 →