CEOInterviews.AI
Start App
Get an email when Tony Fadell gives a new interview
One email per new interview. Unsubscribe in one click.
Tony Fadell
Principal; Founder of Nest, Build Collective

E14 fireside chat with Tony Fadell and Habib Haddad,

📅 Feb 13, 2026 E14 Fund 75 MIN 160 VIEWS 198 SEGMENTS · 2 SPEAKERS
Tony Fadell and Habib Haddad.

Questions asked in this interview

12
  1. 4:12Well, you know, at General Magic, one of the things I think about, you know, what Mike Tyson says is, you have a plan until you get punched in the face, right? Everyone got that?
  2. 16:03So is that maybe something on intuition? That's something you can learn?
  3. 27:37Was that a friction for scale?
  4. 31:26How did you go about shooting off or saying no to things?
  5. 32:50What made him a great co-founder for Nest?
  6. 35:24Would you agree or — at least early on?
  7. 45:32But do you think that's going to mess up a little bit kind of the game?
  8. 47:33So we've been seeing, you know, that's a thing, right?
  9. 54:12And on the opposing side as an investor, what is something that you look for when you judge, when evaluating teams and their ideas?
  10. 58:45Can you talk about how you design for genuine human connection and if there's a way to even substitute or supplement kind of what you mentioned of what we have here of who you know?
  11. 1:03:17what are your thoughts on the future of the user interface?
  12. 1:09:55I'm wondering what would your advice be for, or what would you do if you were an MIT student today?
Interviewer 0:00 ↗
Thank you. Thank you. Hi everybody. Well, thank you, Tony, for coming on such a cold week.
Tony Fadell 0:07 ↗
Yeah, I'm trying to warm up. Seriously, man, you guys rolled out the white carpet. Thanks.
Interviewer 0:14 ↗
So, actually, just today I realized something funny. Besides, you know, what Kev and I share with you, besides being in the same industry and having the same hairstyle, is that you have roots in Michigan, where he grew up, and in Lebanon, where I'm originally from.
Tony Fadell 0:32 ↗
Exactly.
Interviewer 0:32 ↗
So you bring us back maybe to your upbringing. I know you attribute a lot of your builder capabilities and skills to your father, but there's probably a lot of things that happened in your childhood that made you the inventor and builder and founder that we know today.
Tony Fadell 0:47 ↗
Well, a bunch. Yes, my grandfather, you know, he put tools in my hand at four — drills and, you know, electricity and all those things that drive my grandmother and my mom crazy. But that's how I first got, you know, hands-on with things and built, just like you guys are all building here. And probably a lot of you, you know, did the same thing when you were younger. But really for me, what happened was there was two things. One is we were moving all the time. So I moved — I went to 12 schools in 15 years until I ended up at the University of Michigan where I stayed. And through all that moving, the only thing that could come with me were the tools, more or less, because you didn't have the internet, you didn't have any of that stuff. So I would bring my tools first and build stuff, but then it became my Apple II, and then that was the next tool. And through that I had a 300 baud modem and, you know, BBSs and all that stuff to stay connected with the other geeks that I just left at wherever I was. And so through that, that was kind of my way of dealing with moving so often — was that this was my own world that I could create and work with and build. And that was how it all started. And then there were more people like me, you know, that was Revenge of the Nerds days where all the tech geeks were not cool. And, you know, we would just hang out and we started a company in Detroit in 11th grade and then sold that later, and then I started two at University of Michigan and sold one of those, and then ended up in Silicon Valley.
Interviewer 2:24 ↗
I guess also you mentioned tools, but also prior to tools there's culture and mindset. Just the idea of building is probably even more ingrained in you than just the tools. The tools were basically something you took with you.
Tony Fadell 2:38 ↗
Yeah, it was literally — my grandfather told me, he said, 'You see this entire world out there? This was all created by humans just like you. And if they can do it, you can do it too.' So just, you know, use your skills, use your talents, learn, be open, and just start building stuff. And that's really what it was. And so I didn't know anything else from a kid. I was just like, you build, build. And all these other people were like, 'What are you doing? Build, build,' you know, and it was just so much fun. And I do it even to this day, you know, and I can't get enough of it. It's, you know, it's a fun disease to have.
Interviewer 3:13 ↗
Speaking of teaching kids, shout out to Mitch Resnik up there from the Lifelong Kindergarten and inventor of Scratch, which if you think about it, Scratch is kind of like the godfather of vibe coding in a way. Maybe he won't like it or won't like it, but thank you. Thank you, Mitch. Thank you, Mitch. Thanks for being here.
One thing I heard on a podcast which made me laugh — not because you did it, but because I did the same thing. When I first interviewed for my first job at a founding engine company, I also showed up in a suit, and I heard that you did the same thing at General Magic.
Tony Fadell 3:44 ↗
Absolutely. And there are two people in the audience who were there at General Magic when I went and interviewed. I had a jacket and a tie, straight out of the Midwest, and they sat me down in front of the arcade game — you know, the stand-up arcade game in Silicon Valley — and put me on the floor, took off my tie, took off my jacket, and said, 'Okay, now the interview can begin.' I was like, 'Whoa, I'm not in Kansas anymore.' You know.
Interviewer 4:12 ↗
That's awesome. Well, you know, at General Magic, one of the things I think about, you know, what Mike Tyson says is, you have a plan until you get punched in the face, right? Everyone got that? I think that was kind of your first punch after you took the suit off.
Tony Fadell 4:27 ↗
That was my first big punch on a major, major scale. I had other ones, like I did this processor for the Apple II. So a friend and I reverse engineered the Apple II 6502 and created a 65816 processor over a summer and sold it to Apple. And what happened was we only sold, you know, like 20 parts because I didn't understand that, like, there are markets and the Apple II is dying and you need to have customers. So I got punched in the face there after working really, really hard because I was like, I make this really cool thing and it works really well. Oh, there's nobody who wants to buy it. I'm like, duh. Okay, let you know, each stage of my career, we're always getting punched in the face to learn, to then, you know, to put that in, to finally after probably, I'd say, 15 years of trial and error, to finally have my first real success.
Interviewer 5:20 ↗
Maybe from General Magic, then what are some of the learnings that you think are applicable still today?
Tony Fadell 5:25 ↗
Oh, it's all there. Well, first of all, it's in my book, Build, so I put a lot of it in.
Interviewer 5:31 ↗
This is awesome. By the way, if you have copies, can we get us — yeah, we have copies. At least we can get you all hooked up with copies.
Tony Fadell 5:37 ↗
Yeah. But the first thing is you got to really understand the problem you're solving, right? And the why. Why problem are you really solving? Why does it matter? And a lot of times when you grow through the engineering disciplines, you start seeing things and you go, 'Oh, look at that cool thing. Look at that thing.' And you put it together and you go, 'Isn't that cool?' And it's all about the what, but it's not a lot about the why. And I had the same problem. You know, coming through school, I would just put all these basic weird Lego blocks together and go, 'Isn't that cool?' And people go, 'Oh, yeah, I guess so.' But then they didn't resonate. But, you know, when there was another engineer next to me, they'd go, 'Oh yeah, that's cool.' And so, at General Magic, what we were doing was we had this huge sandbox. We had the creators of the Macintosh with us. And we had too much money, kind of like a lot of AI companies today. And we were creating this thing that we just thought was really cool, but we didn't know why we were creating it. And it turned out to be the iPhone 15 years too early. That's what we were creating, but we didn't know it. We were just doing stuff that was cool. But whenever we showed anyone, they were like, 'Yeah, but why do I need it? What are you solving for me?' And the pains that we were solving at General Magic was we were doing email, and almost nobody had email in 1991, '92, unless you were a really big corporation, and even then it was email inside a corporation for the most part. We were solving downloadable games. We were solving e-travel so you could book travel. This was in '91, '92, '93, before the internet. We were doing emojis. We were doing just incredible things that the world — and it was in a portable form factor, and there was no even Wi-Fi. There was no digital or any kind of data networks. There were none of these things. We were building all this stuff and it was like, this is really cool, and nobody — literally we sold a couple thousand of them to the friends who were geeks with us in Silicon Valley, and that was all that bought it. We spent 400 to 500 million dollars in 1992, '93, and it was a huge disaster, and it was because we were making stuff that was great for other geeks, and that was it. And that's when you get punched in the face, and I was like, what are we doing? We spent day and night for four years building this thing, and the whole world said it was going to be the biggest thing. The press said we were going to kill Microsoft, and it just tanked, and then the internet took over, you know, just literally a year later. So the big thing there was we had incredible ideas, but we didn't know why we were building it. We didn't know who we were building it for. We didn't even have the technology ready yet to be able to realize the dreams we had for problems we didn't even have yet. And so then fast forward to, you know, 2007 with the iPhone. You know, people had communications in the phone, they were texting, they were doing internet communications, they were doing productivity tools, they were doing iPod with music and video and photos. And we were like, let's put it all together. And by the way, there was Wi-Fi and 2.5G. And it all came together. And then it made sense, right? But only till society was ready to see the problems, have the problems, or at least some subset of society, to then be able to bring it to them.
Interviewer 9:10 ↗
One of the things I used to say with one of my friends, who was a founder and obsessed product person, is you have to ask yourself always two questions, and when you have answers to these two questions, then you have a good product: 'I'm confused' and 'I don't care.' Keep saying 'I'm confused' and 'I don't care,' and once that doesn't exist, then you have a good product.
Going back to the iPod, and you've also talked about that in your book, there's the vision and details, and there's also maybe in between an intuition. You know, how to think about the balance between your intuition, your vision — 'I believe in this thing and I don't care that they don't care, but I know it's going to get there' — but also 'I'm going to execute on this,' because ultimately if you didn't really believe your intuition and your vision, we wouldn't have had the iPod.
Tony Fadell 9:59 ↗
Well, you know, the iPod — there were MP3 players at the time, and obviously there were Walkmans that came before it. And so for me, when the iPod — when I did the first prototype of the iPod to give to Steve Jobs to put in his hand as a contractor, I had already been working on MP3 players for like two to three years. And I tried to get Swatch to actually build it. I tried to get Palm to actually build it back in the Palm Pilot days. I tried many different companies when I had MP3 players to get them to do it, and they didn't see it, right. So I had already believed in it because I was doing small handhelds after General Magic, small handhelds, and we were the first company to do audible audiobooks in a portable form, and I was a DJ at the time.
Interviewer 10:45 ↗
What was that? What year?
Tony Fadell 10:46 ↗
That was '96 or '97. '96 or '97 we were doing that.
Interviewer 10:52 ↗
Who was born then?
Tony Fadell 10:53 ↗
Yeah. Who was born? Yeah. We'll raise your hand.
And so we were doing the very first digital audiobooks, and I was carrying around all these CDs for these DJ gigs because vinyl was out. Vinyl was dead — not like it is today. And so I'm carrying all these, and I'm like, there's got to be a better way. And I've been working on handhelds for a decade almost at that point. And I was like, what if we could put all of it in a device like that? And so I was doing that for about three, four years. And I was fully a believer. I made a startup around it. I made a startup around it, and Apple found out about me, and it turned into the iPod. But it was just having that conviction the whole way through. You know, General Magic was a disaster. But it was all about digital handheld devices. I was building digital handheld devices at the University of Michigan. Then I went to Philips and started a whole division of Philips called Philips Mobile Computing Group where we did Windows CE handheld devices, and one of them was the one that was playing audiobooks. And during that time the internet happened, and everybody turned to me and said, 'Tony, what are you doing with these stupid hardware things? It's all about the internet. Don't bother with that. You're not going to get any money for it. Nobody wants hardware. It's too hard. Blah blah blah.' And I was like, 'No, I'm just going to keep my head down building this thing.' And then I went off to do my own startup, Fuse, in '98, and doing handheld stuff as well. And everyone's like, 'You're crazy.' I couldn't get any money. I got a little bit of money, and then the bubble burst of the internet in 2000, and there was no more money, and I had to — I scrambled and scrambled and scrambled, and I got a call from Apple, and they said, 'Would you like to come and consult?' And they told me it was — we have iTunes, and would you like to bring all of this — would you like to bring all the iTunes music in a portable form? What would you do taking all the things that I already worked on? So I didn't give up. It was just persistence, persistence, persistence. But all the time, like General Magic was learning about the target customer, and Philips was learning about sales and marketing, and so each of these things — and then it was learning about funding. So each time we failed, I learned, and then I made sure I applied that, and then the iPod happened.
Interviewer 13:15 ↗
But even the iPod — people romanticize that story. Even that story isn't a very sexy story. I mean, it was a few quarters away from Apple going broke, and I'm sure internally people — not everyone loved the product that you were working on or thought that they would.
Tony Fadell 13:29 ↗
There were people who just actually retired from Apple just a couple of months ago who did not want the iPod to even come into play. There was literally a whole set of people saying we have 1% market share in the US and Japan. That was it. Just for computers, two computer models. They had $250 million in the bank and $500 million in debt. There was no retail. Michael Dell said, 'Let's shut down Apple and give all the money back to the shareholders.' Like, it was a disaster company. And this was after Steve came back, and it was going to be the rise of Apple again, and it fell on its face. So I had had 10 years of failure. And so for me to go — Steve goes, 'Okay, now we're going to do this iPod thing.' And Sony's number one in the market. You know, he's like, 'Now you're going to join us.' And I'm like, why do I want to join Apple? Like, you got to convince me. Like, now it's like, of course, duh. But then it was literally on its last legs.
Interviewer 14:26 ↗
But and then also like in the iPod story, there's also building under constraints and politics and all of that.
Tony Fadell 14:36 ↗
Sure. Well, so we had a whole faction of people who didn't want to do the iPod at Apple. Okay. But there was Steve, and Steve wanted it to happen, and he literally said, 'If anyone gets in your way, call me.' And so a few people got in the way. I told Steve, and Steve — you know, I would call in the air strike from above, you know, Steve would go boom, boom. And it happened two or three times, and everybody got the message because Apple was 3,500 people, maybe 4,000 people at a time. The message spread quickly: if this guy's calling, just give him what he wants and don't give him any grief, because Steve's going to literally go after you. And so we had this air cover, and this is what you have to do when you have a small team in a large company — even then it was a large company — is that you have to treat it like a baby. It can't be treated like another project. It's a baby, and you have to feed it, and you have to care for it, and watch over it, and he did that for us. So he cleared the path while we just ran night and day and shipped the iPod 10 months later.
Interviewer 15:44 ↗
So I get like being stubborn actually, you know, you've been stubborn for seems like a few decades before the iPod, you know, just going at it, going at it, but learning and learning and not making the same mistakes.
Tony Fadell 15:52 ↗
Yeah. Yeah. It was heads down. I just believe in this. I believe in this, and while the whole world was saying go somewhere, I just kept going because I knew that this was an eventuality.
Interviewer 16:03 ↗
Talk about taste in your book. So is that maybe something on intuition? That's something you can learn?
Tony Fadell 16:08 ↗
Well, you need to have taste. Yeah, absolutely. You know, yeah, I learned it, but it's by discerning. It's, you know, you have taste when you design something from the guts, maybe when you're doing software or something. We know when an architecture is beautiful — a software architecture, a hardware architecture, all these kinds of things. But you also have to look at beauty from a customer journey, beauty from the branding, beauty from the ID perspective, all these different user interface. So there is this sense of taste, and what happens is in this day and age a lot of times people just want to keep revving things and getting data, and the data will inform you of what way to go, and that's not the right way to do a 1.0 of anything. A 2.0, a 3.0, yeah, a little bit of data-driven decision making is good, but most of the stuff in a 1.0 is opinion, especially the ones that count for the customer differentiation, is opinion-based decisions. And most people treat opinion-based decisions as data-driven decisions. So if you go into large companies or even small companies, and especially with investors and everything, 'show me the data why this is the right direction,' and you're like, no, this is just a taste decision. This is a vision decision. It's these kinds of things. And you have to have real strong reasons why the vision is the way it is and why it's not this and not that, but you'll never have the data. And now we have a whole set of companies around the world who just take your vision and they put data around it and they charge you $2 or $3 million. Those are consultancies, and they go, 'Okay, we have this idea,' and you go and pay them $2 million, and they come back with a whole stack of data: this is why it's successful. So you can give it to your board, you can give it to your investors, you can give it around and say, 'See, they say it's going to be successful,' and then you get the money and whatever else. And also when it fails, because they don't know any better, you can point to them and go, 'They got it wrong. I was just following their advice.' So you have to really understand the difference between data and opinion-based decisions, especially with the 1.0, and it does require vision, taste, and a lot of fuzziness, and it's not just engineering-driven, data-driven decisions.
Interviewer 18:23 ↗
So it's opinions or opinion-based because you seem like you have to take — you have to put yourself in —
Tony Fadell 18:28 ↗
You can't have consensus. You have to have one, two, maybe three people total who really come together with that vision and say this, not that, this, not that. And you have to articulate it to the team. So you don't just say, wave the wand and say we're going this way and this is the only way and don't challenge me. No, people can challenge, but you have to have really good reasons and rationale for why we're doing this and not that. So the team understands in their core why that decision was made and that they were heard — like, we thought this, and like, we wouldn't do that because this, or we can do that but version two because we don't have time for this or whatever it is. And so you really need to make sure that when you are in charge of these opinion-based decisions, you also listen to other people, and you also tell them the reasons behind the decisions the way they're made so people can get on board. Or if they don't, you say, 'Okay, leave the company or leave the project, go somewhere else, but get on board,' so that everybody is pulling in the same direction and there's not a lot of, you know, this and that and blame and everything else.
Interviewer 19:34 ↗
At E14 we talk a lot about founders having two brains at least initially — this community is a scientist brain and the founder brain — and they usually, some of these brains are at odds, where a scientist maybe is optimizing for universality, a founder is optimizing for just grit and for even sometimes cutting corners and just doing it. It seems that also like the taste brain or these like multiple brains in your head that you almost have to —
Tony Fadell 20:00 ↗
Yeah, absolutely. You have to think of all those. But, you know, frankly, when you go to do your own company and you're getting money, you know, from third parties or whatever, you have to get on to engineering and developing and going. So before you commit to doing this thing, you got to know that the science for the most part's worked out. You don't go and do these other things because no one's going to fund a research project. Sorry. They're going to, 'Oh yeah, okay, that's interesting.' I know there are AI companies that are saying they're fundamental labs, and they're, you know, this is a very special time, but if you do anything that's not AI right now, you're not getting any money. It's crazy how, you know, you know this, right? No one's getting any unless you have a really clear idea with a clear market, with a clear customer, in some cases customer traction. So the scientist brain that will lead you to get to a business, but at some point you have to turn it off because you can't — when you start to see product-market fit and all that stuff, then you can go into research mode again, but you're not doing basic science, basic research, you're taking — you're doing applied stuff. So you come to — that's why you see all these companies hanging around the Media Lab and everything else. They're like, 'What's those latest ideas? Okay, we're going to translate that into a product,' right? They're letting you guys do the science and research, and then they're trying to do the productization.
Interviewer 21:17 ↗
You activate the engineering brain. You know, MIT is Mens et Manus, maybe you activate now the hand part of the brain, like the engineering part versus the scientist.
Tony Fadell 21:25 ↗
Yeah. Yeah. You have to activate the hand, and so you do the engineering side. But the thing is, especially if you're a technical founder, you have to really understand the soft skills of marketing and messaging, target customer development, user interface or user experience, customer journey design, all of those other things. And that's actually why I'm here, is because tomorrow I'm going to teach the first class on design of the customer journey. And we're —
Interviewer 21:55 ↗
Why are you here?
Tony Fadell 21:56 ↗
Why am I here? I was asked to be a designer in residence at MAD, at the Morningside Academy of Design. And I'm here working with teams who are doing big projects, or alumni teams as well as graduate teams who are working on making their companies and helping them with discerning what it is they're doing, the why about it, their target customer, their go-to-market, all of those things, to really bring a board-level like discussion and mentoring discussion into this kind of setting. Because a lot of times you get — you here, you guys get, 'Oh yeah, keep going for it. Yeah, yeah, yeah.' And then you might get a little money because you're being very supportive, but you know, you're very early stage. I'm looking — I'm Series A, I'm Series B, and I'm looking at going, 'You don't got this right. Like, you got to worry about this and this, and you did that right, but you got to worry about all these other things to actually make a real company.' And that's what I learned in those 10, 15 years of failure. And I still fail and still learning. So it's bringing all of that kind of stuff beyond the product itself.
Interviewer 22:58 ↗
Yeah, really understanding the other aspects that usually your technical brain doesn't think about.
You mentioned earlier with the iPod that, you know, it's hardware and hardware is hard, but you kept at it. You came — you took a break and you came back and went at Nest.
Tony Fadell 23:15 ↗
Yeah, I took a year and a half off.
Interviewer 23:17 ↗
Well, actually before — actually the Nest, like, and I've seen that you do it — you did that a couple of times, when after Nest you did it. And say more, say more about the importance of breaks when you —
Tony Fadell 23:27 ↗
Yeah. Well, for me, you know, you go intensely in, and you go into a rabbit hole of building the company you want to build. And, you know, you got to sometimes tune out a lot of the naysayers. You got to listen to certain people that you really respect and try to navigate through all that. And it really — it's draining. It's full-on, you know, you got to be all in for that. And 18 generations of iPod, 18 generations of iPod and three generations of iPhone, yeah, in 10 years. So that was a lot. Plus all the accessories, you know, there's all and all the other variants and all the other things. So that's just the tip of the iceberg kind of thing, and putting up manufacturing and so it's an intense, it's an intense time. And so what I was like — I was like, 'Oh, well, do I want to do version 19 of the iPod? Do you want to use?' And then the iPhone's like, 'Oh yeah, we got the next one.' I'm like, I've been on this treadmill. Enough of this treadmill. I can't do this anymore. I was like, I need to do something else. We have a great team. The people behind me are going to be able to rise up and take it over. And they did, right? It's working brilliantly. And so I wanted to take time off, and I wanted to get out of Silicon Valley, and I went traveling around the world. And I went traveling around the world because I wanted inspiration from real problems. For me, it's problems that give me the inspiration to build what it is we build. And starting with that pain, and then trying to find the right painkiller. And so as I traveled around the world for a year and a half, and I already had a pain of controlling my thermostat in a remote mountain location and mocking it up for, you know, eight, nine years, and it was all failing. I was like — and I was building a new house. I was like, 'Oh, someone over those 10 years must have solved this problem.' No one solved the problem. And then I was like, 'Okay.' And then I'm traveling around the world, and I'm like, 'I'm in Spain, thermostat sucked. I'm in the UK, thermostat stuck. France, the thermostat stuck. I'm in Hawaii. I'm in Asia.' And like everywhere I went, I was like, 'This is a global problem. Everybody has the same problem. No one's fixed it anywhere.' I was like, 'Ding, ding, ding, ding, ding.' You know, and so I was like — and we can take all that stuff that was learned from iPod and iPhone and before that and say, 'Okay, and now we have all the technology, and people have the remote control to their life in their hand, which is a smartphone. Okay, now let's have devices that you're going to control remotely and put AI in them.' You know, the Nest thermostat was one of the very first consumer products to actually have real working AI in it in 2011.
Interviewer 26:13 ↗
We didn't call it AI.
Tony Fadell 26:14 ↗
We didn't call it AI because AI would have scared people. Now, if you don't have AI, forget it. You know, you're nobody. But then we had to call it learning. So we called it learning.
Interviewer 26:23 ↗
What did you underestimate going into Nest?
Tony Fadell 26:25 ↗
What did I underestimate? It's a good question.
To tell you the truth, we underestimated how freaking popular the product would become. We were like, 'This is a crazy idea. We're going to make, I think it was 10,000 units for the first production. We're going to just buy all that stuff.' We were out of stock for two and a half years. We could not — and we would keep ramping up the quantities, and we could never fulfill demand. It was crazy. People were putting them under the Christmas tree and giving them as gifts. They were on the talk shows, the late-night talk shows. Like, it was crazy. So what we underestimated was just how much people were wanting these things. And it wasn't just geeks. It was people who really wanted to save energy, or they just couldn't stand looking at the ugly thing on the wall anymore, and they didn't know how to use it. So that was, I think, what it is. Other than that, we had a stellar team, and, you know, we really, you know, had — because a lot of us had worked together for 10 years, some of us 20 years at that point. So —
Interviewer 27:37 ↗
The product is gorgeous and was gorgeous even back then. What about installations for the Nest? Was that a friction for scale?
Tony Fadell 27:46 ↗
Yeah. Well, that's the customer journey. And so what we quickly learned was as we were — we said, 'Okay, we're going to have a great product, but right now nobody knows how to install the product. You have to call, you know, the overalls and the butt-crack plumber or HVAC guy to come and install it.' And what would turn out — and this is what we learned — was these guys were actually — they would get bonuses from Honeywell and the competitors in the field. So if they sold 10 of their thermostats or 20 thermostats in a quarter or something, they get a free trip to Hawaii. Okay. So if we had these people, we're trying to convince them to sell our product that was more expensive, that didn't give them a trip to Hawaii, that it was like digital, and they're like, 'What is that? I can just sell 20 of these.' And like, there was no way we're going to get this to market. So we had a disruptive product, but we had to find a disruptive way to market because it wasn't going to happen that way. And what that meant was you go to Best Buy or somewhere and you figure out how to self-install it. So we had to create all of these configurators, these special switches on the device, these installation menus and things, very, very streamlined. And we were worried that we were like — okay, I was like, if we could get 40 to 50% of the products to be self-installed, we've won. So 50% self-installed, 50% professional installed. We spent so much time and energy on it. We put a screwdriver in the box. We probably put $15 more in components in the product to make it self-installable. That after the first quarter, 90 to 95% of all the products were self-installed. And that blew us away. And that's why we had the volumes that were crazy. We had grandmas going on YouTube videos going, 'I just installed this,' and we're like — and it became this thing. And so we didn't know. And so when you do a really great job of not just the product but the whole customer journey, because there was all kinds of things on the marketing, on the website, all these different things to make sure you knew how to install it really easily, that it was frictionless for a lot of people, and they felt like it was a superpower. A lot of them weren't makers. Nobody really installed these kinds of things. They wouldn't install an electrical switch in their house, but they installed a thermostat, and it worked, and they go, 'Oh my god.' It was almost like — that was also in the maker days, too. And be like, 'Ah.' You know? So it was really cool.
Interviewer 30:34 ↗
What was a non-obvious design decision? Non-obvious.
Tony Fadell 30:42 ↗
Well, okay. There was one thing which was because it was round, you know. How do you know? Because you had to put a plate on the wall, and then you had to put the face plate on the — or the front half of it on there. And people would be like, 'Well, if I put it on wrong, it's going to be like the interface could be tilted or whatever.' So I said, 'Let's put a level on it.' So we put a bubble level on it so that you could bubble level the backs to get it right, screw it in, and then it worked every time, right? So it was like that was non-obvious. And now guess what? If you go and look at almost all the thermostats that are out there now, they all have bubble levels in it.
Interviewer 31:16 ↗
That's going back to your grandfather's, actually.
Tony Fadell 31:18 ↗
Exactly, all the way back to real analog. And that thing, I think in the bill of material, I think that was about 15 cents, that alcohol bubble level.
Interviewer 31:26 ↗
I'm sure you had plenty of ideas for the Nest, and you had to kill a lot of them. I'm just — if I'm in your shop, I'm just guessing like you can do this thing and that thing and this thing and whatever, but you kept true to the product, and the simplicity was ultimately the beauty of the product. How did you go about shooting off or saying no to things?
Tony Fadell 31:46 ↗
Well, the great thing there was it was mostly software-driven. Once you had the hardware, it was software-driven. So we could say, 'Okay, that'll be the next version of software, next version of software,' because it was, you know, Wi-Fi connected, whatever. So we could update it. You know, thermostats had none of that, right? But we knew what it was like to have it in our smartphones, right? So we were just like, hey, we just need to get it out there for this, and we'll make it better over time.
Interviewer 32:13 ↗
That's great. Early days also of Nest. Maybe I want to talk about founders. A lot of founders in the room, they want to think about finding co-founders and early team. If I'm not mistaken, your co-founder at Nest also worked with you at Apple.
Tony Fadell 32:30 ↗
Well, he was my first intern on the iPod project. So my co-founder at Nest was my first intern on the iPod project.
Interviewer 32:36 ↗
And how long did you work together on the iPod?
Tony Fadell 32:39 ↗
Well, he was an intern two years — for two summers, and then he came on full-time after it. So we were probably together, I don't know, like five years, five something like that.
Interviewer 32:50 ↗
What made him a great co-founder for Nest?
Tony Fadell 32:53 ↗
Oh, he was just absolutely incredibly curious. He would just make it happen. It was, you know, it was clear. You're like, 'Oh, you know, outstanding guy.' And people — the other thing that happened was, and you have to do this when you're, you know, when you're building a team in a startup, you need to make sure your first hires are seed crystals, right? We all know what seed crystals are from chemical engineering, right? Boom. You get that one person who has a network of people who they can pull in, right? And he was also a generation below me, so he could get all the younger engineers. I could get all the older people. It's because what happens is if you don't get all of that age right, you're going to get one class of people in there, and you want both. And then over time as Nest grew, I was like, every team, 10% to 15% of all of your new employees had to be fresh grads. And they'd be like, 'No, they don't have any experience.' I said, 'I don't care who gave you the leg up when you were coming out of school. We need to keep refreshing the talent in our organization and staying young.' And the way we're going to stay young and keep thinking young is to make sure we have other young people on the team, because you can see these kind of, you know, startups age up and they don't hire because they're like, 'I don't want to invest in the latest generation because they're too hard or they're millennials or whatever, Gen Z.' And it doesn't work that way, you know.
Interviewer 34:22 ↗
Maybe the opposite side. What was the most expensive or most costly hire? Costly hire from a mistake perspective.
Tony Fadell 34:33 ↗
Well, you're going to always make mistakes in hiring. Like, you got to have to — you have to understand, just like in engineering or coding or anything, you're going to make a mistake. Just fix it really fast. So when you do make a mistake, you can see it and you go, 'Look, this isn't working out,' and you got to exit that person pretty fast. I'm not saying you fire them in a, you know, in a guillotine or something like that, but no. But what I'm saying is you got to exit it really fast. And what happens is almost everybody who works with that person in the team knows it's a problem. They're just waiting for you to actually make the action. You know, they're all like, 'Okay.' And so they're like, 'Okay, when is it going to happen? Because it's not working.' And then finally you do it, and they're like — everyone's like, 'Thank God.' But nobody tells you this really. Maybe there's one or two, but nobody really tells you this the way — but the team knows it already.
Interviewer 35:24 ↗
Yeah, we with our founders at E14, I don't think there's any founder who said, 'I wish I fired that person a bit too late, a bit later.' It's always like, you know, you get to know it earlier. But also the biggest mistake that founders make, particularly in this crowd — engineering, scientist, etc. — is hiring a salesperson because they're going to come and help you save and sell. And we always talk about founder-led sales and how as an engineer, as a scientist, you are the one who knows your tech the best, and you're the one who has to go at it. Would you agree or — at least early on?
Tony Fadell 36:00 ↗
Well, it depends on how early. And, you know, to really understand product-market fit and to really understand your customer — and this isn't — we're talking about a B2B sale here, not a B2C. B2B companies and B2C companies are totally different in how you staff them, how you think about designing the product and everything. And most companies, unless they're really big conglomerates like Microsoft that can have Xbox on one side and, you know, corporate Windows on another and servers, you can do that. But most companies, small companies or even medium-sized, they're B2C or B2B. They can't be both because they get schizophrenic because you're hiring two different types of people. You design your products differently, spec them differently. And so in a B2B area, yes, you can be a founder-led sales because you're going to go sit with those customers, listen to them, you know, and over time, you know, modify the product roadmap and stuff. In a B2C, you don't get that. You get one shot to get it right. And so you get out with the brand, and we saw what happened with Humane. We saw what happened with Rabbit. We saw, you know, all that stuff. And so, you know, they just didn't hit it because they just thought about technical or geek stuff. They didn't think about all the other pieces of the puzzle to make that thing work.
Interviewer 37:20 ↗
We were talking earlier, just before going on stage, about some of these crazy valuations these days and AI companies, and I asked you something and —
I didn't hear the full answer, but I'd love to hear it here. What have you seen good AI products?
Tony Fadell 37:37 ↗
Absolutely. We're investors in a few of them.
Interviewer 37:39 ↗
Tell me more.
Tony Fadell 0:40 ↗
But we started investing 10 years ago, eight years ago in companies that did AI. We have a company called Orionis Biosciences right here in Waltham, and they do AI drug design, and they've been working on their engine for, like I said, 10 years. And we have multiple drugs. One's in FDA phase two. We're already helping people. We have tons of drugs behind it. We've done hundreds of millions of dollars of contracts with Genentech, Novartis, and it's all based on our AI-driven affinity binding solutions. And yeah, so that's one. We have another one called Nabla out of Paris. We are a medical assistant for medical scribe, medical billing, insurance, pre-authorization, all of the paperwork, everything. And that was out of Paris, and now they're number two here in the US doing it. And they got, you know, $40, $50 million in revenue now. And that's AI-driven. We have one in recycling, so doing classification and sorting for recycling with AI as a camera, you know, the conveyor belt goes and helps you do that analysis. So yeah, there's lots of stuff, but it's not these...
It's not these AGI boil-the-ocean tens of billions of dollars necessary to build. There's lots of incredible narrow-focused AI stuff that doesn't hallucinate that's incredibly valuable. It's like they're shooting the moon as opposed to, okay, what are the things, the pains that can be solved today? Like humanoid robots. Yeah, right. So they're cool, but no, it's just like self-driving cars in 2006. They're cool. They're finally here 20 years later. If you started a company anywhere along the route, it's more or less dead, unless you were Google where you funded Waymo with all your advertising for years and years and years. So you got to remember again, this is just like General Magic. When's the right timing? And it's not just when society will adopt it, but when all the technology lines up and when it's going to be just about economical, right? And we don't even have the right AI base technology to be able to do the things we need to do for humanoid robots. We don't even have the tactility or the sensing that we need for humanoid robots.
Interviewer 40:14 ↗
Yeah, it's great. Well, we're privileged at E14 to work with many amazing founders in AI, including manipulation and dexterity, and also on the fuel for AI on the bottom of the layer. I think you're also on the board of ARM. We have a few companies on the memory side. I think one of the founders is in the room decoupling memory from GPU. So also on the knowledge like...
Tony Fadell 40:33 ↗
All that stuff is great stuff, and those things are all building blocks for these things that we're talking about, right? It's all coming up. I was an investor in Groq, and you know that just went. And so, but you got to be a smart investor and also a smart entrepreneur. You have to understand that you can shoot the moon, but once you look at all the other pieces of the puzzle that are going to need to be morphed on to be able to get to this vision, and that's what we were doing post-General Magic with all the other devices and the things I was working on to finally make the iPhone. The iPhone wouldn't have happened if you didn't do the iPod.
Interviewer 41:06 ↗
Yeah. That's why like we're investing in the whole stack. We think there's opportunities across knowledge workers, physical workers, and kind of the fuel.
Tony Fadell 41:14 ↗
Absolutely.
Interviewer 41:14 ↗
I want to go through kind of quick underrated, overrated, and why?
Tony Fadell 41:21 ↗
Underrated or overrated?
Interviewer 41:22 ↗
Yeah. Right.
Tony Fadell 41:22 ↗
All right. We'll start with easy ones. Vision.
Interviewer 41:25 ↗
Vision.
Tony Fadell 41:27 ↗
It's in the middle. If you can't implement, so it's a maybe. If you can't implement, vision's no good. Everyone has an idea, you know. But if you can't implement, it doesn't matter. So you got to have both. You can't just implement. You got to have both.
Interviewer 41:43 ↗
Failing fast.
Tony Fadell 41:44 ↗
Failing fast. Failing quickly. I wouldn't say fast fast because that's how we learn. You know, when we learn to walk, we don't learn to walk the first time. We fail a thousand times before we learn to walk. So we have to, you know, keep iterating to get there, but that's the only way we learn. So you need to fail to learn.
Interviewer 42:06 ↗
MBA.
Tony Fadell 42:09 ↗
Overrated.
Let's see. I guess I didn't have to tell you why.
Interviewer 42:18 ↗
Oh, we agree. Why? Yeah. Why? Why?
Tony Fadell 42:22 ↗
Why? Oh, very simply. Because actually that stuff's easy to learn, and there's a lot of people who will teach you on the job. Engineering and fundamental sciences and building things and how to do messaging and that stuff, that's really hard. But MBA stuff, there's a lot of stuff. And frankly, I think if you can think of one thing that AI could actually do pretty well, it's that.
Interviewer 42:48 ↗
Being data-driven.

86 more exchanges in this transcript

Sign in free to read the rest of this interview. No card required.

Sign in to read the full transcript

Cite this transcript

APA, MLA, BibTeX
APA

Fadell, T. (2026, February 13). E14 fireside chat with Tony Fadell and Habib Haddad, [Interview transcript]. E14 Fund. CEOInterviews.AI. https://ceointerviews.ai/interview/3177852/

MLA

Tony Fadell. "E14 fireside chat with Tony Fadell and Habib Haddad,." E14 Fund, 13 Feb. 2026. Transcript, CEOInterviews.AI, https://ceointerviews.ai/interview/3177852/.

BibTeX
@misc{fadell2026_3177852,
  author       = {Tony Fadell},
  title        = {E14 fireside chat with Tony Fadell and Habib Haddad,},
  howpublished = {Interview transcript, E14 Fund. CEOInterviews.AI},
  year         = {2026},
  month        = {feb},
  url          = {https://ceointerviews.ai/interview/3177852/},
  note         = {Speaker-attributed transcript with timestamps}
}