Discover how Tony Fadell, creator of the iPod and iPhone, builds world-changing products. Learn the role of taste, judgment, vision, and storytelling in crea...
How to Build Iconic Products in the AI Era: Lessons from the iPod and iPhone Creator
Key Insights
- Humans remain essential: AI is a powerful tool, but don't surrender your judgment to machines. The best products come from combining human creativity with technological capability.
- Opinion-based decisions drive innovation: When building truly new categories, data is unreliable. A strong leader with informed judgment must make the critical calls and articulate a clear vision.
- Marketing is product design: The customer only perceives your product through marketing and storytelling. Technology serves the customer, not the other way around.
- Three generations to success: Most products need three iterations: make the product, fix the product, then fix the business model. Expect failure along the way.
- Full-stack thinking wins: Revolutionary products require innovation across hardware, software, networks, and distribution. Partial solutions don't deliver lasting impact.
Building Products with Intention and Craft in an AI-Driven World
The rise of artificial intelligence has sparked an important conversation: Should we surrender to the machine or maintain human judgment in the creative process? According to Tony Fadell, the legendary designer behind the iPod, iPhone, and Nest Thermostat, the answer is unambiguous. We must keep humans in the loop.
"You still need humans in the loop. Don't surrender to the machine," Fadell emphasizes. The ease of AI-generated outputs—prompts that instantly produce results—creates a dangerous illusion of progress. When builders lean too heavily on AI without critical thinking, they're "building on a really crusty foundation" and accepting "short-term gain for very, very long-term loss." This warning resonates deeply in an age where rapid iteration sometimes masks poor decision-making.
The problem isn't technology itself—it's the mindset that surrounds it. When developers use AI to generate code without architectural oversight, or when product teams use AI to generate features without customer understanding, they accumulate technical debt that eventually becomes unsustainable. Fadell witnessed this firsthand when Anthropic's Claude source code leaked. Engineers reviewing the code were horrified. The AI had written functional code, but it was brittle, unreadable, and unmaintainable. The main loop wasn't properly segmented; it lacked the layered approach that experienced architects would design. "You're getting short-term gain for very, very long-term loss," Fadell says. This is called technical debt, and it haunts companies for years.
For product teams, the lesson is clear: AI can generate prototypes and help with limited-scope tasks, but it cannot replace the architecture, judgment, and intentional design that separates great products from disposable ones. As Fadell puts it, the difference between fast fashion and luxury goods applies to software too. "If you're going to build a real company, it can't be throwaway."
Starting with Pain: The Formula for Breakthrough Innovation
Great products don't begin with technology. They begin with a deeply understood problem. Fadell learned this principle early and has applied it throughout his career, from the iPod to Nest and beyond. When asked how he decides what's worth building, his answer is always the same: start with pain.
"I always start from pain," Fadell explains. "Are there new technologies to solve that pain? Bring innovation in, revolution in, then redefine the space." This framework has guided every major product he's created, and understanding it is crucial for any builder hoping to create something that matters.
The pain can be habituated—something people have grown so accustomed to that they no longer recognize it as a problem. Before Nest, people were uncomfortable in their homes or wasting money on heating and cooling systems that were nearly impossible to use. Thermostats required programming that felt like setting up a VCR. Utility companies offered rebates to use these devices efficiently, but the interfaces were so arcane that most people simply ignored them. This was the pain Fadell identified. "People either feel uncomfortable, or they're wasting money because the systems are inefficient and hard to use," he recalls.
The second element of the formula is identifying new technologies that have just become viable. For Nest, that technology was AI—not the large language models of today, but machine learning that could learn patterns and adapt to user behavior. Combined with better processors, improved sensors, and modern design, AI could learn a user's heating and cooling preferences automatically. The device could make a home more comfortable while saving money without requiring manual programming.
But here's where most builders make a critical mistake: they stop thinking about the product itself and ignore everything else needed to succeed. Fadell and the Nest team didn't just build a better thermostat. They rethought the entire customer journey. Traditionally, people bought thermostats through HVAC installers at low price points. Nest changed the distribution channel, the pricing strategy, the installation process, and the packaging. They created a premium product that cost five to six times more than traditional thermostats but promised to pay for itself within a year or two through energy savings. This wasn't just a product innovation—it was a system innovation.
This applies equally to the iPod and iPhone. The iPod wasn't simply a portable music player; it was the iPod plus iTunes plus the iTunes Music Store—a complete ecosystem. The iPhone wasn't just a smartphone; it was the iPhone plus the App Store plus the cellular network plus partnerships with carriers. Great products reshape entire systems around them.
Opinion-Based Leadership: Making Decisions When Data Fails
One of the most heated debates during iPhone development was whether to include a physical keyboard or rely on a virtual touchscreen keyboard. The BlackBerry's success seemed to argue for a physical keyboard. Many team members at Apple believed the iPhone needed one. This wasn't settled by surveys or user testing—it was settled by leadership conviction.
"It was the most heated conversation and it dragged out the longest," Fadell recalls. The tension came from two competing perspectives. One view held that Apple should pursue BlackBerry users by offering what they already loved. The other perspective asked: What about the 98 percent of mobile users who didn't have a BlackBerry? What would they want? What needs weren't being addressed?
Fadell had been working with virtual keyboards since his days at General Magic in the 1990s. He understood their limitations intimately. But he also believed that multi-touch technology could overcome those limitations in ways that previous touchscreen attempts could not. The team set out to test both approaches—a physical keyboard and a virtual keyboard with multi-touch. They measured typing speed and error rates. They iterated on the software and hardware, adjusting and refining. Over months, the virtual keyboard improved, slowly becoming "good enough"—not as fast as a physical keyboard, but fast enough to work.
The critical moment came when Steve Jobs made a decision: "We are going this way." Some agreed; many didn't. Jobs made it clear that if you weren't willing to get on board with his vision, you could work on a different project. This was a classic case of opinion-based leadership overriding conflicting viewpoints.
The data didn't definitively prove one option superior to the other. Both approaches had merits and drawbacks. This is the reality of innovation: when you're creating a new category—a device the world has never seen before—there are no reliable analogs for data-driven decisions. Real customer feedback only comes after people have spent their own money on the product and used it in their lives. Therefore, someone must make an opinion-based decision and commit to it.
This requires a "benevolent dictatorship" where the vision is set clearly, even if team members disagree. "A great product manager or a great person leading this thing has to understand that they have to make this decision, and we are going to select this, and yes, we might be wrong," Fadell explains. "We will correct it later, and we'll take the heat for that." This willingness to take responsibility for major decisions—and to course-correct if necessary—is what separates leaders who drive innovation from those who hide behind data.
For B2C products specifically, the entire ecosystem must be envisioned and built out completely so consumers can evaluate it in full context. This inherently involves taking risks. Most people in supporting functions are risk-averse. But leaders with informed instinct, deep domain knowledge, and clear articulation of their vision can align entire teams around these risky, opinion-based decisions.
Micromanaging the Details That Matter
The term "micromanagement" carries negative connotations. Leadership advice typically counsels against it. But Fadell argues that micromanaging certain details is absolutely essential for building great products. The key is understanding which details merit close attention and which can be delegated.
"There's only a few key things, mostly for the customer or maybe certain things from manufacturing or cost or something, where it really needs to be very clear or related to a long-term vision," Fadell explains. "But then you can delegate other things. Certain pieces of it, you really need to micromanage the decision, not necessarily the operations of doing it."
When Fadell says "micromanage the decision," he means ensuring you have the right data to make an informed judgment. With the iPhone keyboard, micromanagement meant continuously gathering data on typing speed and error rates, then using that data to inform the opinion-based decision. It meant orchestrating constant iteration between hardware and software teams, understanding how changes in one domain rippled through others.
The iPhone keyboard required alignment across multiple layers: hardware design, software algorithms, filtering logic, and graphics rendering. "You had all of these layers that had to constantly change and adjust," Fadell recalls. "Someone has to be the orchestrator of this huge orchestra of many different components to make it all come together and be harmonious." Without that orchestration—without that micromanagement at the decision level—the layers would have remained out of sync, and the product would have failed.
Micromanagement also becomes essential when system-level changes are required. If you need to fix something at the low level, but that fix requires corresponding changes at higher levels, and those higher-level changes have downstream implications, someone must coordinate all of it. "You have to micromanage because everybody wants to find excuses why they can't do that," Fadell says. When you micromanage the decision-making process, you're not dictating how each person does their job; you're ensuring that critical dependencies are understood and managed together.
The Complete Customer Journey: Why Builders Overlook Marketing
Too many product builders believe that building the best product guarantees success. They focus entirely on the product itself and treat marketing as an afterthought—something to hand off to the marketing department after engineering is done. This approach routinely fails, even with exceptional products.
The truth is that customers don't perceive your product directly. They perceive it through marketing, sales, distribution, and storytelling. Your product exists in their minds before they ever touch it. If the story you tell doesn't resonate, if it doesn't meet them where they are, they won't buy it no matter how good it is.
Fadell learned this by watching Steve Jobs, who understood that the customer experience begins with perception. Jobs didn't treat the iPhone launch as a one-time event. He spent two and a half years honing the story. He practiced his pitch repeatedly, refining it based on feedback from trusted friends, iterating until the narrative flowed effortlessly. When Jobs finally took the stage in 2007, it wasn't improvisation—it was the culmination of thousands of hours of preparation and refinement.
"The customer only sees what they see through the lens of marketing," Fadell emphasizes. "You have to put your product in their context and make the visuals and make the words and everything sing to them. If not, they're not going to get it." This isn't manipulation; it's respect. It's understanding that you share a responsibility to meet people with clarity and honesty about what you've built and why it matters to them.
Consider the famous tagline "A thousand songs in your pocket." This wasn't a technical description. It was a crystallization of the value proposition. It spoke to people who wanted music portability without needing to understand the underlying technology. The tagline told a story that made sense in the context of people's lives.
When Fadell's team wanted to expand the iPod to Windows users, Steve Jobs initially refused. His logic was that the iPod would help sell more Macs. But the team knew better. If the iPod remained Mac-only, it would only ever appeal to Mac loyalists—roughly 1 percent of the market. The other 99 percent would never experience it, and Apple needed mass-market success to survive. The argument was framed as a business math problem: "The iPod isn't a $349 product if you have to buy a Mac first. It's a $3,000 product. People won't risk $3,000 on a company that's almost bankrupt. But at $349, with Windows support, they'll try it."
Eventually, after extensive internal debate and some creative skunkworks efforts, Windows support came to the iPod. And what happened? The iPod became the mass-market phenomenon that saved Apple, and the brand loyalty built through the iPod experience made customers willing to try other Apple products, including the Mac itself. The better strategy wasn't "sell more Macs by making the iPod exclusive." It was "build trust and delight through an affordable, universal product, and customers will reward you with loyalty."
This same principle applies to messaging across different markets. When Apple tried to expand the iPod to Europe using the same marketing that worked in the US, sales flatlined. The problem wasn't the product; it was the messaging. European early adopters adopted technology differently than American consumers. They required different storytelling, different positioning, different context. Once the team adjusted the marketing to meet Europeans where they were, sales took off.
The Role of Storytelling in Product Design
Great storytelling isn't decoration. It's the fundamental way humans make sense of the world and commit to action. We remember stories better than facts. We're moved by narrative more than by specifications. "Stories are so fundamental to who we are," Fadell reflects. "We go to the movies for stories, we have books, all this stuff. It's just so essential to us because we like to be taken on a journey."
The best teachers don't just deliver information; they take students on a journey. A gifted math teacher doesn't just explain theorems—they explain why math matters, why it's beautiful, why understanding it opens the world. A compelling salesman doesn't just list features; they tell a story that shows why the product solves a problem you didn't know you had.
In product marketing, the difference between "what" and "why" is enormous. Technology-led marketing focuses on the "what"—the specifications, the features, the technical capabilities. But most people don't care about the "what." They care about the "why"—why this matters to them, how it improves their lives, what becomes possible because of it.
When marketing a thermostat, you could focus on "learning algorithm," "machine learning," and "adaptive heating." Or you could focus on the "why": comfort without effort, savings without sacrifice, a home that understands you. The second approach connects to people's actual lives and values. It's the difference between a feature and a benefit, between a specification sheet and a reason to care.
Fadell recalls observing how infomercials—despite their often over-the-top production—master certain psychological techniques. They identify a relatable pain point, often exaggerating it for effect. Someone struggles with a cheese grater; the product makes it effortless. The technique works because it creates what Fadell calls a "virus of doubt": the viewer recognizes themselves in the problem and suddenly wants the solution. While infomercials often overhype and underdeliver, the underlying principle is sound. When dialed back and grounded in truth, these techniques become powerful marketing.
The key is honesty. "The best marketing simply tells the truth, perhaps with some creative words, but always rooted in honesty," Fadell says. Steve Jobs modeled this throughout his career. He believed that if you're passionate about your product and you truly understand it, you can craft a compelling story that is also completely honest. The danger comes when you try to market something you don't believe in, or when you oversell something that underdelivers. That erodes trust.
The Three-Generation Rule: Why Great Products Take Time
One of the most underestimated truths about product development is that truly great products rarely succeed immediately. Instead, they follow a pattern: make the product, fix the product, fix the business. This typically takes three generations.
The iPod exemplifies this pattern. The first-generation iPod was only successful with Mac enthusiasts—less than 1 percent of the market. It would sell out in the first quarter, then sales would die. The second generation had similar results. It wasn't until the third generation, when the team added Windows connectivity and the iTunes Music Store fully launched, that the iPod became the mass-market phenomenon everyone remembers.
Many observers look back at the iPod's success and assume it was inevitable. In reality, it faced near-constant skepticism. After the first generation's lackluster performance, there were serious questions about whether to continue. Steve Jobs initially opposed Windows support. The business model required rethinking. But the team believed in the product's potential and persisted through the iterations.
"You got to fail a few times until you find your way," Fadell emphasizes. But notice the framing: it's not about individual failures; it's about iteration. As Jeff Bezos has said, "You only fail if you stop." If you keep iterating, keep learning, keep improving, then what looks like failure is actually learning. This distinction is critical for founders and builders who often face pressure to succeed immediately.
The three-generation pattern applied to the iPhone as well. The first iPhone had limited capabilities—it only worked in the US, operated on slow 2.5G networks, and lacked many features that competitors offered. Over multiple iterations, the product evolved, the business model matured, and the features solidified. By the third generation, the iPhone had found its form, the margins made sense, the volume was scaling, and the reliability was proven.
This pattern also applied to Nest. The Nest Thermostat went through multiple generations before the business model worked. The Nest Protect smoke detector—which Fadell describes as one of the most difficult products his team ever made—required years of iteration to achieve the quality and feature set it eventually delivered. That smoke detector even included a thoughtful detail that seems simple but required careful engineering: a voice alert warning you before the alarm sounded its loudest alert. "I'm about to make a loud noise," it would say. This prevented the panic and PTSD that come with smoke alarms—a small detail born from deep understanding of customer pain.
The implication for builders is clear: expect to iterate multiple times. Don't expect to get everything right the first time. Understand that the first version makes the product work, the second version fixes the product based on customer feedback, and the third version fixes the business model—pricing, margins, distribution, scaling. Only then do you have something that can truly succeed long-term.
Full-Stack Innovation: Why Hardware Plus Software Wins
Throughout his career, Fadell has consistently built products that integrate hardware and software, networks and distribution. This full-stack approach is often more expensive and takes longer to scale than software-only solutions. Yet it's this integration that creates defensibility, durability, and lasting impact.
The lesson applies across multiple generations. In the 1990s, when Fadell was pitching hardware ideas in Silicon Valley, everyone dismissed him. "Tony, you're crazy," they said. "It's all about the internet. We don't need any hardware." Then the iPod launched. Suddenly hardware was exciting again.
Years later, when software was ascendant and mobile platforms were all that mattered, the cycle reversed. "Okay, we don't need anything [hardware] because we can't get to the next level of software if we don't make the next level of hardware," Fadell realized. The revolution had to happen completely. You needed the mobile network infrastructure and the software that ran on it. You needed the MP3 player and the digital music format and the online music store. You needed all the pieces working together.
With AI, the same principle applies. You can't achieve breakthrough AI capabilities without the supporting infrastructure: data centers, edge computing, sensors, networks, devices. As Fadell observes, "We gotta have AI plus all the data centers and edge compute to make that work." This is why companies like Waymo—building an electric vehicle platform with thousands of sensors, running advanced AI—represent a different level of innovation than pure software plays. The hardware enables capabilities that software alone cannot achieve.
Today, venture capitalists are rediscovering this truth. After years of funding software-only companies, they're now prioritizing businesses with "atoms"—hardware, physical products, tangible innovation. Fadell finds this amusing: "I'm like, 'Duh!' Like, 'Where have you guys been?'" He's been pursuing full-stack approaches for decades, watching the cycles turn.
The advantage of full-stack businesses is staying power. Yes, they require more capital and take longer to scale. But they create moats that pure software struggles to defend. They enable features and capabilities that software alone cannot deliver. And they can be continuously improved as new hardware capabilities emerge. Consider Symbi Robotics, a company in Fadell's portfolio that uses AI for retail inventory management. It's not a pure software play; it's a robot with AI. It solves a real pain point for retailers and workers who hate doing inventory manually. The combination of the robotic platform and the AI software makes the product valuable in ways neither could achieve separately.
Ethics, Responsibility, and Long-Term Thinking in Product Design
As AI becomes more powerful and ubiquitous, the conversation about ethics and responsibility in product design becomes more urgent. Fadell believes this conversation must start with principles, not technology.
"You really need to be well-grounded and have real principles when you're designing something," he urges builders. This isn't about being preachy or self-righteous. It's about recognizing that products have consequences, intended and unintended. The iPhone, in many ways, has been transformative for humanity. It's also contributed to social media addiction, mental health challenges, and attention fragmentation. These consequences weren't intentional, but they're real.
Fadell points to Apple's privacy stance as an example of principled product design. The company has prioritized user privacy even when it meant being less competitive in certain areas or losing certain revenue opportunities. This wasn't a marketing stunt; it was a deliberate choice about what kind of company Apple wanted to be. And users have rewarded that choice with loyalty, even when the company was criticized for being behind in other areas.
The tension arises when companies try to maximize engagement or revenue in ways that contradict user wellbeing. Creating products designed to be addictive, optimizing for dopamine hits rather than genuine value, exploiting dark patterns—these practices extract short-term value at long-term cost. Fadell compares it to junk food: we have an obesity crisis because the food system is optimized for caloric density and taste, not health. We need nutrition labels, regulations, and tools to help people make better decisions. Similarly, we need digital nutrition labels, age restrictions, and tools to manage digital consumption.
"When you're really doing it and you can see that you're doing it, and you're trying to get people hooked or thinking, 'oh, I get more dopamine or what have you,' that's when you have to start really looking at things," Fadell says. He's not arguing for puritanism or judgment. He's arguing for responsibility and honesty about what you're building and what impact it has.
Interestingly, Fadell believes that principled product design often serves business better in the long run. "Users will feel that, and I think they will reward that, as we see with Apple with privacy." People want to use products they trust, products that respect them, products that genuinely serve their interests rather than exploit them. Building those products requires discipline, but it creates sustainable businesses.
One vivid example illustrates this: when the iTunes Video Store was being designed, someone suggested adding pornography to the catalog. The business case was straightforward—expanded content, increased engagement, more revenue. Steve Jobs shut it down immediately. "Is that the kind of world you want your kids to grow up in? And Apple is related with that?" he asked. It was a question about what kind of company Apple wanted to be, and the answer wasn't negotiable. "We need leaders like that," Fadell reflects, "leaders who are very clear as opposed to, 'I'm going to make a huge service for everyone.'"
AI as a Tool, Not a Replacement: Maintaining Human Judgment
The emergence of large language models and generative AI has created both opportunity and danger. The opportunity is obvious: these tools can accelerate certain tasks, generate prototypes, and expand what's possible. The danger is less obvious but equally important: the temptation to outsource judgment to machines.
Fadell's warning is clear: "Don't cognitively surrender." AI should amplify human capability, not replace human decision-making. This is particularly critical for product leaders. A product manager should use AI to generate ideas, explore scenarios, and prototype alternatives. But deciding which direction to pursue, which customer segments matter most, which trade-offs to make—these decisions require human judgment informed by deep domain knowledge and ethical principles.
The same applies to software architecture. AI can write functional code, but architecture—the structure that makes code maintainable, secure, scalable, and understandable—requires human expertise. Fadell emphasizes this: "There's software architects, and then there are software optimizers, and then there are just general coders, and then there are security reviews. If you don't have those different mixtures of experts around the code structuring it so that subsequent generations can get better and better, and it just kind of devolves into this mass of things you don't know, you're getting short-term gain for very, very long-term loss."
The principle extends to product design. AI can generate features, but it can't generate taste. It can create options, but it can't make the judgment calls about which options align with your vision and serve your customers best. Great products require what Fadell calls "luxury software"—the kind that's been thought through, crafted, and refined by humans who care deeply about quality.
This doesn't mean avoiding AI. It means using AI strategically: as a tool for exploration and iteration, particularly in the early stages of product development. Use AI to create prototypes that help you develop your informed gut, make opinion-based decisions, and architect the solution. Then, once the direction is clear and the architecture is sound, you can potentially use AI to help execute and optimize. But don't reverse the order. Don't let the ease of generation short-circuit the hard work of thinking.
The Future of Devices: Voice, Displays, and the Inversion of Interface Hierarchies
What's next for consumer devices in an AI era? Fadell offers a perspective grounded in decades of product development: displays and screens will remain essential, but the hierarchy of interaction methods will invert.
Today's interface hierarchy prioritizes tapping and swiping, followed by keyboard input, with voice as a distant third. This hierarchy made sense when touch was novel and voice recognition was unreliable. In an AI-enabled future, this order will reverse. Voice becomes primary, keyboards become secondary, and tapping/swiping becomes tertiary.
"The reason voice input hasn't fully taken off is because it was always an add-on, a 'gizmo' that 'sort of works,'" Fadell explains. Voice was bolted onto devices after the fact, lacking the intelligence and reliability to be a primary interface. But once voice becomes truly intelligent—understanding context, maintaining memory, acting on nuanced requests—it can become the default interaction method.
Yet displays won't disappear. Some tasks require visual information. Maps are easier to navigate with visual reference. Complex information is often better conveyed visually than through voice alone. Until brain-computer interfaces or retinal projection becomes commonplace, displays will remain necessary. But they might evolve—perhaps foldable forms, perhaps smaller and more compact. The key insight is that the device will still be a piece of glass you look at, just deployed more intelligently within a voice-first interaction model.
The Humane AI Pin attempted to replace the display with hand projection. But as Fadell points out: "It's just different, not better. You still need a screen or something to project on. So it is a screen at the end of the day." The movie "Her" nailed this—despite being set in a future with advanced AI, it still featured glass and visual displays for certain tasks. Technology often follows the form factors that genuinely serve human needs.
Building a Better Future: The Role of Taste, Judgment, and Care
Throughout his career, Fadell has been guided by a simple principle: great products matter. They improve lives, solve problems, and create possibilities that didn't exist before. But great products don't emerge from cutting corners, rushing launches, or outsourcing judgment to machines.
They emerge from teams that care deeply about craftsmanship. They emerge from leaders who understand that marketing and storytelling are essential, not afterthoughts. They emerge from individuals who have informed judgment, deep domain knowledge, and the courage to make opinion-based decisions when data is inconclusive. They emerge from organizations that are willing to iterate multiple times, persist through the three generations required for success, and think holistically about the entire customer journey and ecosystem.
Most importantly, they emerge from a commitment to building things that last, that serve genuine needs, and that reflect principles about the kind of world we want to create. "Don't chase the money for tearing apart the fabric of the society that we built," Fadell urges. Build products that respect users. Build products that you'd be proud for your children to grow up with. Build products that serve long-term human flourishing, not just short-term engagement metrics.
This is the challenge and the opportunity before product builders today. AI has made it easier to build things. That means the things that stand out will be the things that are genuinely well-thought through, carefully crafted, and grounded in human judgment and values. The competitive advantage now belongs to teams that understand their customers deeply, tell compelling stories, think systemically about entire ecosystems, and maintain the discipline to build products that matter.
Conclusion
Tony Fadell's journey from General Magic pioneer to iPod and iPhone creator to Nest founder to today's investor and mentor offers a masterclass in product thinking. The core lesson, repeated throughout his career, is simple but profound: great products emerge from understanding pain deeply, identifying enabling technologies, making informed opinion-based decisions, crafting compelling narratives, and maintaining the discipline to iterate until you get it right.
In an AI era where technology has become democratized and tools are abundantly available, the scarcest resource is human judgment—taste, vision, ethical clarity, and commitment to quality. These elements can't be AI-generated. They require the kind of deep thinking, customer empathy, and principled decision-making that separates transformative products from forgettable ones.
Start with pain. Find the enabling technology. Make the hard decisions. Tell the story honestly. Iterate through the three generations. Think systemically about your entire ecosystem. Use AI as a tool, but keep humans in the loop. And never surrender your judgment or your principles to the convenience of automation.
The products that will define the next era won't be the ones that are fastest to market or cheapest to build. They'll be the ones that are most carefully thought through, most generously designed for human flourishing, and most grounded in a clear vision of the better world the builder is trying to create. That's the challenge. That's also the opportunity. The next great products are waiting to be built by those willing to do the hard work.
Original source: Father of the iPod and iPhone on building taste, judgment, and creativity in the AI era
powered by osmu.app