"Make Your Beer Taste Better" Focus Filter
A decision filter for separating what actually differentiates your business from undifferentiated heavy lifting.
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 5
- Confidence
- 80%
This mental model, used by the Acquired hosts to explain the deeper motivation behind Amazon's internal API mandate, asks a simple question of any piece of work: does this make the beer taste better? If a task doesn't directly improve the customer experience, new features, satisfaction, or revenue, it's 'technical junk' — undifferentiated heavy lifting that should be standardized, automated, or outsourced rather than built and maintained by your core team. Applying this filter is what led Amazon to turn internal infrastructure into standardized APIs so engineers could spend their time on customer-facing innovation instead of coordination overhead. The same filter explains why founders shouldn't be doing their own bookkeeping or why companies should offload commoditized infrastructure to a cloud vendor.
Origin
Coined by the Acquired hosts while explaining why Jeff Bezos pushed Amazon toward service-oriented architecture — freeing engineers from infrastructure concerns to focus on the actual product.
Core principles
- 01Only work that visibly improves the customer experience deserves direct team focus
- 02Everything else is undifferentiated heavy lifting and should be standardized
- 03Standardization often takes the form of an API, vendor, or managed service
- 04Freed capacity should be explicitly redirected to customer-facing work
- 05This filter must be reapplied continuously as the business grows
How to run it
- 1
Identify What Actually Moves the Customer Experience
List the work that directly drives customer satisfaction, new features, or revenue — this is 'the beer.'
- 2
Label Everything Else as Undifferentiated Heavy Lifting
Categorize infrastructure, tooling, and process work that customers never see or care about as candidates for standardization.
- 3
Standardize or Outsource the Undifferentiated Work
Turn undifferentiated work into a documented API, internal service, or third-party vendor relationship rather than continuing to build and maintain it bespoke.
Pro tip This is exactly the mechanism that turned Amazon's internal infrastructure into AWS.
- 4
Redirect Freed Capacity to Customer-Facing Innovation
Explicitly reallocate the time saved toward building new features and improving the core product.
- 5
Re-Audit as the Business Grows
Periodically revisit the list, since what counted as differentiated work last year may become commoditized (and outsourceable) this year.
Watch out Failing to revisit this list means teams keep doing manual work long after a standardized solution exists.
In the wild
Before AWS-style infrastructure existed, development teams were estimated to spend roughly 70% of their time on infrastructure and setup and only 30% on actual software development; standardized cloud infrastructure flipped that ratio.
→ Engineers spent the majority of their time on customer-facing product work instead of undifferentiated infrastructure tasks.
A startup founder spending a Saturday reconciling QuickBooks instead of talking to customers is doing work that doesn't make the product better — a case for outsourcing finance operations to a specialized service instead.
→ Reclaiming that time for customer-facing work improves the actual business.
Common mistakes
Confusing Infrastructure Work With Differentiation
Teams often invest heavily in building custom infrastructure that customers never notice or value, mistaking technical sophistication for customer value.
Failing to Standardize Before Delegating
Handing off undocumented, ad hoc processes doesn't work — the work must first be turned into a clean, documented interface or service.
Not Revisiting the List as Priorities Shift
What was core differentiation a year ago may now be commoditized and available as a standardized service, but teams keep building it themselves out of habit.
Is it for you?
Best for
Leaders and teams trying to decide where to focus scarce engineering or operational resources.
Not ideal for
Situations where the 'undifferentiated' work is actually a core competitive advantage in disguise (e.g., a company whose infrastructure IS the product).
From the transcript
“this is the beginning of focus on what makes your beer taste better”
“none of that makes the beer taste better so let's standardize get rid of all communication api a size all of it”
From the episode
Amazon Web Services