Don’t surrender to the machine, says the man who built the iPod

This article summarizes an episode of Lenny’s Podcast’s video series featuring Tony Fadell, founder of Nest.

Tony Fadell, iPod inventor, iPhone co-inventor, Nest founder, Build Collective principal / Photo credit: Build Collective

Tech companies rely on data and team agreement to build products, but Tony Fadell, creator of the iPod, co-creator of the iPhone, Build Collective principal, and founder of Nest, which he sold to Google for US$3.2 billion, argues this approach stops invention.

With over 300 patents to his name, he argues that launching a business still demands human storytelling, strict review, and moral decisions.

Making things no one has made before

Tech teams often wait to release products until data guarantees success. That method fails when building something new. Relying on group agreement does not work when the market does not exist yet.

“When you’re doing anything that matters and it’s a 1.0 [version], and it’s a new category or a new device the world hasn’t seen before, you have very few analogies that you can use to make data-driven decisions,” Fadell argues.

Because most decisions for a first version rely on opinion, he insists a small group of people must make the final call. To make these choices and build a successful first version, leaders must follow these steps:

• Find the problem: Ask if people suffer enough to change their habits. Nest succeeded because old thermostats were confusing and cost homeowners money.
• Find new tools: Builders must use new technology to fix old problems. Multi-touch screens made the iPhone keyboard work, just as better batteries made the iPod possible.
• Build the whole system: A single product rarely wins. The iPod required iTunes and Windows support; Nest relied on easy retail sales, simple setup, and software that learned how to save money.
• Make educated guesses: Good choices come after building early versions, talking with the team, and asking experts. Blind guessing is dangerous, but leaders must look at the facts and take responsibility for the choice.
• Control the main details: Leaders must decide the parts that shape the customer experience, software design, costs, and future plans, trusting their teams to handle the rest.
• Plan for updates: Expecting immediate perfection leads to disappointment. Early mistakes just show where the team needs to learn more.

Wait for profits
Shipping the first version starts a long process of fixing the product and making money. “You make the product, you fix the product, then you fix the business,” Fadell says. Having never seen a team get everything right on launch day, he advises founders to focus on customer feedback before worrying about profit margins.

Selling the product to people

Engineers often love complex features, assuming buyers will appreciate the hard work behind the technology and this ruins sales. Treating marketing as part of the build process reveals whether the technology is actually useful to a normal buyer.

“When I do the press release, I can only have three or four key features,” Fadell says. “After that, it becomes gobbledygook for a customer.”

To clear the confusion and ensure customers grasp the product, teams must take these actions:

• Write the story early: Define the message before engineering teams bury the main point under extra features.
• Limit the promises: Highlight exactly three or four features. Making too many promises confuses people.
• Plan the whole process: Customer trust builds across the entire experience, from finding and buying the product to setting it up and using it daily.
• Talk to the right audience: Give early buyers one clear message, while providing regular buyers with proof that the product is safe and reliable.
• Adapt to different countries: Reusing old ads in new markets guarantees failure, much like when Apple struggled to sell the iPod in Europe using an American pitch.
• Make sure the product works: A great story cannot save a broken tool. The best marketing tells the truth and sets goals the software easily meets.

His thoughts on OpenAI serve as a warning. While new technology demos create short excitement, building a lasting company requires clear goals, reliable tools, defined customers, and simple language.

The hidden costs of automated code

Defending human choices in the age of computers