ExpertsFM#421 Jony Ive
Founders · June 10, 2026
5 Selected Lessons:
heuristic · 2 reasoning_pattern · 1 case · 1 framework · 1
Design-to-manufacture collaboration via 'ideal product first' framing with suppliers
Source
Founders — #421 Jony Ive (June 10, 2026) · at 44:57 ▸ · at 47:15 ▸
When this applies
when working with vendors/suppliers/engineers to make a hard-to-produce idea real
The takeaway
Define the ideal end state without accepting early 'it's impossible' pushback, and work backward from that ideal with the people who will build it, spending the bulk of effort on implementation, not ideation.
Why it works
Framing the ideal outcome first, and removing cost as an initial constraint ('bucket of money'), pushes suppliers to find a path to the ideal rather than negotiating down to what's convenient for them.
One level up
The ratio of time spent conceiving versus implementing an idea should heavily favor implementation once the idea is set.
Where it stops holding
This stops working when the cost or physical constraints are truly fixed (not negotiable even with unlimited budget), making 'ideal first' framing unproductive.
Detail
procedure:
- Spend minority of time (10%) on ideation/sketching/models.
- Spend majority of time (90%) working directly with manufacturing to implement.
- Present suppliers with the ideal product and tell them not to say it's impossible.
- Offer effectively unlimited resourcing framing ('bucket of money') to push for the ideal solution rather than a compromised one.
benchmarks: {"time_split":"10% ideation / 90% implementation with manufacturing"}
rationale: Removing financial/possibility objections upfront lets suppliers focus on how, not whether.
In their words
Imagine I have a bucket of money in my hand. I will let you pull out as much as you want to make this happen.
Design-story-first approach
Source
When this applies
when starting any product, feature, or offering design
The takeaway
Before specifying features, define the story/metaphor that makes the thing relatable to the user's everyday life.
Why it works
Starting from the narrative of how a person will relate to and use the thing surfaces the right metaphor and emotional frame, which then drives concrete design choices (like the lid, the handle).
One level up
Meaning and perception precede mechanism; define what something should feel like before deciding what it should be made of.
Where it stops holding
This stops working when the product category has no natural human metaphor or when speed-to-market precludes this kind of narrative exploration.
Detail
approach: Ask 'what is the story of this product' instead of accepting a generic category label (e.g., 'PDA').
signals:
- product doesn't relate to people's everyday lives
- no metaphor users can grasp
- first interaction (lid, handle) treated as throwaway rather than special
rationale: A relatable story turns a technical object into something humans want to touch and understand.
In their words
The problem with the first Newton was that it didn't relate to people's everyday lives, Johnny said. It didn't offer a metaphor that users could grasp.
Reduce to essentials, repeatedly
Source
When this applies
when building anything with parts, steps, or features — a product, a process, a pitch
The takeaway
Continually ask whether each component is truly necessary, and whether one element can do the job of several, before adding anything new.
Why it works
Removing non-essential parts forces each remaining part to justify its existence, which simultaneously improves usability and manufacturability.
One level up
Default design behavior is additive; deliberate, repeated subtraction is what creates differentiated simplicity.
Where it stops holding
This stops working when complexity is genuinely required for function and removing parts degrades core performance or safety.
Detail
rule: Go back to the beginning again and again, asking 'do we need this part' and 'can one part perform the function of several.'
threshold: Reduce until only what is absolutely essential remains — repeated iteration, not a single pass.
rationale: Invisible effort in reduction makes the product easier to build and easier for people to use.
In their words
We wanted to get rid of anything other than what was absolutely essential, but you don't see that effort. We kept going back to the beginning again and again and again.
Don't make focus-grouped / Me-Too products
Source
When this applies
when deciding whether to copy a popular but cheap/compromised competitor offering versus building something categorically better
The takeaway
Ask 'what should this be' from a designer's/expert's forward-looking view rather than asking current customers to validate something outside their frame of reference.
Why it works
Customers can only react to what already exists; asking them to evaluate something genuinely novel from today's frame of reference undervalues future possibilities, so relying on focus groups biases you toward incremental, derivative products.
One level up
Breakthrough products require someone to hold a vision that the market cannot yet articulate for itself.
Where it stops holding
This stops working when the market truly understands its needs better than the maker (e.g., mature categories with well-informed professional buyers), where ignoring feedback risks real misses.
Detail
rule: We don't do focus groups because that is the job of the designer.
threshold: iPad outsold the entire netbook category by 2011 (63M vs 30M units) despite entering after the category existed.
rationale: It is unfair to ask people who don't have a sense of the opportunities of tomorrow from the context of today to design.
In their words
We don't do focus groups because that is the job of the designer. It is unfair to ask people who don't have a sense of the opportunities of tomorrow from the context of today to design.
Apple's consensus-by-committee culture before Jobs' return
Source
Founders — #421 Jony Ive (June 10, 2026) · at 20:12 ▸ · at 23:06 ▸
When this applies
when an organization requires cross-functional consensus (marketing, engineering, UX documents, executive committees) before any product decision
The takeaway
Decision-by-committee systematically produces middle-of-the-road output and erodes the best people's motivation to stay.
Why it works
Requiring consensus across many stakeholders averages out strong points of view, producing safe, generic products and driving away ambitious talent who feel they're wasting time.
One level up
Speed and ownership concentrated in a single accountable point of view is what produces 'spark of genius'; distributing ownership to avoid risk guarantees mediocrity.
Where it stops holding
This stops working as a lesson when products genuinely require multi-stakeholder tradeoffs that no single person can safely own (e.g., regulated safety-critical systems).
Detail
situation: Apple required three documents and multi-committee sign-off for every new product, taking years, after rejecting Jobs' earlier 'tyrannical' single-owner approach.
decision: Brunner spent most of his time in unnecessary management meetings and eventually left out of frustration.
outcome: Four years elapsed between a design brief and a shipped product; Apple drifted and nearly lost key design talent.
lesson: The businessman wants to create something for everyone, which leads to products that are middle of the road — consensus kills the spark of genius.
In their words
The businessman wants create something for everyone, which leads to products that are middle of the road. It becomes about consensus, and that's why you rarely see the spark of genius.