People Don't Buy Products. They Hire Them for Jobs.

In 1977 Lynn Shostack sat in a Citibank conference room while a colleague walked a new private-bank package on slide four: fee tiers, statement design, envelope stock. She had spent the prior years at Greenwich Associates watching financial services firms market trust the way supermarkets market soup. princeton-shostack She was vice president by then, marketing director for the investment management group, shostack-1977 and the room was nodding on autopilot. Then she asked the only question the deck could not answer: what happens to the client on the morning the report is wrong and nobody picks up the phone?

No transcript captures that room; what follows matches her published role and the argument she would take to print. Her colleague said operations would cover it. He opened slide five. Nobody in the room could describe that morning. That silence is not a sales failure. It is a category error. Nobody buys your product. They hire something to make progress on a job in a specific circumstance, then fire it when progress stalls or a better hire appears. Shostack published the argument in the Journal of Marketing in April 1977 under the title "Breaking Free from Product Marketing." shostack-1977 Tech would spend the next fifty years repackaging the hire logic and forgetting who drew the blueprint first.

We all have sat in a similar room wearing different clothes. Hers was fee tiers and envelope stock on slide four. Yours might be forty integrations and a per-seat price on slide six. In both rooms the deck skipped the same beat: what happens the morning after sign-off, when the exception queue lands and nobody from the vendor picks up the phone. Or you subscribed to a tool you "should" use while still doing the job in a spreadsheet because the hire never started. The claim is not about catalogue purchases made for pleasure or status. It is the hire logic that shows up when a team renews software while the spreadsheet still runs the job. AI copilots have pushed many category reviews toward one blunt question: what job does this replace in someone's actual week? The purchase was not possession. It was temporary employment with a performance review you never scheduled.

Feature Roadmaps Are HR Departments for Objects

The conventional view is simple and wrong in a useful way: we sell products, growth means more seats and more releases, and a healthy account expands. That story benefits vendors who earn expansion revenue when a module ships. It benefits agencies who sell integration statements of work that grow with every connector badge, analysts who sort firms into quadrants by feature breadth, and product managers whose promotion packet needs a visible widget in the sprint demo. Jobs are harder to commit to in Jira because they expire when context changes. A feature can sit on a roadmap for three quarters and still look like progress.

We measure the wrong instrument and call it health. Activation funnels, monthly active users, time-in-app: these track whether the object stayed on the payroll, not whether the job got done. Shostack saw the same mismatch in banking dashboards that counted accounts opened while the service experience leaked at the touchpoints nobody mapped. The label was wrong before the metric was.

She Watched Banks Market Trust Like Soup

For a century, product meant something you could hold, stock, and ship: inventory on a shelf, a drill in a box, a milkshake in a cup. Much of B2B SaaS imported the word anyway. Subscriptions, onboarding calls, success managers, and API limits became "products" because the label sounded scalable and pitch decks already had a slide for it. Shostack had started as an art major at the University of Cincinnati and finished at Harvard Business School with no interest in business until she discovered it was plastic enough to mould. princeton-shostack Her father was a mechanical engineer with a workshop in the garage. She learned early that performance happens over time, not at the point of sale.

In 1977 she argued that services are intangible, co-produced with the customer, and consumed as they are delivered, which means marketing them with product playbooks is mirror-image wrong. shostack-1977 Seven years later, in Harvard Business Review, she opened with the symptoms everyone recognises: the shirt that returns with a broken button, the car rattle that reappears after an expensive repair, the representative who promises a callback and does not call, the cash machine that swallows your card. shostack-hbr-1984 She argued that services need their own design discipline and drew the service blueprint so teams could see the backstage work a client never should have to notice. Stephen Vargo and Robert F. Lusch argued in the Journal of Marketing in 2004 that value is co-created through service, not transferred like goods on a loading dock. vargo-lusch-2004 I have shipped onboarding flows that looked like product tours because the roadmap was written in features, not acts in a service over time. You do not unbox a subscription. You live inside it until you fire it.

The Same Milkshake Hires Two Different Employees

Clayton Christensen turned hire logic into the Jobs to Be Done framework: customers make progress in a circumstance, not collect features on a shelf. His milkshake research is the textbook case. The same cup gets hired twice in one day, thick enough to kill boredom on a morning commute, sweet enough to bribe a parent with a child in the evening. The milkshake was a product in the old sense, tangible and stocked. Christensen still wrote product; the hire logic travels when Silicon Valley mislabels a service as one. He codified the theory in Competing Against Luck (2016), with Taddy Hall, Karen Dillon, and David S. Duncan, and in "Know Your Customers' 'Jobs to Be Done'" in the Harvard Business Review in September 2016. christensen-luck christensen-jtbd-hbr Different employer, different success criteria, different substitute when the hire fails.

Theodore Levitt made the earlier version in "Marketing Myopia" in the Harvard Business Review in July 1960: industries decay when they ship drills instead of holes. levitt Christensen, Scott Cook, and Taddy Hall had already argued in "Marketing Malpractice" in the Harvard Business Review in December 2005 that firms should segment by job, not demographic, before the framework had its name on the slide. christensen-malpractice I argued the buyer's side of that table in People Love to Buy: agency lives in naming the problem before anyone opens a deck. Shostack arrived earlier with a different instrument: map the service before you market the package. The competing hire is rarely your listed competitor. It is Excel, a shared inbox, an intern for a week, or the workaround someone built at midnight because the SaaS never matched how exceptions actually move. Every category review eventually returns to the same blunt question she asked in that Citibank room: what job does this replace, and what happens to the person still doing it manually?

Firing Is Not Churn. It is the Performance Review.

Switching tools is not betrayal. It is HR. The customer fired the incumbent because progress stalled, the onboarding never transferred the job, or a cheaper hire appeared that actually cleared the queue. Churn charts record the exit interview after the decision was made. By the time renewal fails, the spreadsheet has often been doing the work for months. The vendor learns about the firing from a logo churn slide, not from the morning in week two when the tab stopped opening.

Demand, when it is real, is for the job done at economics that work, not for your SKU on the invoice. I wrote that shortage logic in Product Market Fit Is What Economists Call a Shortage: pull at a viable price means people want more of the outcome than you can comfortably deliver, not more of your feature map. Shostack's HBR symptom list is a performance review written in domestic prose. A team still colour-coding exceptions at ten in the evening while the subscription renews is not a retention problem waiting for a win-back email. It is an employee who never showed up for the shift.

She Drew the Blueprint. I Renamed the Epics.

Shostack did not leave banking marketing to write theory and stop. She went on to Bankers Trust, then manufacturing, then a long second act in philanthropy and investment with her husband David Gardner, a Princeton graduate who died in 2001. princeton-shostack She funded endowments for curiosity without quarterly justification, including Princeton's Project X fund for engineers who need freedom to chase a hunch. She chronicled coming up through a world of men in a private book called Men in Business. men-in-business The through-line is the same: name the work, then design the system that performs it.

I ran a Jobs to Be Done workshop at a client offsite once. Sticky notes lined the wall, each labelled "Job," and by the second coffee break I could see they were epics in disguise: "Streamline workflow," "Increase visibility," "Enable collaboration." Nobody wrote what changed in an inbox before noon. Shostack would have asked for a blueprint line by line. shostack-hbr-1984 I did not push. That was the brief. I left with a workshop fee and a slide titled "Innovation." They left with the same dashboard she would have recognised from 1977.

Product Designer Is the Trendy Mislabel

I call myself a product design expert on profiles and proposals because the label wins searches and signals fluency in the current jargon. The work is often service design by Shostack's definition: onboarding choreography, handoffs, exception flows, the week after sign-off. Experience designer would be closer. Service designer would be honest. Product designer is what clients expect to buy, and I have not corrected them.

Sir Jony Ive trained in industrial design and built a career on objects you could hold: hinge tolerances, chamfered aluminium, weight in the palm. ive-industrial-design I have never shipped a billet. I suspect he would find our title inflation absurd even if he never said so on the record. The hypocrisy is not only in the vendor deck. I wear the mislabel because it rents well.

The Expensive Striker Still Gets Benched

You have watched a football match turn and felt the frustration before you had the vocabulary for it. Your club is losing. The manager benches the £50 million signing at the sixtieth minute and sends on a kid from the academy who has not scored in months. Nobody in the stand thinks loyalty to the transfer fee matters. The job tonight is to score. The asset is the player's CV. Expected-goals charts arrive on the phone later. Your stomach already knew at the hour mark.

That substitution is what your customer does when they reopen the spreadsheet. They are not being disloyal to your roadmap. They are losing, and you stayed on the pitch while the queue kept growing.

The Strongest Case for Selling the Product, Not the Job

Let me state the strongest case against this, because the alternative is a workshop handout. Customers cannot articulate jobs in interviews. They lie, post-rationalise, and describe the product they already bought. The Jobs to Be Done framework can become retroactive storytelling after the fact. Christensen and colleagues argued in the September 2016 Harvard Business Review that the job is often discovered through observation in context, not through a survey that asks what people want. christensen-jtbd-hbr In enterprise software the purchase is often risk transfer: vendor balance sheet, SOC 2 certificate, latency SLA, the name on the contract when audit asks questions. Technical buyers genuinely hire specs, not feelings. Clayton Christensen acknowledged jobs shift when context shifts. Good product managers already track outcomes and north-star metrics. In categories where compliance is the job, selling "progress" sounds like marketing fluff next to a procurement matrix. If you wait for perfect job clarity, you never ship. The incumbent with the louder feature list wins by inertia.

The gap is not whether specs matter. It is whether your firm can state the job you are hired for before the customer writes the performance review for you. Clayton Christensen, Scott Cook, and Taddy Hall argued in "Marketing Malpractice: The Cause and the Cure" in the Harvard Business Review in December 2005 that segmentation by job, not demographic, predicts which innovations succeed, and that most companies cannot articulate the job they are hired to do. christensen-malpractice Alan Klement pushed the same line in When Coffee and Kale Compete (2018): customers pull products that help them make progress, not products that win feature comparisons on a slide. klement-coffee-kale Shostack's blueprint was the operational answer Christensen's milkshake case still leaves abstract: draw the morning the client is living, then decide if your service earns a renewal.

Customers hire for progress and fire for stall. Until your success metric names the before-and-after in the customer's week, you are optimising a CV, not a hire. Lynn Shostack drew the blueprint more than forty years ago; the spreadsheet is still doing the job her line of visibility was drawn to protect.