,

They Didn’t Sell Bacon. They Changed What Breakfast Meant.

They Didn’t Sell Bacon. They Changed Breakfast | JTBD and Product Management
Product Management · Customer Psychology · JTBD

The story of Beech-Nut, Edward Bernays and the campaign that helped popularise bacon and eggs as an American breakfast. And what it teaches Product Managers about understanding customer behaviour before building a product.

1. The Story: A Company Wanted to Sell More Bacon

Imagine it is the 1920s in America.

You run a company that sells bacon. You have a good product, production capacity and customers who already buy it.

But there is a problem: people are not eating enough of it.

That was the challenge facing the Beech-Nut Packing Company, which hired public relations consultant Edward Bernays to help increase bacon sales.

At the time, many Americans were moving towards lighter breakfasts. A typical morning meal might consist of coffee, toast, a roll or cereal. Bacon existed as a food people could eat, but it was not necessarily the centrepiece of everyone’s morning.

Beech-Nut had a commercial problem. It wanted people to buy more bacon. One obvious approach would have been to advertise its bacon more aggressively, promote discounts or persuade customers to switch brands.

Bernays took a different approach.

The strategic question

Instead of asking only how to persuade people to buy Beech-Nut bacon, Bernays looked at the behaviour surrounding the product.

What if more people could be persuaded to eat a substantial breakfast, and bacon became part of what a substantial breakfast meant?

This was a much bigger opportunity than convincing someone to choose one bacon brand over another.

If people changed their breakfast habits, the market for bacon could grow. The company would benefit not just from winning customers away from competitors, but from encouraging a broader eating occasion.

Bernays was not simply trying to make people prefer a product that already existed. He was working to change the context in which people thought the product belonged.

How Did He Bring Doctors Into the Campaign?

Bernays understood that people do not make decisions based only on advertisements. They also look to people and institutions they consider credible.

For a question about food and health, doctors were an especially influential group.

Bernays approached a physician and discussed the idea that a more substantial breakfast could be preferable to a very light one. He then arranged for the physician to contact 5,000 other doctors to ask whether they agreed.

According to Bernays’s account, approximately 4,500 doctors responded, and the responses generally favoured a more substantial breakfast.

Bernays publicised the results. Newspapers reported on the doctors’ views, and bacon and eggs became associated with the idea of a hearty, substantial American breakfast.

An important historical distinction

The survey asked about the merits of a substantial breakfast. It did not establish that bacon and eggs were medically necessary, nor did it prove that this specific meal was healthier for everyone.

The public story connected a broad endorsement of a hearty breakfast to a specific meal that suited the client’s commercial interest. That distinction is important when evaluating the campaign.

The campaign is commonly cited as a successful example of early public relations. Bernays later described the favourable publicity and the resulting increase in bacon sales.

The bigger idea was that a company could benefit by changing the way people thought about an entire behaviour, rather than merely promoting its own product.

Historical background: Edward Bernays’s account of the campaign, coverage from the American Psychological Association, ABC News and Journalism History are listed in the sources at the end of this article.

2. The Clever Part Was Not the Bacon

Let’s look at the problem from the company’s perspective.

Beech-Nut could have tried to solve the problem at the product level:

  • Make its bacon packaging more attractive.
  • Advertise the taste.
  • Offer promotional pricing.
  • Persuade customers that its bacon was better than another brand.

These tactics might help a brand win a larger share of existing demand. But they do not necessarily change how often people eat bacon.

Bernays approached the challenge at a different level: the behaviour and beliefs that created demand in the first place.

Product-focused thinking Behaviour-focused thinking
How do we sell more bacon? How could bacon become a more regular part of breakfast?
How do we make our product more appealing? What makes people choose a light or substantial breakfast?
How do we win customers from competitors? How might we expand the occasions when people want the product?
How do we communicate product features? What beliefs and circumstances shape the customer’s decision?

This is where the story becomes relevant to Product Management.

A product team often receives a request that appears straightforward: build a dashboard, add a chatbot, introduce an integration or automate a workflow.

But the request is only the visible part of the problem.

Behind it is a person trying to achieve something, in a particular situation, with particular constraints and expectations.

The feature is what the customer asks for. The job is the progress they are trying to make.

3. What Is Jobs to Be Done?

Jobs to Be Done, or JTBD, is a way of understanding customers through the progress they want to make in a given situation.

The central idea is often expressed as people “hiring” a product to accomplish a job.

They are not necessarily looking for a particular feature. They are trying to move from their current situation to a more desirable one.

The JTBD question

What is the customer trying to accomplish, and why is their current way of doing it not good enough?

Consider someone buying a drill.

They may compare battery life, speed, weight and price. But the underlying job might be to hang a shelf securely.

If the job is hanging a shelf, a drill is one possible solution. Depending on the situation, another mounting system or a handyman might also get the job done.

The customer is not necessarily loyal to the drill category. They want the outcome.

That distinction gives the Product Manager more freedom to find a better solution.

A Job Is Not the Same as a Feature

Concept Example
Job Make sure important patient follow-ups happen on time.
Pain point Staff manually check multiple lists and sometimes miss tasks.
Desired outcome Reduce manual tracking while improving follow-up reliability.
Feature request Automatically create follow-up tasks.
Potential solution A workflow that identifies eligible tasks, assigns responsibility and tracks completion.

Notice the order.

The feature makes more sense once the job and desired outcome are clear.

Functional, Emotional and Social Jobs

Customers are not always trying to accomplish a purely practical task. Their decisions can also involve how they want to feel and how they want to be perceived.

Type of job Question Example
Functional What do I need to get done? Complete patient follow-ups without manually checking every list.
Emotional How do I want to feel? Feel confident that important work is not being missed.
Social How do I want to be perceived? Be seen as organised and reliable by colleagues and patients.

Understanding these dimensions can help a team design a more complete experience instead of solving only the most visible task.

4. How the Bacon Story Connects to Product Management

The Beech-Nut story is not a literal example of a modern software product team applying JTBD. Bernays was running a public relations campaign, and his methods should not be confused with evidence-based product discovery.

But the story provides a useful analogy for a fundamental product management challenge:

Are we trying to sell a solution, or do we understand the situation that makes people need a solution?

Imagine a Modern Product Team

A company builds an AI meeting assistant. The team believes its product should attract customers because it can automatically transcribe meetings, generate summaries and extract action items.

After launch, sign-ups are healthy, but very few people continue using the product.

The team starts proposing more features:

  • More AI models.
  • Custom summaries.
  • More integrations.
  • Advanced search.
  • Additional reporting.

But nobody has properly investigated why people are leaving.

A JTBD-oriented PM would step back and ask what job customers were trying to accomplish when they tried the product.

A possible discovery

The customer may not really want another meeting summary.

They may want to leave a meeting knowing exactly what was decided, who is responsible for each action, and what needs to happen next.

The job could be: “Help me turn a meeting into clear, accountable next steps without having to reconstruct the conversation afterwards.”

That discovery changes the product discussion.

Instead of building a more sophisticated summariser, the team might test whether action-item assignment, reminders and task-system integration create more value.

The right answer still needs to be validated. JTBD does not magically reveal the solution. It helps the team ask a better question before spending time and money building one.

The Product Manager’s Equivalent of the Bacon Campaign

The useful parallel is not “make customers believe whatever we want.” It is to understand the context in which customers recognise a problem and choose a solution.

Beech-Nut story Product Management equivalent
Understand existing eating habits. Research the customer’s current workflow and behaviour.
Identify a wider breakfast occasion. Identify the underlying job and when it arises.
Use trusted voices to communicate a message. Use credible evidence, customer stories and relevant experts to explain genuine product value.
Change how a product fits into a routine. Design an experience that fits naturally into the customer’s workflow.
Observe changes in demand. Measure activation, adoption, retention and customer outcomes.

The most important difference is that product teams should validate their claims, not manufacture credibility. The objective is to help customers make an informed choice about a product that genuinely solves their problem.

5. How to Discover the Real Customer Job

JTBD is useful only when it changes what you investigate and what you decide to build.

Here is how I would apply it as a Product Manager.

STEP 01

Start With a Situation, Not a Solution

Suppose a clinic manager tells you: “We need an AI tool for patient follow-ups.”

Do not immediately add an AI feature to the roadmap.

First ask when the problem occurs, who experiences it, what triggers the need and what happens if the task is not completed.

The phrase “we need AI” is a proposed solution. It is not yet a clear statement of the problem.

STEP 02

Investigate What Customers Actually Do

Ask the customer to describe the last time they completed the task. If possible, observe the workflow.

Find out which systems they use, how information moves between them, where delays occur and which steps require manual work.

Actual behaviour often reveals problems that broad requests hide.

STEP 03

Understand the Trigger

Ask what made the customer look for a solution now.

Was there a missed follow-up? A new regulation? A larger workload? A new manager? A system that stopped meeting their needs?

The trigger can reveal when the job becomes urgent enough for the customer to change their behaviour or consider buying a product.

STEP 04

Understand the Alternatives

Customers already have ways to get their jobs done, even when those methods are inefficient.

Their alternatives might include spreadsheets, email, manual processes, another product or simply accepting that the problem will continue.

Your product competes with those alternatives, not just with products that look like yours.

STEP 05

Identify the Desired Progress

Ask what would be different if the task went well.

Would the customer save time? Make fewer errors? Feel more confident? Improve visibility? Reduce uncertainty?

Turn the answers into a clear desired outcome that can guide product decisions.

STEP 06

Look for Evidence Across Customers

One customer’s experience is a useful starting point, not proof that every customer shares the same job.

Compare interviews, observe workflows, examine support requests and review product analytics. Look for patterns, differences and contradictory evidence.

Questions I Would Ask in a JTBD Interview

  • “Tell me about the last time you had to do this.”
  • “What happened that made it necessary?”
  • “Can you walk me through how you handled it?”
  • “What was the most difficult part?”
  • “What did you try before your current solution?”
  • “Why did you decide to change your approach?”
  • “What happens if you do not complete this task?”
  • “What would a successful outcome look like?”
  • “What would make you reluctant to adopt a new solution?”
A question to avoid asking too early:

“Would you use an AI feature that automatically does this?”

This invites the customer to evaluate your idea instead of helping you understand their actual problem. Explore the current behaviour first; test the proposed solution later.

6. A Complete Case Study: Building a Healthcare Automation Product

Let’s walk through how a PM might take a vague request and turn it into a product opportunity.

The Initial Request

The sales team tells the product team:

“Customers want AI-powered patient follow-up automation. We should build it.”

This request may contain a genuine opportunity. But before committing engineering resources, I would investigate the underlying job.

Discovery: What Is Actually Happening?

I speak with practice managers, receptionists, administrators and clinicians. I ask them to walk me through their current follow-up process.

I discover that staff may need to:

  1. Identify which patients need follow-up.
  2. Check records and existing task lists.
  3. Decide who is responsible for each action.
  4. Contact patients using an appropriate process.
  5. Record the result and any next steps.
  6. Check which tasks remain outstanding.

The work is spread across several steps. Some information is recorded in different places, and staff must remember to return to outstanding tasks.

The initial request focused on sending messages. The broader workflow reveals a different opportunity.

Define the Job

Job statement

When patient follow-ups are due, clinic staff need to identify and coordinate the required actions so that important follow-ups happen reliably without excessive manual tracking.

This statement describes the situation, the person doing the work and the outcome they are trying to achieve. It does not prescribe a specific technical solution.

Separate the Job From the Pain Points

Observed pain Possible desired outcome
Staff repeatedly check lists. Spend less time manually identifying outstanding work.
Tasks are not always clearly assigned. Know who is responsible for the next action.
Managers lack a clear overview. See pending, completed and overdue tasks.
Follow-up information is spread across systems. Find the relevant information in the appropriate workflow.

These are hypotheses based on the discovery scenario. A real product team would validate how frequently each problem occurs, how serious it is and which customer segments experience it.

Explore Solutions Before Selecting Features

Once the job is understood, I would explore several ways to solve it.

Possible solution What it could improve What needs validation
A shared follow-up queue Visibility of outstanding work. Whether staff can maintain the queue reliably.
Automatic task creation Reduces manual task entry. Whether eligibility rules are accurate.
Reminders and escalation Helps staff notice outstanding tasks. Whether reminders are useful or create noise.
AI-assisted prioritisation Helps staff review work in a useful order. Whether recommendations are reliable, explainable and appropriate.
Automated patient communications May reduce repetitive administrative effort. Whether messages are appropriate, approved and safely delivered.

Define the MVP

The MVP should test whether solving the job creates meaningful value. It does not need to include every possible capability.

Depending on the research, a first version might:

  1. Identify eligible follow-up tasks using agreed rules.
  2. Create tasks for the appropriate staff members.
  3. Display pending and completed work.
  4. Allow staff to review and record actions.
  5. Keep an appropriate audit trail.

AI-generated communications or more advanced prioritisation could be explored later if the evidence shows they solve an important part of the job.

The product decision:

We are not building automation because AI is fashionable. We are testing whether reducing manual coordination helps clinic staff complete follow-ups more reliably.

7. How JTBD Helps You Prioritise the Roadmap

Imagine three customers ask for three different features:

  • Customer A wants a dashboard.
  • Customer B wants automated reminders.
  • Customer C wants AI-generated messages.

A feature-voting approach might rank these requests and start building whichever receives the most votes.

A JTBD approach investigates why each customer wants the feature.

Request Underlying job to investigate
Dashboard Understand which work requires attention.
Reminders Avoid forgetting important tasks.
AI-generated messages Reduce the time required to prepare appropriate communications.

These may be three distinct jobs, or they may be connected parts of a larger workflow. Research helps determine that.

The team can then compare opportunities using factors such as:

  • How important the job is to customers.
  • How frequently the situation occurs.
  • How poorly existing alternatives perform.
  • How many target customers experience the problem.
  • Potential business impact.
  • Implementation cost and risk.
  • Evidence that the proposed solution will help.

JTBD does not give you an automatic priority ranking. It improves the quality of the evidence you use to make the decision.

Use the Job to Write Better Product Requirements

A feature-led requirement might say:

“Build an AI-powered dashboard with automatic patient follow-up reminders.”

An outcome-led requirement starts with what the product must help the customer achieve:

Desired outcome

Clinic staff can identify follow-ups requiring attention, understand who is responsible for them and record completion without manually reconciling multiple task lists.

The team can then explore the interface, automation rules and technical implementation that best support this outcome.

8. How Do You Know Whether You Solved the Job?

Launching a feature is not proof that the customer’s job has been solved. A PM needs to measure what happens after release.

For the healthcare example, I would consider a set of connected metrics.

Question Possible measure What it tells us
Are customers adopting the feature? Eligible clinics activating the workflow. Whether customers start using it.
Are they receiving value? Eligible tasks completed through the workflow. Whether the workflow is being used to achieve the intended job.
Is the process improving? Staff time spent on manual tracking. Whether administrative effort is changing.
Is the workflow reliable? Missed, duplicated or incorrectly routed tasks. Whether automation introduces operational risks.
Does value continue? Repeat usage and customer retention. Whether customers continue finding the workflow useful.

The specific measures, baselines and targets should be agreed with customers and the business before launch.

In healthcare, operational metrics should also be interpreted alongside appropriate safety, privacy and clinical governance requirements. A higher automation rate is not automatically a better outcome if the process becomes less reliable.

What If Usage Is Low?

Suppose the feature launches and very few clinics use it.

A feature-focused team might add more capabilities.

A JTBD-oriented PM would investigate:

  • Is the underlying job important enough to justify changing behaviour?
  • Does the product fit the customer’s existing workflow?
  • Is setup too difficult?
  • Does the product actually save time?
  • Do customers trust the automation?
  • Is the product solving a problem customers already have another good way to handle?
  • Are we targeting the right customer segment?

If the job is important but the experience is poor, improve the product. If the job is less important than expected, revisit the opportunity. If the product is solving the wrong problem, return to discovery.

Measure whether the customer’s situation improved, not merely whether they clicked the feature you shipped.

9. The Ethical Lesson: Understanding People Is a Responsibility

There is another side to the Beech-Nut story.

Bernays’s campaign illustrates how trusted voices and public narratives can influence people’s decisions. It also illustrates the risk of presenting a commercial message in a way that makes it appear to be a stronger scientific conclusion than the underlying evidence supports.

For Product Managers, that is an important distinction.

Understanding customer psychology can help a team build a genuinely useful product. It can also be used to exploit fear, create artificial urgency or make unsupported claims.

We should not confuse the ability to influence behaviour with proof that a product benefits the customer.

How This Applies to Modern Products

Risky approach Responsible product approach
Use authority figures to imply benefits that have not been established. Make accurate claims and explain the evidence behind them.
Use fear to push people towards a purchase. Explain genuine risks and benefits without exaggeration.
Optimise clicks regardless of customer outcomes. Measure whether customers actually achieve their goals.
Hide limitations that might affect a buying decision. Be transparent about capabilities, limitations and trade-offs.
Make a product difficult to leave or cancel. Support informed choices and straightforward exit paths.

In other words, JTBD should help us understand customers so we can serve them better, not simply make them easier to persuade.

10. A Practical JTBD Checklist for Product Managers

Before committing to a new feature, I would ask:

  • What situation causes the customer to need help?
  • What job are they trying to accomplish?
  • What triggers the need to act?
  • How do they currently solve the problem?
  • What is frustrating or ineffective about that approach?
  • What alternatives are available to them?
  • What does a successful outcome look like?
  • How important and frequent is the job?
  • Which customers experience the problem most strongly?
  • What evidence supports our understanding?
  • What is the simplest solution worth testing?
  • How will we measure whether the customer’s situation improved?
  • Are our product claims accurate and our design choices responsible?

Final Thoughts: Don’t Start With the Bacon

Beech-Nut wanted to sell more bacon. Edward Bernays helped turn that commercial challenge into a broader campaign around the idea of a substantial breakfast.

The historical lesson is not that every product should imitate a clever marketing campaign. It is that customer behaviour is shaped by much more than a product’s features.

People make decisions in particular situations. They have habits, alternatives, concerns, expectations and outcomes they want to achieve.

A Product Manager who understands those factors has a better foundation for deciding what to build, how to position it and how to measure success.

The takeaway

Don’t begin by asking how to sell more of what you have built. Begin by understanding what customers are trying to accomplish, what gets in their way and whether your product genuinely helps them make progress.

That is the practical value of Jobs to Be Done.

Not a trick for persuading people to buy. A framework for discovering the problem worth solving before you invest in the solution.

Leave a Reply

Your email address will not be published. Required fields are marked *