Build

Build Plot Summary

Introduction

The garage was filled with squirrels. Not metaphorical ones—actual squirrels that would wander into meetings, causing momentary chaos before scurrying away. The ceiling leaked when it rained, forcing the team to strategically place buckets across the floor. The chairs were beaten-up relics from the '80s, with not a single one having all four legs touching the ground simultaneously. This wasn't some struggling startup on its last dime—this was the deliberate, chosen headquarters of Nest, a company that would eventually sell to Google for $3.2 billion. Tony Fadell, fresh from his success creating the iPod and iPhone at Apple, could have chosen gleaming offices with all the amenities Silicon Valley had to offer. Instead, he and his cofounder Matt Rogers deliberately chose this humble space to set the tone for their company culture. The message was clear: we're not here for comfort or status; we're here to build something revolutionary. This philosophy of substance over style would become a hallmark of Fadell's leadership approach, guiding him through the creation of products that would transform how we interact with technology and our homes. His journey reveals that innovation doesn't emerge from plush surroundings but from the right people with the right mindset, focused relentlessly on solving real human problems.

Chapter 1: From Failure to iPod: The Genesis of Innovation

The air was thick with anticipation as Tony Fadell walked into the meeting room at Apple in 2001. Just months earlier, his startup Fuse Systems had been on the brink of collapse when the dot-com bubble burst. After eighty failed venture capital pitches, he reluctantly took a consulting gig with Apple, hoping to make enough money to keep his employees paid. Now he was about to pitch Steve Jobs on a radical idea: a portable music player that could hold "1000 songs in your pocket." With a crude Styrofoam model in hand, Fadell made his case. The device would be simple, beautiful, and revolutionary. Jobs, known for his brutal honesty, was intrigued. Within days, Fadell became a full-time Apple employee. By October—just ten months after that initial meeting—the first iPod was born, transforming both Apple and the music industry forever. What's remarkable about this story isn't just the speed of execution but the journey that preceded it. Fadell had experienced a string of failures before the iPod's success. At General Magic, he watched a visionary product implode after four years of work. At Philips, he created award-winning handheld devices that retailers didn't know how to sell. His own startup Fuse was dying when Apple called. Each failure taught Fadell something crucial. General Magic showed him the danger of building technology without considering real customer problems. Philips taught him about retail challenges and sales channels. These weren't just setbacks—they were the building blocks of future success. The iPod had to ship by Christmas 2001. Not because Jobs set a crazy deadline, but because Fadell did. Having experienced project cancellations at Philips, he knew they needed to prove themselves quickly. With a tiny team pulling resources from Apple's core business, they faced internal resistance and external competition. The pressure was immense. This pattern would repeat throughout Fadell's career: learn from failure, apply those lessons to the next venture, and eventually transform an entire industry. His journey reveals that innovation isn't a straight line from idea to success, but rather a winding path of failures, lessons, and persistent vision. The most revolutionary products aren't created by those who avoid mistakes, but by those who embrace them as essential steps toward creating something truly meaningful.

Chapter 2: The Nest Revolution: Creating Products That Matter

When Fadell left Apple in 2010, he had no intention of starting another company. After a decade of relentless work developing the iPod and iPhone, he and his wife traveled the world, deliberately avoiding thoughts of business. Yet everywhere they went, one frustrating device followed them: the thermostat. Ugly, inefficient, and impossibly difficult to program, these devices controlled half of home energy bills but hadn't meaningfully evolved in decades. The idea began to chase him. For months, he researched the technology, the market opportunity, the competition. He sketched designs, built prototypes, and consulted experts. When his former Apple colleague Matt Rogers reached out, Fadell shared his vision for a learning thermostat that would save energy while looking beautiful on your wall. Rogers was immediately enthusiastic, providing the final push Fadell needed to commit. Together they formed Nest, pitching investors on a connected thermostat that would learn your preferences, allow smartphone control, and turn itself down when you weren't home. But their true vision was much larger—they were building a platform for the connected home, starting with just one perfect product. The Nest Learning Thermostat launched in October 2011 and sold out immediately. Two years later came the Nest Protect smoke and carbon monoxide alarm, addressing another universally frustrating home device. When developing the Nest thermostat, the team faced a crucial challenge: how would customers install this sophisticated device themselves? Traditional thermostats required professional installation, but Nest's direct-to-consumer model demanded simplicity. The solution came through relentless prototyping of the entire customer experience. The team created a complete installation kit, including a special screwdriver designed specifically for thermostat mounting screws. When they discovered that people couldn't hold the thermostat base against the wall while simultaneously marking screw holes, they built a level directly into the base and added a pencil holder. This approach reveals a fundamental truth about product development: great products don't just showcase interesting technology; they make the intangible tangible. They consider the entire customer journey from discovery to installation to daily use. At Nest, this meant everything from packaging design to including that special screwdriver that made installation easier. These details weren't afterthoughts—they were central to creating products that people would love and recommend to others, transforming unloved but essential objects into beautiful, thoughtful technology that people actually wanted.

Chapter 3: Leadership Under Fire: Managing Through Crisis

The lab test results hit Fadell like a punch to the gut. During routine testing of the Nest Protect smoke alarm, engineers discovered that a particularly tall, dancing flame could accidentally trigger the "Wave to Hush" feature—potentially silencing the alarm during an actual fire. This wasn't just a product issue; it was a potential safety hazard that could destroy the company's reputation and, worse, put customers at risk. Fadell immediately shifted into crisis mode. He cleared his calendar and assembled a team to parallel-path every possible solution: Was this a fluke? Could it be fixed with a software update? Or would they need to recall every single Nest Protect? The pressure was immense—not just to solve the technical problem but to maintain trust with customers who had invited Nest into their homes to protect their families. After thorough investigation, they determined the issue was extremely unlikely to occur in real-world conditions, but they couldn't take any chances. They pulled Nest Protect from store shelves, disabled the Wave to Hush feature via software update, and offered refunds to any customer who wanted one. Most importantly, they communicated transparently about what happened. "We'll get through this. We've done it before. Here's the plan," became Fadell's mantra during the crisis. He repeated it to his team, to investors, to himself. And they did get through it. The Nest Protect survived and eventually thrived, with the team implementing a more reliable way to silence false alarms in future versions. This experience illustrates a critical leadership lesson: crises are inevitable when you're building something new. What matters isn't avoiding them but how you respond. Fadell's approach—focusing on solutions rather than blame, getting deeply involved without micromanaging, seeking advice from mentors, communicating constantly, and taking responsibility—provides a playbook for navigating any business emergency. The most valuable outcome of a crisis isn't just survival but the story that emerges. After weathering the storm, Nest had a powerful narrative about overcoming adversity together—a story that became part of the company's DNA and prepared them for future challenges.

Chapter 4: Building Dream Teams: The Human Side of Innovation

"I remember walking into meetings and everyone rolling their eyes and sighing," Fadell recalls of his time leading product development. "I could see it on their faces: 'Oh fuck, here we go again.'" The team knew he was about to harp on that one thing everyone was sick of hearing about—that feature or detail that was already 90 percent great but that Fadell insisted could be better. In those moments, he wasn't trying to be liked; he was pushing for excellence. This tension between being respected and being liked defines one of the central challenges of leadership. When Steve Jobs insisted the first iPhone needed a glass front face instead of plastic—just five months before shipping—the entire team thought it was impossible. The schedule was already tight, the manufacturing challenges enormous. But Jobs pushed, knowing that plastic would scratch easily and diminish the experience. The team had to work nonstop, sacrificing time with their families and personal plans. They cursed Jobs under their breath, but they did it—and the result was revolutionary. Fadell distinguishes between different types of difficult leaders. There are "mission-driven assholes" who push relentlessly toward greatness, demanding excellence because they genuinely care about the product and customer. Then there are "controlling assholes" who micromanage out of insecurity, "political assholes" who manipulate others to advance themselves, and "aggressive assholes" who simply enjoy wielding power. Only the first type—the mission-driven leader—creates lasting value, even if they're occasionally resented in the moment. At Nest, Fadell implemented a hiring process called "Three Crowns" where candidates interviewed not just with their potential manager but also with managers of teams they would work with. This ensured new hires would collaborate effectively across the organization. He carefully integrated newcomers through "positive micromanagement"—giving detailed guidance during their first months rather than throwing them into the deep end. He hosted regular brown-bag lunches where employees could ask him anything, creating direct connections between leadership and staff. The human side of innovation is often overlooked, but Fadell understood that what you're building never matters as much as who you're building it with. He hired multigenerational teams, bringing together twenty-year-olds and seventy-year-olds to balance fresh perspectives with hard-earned wisdom. This approach to team-building reveals a profound truth: technology companies aren't really about technology. They're about people creating technology together. The most brilliant product vision means nothing without the right team to execute it, and the most talented individuals accomplish little without a culture that channels their efforts toward a common goal.

Chapter 5: The Customer Obsession: Why Product Stories Matter

"One thousand songs in your pocket." When Steve Jobs introduced the first iPod in 2001, this simple phrase captured the imagination of millions. It wasn't a technical specification or feature list—it was a story that instantly communicated why this new device mattered. Fadell watched Jobs refine this narrative for months before the launch, testing it on employees and friends, polishing it until it was irresistible. This lesson in storytelling stayed with Fadell throughout his career. At Nest, every product had a narrative that explained why it needed to exist and how it would solve real problems. The thermostat wasn't just a temperature controller; it was a learning device that saved energy while looking beautiful. The smoke alarm wasn't just a safety device; it was peace of mind that wouldn't annoy you with false alarms or mysterious chirping. These stories weren't just marketing tools—they drove product development. If a feature didn't support the core narrative, it was questioned or cut. When Nest created a demand-response program with energy companies, they faced the challenge of explaining a complex concept simply. After countless iterations, they settled on "Rush Hour Rewards"—an analogy everyone could understand. Just as traffic rush hours cause congestion, energy rush hours strain the grid. With three words, customers grasped the concept and their role in solving it. Fadell's approach to product storytelling extended to every touchpoint. At Nest, this meant creating detailed personas with names, faces, and life stories. When designing the thermostat's packaging, they constantly asked: "Would Beth from Pennsylvania pick this up? Would she understand it immediately?" This customer obsession extended to everything from advertising to installation to support. The most powerful aspect of great product stories is that they eventually stop being yours. When customers internalize your narrative and share it with others, that's when true success begins. As Fadell notes, "Someone else telling your story will always reach more people and do more to convince them to buy your product than any amount of talking you do about yourself." This reveals a fundamental truth about innovation: the "why" must come before the "what." Before you can build something meaningful, you need to understand why people will want it. This requires empathy—truly seeing the world through your customers' eyes and crafting stories that resonate with their deepest needs and desires.

Chapter 6: Scaling Without Breaking: Growth and Culture

"If you have a team of six, then six days of the year it's someone's birthday," Fadell observes. "So you get a cake, take the afternoon to celebrate. It's nice." But when your team grows to three hundred, there's a birthday practically every day. Should you still celebrate each one? Can you afford to have the whole team taking afternoons off constantly? And who's paying for all that cake? This seemingly trivial cake dilemma represents a profound truth about organizational growth: what works perfectly at one size becomes completely unworkable at another. Fadell identifies specific "breakpoints" where companies must fundamentally reinvent how they operate or risk collapse. These transitions—typically around 15-16 people, 40-50 people, 120-140 people, and 350-400 people—are where most organizations stumble. At Nest, the transition beyond 50 employees required creating a management layer for the first time. Some star individual contributors had to become managers—a role many initially resisted. "I'm an engineer, not a babysitter," was a common refrain. Fadell's approach was to offer these reluctant managers a trial run: "Let them try out the role and see how they feel. Go on vacation and hand over the reins. Tell everyone that this person is in charge." Some discovered leadership talents they never knew they had; others confirmed management wasn't for them and found different paths to grow. The most challenging breakpoint comes around 120 employees. At this size, communication breaks down catastrophically. The informal conversations that once kept everyone aligned no longer work. Information gets bottlenecked, teams develop their own subcultures, and the founding vision becomes diluted. Companies that don't prepare for this transition often experience mass departures and cultural collapse. At Nest, Fadell addressed this by codifying the company's values and processes, creating structured communication channels, and ensuring that new employees were properly integrated into the culture. Throughout this scaling process, Fadell maintained cultural touchpoints that connected everyone to the company's mission. The brown-bag lunches with the CEO continued. The focus on hiring remained the first agenda item in management meetings. The core values that defined Nest—customer obsession, mission focus, honest communication—were reinforced at every opportunity. This approach to scaling reveals a fundamental truth about organizational growth: culture isn't preserved by keeping things the same; it's preserved by evolving thoughtfully. The goal isn't to freeze the company at its "perfect" early stage but to carry forward what made that stage special while building structures that enable continued success.

Chapter 7: The Entrepreneurial Balance: Work, Life, and Legacy

On a crisp morning in 2015, Tony Fadell called an all-hands meeting at Nest. Hundreds of passionate, brilliant people who had built the company from nothing—from a sketch, from a leaky garage with a squirrel problem—sat watching him in anticipation. He looked at them, teared up, and told them he was done. After Google's decision to sell Nest (a decision they would later reverse), Fadell had made the painful choice to walk away from the company he had founded. This moment illustrates one of leadership's hardest truths: knowing when to push forward and when to let go. Throughout his career, Fadell had been the one pushing—for better products, higher standards, greater innovation. But sometimes the wisest move is stepping aside. "A CEO is not a king or queen," he reflects. "It's not a lifetime appointment. At some point, you have to step down." Leaving feels like death. "When you're a founder, leaving your company can feel like a limb hacked off," Fadell writes. "A friend you've loved dearly and grown up with, gone forever." The emptiness that follows can be overwhelming—days and nights that were once consumed by work suddenly stretch out, formless and quiet. Many leaders immediately jump into new roles to distract themselves, but Fadell advises against this: "Resist the urge to worry that your market value is declining every day you're not working. This feeling is usually driven by self-doubt, not the reality of the job market." Instead, he suggests embracing the grief process. It typically takes about eighteen months to fully process the experience—six months to get over the initial shock and work through the list of things you've been neglecting, another six months to start reengaging with the world, and a final six months to look at life with fresh eyes and consider what's next. "There's a half-life to everything," he observes. This intense work schedule left little room for traditional work-life balance. Like many entrepreneurs, Fadell found himself thinking about work constantly, even during rare vacations. But he learned to create what he calls "personal balance when you're working"—designing his schedule to include moments of respite for his brain and body. His advice is practical: block time for thinking and reflection 2-3 times weekly; exercise 4-6 times weekly; eat well; and engineer your calendar to include breaks. This wisdom extends beyond CEOs to anyone facing major transitions. Whether leaving a job, ending a relationship, or closing a chapter of life, the process requires patience and self-compassion. The entrepreneurial journey is inherently unbalanced, but finding sustainable imbalance is the key to lasting impact.

Summary

Throughout his remarkable journey from programming Apple computers in his childhood bedroom to creating revolutionary products that changed how we interact with technology, Tony Fadell has distilled wisdom that transcends the tech industry. His experiences reveal that building anything meaningful—whether a product, a team, or a company—requires both unwavering vision and unflinching honesty about what's working and what isn't. The greatest innovations emerge not from comfortable environments with abundant resources, but from constraints that force creative problem-solving and relentless focus on what truly matters. Perhaps Fadell's most powerful insight is that the things we build are ultimately reflections of the relationships we forge. The iPod, iPhone, and Nest thermostat weren't just clever assemblies of components; they were manifestations of teams pushing each other toward excellence, of leaders caring deeply about details others might overlook, of cultures that valued substance over style. Even after leaving Nest, Fadell found his greatest satisfaction came not from the products themselves but from helping the people who created them discover capabilities they never knew they possessed. In this light, the ultimate measure of success isn't market share or acquisition price, but how many people discover their potential through the journey of building something extraordinary together.

About Author

Loading...

Tony Fadell

Anthony Michael Fadell is an American engineer, designer, entrepreneur, and investor. He was senior vice president of the iPod division at Apple Inc. and founder and former CEO of Nest Labs.

Read more