Open Reader

Tony Fadell: How to build real taste (and why AI makes it matter more)

completed 1:35:07 Jun 07, 2026 Watch on YouTube

Current Status

completed

Video ID

RJjl1TwyfWM

RAG / Chat

Enabled
Tony Fadell: How to build real taste (and why AI makes it matter more)
Description

Tony Fadell created the iPod, co-created the iPhone, and founded Nest (which he sold to Google for $3.2 billion). He’s co-authored over 300 patents, was part of the legendary team at General Magic, and wrote one of the most important and inspiring books for builders, called Build. *In our in-depth conversation, we discuss:* 1. The heated internal debates about whether the iPhone should have a physical keyboard 2. Why opinion-based decisions are essential for v1 products 3. Why marketing matters as much as the product itself, and how the iPod almost failed 4. Why voice will eventually become the primary interface with AI 5. Why cognitive surrender to AI is the biggest risk facing product builders today *Brought to you by:* WorkOS—Make your app enterprise-ready, with SSO, SCIM, RBAC, and more: https://workos.com/lenny Vanta—Automate compliance, manage risk, and accelerate trust with AI: https://vanta.com/lenny *Episode transcript:* https://www.lennysnewsletter.com/p/father-of-the-ipod-and-iphone-on *Archive of all Lenny's Podcast transcripts:* https://www.dropbox.com/scl/fo/yxi4s2w998p1gvtpu4193/AMdNPR8AOw0lMklwtnC0TrQ?rlkey=j06x0nipoti519e0xgm23zsn9&st=ahz0fj11&dl=0 *Where to find Tony Fadell:* • X: https://x.com/tfadell • LinkedIn: https://www.linkedin.com/in/tonyfadell • Website: https://www.buildc.com *Where to find Lenny:* • Newsletter: https://www.lennysnewsletter.com • X: https://twitter.com/lennysan • LinkedIn: https://www.linkedin.com/in/lennyrachitsky/ *In this episode, we cover:* (00:00) Introduction to Tony Fadell (02:23) The Blackberry vs. iPhone keyboard debate (07:50) Micromanaging vs. kind lies: what great products actually need (15:57) The Nest thermostat and smoke alarm story (21:22) How to decide what’s worth building: pain plus new technology (27:36) The three-generation rule: why nothing works the first time (34:20) The full customer journey: why marketing defines your product (40:53) The power of storytelling and the press-release-first app

Summary

Generated by gpt-5.6-sol

At-a-Glance

  • Verdict: Watch fully
  • Core thesis: As AI makes implementation cheap and abundant, durable differentiation shifts toward human taste: choosing the right pain, imposing a coherent system architecture, refining the customer story, and refusing to surrender judgment to the machine.
  • Why it matters: Fadell connects product taste directly to AI-assisted engineering, technical debt, human control, full-stack orchestration, trust, and the practical path from prototype to enduring company.
  • Best use: Use the interview as a product and architecture review framework for AI agents, OpenClaw, and portfolio companies: validate the pain, define the system and story before building, constrain AI to well-bounded work, and preserve accountable human decision-makers.

Executive Summary

Fadell argues that genuinely new 1.0 products cannot be created through consensus or retrospective data alone. When useful analogs do not exist, a small group of informed tastemakers must synthesize engineering, customer, marketing, sales, and operational knowledge, make an opinion-based decision, and accept responsibility for being wrong. The iPhone's virtual keyboard illustrates the pattern: Apple measured speed, errors, correction behavior, and hardware-software interactions, but the evidence remained ambiguous enough that Steve Jobs ultimately had to choose a direction.

His product-discovery formula starts with a persistent or habituated pain and asks whether newly available technology can now remove it. The resulting product must be designed as an entire customer system, not an isolated feature. Nest combined learning algorithms, sensors, industrial design, installation, retail distribution, and an economic promise; the iPod required portable storage, batteries, ARM processors, digital music, Windows support, iTunes, and the Music Store. Fadell cautions against judging such bets from their first release because durable products commonly need three generations: make the product, fix the product, then fix the business.

AI intensifies rather than eliminates the need for taste. Fadell sees coding agents as excellent prototyping and scoped implementation tools, but warns that unconstrained generation can create brittle, unreadable systems with hidden security, maintenance, rollback, and technical-debt costs. His prescription is to have humans define and lock the architecture, divide work into bounded subsystems, retain domain experts and review functions, and use AI within those constraints. As undifferentiated software becomes easier to copy, products such as Flighty stand out through coherent architecture, restraint, detail, and an experience that people voluntarily recommend.

The same holistic logic applies to go-to-market and future AI interfaces. Marketing should help define the product before development by forcing the team to state the customer context, the why, and three or four tent-pole benefits. Fadell expects AI devices to become voice-primary only after models earn sufficient trust and memory, while displays remain necessary for visual tasks. He is more optimistic about scoped AI embedded in full-stack systems—robotics, recycling, manufacturing inspection, drug design, and contextual home devices—than about generic AGI promises or autonomous systems that ask users to surrender oversight.

Key Takeaways

  • Claim: AI lowers the cost of producing software but raises the value of human taste, system architecture, and disciplined feature selection. | Evidence: Fadell contrasts easily generated or copied software with Flighty, which he calls “luxury software” because its pixels, architecture, and complete experience were deliberately crafted; he argues that only three or four key features can usually be communicated and sold clearly. | Implication: Ken should treat model output as abundant implementation capacity, while making product coherence, architectural boundaries, and accountable judgment the scarce control layer. | Caveat: He is not rejecting AI coding: he explicitly recommends it for rapid prototypes and tightly scoped subsystems after humans establish and refine the architecture.
  • Claim: Unconstrained agent-generated code can exchange short-term velocity for long-term technical debt, so humans must retain architectural, security, maintenance, and rollback responsibility. | Evidence: Fadell cites an alleged leak of Anthropic's Claude source code and says experienced engineers viewed its main loop as brittle, unreadable, and insufficiently decomposed; he then lists security, maintainability, debugging, and rollback as concerns that passing tests alone do not resolve. | Implication: For OpenClaw and other agent systems, successful execution tests are insufficient; Ken needs explicit module boundaries, human-readable designs, observability, security review, version control, and recoverable state. | Caveat: The transcript does not independently verify the alleged leak, its provenance, or Fadell's characterization of Anthropic's code, so the anecdote should be treated as an illustration rather than established evidence about Claude's production architecture.
  • Claim: A differentiated 1.0 requires a small, accountable tastemaker group because data cannot resolve choices for which no close precedent exists. | Evidence: Apple tested iPhone virtual-keyboard typing speed, error rates, corrections, and hardware-software changes for months. The virtual keyboard became “good enough” but not objectively superior to BlackBerry's physical keyboard, so Steve Jobs made the final opinion-based decision and required the team to commit. | Implication: Ken should assign clear decision rights for novel agent behavior and product architecture rather than allowing committees, benchmarks, or consultants to conceal unresolved judgment calls. | Caveat: Fadell distinguishes informed judgment from arbitrary intuition: the decision-maker must solicit expert input, generate relevant evidence, articulate the cross-functional rationale, and take responsibility for the risk.
  • Claim: The strongest product opportunities combine a meaningful pain with a newly viable enabling technology and redesign the complete system around the solution. | Evidence: Nest addressed confusing programmable thermostats and heating and cooling costs—approximately 50% of the household energy bill in Fadell's account—with learning algorithms that inferred occupancy and temperature preferences. The $249 device was positioned to save roughly $800 to $1,200 annually, while Nest also redesigned installation and retail purchasing. | Implication: Ken should evaluate AI opportunities by the severity of the workflow pain and the readiness of the full operating system around it—not by model novelty or demo quality alone. | Caveat: A new technology is not sufficient by itself; General Magic built a smartphone-like vision roughly 15 years too early, showing that customer need, infrastructure, timing, and the surrounding ecosystem must also be ready.
  • Claim: Novel products should usually be financed and managed across three generations: make the product, fix the product, then fix the business. | Evidence: The first two iPod generations mainly reached Mac loyalists, who represented less than 1% of the market; broader adoption arrived with the third generation after Windows support and the iTunes Music Store reduced the effective commitment from buying a roughly $3,000 Mac setup to buying a $349 iPod. Fadell says early iPods and iPhones also lacked healthy margins. | Implication: Ken should judge early AI products against generation-specific learning goals and ensure the roadmap and capital plan survive long enough to improve reliability, distribution, and economics. | Caveat: Persistence is justified only while evidence supports the underlying pain and direction; Fadell allows that a severely flawed premise may require a restart rather than another incremental release.
  • Claim: Marketing is part of product architecture because it forces the team to define the customer's context, the product's why, and the few benefits that justify conversion. | Evidence: Fadell recommends drafting the press release before development, limiting it to three or four tent-pole features, and checking proposed feature cuts against that story. He recalls that late-adopter iPod messaging from the United States failed when reused in Europe because European buyers were at an earlier adoption stage and lacked the same word-of-mouth base. | Implication: Ken should use messaging artifacts as design constraints for agent products and tailor the narrative to each buyer's maturity, trust level, and existing workflow rather than relying on generic AI claims. | Caveat: Storytelling cannot compensate for a weak experience; he says the best marketing tells the truth and the promised story must emerge from the product itself.
  • Claim: The likely AI-device transition is from touch-primary to voice-primary interaction, but screens, apps, human control, and gradual trust-building will remain necessary for a substantial period. | Evidence: Fadell proposes reversing today's hierarchy from touch, keyboard, then voice to voice, keyboard, then touch once assistants have reliable intelligence and memory. He argues that maps and other visual information still require a display, dismisses Humane's hand projection as “different, not better,” and compares consumer trust in agents to the long wait for dependable full self-driving. | Implication: Ken should build multimodal, reversible agent experiences that earn delegation progressively instead of assuming voice-only, app-less, or fully autonomous behavior is already acceptable. | Caveat: He considers this a long-term direction, not an imminent replacement cycle; current model reliability, social trust, and subscription prices of roughly $20 or $200 per month remain adoption barriers.

Detailed Brief

Selective micromanagement as cross-layer orchestration

  • Claims: Fadell distinguishes micromanaging high-leverage decisions from controlling every operational detail.; Leaders should intervene deeply where a customer-defining detail, crisis, cost constraint, or system-level dependency requires coordinated changes across teams.; The leader's job is to keep asking why, demand the exact evidence required for an informed decision, and orchestrate dependencies that individual functions are incentivized to avoid.
  • Evidence: Making the iPhone keyboard viable required simultaneous iteration across touch hardware, software, input filtering, graphics, calibration, and error correction.; Fadell says he initially treated every detail as equally important, exhausted himself and others, and later learned to separate the few details requiring direct attention from work that should be delegated.
  • Caveats: Micromanagement becomes destructive when it means requiring everyone to execute work exactly as the leader would rather than focusing attention on a small set of consequential decisions.
  • Implications: The useful leadership model for complex agent systems is selective control of interfaces, invariants, and acceptance criteria—not blanket involvement in every task.

Ambient context and the unrealized Nest 2.0 opportunity

  • Claims: Fadell believes useful home AI requires contextual sensing distributed through the environment rather than a standalone chatbot with little knowledge of occupancy or activity.; He views the discontinued Nest Protect and the stagnant Nest ecosystem as products orphaned by organizational and cultural mismatch inside Google, not as proof that the category lacked value.; A privacy-conscious successor could use appropriately placed sensors to support an assistant available throughout the home.
  • Evidence: Nest Protect's “Heads-Up” feature warned users before sounding a loud alarm, illustrating how contextual design could reduce stress in a safety-critical product.; Fadell says a future home system could infer comings and goings, room occupancy, identity, and voice context while attempting to avoid invasive surveillance.; He reports receiving business plans for “Nest 2.0” concepts and contrasts the opportunity with Ring, which he considers less privacy-focused.
  • Caveats: The required sensing creates substantial privacy, identity, authentication, retention, and consent risks that the interview acknowledges but does not solve technically.; High-quality physical products require sustained organizational attention and may be too small to survive inside a platform company even when they lead their category.
  • Implications: The control plane for ambient agents may depend as much on trustworthy context acquisition and organizational ownership as on the intelligence of the underlying model.

Ethics as a product requirement rather than a post-launch policy

  • Claims: Fadell argues that builders should treat moral boundaries with the same seriousness as interface and architecture constraints.; He opposes optimizing products to addict users or replacing messy human connection with commercially optimized AI relationships.; He calls for stronger digital-consumption information, controls, habits, and age-appropriate protections analogous to nutritional labels and physical-product regulation.
  • Evidence: He recalls Apple rejecting pornography for the expanding iTunes video ecosystem after Steve Jobs framed the question around the world the team wanted children to inhabit.; He compares smartphones to refrigerators that can contain healthy or unhealthy food and notes that even healthy content can be consumed compulsively.; He points to Apple's privacy positioning as an example of a constraint that may slow some capabilities but can create durable user trust.
  • Caveats: Fadell does not provide a detailed governance framework and acknowledges that people disagree over acceptable boundaries and individual rights.; He separates intended product design from unintended ecosystem consequences, noting that Apple did not set out to create social-media addiction even though the iPhone distributes those applications.
  • Implications: Agent governance should examine not only task accuracy and safety incidents but also incentive design, dependency, manipulation, and long-term effects on user agency.

Notable Concepts & Terms

  • Informed gut: Opinion-based judgment earned through experiments, expert input, prototypes, and cross-functional understanding rather than unsupported instinct.
  • Tastemaker: The small, accountable person or team authorized to resolve ambiguous 1.0 product choices and maintain a singular vision.
  • Three generations: Fadell's sequence for durable innovation: make the product, fix the product with real feedback, then fix margins, scale, reliability, distribution, and the business.
  • Pain plus enabling technology: The opportunity test that pairs a persistent customer problem with a newly mature technology capable of solving it in a materially different way.
  • Full-system product: A product understood as hardware, software, services, distribution, installation, marketing, support, and economics rather than only the visible device or feature.
  • Luxury software: Software differentiated by coherent architecture, restraint, detailed craft, durability, and felt quality rather than a large quantity of cheaply generated features.
  • Cognitive surrender: Fadell's warning against outsourcing judgment, architecture, ethics, or accountability to AI merely because the machine can generate an answer or implementation.
  • Digital nutrition: The analogy that digital products need clearer consumption information, controls, healthy defaults, and protections similar to those developed around food.

Operator Notes / Why Ken Should Care

  • Add an architecture gate to OpenClaw releases requiring named human owners for module boundaries, permissions, state recovery, security review, and rollback behavior.
  • Separate prototype-generation agents from production-writing agents, with narrower tool permissions and stricter acceptance criteria for the latter.
  • Require every new agent initiative to identify one painful workflow, the specific enabling-technology change, and the surrounding integrations or operational changes needed for adoption.
  • Create a three-release capital and learning plan for strategic AI products, with explicit V1 product, V2 reliability, and V3 business-economics gates.
  • Draft a customer-facing launch narrative with no more than four tent-pole benefits before approving major development, then reject features that do not strengthen those promises.
  • Implement progressive delegation levels so users can move from recommendations to approval-based execution and only then to bounded autonomy after trust is demonstrated.
  • For ambient or context-aware agents, require a privacy threat model covering sensor minimization, identity resolution, consent, retention, access control, and local-versus-cloud processing.
  • Add user-agency and dependency risks to product reviews, including whether engagement incentives encourage compulsive use, emotional manipulation, or inappropriate replacement of human relationships.

Source/Metadata

  • Title: Tony Fadell: How to build real taste (and why AI makes it matter more)
  • Transcript words: 27644
  • Duration seconds: 5707
  • Timestamp note: No timestamps or chapter markers were present. The supplied transcript contains substantial duplicated passages, including a repeated appended section, but retains enough substantive material for analysis.

Transcript

17800 words en Processed in 1066.2s

You still need humans to lose. Don't surrender to the machine. We can use the machines, but don't cognitively surrender. Because it's so easy to build, the things that stand out are the things that are really well thought through. [SPEAKER_01] Today in the AI world, I can just make a prompt and all of a sudden it gets spit out. [SPEAKER_01] You're building on a really crusty foundation. You're getting short-term gain for very, very long-term loss. If you're going to build a real company, it can't be throwaway. [SPEAKER_00] One of your colleagues, Herman Hauser, I asked him how he decides what is worth building. I always start from pain. Are there new technologies to solve that pain? [SPEAKER_01] Bring innovation in, revolution in, and redefine the space. What's the threshold? What's the sign of, okay, this isn't big enough? [SPEAKER_00] Oh, the iPod wasn't big enough. It took three generations of the iPod before it became successful. You got to fail a few times until you find your way. [SPEAKER_01] You are so into marketing, that piece of building that I think a lot of builders don't think about at all. The technology is in service of the customer, not we're going to jam the technology down the customer's throat. A customer only sees what they see through the lens of marketing. You often come back to the value of storytelling for product builders. [SPEAKER_00] Too many times when we're technology-led, we talk about the what. [SPEAKER_01] We don't talk about the why. [SPEAKER_01] The why is storytelling. [SPEAKER_01] When I watched Steve, he was honing the story of the iPhone every day. And so when you saw him come on stage, it was just perfect. Because he had done it 100,000 times. [SPEAKER_01] Today, my guest is Tony Fadell. [SPEAKER_00] Tony doesn't know this, but ever since I started this podcast, he's been near the top of my wish list of people that I've dreamed to have on this podcast. [SPEAKER_00] And that's because Tony is the epitome of what most people listening to this podcast want to become. [SPEAKER_00] He co-created some of the most innovative and beautiful and popular products in history: the iPod, the iPhone, the Nest Thermostat. [SPEAKER_00] He's also famous for being part of the legendary team at General Magic. [SPEAKER_00] He's co-authored over 300 patents. [SPEAKER_00] He also wrote one of the most important and valuable and inspiring books for builders called Build. Tony is currently an active investor and advisor to deep tech startups with his team at the Build Collective. He was recently named the inaugural designer in residence at the MIT Media Lab of Design. There's so much gold in this episode. I could go on and on. I'm going to leave it there. Before we get into it, don't forget to check out Lenny's productcast.com for a free year of some of the hottest and most well-crafted AI products in the world, available exclusively to Lenny's newsletter subscribers. With that, I bring you Tony Fadell. Tony, thank you so much for being here and welcome to the podcast. [SPEAKER_01] Thanks for having me. I appreciate it. I have a bazillion questions I want to ask you. I feel like I could fill four hours of conversation with all the things that I want to get out of your head. I want to start with BlackBerry. I was just watching the BlackBerry movie recently, and it's this journey of the BlackBerry founders and their story. And then at the end, they were like, oh, and this iPhone thing launched. And they're like, no, this is dumb. It's no keyboard and it's not serious. You can't do anything with it. And I've always wondered just being on the other side of this, being within Apple, building the iPhone, how much did you guys actually doubt that? Okay, maybe they have something. Maybe we need to add a keyboard. [SPEAKER_01] It was the most heated conversation and it dragged out the longest. [SPEAKER_01] There was one way of looking at the BlackBerry, which was that is the market we want to go after or we want to win. [SPEAKER_01] And then there's the other side, the flip side of that argument, which is only 1% or 2% of mobile phone users at the time had a BlackBerry, knew what a BlackBerry was. [SPEAKER_01] So what about the other 98% of the people? [SPEAKER_01] What would they want? [SPEAKER_01] What would they need? [SPEAKER_01] Why are we going to go after winning this very loyal and incredibly passionate user base and try to pull them away from something? [SPEAKER_01] And so there was this head to head competition between a display keyboard or a virtual keyboard and a physical keyboard. [SPEAKER_01] I had been doing virtual keyboards for a while since General Magic and then in the nineties. [SPEAKER_01] And I knew what handwriting was and keyboards were like on these touch screens. [SPEAKER_01] But I was only doing it on a display and I was writing software and calibrating them, making, trying to make them work with a single touch display, resistive or what have you. [SPEAKER_01] And so I knew what the limitations were of those kinds of things. [SPEAKER_01] So I was thinking, this is really going to be difficult. [SPEAKER_01] And we hadn't, you know, multi-touch was just on a big ping pong table. [SPEAKER_01] It hadn't been scaled down. So it wasn't something in a consumptive form where you could really do user tests with it. And so we set out a set of tests: okay, how fast can I type text? How fast can I do this on a hardware keyboard? And then how can we do this on the virtual one with multi-touch? And it was a hardware software integration challenge of how we could get this to work. So we were going back and forth and back and forth. Oh, that doesn't quite work in the software. Oh, we need to change this in the hardware. And so over a set of months, okay, the hardware keyboard is here, and depending on how much you've been using it, there's this margin of error and we could really understand it. Over time, it started way down here and it started to get a little faster and a little faster and a little faster. And how many errors—not just how fast, but how many errors and how do you correct the errors and all of those things. And at the end of the day, I was able to convince myself it wasn't going to be a hardware issue. And I was convinced at some point that we were good enough. Were we as good as a hardware keyboard? No. But were we good enough? Yes. And then other people came to that conclusion. But there's this margin error and we could really understand it. This, over time, was started way down here and it started to get it, and it got a little faster and a little faster and a little faster. And how many errors, not just how fast, but how many errors and how do you correct the errors and all of those things. And at the end of the day, I was able to convince myself it wasn't going to be a hardware issue. And I was convinced at some point that we were good enough. Were we as good as a hardware keyboard? No. But were we good enough? Yes. And then other people came to that conclusion. But at the same time, there were other people who were adamant that the hardware keyboard has to be there. And they were unrelenting. And so it came down to a classic data versus opinion-based decision. And if you think about it, you had data that said there was pros and cons on both sides. And what happened was the data was not clear that we should choose one over the other. And Steve said, we are going this way. Enough other people said, yeah, that seems like that's the right thing to do. We're going to get close enough to get there. And then other people were like, no, my opinion is this. And guess who wins at the end of the day? Steve Jobs' opinion does. And he was like, if you're not going to get on board, get out of this room and you can go work on another project, but you're not going to work on this one. This episode is brought to you by our season's presenting sponsor, WorkOS. [SPEAKER_00] What do OpenAI, Anthropic, Cursor, Vercel, Replit, Sierra, Clay, and hundreds of other winning companies all have in common? [SPEAKER_00] They are all powered by WorkOS. [SPEAKER_00] If you're building a product for the enterprise, you've felt the pain of integrating single sign-on, SCIM, RBAC, audit logs, and other features required by large companies. [SPEAKER_00] WorkOS turns those deal blockers into drop-in APIs with a modern developer platform built specifically for B2B SaaS. [SPEAKER_00] Literally every startup that I'm an investor in that starts to expand upmarket ends up working with WorkOS. And that's because they are the best. Whether you are a seed stage startup trying to land your first enterprise customer or a unicorn expanding globally, WorkOS is the fastest path to becoming enterprise-ready and unblocking growth. It's essentially Stripe for enterprise features. Visit WorkOS.com to get started or just hit up their Slack where they have actual engineers waiting to answer your questions. WorkOS allows you to build faster with delightful APIs, comprehensive docs, and a smooth developer experience. Go to WorkOS.com to make your app enterprise-ready today. [SPEAKER_01] One direction I want to get into here is this idea that you talk a lot about, about micromanaging being actually really important and powerful. So there's this image that's floating around Twitter that I don't know if you've seen. I'll show it on the screen as I'm describing it, and hopefully you can visualize it. It's a functional system versus a dysfunctional system. A company that's doing great versus not great. And there's this chart that goes up to more functional that is basically unkind truth, and then another unkind truth. [SPEAKER_00] Another unkind truth creates more functional systems. Kind lie followed by kind lie followed by kind lie leads to dysfunctional systems, something Steve Jobs is very famous for. In your book, you talk about mission-driven assholes. You want a mission-driven asshole. There are certain types of assholes that are great. Talk about just the importance of somebody being very direct in what it takes to build great products. When you're doing a 1.0 of anything, if you're doing anything that matters, and it's a 1.0 and it's a new category or it's a new device the world hasn't seen before, [SPEAKER_01] you have very few analogs that you can use to make data-driven decisions. [SPEAKER_01] And so if most of your decisions are going to be opinion-based decisions for a 1.0, you have to have one or two or a very, very small set of people who are charged with making the opinion-based decisions and can actually get you from a blank sheet of white paper or whiteboard to an actual 1.0 spec. [SPEAKER_01] Because if you try to do data-driven decisions all the way along, you're either not doing a differentiated product because you're taking data from another thing, or you're just getting bullshit data. [SPEAKER_01] So you're going to have to figure out how to get opinion-based decisions to happen. [SPEAKER_01] And that means you have to have, for lack of a better word, tastemakers. [SPEAKER_01] This is what we are doing. We are the person or the team who is going to make those opinion-based decisions. Of course, some people aren't going to like it. And it's going to be like, I'm sorry, this is a benevolent dictatorship. This is what's going to happen. And this is the vision. And we don't know what we don't know until we ship it and we get opinions from the users. Now, it's very different when you do this in a B2B context versus a B2C context. And so the hardest environment to work with it when you have these opinion-based decisions is in a B2C context. Because you have to see these decisions in the full light. And a consumer does. They have to see it from the marketing, from how they discover it in the marketing, the key feature sets, the ability to use the product, all of these different things, for them to actually come up with an opinion of what they like and what they don't like and being able to critique it. And if you're doing a 1.0 and the world hasn't seen it, you're not going to get that from consumers, ever. You have to ship it. And you have to build the entire ecosystem so those consumers see it in the fullness, so that when they do the evaluation and they spend their own money, then you're getting real feedback. When it comes to consumer, atoms-based products, with services or not, whatever it is, you have to build the entire thing and visualize the entire thing to be able to make those opinion-based decisions. And so you need a small team who's looking at the marketing angles, the engineering angles, the sales angles, all those different things to go, okay, that's the way we're going. And there's only so many ways you can do it because the rest of the team doesn't see this either. And so you have to be very articulate about what that opinion-based decision is made for, why, how it might affect marketing, how you do it, and make sure the team understands it. Now, if the team is just fully against it, well, then maybe it has to be unkind. But hopefully, if you've done a good job and you really have an informed gut and you can articulate that, And so you need a small team who's looking at the marketing angles, the engineering angles, the sales angles, all those different things to go, okay, that's the way we're going. And there's only so many ways you can do it because the rest of the team doesn't see this either. And so you have to be very articulate about what that opinion-based decision is made for, why, how it might affect marketing, how you do it, and make sure the team understands it. Now, if the team is just fully against it, well, then maybe it has to be unkind. But hopefully, if you've done a good job and you really have an informed gut and you can articulate that, you can get everybody moving in the same direction, even if it is risky. You're right. You got to know that you got to take risks because most people in those other functions, they don't want to take any risks. And so there's someone who's got to be the target, right? And today, in many contexts, people go and hire consultants, right? They go and hire, okay, we're going to do a user study, we're going to do all this. And they don't have the user studies and have the full context like I was just describing. They don't go buy the product and they don't what have you. And then they get data. And that's because the leader or whoever's in there, a board maybe, it's like, we need data to make sure this 1.0 is going to be a success. And I saw this so many times at all these major corporations. So they're just covering their ass with data and not really doing the hard work of saying, I'm going to make this decision and we are going to select this. And yes, I might be wrong. Or we, as the opinion-based decision makers, are wrong. And we will correct it later. And we'll take the heat for that. So that's the great product manager, a great person who's leading this thing has to understand that that's what they have to do if they're really doing something innovative. [SPEAKER_00] So what I'm hearing here is just the power, especially in a consumer product of a singular vision of a singular leader that drives it, that basically relies on their instinct and their taste and their experience. And a lot of informed judgment from all the experts around asking questions, refining, prototyping, these kinds of things to then make a decision. So it's not just like I woke up one morning and this is now it's, we're going this direction. No, there's a lot of work to get there. I want to come back to the idea of micromanaging, which a lot of people, that word is a bad word. Don't be a micromanager. You advocate for creating great products. You need to actually be really micromanaging. Just speak to that. What do people miss about the importance and power of micromanaging as a leader. You know, we've heard the term sweat the details. It's micromanagement of certain details. And then there's the kind of hands off of other details. You have to really understand the blend of which things really matter, which things don't. When I was early on my career, I thought everything mattered. And I drove everybody nuts, drove myself nuts. The people who hate it, and it became my thing, it became like, everybody's got to do it the way I would do it. It's like, no, no, no, no, there's only a few key things, mostly for the customer, or maybe some certain things for manufacturing or cost or something where it needs to really be very clear, a long-term vision, but then you can delegate other things, but certain pieces of it, you really need to. And when I mean micromanage, it means micromanage the decision, not necessarily the operations of doing it, making sure you're getting the data. Like we did with the keyboard on the iPhone to make sure we're getting the right data to help us get the informed gut to make that opinion-based decision. And so it's the micro specification and delivery of those certain data pieces that you need. And maybe it's also to get out of a crisis, or maybe it's a system level thing where you have to worry about this thing at the low level changing up here and here. And like we could do that, but only if they do this and this is like, okay guys, we're going to fix all of those things at once. And you have to micromanage it because everybody wants to find excuses why they can't do that or they can't do that. So you have to ask why a lot. So it just, and it's all in service of some really key detail that needs to get delivered or some innovation that needs to be delivered. Just like I said, the keyboard, we had to do the hardware. We had to do the software. We had to do the filtering. We had to do how it was, how the graphics were done on the screen. So you had all of these layers that had to keep constantly changing and adjusting. And sometimes you have to micromanage that because there's just too many variables and someone has to be the orchestrator of this huge orchestra of many different components to make it all come together and be harmonious. [SPEAKER_00] I want to go in a slightly different direction. I want to talk about the Nest thermostat, I'm assuming. The thermostat. Yeah. What versus what the bird, a bird. Well, there was many other products. [SPEAKER_00] All the other products. Right. Yeah. Man, the smoke alarm. Is that discontinued by the way, the smoke alarm? [SPEAKER_00] Yeah. I just, oh, you just, what do you, why do you want to stab me in the heart? It feels like, oh, that was one of the toughest products I and our team and Nest and other people who were on the team have ever made in their life. Because it's so hard to make something like that. There's so many constraints. That's an ultimate constraint kind of product to actually innovate in. [SPEAKER_00] Right. [SPEAKER_00] Yeah. [SPEAKER_00] I, yeah. [SPEAKER_00] Man, the smoke alarm. Is that discontinued by the way, the smoke alarm? [SPEAKER_00] Yeah. [SPEAKER_00] I just, oh, you, why do you want to stab me in the heart? It feels like that was one of the toughest products I and our team and Nest and other people who were on the team have ever made in their life. Cause it's so hard to make something like that. There's so many constraints. That's an ultimate constraint kind of product to actually innovate in. So yes, it unfortunately is discontinued, but it was the best product in the space for a decade. And no one changed it. No one invested in it. It is so crazy. It pains me and it pains everyone. People are like, they're expiring around me. What do I do? And I'm like, I wish I could tell you there's something better. No one replaced it with something better. It's mind boggling that the number one product with revenue and everything, you're just going to toss it away. Why do you think that's happening? Cause it was an orphan. It's just not a big enough business within Google. [SPEAKER_00] It's a stepchild. [SPEAKER_00] No, it was a stepchild. They really had to pour a lot of love, a lot of attention, a lot of love to make something that was that crystalline. And it had to be well-formed and nobody really wanted to put in the effort. So they probably like, who wants to do this? Who's excited by it? Nobody was probably excited. And they just said, okay. We'll just, it's not that big a deal in the end of the day where if it was invested in, I think it would have been a critical piece of the next generation AI assistant in your home. [SPEAKER_00] I want to hear more about that. And just on the smoke alarm point, my favorite feature, I was at an Airbnb once and it just started instead of just straight to beeping, it was just like, I'm about to make a loud noise. Like just warning you that it's going to get very loud. We call it heads up. I love that feature so much. It's about to get very loud. So good. You know, it says you don't get PTSD every time. Cause you know, when a smoke alarm, you're like, okay, everyone calm. We're going to do this now, especially when we're doing tests. We're like, when we're, cause people are supposed to test themselves. Everyone stay calm. It's going to be good children. We've got to do this one thing and we'll get through it. Don't worry. [SPEAKER_00] And it's so good. And I was like, thank you so much for telling me. There was a lot of love and care in that thing. So I was going to ask specifically about the Nest. The Nest thermostat is still the best thermostat out there. [SPEAKER_00] I use it everywhere I go. It's just the best. The app hasn't evolved. Nothing's changed for a long time. Is it the same reason you just described is just not a priority? Stabbing the heart. Yeah. [SPEAKER_00] You know, the whole organization was a stepchild for whatever reason. There was cultural mismatch. There was probably a business mismatch. I think if Nest was around and alive today like it was, it would have a whole different thing when Google and Gemini and Google IO was what yesterday or the day before. It would have been one of the centerpieces of what you could do because AI needs context. AI needs a lot of context. And in a home, you want to make everything very seamless. And the way you get best context is by having sensors properly placed around the home that don't necessarily invade privacy, but allow you to pick up a lot of comings and goings and who's who in the room and your voice and these kinds of things. Audio. No, voice. To be able to give AI context so that you can have an anywhere assistant that really knows what's going on. [SPEAKER_00] Is there space for someone to launch the new Nest, do you think? Oh, for sure. For sure. People keep asking me, what are we going to get? It's like, no, absolutely. It's now's the time. If it isn't already happening. I'm actually getting business plans of people who are like, hey, you know, is this interesting to you? Want to invest in it? You want to come and help us build it? This is like Nest 2.0. So they're trying to do stuff like that at Ring. I don't think very, not very privacy focused, but that's what they're trying to do. That was our vision in the beginning, to tell you the truth. That's how we were like, you're going to need lots of context. Because remember, the Nest Learning Thermostat wasn't the Nest AI Thermostat. It could have been called that, but we couldn't call it that in 2011 because people would have freaked out. Now, you would have called it the Nest AI Thermostat, right? And people would have bought it. And so we knew what AI was, right? So since 2010, that was one of the foundational pieces of the company was AI. And so that's how we were able to do a lot of the things we were able to do. But it was much, obviously not LLMs, but smaller stuff. And we said, okay, we can see this world growing and this AI system. And then voice assistants came. And then there was Alexa and all that stuff that happened later on in 2013, 14, 15. It's like, okay. And that was Gen 1. And people would have bought it. And so we knew what AI was, right? So since 2010, that was one of the foundational pieces of the company was AI. And so that's how we were able to do a lot of the things we were able to do. But it was much, obviously not LLMs, but smaller stuff. And we said, okay, we can see this world growing and this AI system. [SPEAKER_01] And then voice assistants came. [SPEAKER_01] And then there was Alexa and all that stuff that happened later on in 2013, 14, 15. [SPEAKER_01] It's like, okay. And that was Gen 1. But we could see this kind of blossoming. And, unfortunately, in the fullness of time, it takes 15 years more from the time Nest launched for that vision to come to fruition. But it is there now. And if Nest was pitched that way, we were just too early. [SPEAKER_01] Let me follow this thread around how to know what to build and how you come up with ideas. So I emailed a bunch of people that know you. I asked them what to ask you. One of your colleagues, Herman Hauser. Herman? Oh, Herman Hauser. [SPEAKER_00] Yeah. [SPEAKER_00] Herman Hauser. [SPEAKER_00] So his question you wanted me to ask, you said, ask him how he decides what is worth building. [SPEAKER_00] Okay. [SPEAKER_00] Well, Herman's agree. I've known Herman since 1987, probably before most of your listeners were even born. But Herman, just for context, Herman was the creator of Acorn Computer, which was the Apple 2 of the UK back in the 70s. And then he created with his team, the ARM processor. So Acorn Risk. So ARM means Acorn Risk Machine from Acorn Computer. And so he was the founder, one of the founders of ARM. And so I was talking about processor. Anyway, so that's, so Herman and I go way, way back. So the thing is how do you solve your, figure out what is worthy to be built and what's not? So the first thing is I start from pain. You know, some people start from other directions. I always start from pain. That's what I learned is what are people's pain right now? Or you can see it on the horizon. They're going to have pain and not too far away. But how do you solve for that pain? And typically those pains were because when those products were created, either it was an unintentional consequence or it was a limitation of the technology at the time it was created. And it kind of just evolved, but it never revolutionized itself. And so it just evolved in that same pain, but it gave you enough of a painkiller for the other problem that having this new pain was worth it. And so I always kind of start with, okay, where's our current pain and are there new technologies to solve that pain? And like in the thermostat case, Nest was we could use AI to learn. So it can learn when you're there, when you're away, what temperatures you like, so you don't have to program it so you can save energy. So the big pain was being either comfortable or saving money because 50% of your energy bill was in this heating and cooling unit that you hated, the interface. You didn't know what it was. You just paid the bill. And so it started from that pain and said, okay, well, programmable thermostats weren't innovative, but they weren't used. A lot of them had it because the energy company would give you rebates for it, but no one knew how to use it because it was arcane. It was programming a VCR. And so what I said was, oh, wait a second. What if it could learn your patterns? [SPEAKER_01] And that was AI. [SPEAKER_01] And so now let's put that together in a much cooler looking, attractive package that costs five to six times more than the things that you're buying today. But that was the crazy opinion-based decision was, okay, yes, it's going to cost $249, but it's going to save you $800 to $1,200 a year. So it could pay for itself literally within a year or two. So that was the big idea. And AI was brought to bear on that old problem and hopefully solved it in a new way. [SPEAKER_01] So it starts with the pain, long-time pain, maybe habituated away pain that you have to discover and new technology bonded with that to then bring innovation in, revolution in, and then redefine the space in a way, which is what we did, which is not with just the product, but how you installed it. [SPEAKER_01] You know, it was always installed by third-party installers as opposed to yourself. [SPEAKER_01] How you bought it, which was you bought it through the installer. [SPEAKER_01] You didn't buy it in Best Buy or somewhere else. [SPEAKER_01] So it was we had to reinvent many different pieces of the puzzle to get Nest to be the Nest. [SPEAKER_01] It wasn't just the product. [SPEAKER_01] It was all the other things. [SPEAKER_01] Just like the iPod wasn't the iPod or the smartphone wasn't the, or the iPhone wasn't the iPhone. It was the iPhone plus the app store, iTunes plus iTunes, iPod plus iTunes, and then the iTunes music store. So you have to think about the full, the full thing you're trying to build, not just the one piece, even though that's what you might remember. You have to remember it's a system that you're going to innovate with. [SPEAKER_00] So these two part kind of formula you shared here, the pain and new technologies. [SPEAKER_00] The second part is really interesting. [SPEAKER_00] Essentially it's like, what's the why now? [SPEAKER_00] What's the new tech that has emerged that now allows us to solve this pain? [SPEAKER_00] It feels like that's a core part of it. [SPEAKER_00] Okay. [SPEAKER_00] It's because it's interesting because when you talked about the iPhone keyboard, it was a similar story of like, okay, we can actually do this virtual keyboard for the first time in history. [SPEAKER_00] Right. Exactly. It could be because of multi-touch. That's really what it was. And then we were just on the verge of having fast enough processors. Right. And we were just on the verge. So it wasn't, you know, if you look at the iPhone or you would nest iPhone or iPod, you can see where all these technologies were just coming to light. So in the iPod, it was just now mass storage that was portable and battery operated. [SPEAKER_01] That was really what it was. [SPEAKER_01] And it was also MP3s or digital music. [SPEAKER_00] Right. Exactly. It could be because of multi-touch. That's really what it was. And then we were just on the verge of having fast enough processors. Right. And we were just on the verge. So it wasn't, if you look at the iPhone or the iPod, you can see where all these technologies were just coming to light. So in the iPod, it was just portable mass storage that was battery operated. That was really what it was. And it was also MP3s or digital music. [SPEAKER_01] Right. [SPEAKER_01] Those were new, and we also had high density. [SPEAKER_01] We were the first products to have lithium ion or lithium polymer cells. [SPEAKER_01] So it was new battery technology, new portable mass storage, and this new generation of digital music. [SPEAKER_01] And we had ARM processors. [SPEAKER_01] Right. [SPEAKER_01] And really low power. So all of those things had to come together to do that. And then on the iPhone, it was multi-touch, but it wasn't just that. It was also the fact that now we had WiFi everywhere. And we knew that 3G was coming. We only had 2.5G when that was, and that was very slow, but we had WiFi. So it was, and we had cameras, right? Digital cameras. We had the digital camera. We had digital video, which we had YouTube at the time. [SPEAKER_01] So it was all of those things just on the verge to say, this is what's going to be very different than what just came before it. [SPEAKER_01] A BlackBerry, which was really just a texting machine and nothing else. [SPEAKER_01] I'm going to close the loop on your advice on finding a great idea. [SPEAKER_00] I'm curious about the flip side of when it's still not good enough. So there are so many gadgets out there that are solving some pain point. Maybe there's a new technology that they integrated, but they're still not a big business. It's not a real company. What's the threshold? What's a sign that this isn't big enough? [SPEAKER_01] Well, the iPod wasn't big enough. [SPEAKER_01] It took three generations of the iPod before it became successful. Everyone, if they remember iPod before iPhone, because iPhone swallowed everything. [SPEAKER_01] It's like the black hole of everything. But the iPod, the first generation was only successful with the Mac geeks and the Mac geeks were less than 1% of the market. And then the second generation was also that way. So when we got there, we'd sell everything we could for the most part in the first quarter. And then it would die because it was just the Mac aficionado, the loyalists who'd come and buy everything. And it wasn't until the third generation where we made it work on Windows. And we had the iTunes Music Store, did it actually start to take off? So sometimes you have to say we're on the right thing, but we need to make some changes to get this market going. And that was a real opinion-based decision to, the team that I was running, we were really clear that we had to have Windows connectivity out of the gate or just after the first iPod shift. And Steve said, over my dead body, no way, this is going to help us sell more Macs. So then, we're making the second one. We're going to keep it with Mac only. We just got to fix a few of these things. And then all of a sudden it'll take off. And it didn't take off. So then it was a long story about how we finally got Windows connectivity, but there was always this skunk works project behind the scenes doing that. I did the same thing with stylus. [SPEAKER_01] Steve never wanted a stylus on the iPhone or the iPad. He never wanted it. He's like, the finger is good enough, and when we can't do it with the finger. And I'm like, we're going to have the B2B context and we're going to have form filling and people are going to write. And he's like, I don't care. That means we're going to get to Windows pen. Because he thought it was going to be like Windows pen, which was, you had to use the pen for everything as opposed to using your finger. So it was like, I want it finger dominant, not pen dominant. But that's what he was saying. But then when we added the stylus, which was another skunk works project, all of a sudden it came out and was like, well, we had to have stylus. Right. And now it's a big feature of the product. Not everyone uses it, but it is a big feature for certain professionals who really want that: artists and hobbyists and stuff. And so sometimes you have to have those skunk works things that, even if the opinion-based leader doesn't like it, you're like, that seems like the right thing. Maybe not right now, but you can see it on the horizon. So you just keep working on those things. But we had to, the iPhone wasn't a hit right away. It was like, oh yeah, I worked on AT&T and it was 2.5G and it was this and that. And it only worked in the US, so we had to get multiple versions till we got out. And in my book, I have it, and it's called "Three Generations." I think it's three generations. Everything needs three generations. [SPEAKER_00] I've learned: you make the product, you fix the product, then you fix the business. So there's no, I've never seen anyone get it all right the first time. You would like to, but you get close. But make the product, fix the product after you get customer feedback, and then fix the business, which means make the margins. On the first iPods, we weren't making any money. First iPhones, we weren't making any money, right? The second iPhone or S and second iPod. Okay. We started getting a little bit better numbers, but we got the features more or less dialed. Third one was like, okay, Windows. So you have, there's no, I've never seen anyone get it all right the first time. You want to, you would like to, but you get close, but make the product, fix the product after you get customer feedback and then make the business, which means make the margins. On the first iPods, we weren't making any money. First iPhones, we weren't making any money, right? [SPEAKER_01] The second iPhone or S and second iPod. [SPEAKER_01] Okay. [SPEAKER_01] We started getting a little bit better numbers, but we got more or less the features dialed. [SPEAKER_01] Third one was like, okay, windows. [SPEAKER_01] We got the margins. [SPEAKER_01] We're getting up the volume. [SPEAKER_01] We got all the right. [SPEAKER_01] And go right. [SPEAKER_01] Reliability, whatever else it had to be. [SPEAKER_01] So you need to stick with your idea, even if it's not necessarily going the first time, unless there's something really severely wrong about whatever it was. You have to restart, but sometimes you have to hang in there. And same thing with Nest, we had to hang in there with two generations of the smoke detector and a few generations of the thermostat before we made the business work. Right. Not just make the product work. There's so many directions I can go here. [SPEAKER_00] One that's interesting is how often Steve Jobs was actually wrong. [SPEAKER_00] Oh yeah. [SPEAKER_00] You had to, you're like, takes a year still. [SPEAKER_00] Okay. [SPEAKER_00] Finally. [SPEAKER_00] We all were wrong at certain times, but you know, it's when you hit those, you, when you hit it big, when you get the right ones, they overshadow all the other stuff. But that's how you have to try and iterate. You know, Jeff Bezos says the same thing. I believe in the same thing. You got to fail a few times till you get to, till you find your way. And but you only fail if you stop. If you keep iterating, keep going, then that's not failure. That's called learning. [SPEAKER_00] The other interesting part of the story you just shared here, which was one of my favorite stories in your book, actually. [SPEAKER_00] The fact you implied this, but basically the first iPod was you had to have a Mac to use it. [SPEAKER_00] And the idea is it would, we want, you want to sell Macs. [SPEAKER_00] This is a way to get people to buy Macs. [SPEAKER_00] And it's like, the way you tell it is basically this ended up saving Apple eventually not selling Macs, but people buying iPods. [SPEAKER_00] And that was like the big part of the business. [SPEAKER_00] Yeah. The mantra was Steve, you know, if we don't have windows connectivity, the iPod doesn't cost $349. It costs $3,000 because you got to buy a Mac and you got to move all your digital life over to it and everything else. People are not about to take a risk on this company. That's almost bankrupt for $3,000. So how are we going to do that? Okay, let's make sure it is only $349 and that they can try it. And once they try the brand, they go, oh, that's pretty interesting. Maybe I should try other products from this company and give them a shot. Because that was just such a sublime experience. And that's how it all changed. And that's how iPhone was able to be created. Because without the iPod, I'm pretty sure there would have been no iPhone. There would have probably been no Apple because it was close to bankruptcy. [SPEAKER_00] Wow. That's crazy how close it was to that if some of these decisions went the wrong way. [SPEAKER_00] Yeah, very close. Remember, there was no retail back then. Apple retailers, none of that stuff. You know, most people don't know how on the ropes Apple was back in 2001. So many stories. [SPEAKER_00] But I want to come back to the customer journey thread that you touched on, which I think is really important for people listening to this podcast to hear. [SPEAKER_00] Something that you reinforce again and again in the book. [SPEAKER_00] And you have this awesome image that we're going to show of the entire customer journey. [SPEAKER_00] And the your point that you make is so many product builders focus on building the product and think, build the best product we're going to win. [SPEAKER_00] And you have this very important advice of there's so much more to it. Talk about, especially the marketing piece. Talk about what you think builders don't really get, even though they hear this advice in many ways. [SPEAKER_01] When we build products, we define products when we build them. [SPEAKER_01] We have a good sense of the context when we are defining those things. [SPEAKER_01] We are living in that world. [SPEAKER_01] Okay. [SPEAKER_01] And so we're like, oh, we're like this. [SPEAKER_01] And these are our issues. And this is who we are. And you know, maybe you put on personas. You know, we would strip out and figure out who our target customers were with their personas. You know, is it a single mom with kids or is it a dual income, no kid family or is it senior citizens or whatever? And we would come up with these personas and we would live inside them as we're thinking about the product. But you have to also remember that these people don't live in those that they live in the context, but they're not aware of your product in their context. And so you have to bring it home to them and meet them where they are. And so your marketing, your website, your Instagram ads, your whatever, your earned, owned and earned and owned media that you do. You really need to put that, your product in their context and make the visuals and make the words and everything sing to them. And if not, they're not going to get it. Right. And so too many times we just say, oh, if we just make the perfect product, no, you have to put it all for a consumer thing specifically. And it's also really good for a B2B product as well is make sure you understand your customer. And they go, you know, and when you say the right word, they go, oh, they get me. Oh, I want to listen to these more. And this is before they ever got the product. You need to get them to convert in some way. And they need to hear that you've already thought about their issues or you know, and you're living in their shoes. And they're like, yes, yes, yes. More of that. [SPEAKER_00] Is this an emotional point? [SPEAKER_00] Is this a rational point? And it's also really good for a B2B product as well is make sure you understand your customer. And they go, and when you say the right word, they go, oh, they get me. Oh, I want to listen to these more. And this is before they ever got the product. You need to get them to convert in some way. And they need to hear that you've already thought about their issues and you're living in their shoes. And they're like, yes, yes, yes. [SPEAKER_01] More of that. [SPEAKER_01] Is this an emotional point? [SPEAKER_01] Is this a rational point? [SPEAKER_01] And you're weaving this tapestry to get them to come to some kind of trial or purchase or conversion of the product. [SPEAKER_01] And the best way to do that is word of mouth, right? [SPEAKER_01] By other early adopters. [SPEAKER_01] But you've got to do the same thing for the early adopters, but the early adopters who other people trust to talk to. Because a lot of other people who are late adopters, they know, oh, that's wacky George. He tries everything. And then, no, no, no. But if so-and-so's tried it, oh, I should take notice of that. Right? And so what you want to do is make sure you understand your customer and where they are and who you're trying to reach. I also updated the crossing the chasm graphic in the book saying how we go about this in your product development. Because you really have to think about who your target user set is and your target marketing based on the version of product you're in and how you're going to get those higher and higher volumes. And it really means speaking to the context. So maybe when you first ship, you can speak to those early adopters and you can put in enough words that they're going to convert. But then the second version of the product, you're getting later adopters and you've got to speak in their language. And the third set of adopters who are really laggards, you've got to really speak to them and go through that. And it could be totally different. And so this was a very interesting story that was so emblazoned in my mind. Back in 2001, two, three, when Apple had no presence outside of the U.S. Apple was really selling in the U.S, some Canada and some in Japan, but that was it. And that was the max. So we were selling iPods into those areas. And so we had the early adopter and then we had some other language. And then by the third, fourth version of iPod, we had some really refined language for those late adopters. So then we said, we're going to go back and get a push into Europe. We're going to get, because iPod hadn't taken off in Europe. So we're going to push iPod into Europe. And so we were on, I think the fourth generation or something like that. And so what did we do in Europe? We ran the same marketing as we were doing in the U.S in Europe. And the thing is it didn't resonate with the early adopters. It didn't resonate with the later adopters because we didn't have the same messages. We were going for a different set of people. And we're like, ding, ding, ding, ding, ding, sales aren't working. We got to change the marketing. We got to meet those Europeans where they're at. Because they're slower to adopt technology versus it starts with the coast and goes inward in the U.S. Right. And so we're like, oh, we got to change things up. And so, you know, sometimes when you get to new areas, you have to rethink your marketing for that area and remember to meet them where they're at and where, if it doesn't have an installed base for word of mouth, you're going to have to get that word of mouth started. So work with those people to get that going. Now it's different with all software products and all these things. And many products can go global right away, but marketing, you still got to tell a story and you know, so it just reminds me that even though we've maybe compressed the time for some pieces of the adoption puzzle, because we can distribute faster, doesn't mean we can. The awareness can get accelerated and we can get people to intelligently understand what this product faster. If we just say the words of somebody who might've known about the product for three years. [SPEAKER_00] I got to ask about maybe the most famous tagline of all time. [SPEAKER_00] When a product was launched "a thousand songs in your pocket," is there a story behind that? I think back in the day at Apple, and I think it's still that way, maybe it's changed now, but back in the Steve days, there were different functions of Apple. And because they were all lean, because the company was only 4,000, 5,000 people, and it was already doing Max and everything, each function was very functional. And so the marketing didn't get into the engineering and the design folks. [SPEAKER_01] It was like separate. Steve was the hub and he was in each of them putting them together. He was the opinion-based decision maker. And so when we heard the tagline for the first time, I was like, that's genius. Now, how long that took, what was the behind the scenes? We were just a tiny team when we were getting this done in ten months. So everybody was just running for it. Right. Whereas with iPhone, we had discussions of it. Should we call it the iPod Phone or should we call it the iPhone? Because Cisco had the iPhone back in the day and there were copyright issues and trademark issues. And so we were into that because it was also a two and a half year development and we were betting the farm and we were going to cannibalize iPod. Right. So there were a lot more discussions, but in those early days, it was everybody running, literally, less than nine. So everybody was just running for it. Right. Whereas versus iPhone, which was, we had discussions of it. Should we call it the iPod phone or should we call it the iPhone? Cause Cisco had the iPhone back in the day and there was copyright issues and trademark issues. And so we were into that because it was also a two and a half year development and we were in some, and it was betting the farm and we were going to cannibalize iPod. Right. So there was a lot more discussions, but in those early days it was everybody running in literally not less than nine. It was really five to six months. Everything got done. Cause we really started it in April and it shipped in end of October. [SPEAKER_00] So I think one of the core takeaways from what you shared here is even if you may have the perfect product, the marketing may be the gap that if something isn't working, it may. Absolutely. Absolutely. And the thing is, I think we're starting to see that the cracks of it. [SPEAKER_01] It might be more than cracks now with OpenAI. What is it? It's like, oh, it's your answer machine, whatever. You're like, well, what does it do for me? And now I got to keep paying you. It was fun as a demo. And if I, but what am I using it for every day? And like, oh, Claude, it does Claude code and it does code, and then what happens OpenAI is like, oh, we have codecs now. But then they were Sora and they were this and they were that. We're going to do sex chat. We're going to like, what are you? And so it's like, oh yeah, you're the greatest. You know, that's game. Everyone went out and bought Netscape Navigator or whatever it was called and then all of a sudden it evaporated. Like, well, what do I use the net for? I got the tool to get onto it, but what do I use it for daily? And what's that? And I had to develop. And so OpenAI is now shifting like, oh, we got to get product teams and we got to start product marketing. We got to, so you know, that is to me, that's marketing. [SPEAKER_01] But if you start, if you are already thinking about the marketing, you're already going to start thinking about the product. And that's the thing is when you're just thinking about the product, you're like, and it was really just a technology demo that went viral and they're like, oh yeah. And they still keep winning on that. They never put product in till it was too late. Now Anthropic's where they are and valued more and higher revenue and all the other stuff. So you know, it just, it just, even if it's a software only product, yes, there's lots of hardware and servers and all that other stuff. You need to think holistically and you need to think about the entire customer journey, the marketing, the sales pieces, the distribution pieces, the product definition, the messaging, the target markets early on. You can't leave it till later and then get it. [SPEAKER_01] Yeah. And then back calculate it. And that's why I say you should really make the press release before you more or less start the project. Yeah. There's a whole chapter on that. We had the found the Amazon's also very famous for that. A whole book on working backwards. That goes really deep on this approach. But the thing is, the thing saying working backwards, would a movie be created that way? Is it called working backwards? When you say I'm going to make a script and I'm making the treatment and I'm going to really know what it is. I'm gonna know what the characters are and how I do character development. Is that really working backwards? It sounds like it's backwards. It's like, no, that's the way you do it. It's just because it's so technology led and technologist. And this is what I thought when I was 20, I was like, yeah, we're, you know, now it sounds backwards. It's actually, no, that's actually insane. It's not working backwards. It's just an insane way of working. Come on, let's really think through this. [SPEAKER_00] I, it says so much that you, as one of the most successful, insightful builders are so into marketing. I think that's a really important takeaway for people. Just how obsessed you are with that piece of building that I think a lot of builders don't think about at all. Well, when you live in that world and you live in the customer, because you're coming from a customer point of view. So you have to see the lens and the customer only sees what they see through the lens of marketing and sales. Right. And so you have to be in their shoes and you go, okay, when I do the press release, I can only have three or four key features. After that, it becomes gobbledygook for a customer. So you're like, okay, what are those three or four things? Okay. What is that? That's what we're going to focus on. And so, no, we're not going to add five more features. That's not going to make it sell better. Right. Or oh, we're going to cut these two features and ship it. It's like, well, wait a second. We cut out two of our three key tent pole features. How are we going to sell that anymore? So it's a holistic design. It's not, you know, because we think the technology, the technology is in service of the customer. Not we're going to jam the technology down the customer's throat and they're going to figure out how to use it. There's too much noise that you've got to make it frictionless and you've got to fit it in. Right. Or, oh no, we're going to cut these two features and ship it. It's like, well, wait a second. We cut out two of our three key tent pole features. How are we going to sell that anymore? [SPEAKER_01] So it's a holistic design. [SPEAKER_01] It's not because we think the technology, the technology is in service of the customer. [SPEAKER_01] Not we're going to jam the technology down the customer's throat and they're going to figure out how to use it. [SPEAKER_01] There's too much noise. You've got to make it frictionless and you've got to fit it in their world and see from their point of view. Oh, that's why I need. General Magic was the perfect story for that. [SPEAKER_01] I don't know if your viewers should definitely watch the movie General Magic. [SPEAKER_01] We made the iPhone 15 years too early. And that was a classic case where we were just making things that were really cool. And nobody needed it. [SPEAKER_00] That documentary is incredible. [SPEAKER_00] It's such a... I like the very young version of you. [SPEAKER_00] Very different than probably people won't recognize me. [SPEAKER_00] You have a whole chapter about just not overworking in your career based on that experience. Which General Magic was for me. I am so excited to tell you about this season's supporting sponsor Vanta. [SPEAKER_00] Vanta helps over 15,000 companies like Cursor, Ramp, Duolingo, Snowflake, and Atlassian earn and prove trust with their customers. [SPEAKER_00] Teams are building and shipping products faster than ever thanks to AI. [SPEAKER_00] But as a result, the amount of risk being introduced into your product and your business is higher than it's ever been. [SPEAKER_00] Every security leader that I talk to is feeling the increasing weight of protecting their organization, their business, and not to mention their customer data. [SPEAKER_00] Because things are moving so fast, they are constantly reacting, having to guess at priorities, and having to make do with outdated solutions. [SPEAKER_00] Vanta automates compliance and risk management with over 35 security and privacy frameworks, including SOC 2, ISO 27001, and HIPAA. [SPEAKER_00] This helps companies get compliant fast and stay compliant. More than ever before, trust has the power to make or break your business. [SPEAKER_00] Learn more at Vanta.com slash Lenny. [SPEAKER_00] And as a listener of this podcast, you get $1,000 off Vanta. [SPEAKER_00] That's Vanta.com slash Lenny. I want to talk about something else around the evolution of the product management role and builders. What's really interesting, going in a different direction, but it's all connected. I feel like you were so ahead on this idea that we are builders versus product managers, engineers, design. I have your book right here. It's called Build. And this is what everyone's starting to call product managers, people on product teams. I'm curious what you're seeing with that, this merging of these roles. Do you feel like everyone just becomes a builder and there's no more designer, engineer, product manager? Do you think they'll continue being these functions, but more merged? [SPEAKER_00] What are you seeing with the discipline of product management specifically? Well, the discipline of product management sits between all of these functional roles. Whether that's marketing, sales, distribution, sometimes manufacturing depends on what the product is. Engineering, obviously. And customer support. So when you sit between all of these things, those roles shift or change, especially depending on what it is you're building and that kind of thing. But you have to interpret what's going on between all of them and stitch them all together to make this thing sing. And what we're saying is, oh, I can today in the AI world, I can just make a prompt and all of a sudden it gets spit out and you don't know what all those little functions are. If you are not aware of each of those functions, even in the AI world, of what those things are, they have very clear definitions of certain points of view for the customer. And you have to consider them and to say that they're going to get washed away and AI is going to come up with it. It reminds me a lot of how software coding is getting done with something like Claude today. I don't know, maybe it was a month ago when the Claude source code leaked. Claude source code leaked. And everybody's like, oh my God, it leaked. And if you, at the time, and me, I don't know, maybe they changed it. Maybe they didn't. But at the time, Dario was saying, you know, 90 to 100% of all our code's written by Claude. And we just monitor it and watch it. And we're like, oh, well, that's really interesting. And then the code leaks. And if you looked at the code, anybody who looked at the code, who's a real software architect and engineer, threw up. They were like, it made what? They're like, this stuff is brittle. Engineers were looking at this should be layered in four or five, actually 12 or 15 different sub functions. This is the main loop of Claude, of Anthropic's Claude. The main loop, not just something off in the. This is the main loop. And people are like, how can you do this? This looks brittle. It's unreadable. And they're like, well, the AI knows it. But when you think about it and you have to maintain it, you can have an agent make code for you and it could work and it could test. But is it secure? Is it maintainable? If there's something going wrong, can you roll things back and understand what's going on? There's so many other aspects to writing code and delivering a product that you still need humans in the loop. And so when I think of product design, I think of software code with AI. And when you look at AI, if it's not architecting things and it's not segmenting things and looking... But when you think about it and you have to maintain it, you can have an agent make code for you and it could work and it could test. But is it secure? Is it maintainable? If there's something going wrong, can you roll things back and understand what's going on? There's so many other aspects to writing code and delivering a product that you still need humans in the loop. And so when I think of product design, I think of software code with AI. And when you look at AI and if it's not architecting things and it's not segmenting things and looking at each of those things, there's software architects and then there's software optimizers. And then there's just general coders and then there's security reviews. And if you don't have those different mixture of experts around the code structuring it so that subsequent generations can get better and better, it just devolves into this mass of things you don't know. You're getting short term gain for very long term losses. And that's called software debt, right? Technical debt. And everybody hates technical debt. So it might be fixing something, but it most likely is giving more technical debt, especially when you're at the high level. So now how does that map to product management? So if you're a product manager and you type this in and you get some results, but you don't have a really good marketer, a really good marketing communications person, a really good sales person, a real good channel sales person, a really good architect, a really good manufacturing manager, all these different things in this thing that you're getting, you're not going to be able. You might be able to make the first one, but when you go to version five, six, how does that work? You're building on a really crusty foundation and people are like, well, my AI is going to be smarter. It's not proven to do that. What's proven is if you properly architected code, Claude code go into certain sub segments or have Claude help you build the architecture. You modify, refine it, lock it in and say, just work on these few things. And when these more limited scoped things, yeah, you can make that work. And I think that's the way we have to consider how we use these tools in a product management capability as well. To just say, it's all abstracted away. It's all going to be better. And when you ask specific pointed questions, you want this thing fixed in your marketing thing or whatever, and then they're going to like, well, the AI should just figure that out too. It's like you have given up so much. That's to me. Sure, you can write code, but there's going to be the difference between H and M and a luxury brand. You can go get certain things that look like that and copies that and edit, but it doesn't last more than one washing or one season and you throw it away. It's cheap. Or you go to the luxury thing and you pay more and it's crafted, it's handcrafted, and you know it's going to be around for a while. There is this dichotomy of fast and throwaway. We got fast fashion. We got fast software, but software, if you're going to build a real company, can't be throwaway. Maybe it can, but I don't think it can be if you're really going to do this because you get technical debt and you've got to start over again. So you've got to really understand how you're using these tools. And a lot of these things that these AI coders can do, agent coders can do, can make you incredible prototypes, do more prototypes to help you get that informed gut to say, we're going this direction, architect that in, and then work on the sub segments below it and all the expert systems and expert things that you need in each of those domains. [SPEAKER_00] And I think what you may also be saying here, which I think is really important is that because it's so easy to build, people can just build all these features and additions and the value accrues. You build something awesome and the product mind becomes more important to help push this stuff from just a sloppy, every feature, every checkbox to something awesome that people actually use. Right. Because at the end of the day, if you're building it for yourself, whatever, go have fun. But if you're going to build it and you want to sell it and you only need three key features to sell it to someone, it's going to have to be boiled down. It's going to have to be figured out because you're still selling it to a human who needs to understand it. Now, do you think you could vibe code flighty? Probably. [SPEAKER_00] Maybe now that flighty exists, you could. Right. [SPEAKER_00] Copy this. You could do version two of flighty, maybe vibe coding because you say, look at flighty, but the original flighty, that's to me, that's luxury software. Right. It was understood how the pixels are done. So you got to remember, is it version one or is it version two, three, four? Because an opinion-based thing on highly innovative, differentiated stuff, it doesn't have a model for that. There's not that stuff in there. You still need the very version one to be done. So maybe you can prototype with these things. So I could go on for hours, but that's just one old guy's point of view. I think it's really important. [SPEAKER_00] And this insight that as it becomes easier to build, the things that stand out are the things that are really well thought through and great and luxury, almost as you described. And you can feel it. Right. And you go, oh my God. And I'm like one of the biggest proponents of flighty. I'm always telling people flighty, flighty, because all the people in my sphere, they're all flying all this. I'm like, have you tried it? It's insane. That's just one old guy's point of view. I think it's really important. [SPEAKER_00] And this insight that as it becomes easier to build, the things that stand out are the things that are really well thought through and great and luxury, almost as you described. [SPEAKER_00] And you can feel it. Right. And you go, oh my God. And I'm one of the biggest proponents of Flighty. Because all the people in my sphere, they're all flying this. I'm like, have you tried it? It's insane. So you get the word of mouth and things take off because there has been that level of care and craft to it. And yeah, maybe a lot of the sub functions of Flighty could be built from cloud code or whatever. But the whole thing and the architecture and everything, I don't think so. And if someone hasn't tried Flighty, clearly download and play with it. [SPEAKER_00] This is an example of an amazing product. [SPEAKER_00] That's a really cool one. [SPEAKER_00] And it's all software. [SPEAKER_00] It's all software. Yeah. [SPEAKER_00] Something along these lines, as people hear you talk, clearly you are an amazing storyteller. [SPEAKER_00] And in your book, you often come back to the power of storytelling, the value of storytelling for product builders. [SPEAKER_00] What's one thing—why is that so important? [SPEAKER_00] Do you think? [SPEAKER_00] And two is, what's one tip you could give people to get better at storytelling? Storytelling, that's how we passed information down or got people to commit to doing something. Stories are who we are. We go to the movies for stories. We have books. We have all this stuff. It's just so essential to who we are because we like to be taken on a journey. And hopefully when you're buying a product or licensing one or subscribing, you're taking on a journey that meets your expectations or is better than what the expectations were set. It's outsized that. Dave Chappelle, when it comes to comedy and storytelling, the way he weaves it, he can weave a story for 20 minutes to get to the punchline. And you're just in it. Right. I just love his comedy as opposed to the punchline guys. [SPEAKER_01] There's something in our nature, human nature. [SPEAKER_01] We were told stories when we were a kid. [SPEAKER_01] We read or watched the same movies a hundred times when we were kids. There's something about being taken on that journey that we love. And people love to be educated that way. Your best college professors and high school teachers, whatever, they taught you why you should love certain math or certain physics or whatever and took you on a journey of why it mattered. And you're like, oh, now I get it. You can learn all the basics of how to do something, but that doesn't really tie it to something that's meaningful. And when you tie it to something that's human, that's when it becomes accessible for humans and it's relatable. That's when great marketing and great sales happens and great storytelling through the product design. That's even better. Right. Because it wasn't just perfuming this pig and putting some gloss on a bad product and saying, oh, try it. And then it doesn't meet the expectations. But when it sings from the depths of the product, like you were bringing up with the Nest Protect thermostat or the smoke detector itself, when we had all that and you could feel the love and care, that's when people go, oh, I love this and I want more from that brand or from that company or that team. That's what they want. And to get better at it, I've learned it because I watched my dad. He was in sales. Right. So I watched how he would sell Levi's and I would watch him and he wasn't always selling to sell. Sometimes he was convincing them not to buy something because that wasn't the best product they had. Buy this one instead. Actually, go to my competitor down the street because he was building a relationship and storytelling because these people loved what it was. So sometimes it's not just setting expectations and telling a story, but it's also saying, hey, maybe I'm not for you. And that's truth. That's also truth. And Steve always said, the best marketing just tells the truth. Now, it might put nice words around it, nice creative and everything, but it's telling the truth. And when I watched Steve prepare, and like I said, when we did the two and a half years with the iPhone, he was honing the story of the iPhone every day. He didn't give it to marketing. [SPEAKER_01] He knew what that thing was and what those key features were, and he would micromanage those features because he knew those were the things the world was going to take notice of. [SPEAKER_01] And he would refine the story and then tell other people who were really smart and say, I'm going to give you the pitch and give you the pitch. [SPEAKER_01] And he would refine, refine, refine. [SPEAKER_01] And when you saw him come on stage, it was because he had done it 100,000 times or at least 10,000 times. Right. And he knew it. Boom, boom, boom, boom, boom. It just came off. And I watched and learned from that. And that's what we did for the Nest Learning Thermostat. That's what we learned for each of those things. It was just that same storytelling over and over. What does it matter? Why does it matter? Why does it matter? And because too many times when we're technology led, we talk about the what. We don't talk about the why. And the why is where the storytelling is. Because you want to take a journey of why it matters to you. And if you're talking about the what, you're just talking to another geek. Love geeks. No problem. That's what we learned, we did for each of those things. It was just that same storytelling over and over. What does it matter? Why does it matter? Why does it matter? And because too many times when we're technology led, we talk about the what. We don't talk about the why. And the why is where the storytelling is. Because you want to take a journey of why it matters to you. And if you're talking about the what, you're just talking to another geek. Love geeks. No problem. I'm one of them. But we can relate on that level. But most people who are not in the technology world, they want a story and they want something that touches them in some way. [SPEAKER_00] One lesson I'm hearing from what you just described is telling the story over and over and refining it over time is where the best stuff comes from. [SPEAKER_00] Not just here. [SPEAKER_00] I just came up with this and it's going to be amazing. [SPEAKER_00] Yeah. Oh, absolutely. Because you need to tell it to other people who don't, to see if it resonates. I remember the number of times I told the Nest story before Nest came out because I was thinking, this is crazy. This thermostat thing, I'm thinking, okay, let me set up the virus of doubt, which was, do you know how much you spend on your energy bill every year for your heating and cooling? [SPEAKER_01] Don't you hate your thing? [SPEAKER_01] Now there's another way. [SPEAKER_01] There's another way to look at the storytelling. [SPEAKER_01] And this is, I put this in the book. [SPEAKER_01] Or no, I didn't put this in the book. We all have seen infomercials. They exaggerate everything and they show you all the pain points of it. And then they show how wonderful and easy it is to use whatever they're selling. And then it's easy to buy. And then it's easy to return. And it's overly dramatic. We all know it's wrestling. It's all an act. It's not real, but it is storytelling in a way. And not that you should do that because they overhype the expectations, but look at the techniques that are used, the psychological techniques, the emotional techniques to get there and then dial it back and go, okay, I'm going to do that but with truth, and that's when things start to go pop, pop, pop, or at least that's what I've seen. And so I always use that as another metric. And it's not just telling the story over and over. It's what story you are telling. And so I try to think of that as well, but not obviously clowny and cheesy, but it is a caricature of doing good marketing. [SPEAKER_00] I feel this is a really interesting lens into the press release first or working backwards ideas, create the infomercial first and go extreme. [SPEAKER_00] You could know what you don't want to do for sure. But it's a cool lens to go really far and then pull back the best parts and make it honest. I think we just came up with a really good idea here. I want to come back to the iPhone. So it came out almost 20 years ago at this point, right? It launched in 2007. [SPEAKER_00] Yeah, 2007. [SPEAKER_00] It's crazy as people are still trying to build the next iPhone, especially with AI. [SPEAKER_00] Everyone's just like, what's this? We've had this thing forever. [SPEAKER_00] Why has nothing changed? [SPEAKER_00] I'm curious. I imagine people ask you this question. What do you think the next iPhone may look like with AI? [SPEAKER_00] What's the device that you think emerges over time? [SPEAKER_00] Yeah. There's what it could look like long-term and what it could look like soon. A lot of people think, okay, there's the long-term thing. And when we can trust the models and when they have memory and when they do this stuff, man, we're still going to need a display. Sorry, people, unless we're plugging it into our brain like a BCI brain computer interface, or there's some laser thing going into our retina, we're going to need a display. So barring those kinds of technologies, we're going to need a display. And the best display that we have is a smartphone-like thing. It's not going to be this tiny thing. We saw what happened with Humane and all that other stuff. So you're going to have some kind of device because the best way to visualize visual information is with a display. So we're going to have some kind of small slab. Maybe it's foldable like we see today, so that you can access it. Maybe many things you don't need a display for, but a lot of things you still do. Because you might not be tapping and swiping. So I am of the opinion that long-term, if you look at how a device is layered today, and this is many devices and the iPhone specifically started this, which was tapping and swiping. That was the first thing: you use your finger. Then after that was keyboard. And then after that, the tertiary thing was voice input. We need to flip it. We need to absolutely flip it. And we have to say, and this is what I always wanted to do at Nest, which is, I want to remove displays and we need to have voice as the number one primary feature. And you build around voice. Then we have keyboard if necessary, and then we have tapping and swiping. It should go exactly the opposite. And the problem why most of us don't go around talking to our phones is we saw this also happen with cars. [SPEAKER_01] There were tactile buttons and then there were touch screens. [SPEAKER_01] We need to flip it. [SPEAKER_01] We need to absolutely flip it. [SPEAKER_01] And we have to say, and this is what I always wanted to do at Nest, which is, I want to remove displays and we need to have voice as the number one primary feature. [SPEAKER_01] And you build around voice. [SPEAKER_01] Then we have keyboard if necessary, and then we have tapping and swiping. [SPEAKER_01] Okay. It should go exactly the opposite. And the problem why we know most of us don't go around talking to our phones and everything. [SPEAKER_01] And we saw this also happened with cars. [SPEAKER_01] There was tactile buttons and then there was the touch screens. [SPEAKER_01] And then they also added the voice in, but nobody really uses voice in the car, unless it's some accessibility thing. [SPEAKER_01] Right? [SPEAKER_01] Because voice was always added at the end because it was always, well, it works. [SPEAKER_01] And it's a gizmo, but it's like Alexa was for version 1.0 or Siri was whatever. [SPEAKER_01] But when we actually have really good voice input with not just understanding us like Whisper Flow or something, because that's great. [SPEAKER_01] What I'm saying is the intelligence behind it with memory and everything else. [SPEAKER_01] So then we can start to say, and we can start to use that much more specifically, and then deprecate those other things, but we always have to have them there as a crutch for voice because voice has never been able to deliver. [SPEAKER_01] So that's the long-term thing. [SPEAKER_01] So it'll have some kind of display, but it's going to be much more voice primary. [SPEAKER_01] And then you're going to have the other things as secondary and tertiary in the middle now, or sometimes soon, it's going to look much, much like this, the smartphone is because we're not going to get away from the all app interface anytime soon. [SPEAKER_01] We're not going to get away from things, but we don't trust it yet. [SPEAKER_01] It's going to take a while till we trust it. [SPEAKER_01] And we are literally turning over a lot to this trusted thing, right? [SPEAKER_01] Because tapping and swiping, we know what that is for the most part. [SPEAKER_01] We know that we can trust ourselves when we're tapping and keyboarding or whatever. This other thing we don't know. [SPEAKER_01] And so it's going to take a lot of time. It reminds me of General Magic in a way for us to be able to get on mass to trust it. [SPEAKER_01] And we're already seeing this with coding agents and everything else. They deleted my source code. And again, I'm not trying to be an old guy who's saying it's not going to work. Sure, it's going to work in certain things. I'm saying for consumers every day and the things they want and it's cheap enough. So it doesn't cost them a lot. [SPEAKER_01] Right. Today, people are like, yeah, I'm going to try ChatGPT or whatever. [SPEAKER_01] It's $20 a month or $200 a month. That is unsustainable if you think consumers are going to pay that. There's just no way. Unless it's incredible, but they're not going to. They tried it and now they're getting their Siri. [SPEAKER_01] A lot of them are getting their Siri 1.0 with this. I paid for it, but it's really not all that yet. And it's like full self-driving. I paid for full self-driving. It's 15 years later. I'm still waiting for full self-driving. So I think we understand what we think we want, but where the technology is and the social adoption and the social trust that needs to be created around that is going to take a lot of time. It's going to take a lot of iterations to get there, especially if you're going to have to pay for it. [SPEAKER_01] It's really interesting to hear you say that long-term even we're going to need a screen. [SPEAKER_01] Because I think a lot of people are trying to go to just an AirPod or some kind of magical device. Sure. And how are you going to look at a map? If you want to look at a map, you're going to listen, put on the voice stuff in your car and never look at the map on your car and say, turn left in 200 feet, turn left in one? Or if you're like, shut up, I can't hear you anymore. I just want to glance over. So I don't buy it. Unless you have a jack in your brain or into your eye or some other way, it's getting into your cortex. That is so interesting. And you're not a fan of the Humane approach. I think it was like a little projection on your hand as a screen replacement, right? Yeah. Why? [SPEAKER_01] It's just different, not better. [SPEAKER_01] So funny. I guess the advantage obviously is it's like a small little device you could just put somewhere versus a screen, but yeah. Yeah. And you're like, oh, it's like the hologram projections of Star Wars or something. You're like, that's cool. But you still need a screen or something to project on. So it is a screen at the end of the day, you have to still project it onto something. [SPEAKER_01] Yeah. Because everyone keeps saying, how is it possible that the ideal product is a piece of glass that we look at and you're sharing here is just, that's actually maybe the ideal product. Yeah. And I said, you fold it up, you put it in your thing and it rolls out or whatever else. But I still think there's going to be that thing. If you look at the movie Her, they had glass. There was glass there for certain things. If you remember the movie Her, they had glass. There was glass there for certain things. Wow. I completely don't remember that. Yeah. You have to go back and watch the movie. It's there. Oh my God. That movie. I nailed it. Oh man. Go Spike. Spike Jones, right? Yep. I wanted to ask also, it's interesting that basically everyone is getting to hardware now. [SPEAKER_01] It's like you've been at this for so long, building hardware in AI and now it's just the hottest thing. Everyone's building hardware. So funny. Thoughts? I don't know. How does that feel? Look, I was building hardware when it wasn't in vogue in 1995 and 96. Everyone's like Tony, you're in the valley. Tony, you're crazy. It's all about the internet. We don't need any hardware. And then iPod comes out and I was pitching new businesses in 99 and 2000. They're like, well, that's the stupidest idea ever. Then the iPod comes out, Tony, you want to You've been at this for so long, building hardware in AI and now it's the hottest thing. Everyone's building hardware. So funny. Thoughts? How does that feel? Look, I was building hardware when it wasn't in vogue in 1995 and 96. Everyone's like Tony, you're in, this was in the valley. Tony, you're crazy. It's all about the internet. We don't need any hardware. And then iPod comes, and I was pitching new businesses in 99 and 2000. They're like, well, that's the stupidest idea ever. Then the iPod comes out, Tony, you want to leave Apple and start that business you wanted to do with hardware? And then it was like, yeah, okay. Then it was all software, mobile stuff again. We don't need anything. But we can't get to the next level of software if we don't make the next level of hardware and it has to happen completely. You gotta have the mobile network and the mobile network software for the mobile network to work. You had to have the MP3 player and the MP3 format bits to make that work. We're seeing with AI, we gotta have AI plus all the data centers and edge compute to make that work. And then over time, the hardware becomes less, it becomes more mundane. But all the software starts to then be great. So I've always just been continually going through the things that I love to do and doing the things at the full stack level, because that's where I know is innovation. That's what we had to do at Nest. We had to innovate at the software level, the hardware level, the network level to get the first thermostat out and then the Nest Protect and all that stuff. [SPEAKER_00] So if we look now going on, people are like, if you're a SaaS company or if you're a software only company, your software companies do worthless because anyone can code it into the thing. And now they're like, we're only funding companies that have atoms in their business plan with software. I'm like, where have you guys been? It's just funny to watch these cycles go and happen. All right, you guys can go chase your tails. I'm going to just keep here doing these full system products and businesses. Yes, they're a lot harder and yes, they cost more money and yes, they're going to take longer to scale and adopt, but they have staying power for years. And they bring new features that you could have never had if you just did software only. Especially in robotics, you need new sensors. Look at Waymo. It's an electric car with tons of sensors. It's a hardware platform. Maybe it doesn't look as streamlined as a smartphone, but it's an incredible hardware platform with an incredible software platform. And that is something that we're going to be able to innovate on and it'll become a platform for something else. Delivery or whatever else. When Evan Spiegel is on the podcast, Snapchat founder, he said exactly this. This is why they've spent so much money on these specs. And he's just like, this is the only way to survive in software is you need to have a hardware component now. Just very interesting. Everything old is new again. I've been in this game 35, 40 years. You just see it and you're like, okay, I was there at 99 when the bottom fell out and AI is different, but there's a lot of similarities and we're going to have the gen one companies, the gen two companies. And when people really understand product instead of selling technology platforms that people have to figure out for themselves. It's fun to watch. It's a game. [SPEAKER_00] Okay. Maybe one more question before we get to our very exciting lightning round. What are you most excited about these days in terms of gadgets or hardware or technology that's emerging? Is there anything you're like, pay attention? I've been doing this AI plus hardware thing now, not just at Nest, but in many of the startup companies that we funded at Build. Company like Simbi Robotics. We were doing robotics where now it's not a humanoid, but it does inventory of retail stores. We've been at it seven, eight years now. And now it's just taking off. It does have AI and it has a robotic platform. It really solves real pain points for the retailers of inventory. The workers hate doing inventory, counting everything on every shelf. It really works. I love seeing that stuff. We're doing the same thing at Great Parrot with AI and recycling. It's literally figuring out what things should go in this recycling bin versus that, doing it really fast with cameras and all this stuff. And we've been at that for a few years and we have AI plus textiles. Most textiles have weaving errors and color errors and defects. People still make all of these products, but then they have to incinerate them because they're not perfect at the end because they don't catch the quality problems early enough in the product. We're doing AI plus cameras to spot all this stuff. We're doing AI and drug design now for 10 years at Orionis, and that's taking off. So I'm really interested in not just these frontier models. This is really good AI that you can trust, scoped correctly, solving real problems every day, as opposed to pipe dream AGI. You can go solve that. I'm going to go and build all these businesses that really matter right now. We're finally getting traction because people are like, AI and robotics, and now all of a sudden we're in vogue and we've been here really working on our product market fit, working on our marketing, working on version 3.0 of the device and everything. And people are adopting them and that's what's wonderful to see. I'm excited by all that. and this whole thing is really good AI that you can trust, scoped correctly with this, solving real problems every day, as opposed to pipe dream AGI. Okay, you can go solve that. I'm going to go and build all these businesses that really matter right now. And we're finally getting traction because people are like, what AI and, oh, we're robotics and, and now all of a sudden we're in vogue and we've been here really working on our product market fit, working on our marketing, working on version 3.0 of the device and everything. And people are adopting them and that's what's wonderful to see. And so I'm excited by all that. We have another one, AI infusion, and doing that or, finally doing, tons of software with chemical reactions. And now we're turning, we have an agricultural, clean agricultural, fuel and oils company that is cleaning up farms all around Central America. So and we're almost all AI plus software in some way. And so it's just nice to be sitting here and knowing that we made these bets a long time ago and we're doing it now. We're not necessarily, I was early on in Grok, right. Because I was like, and it was cheap then. And it was like, yeah, that's the right way to go. And my friends were in Cerebris and I got into that. And then it's, but these are long-term plays and they're finally coming to fruition, but we did invest in it not when it was hyped and it's, we were doing it back when unicorn valuations were billions of dollars. Today, if you don't have a $5 billion round raised, you're not anything. It's like, okay, well that doesn't work from a venture perspective. With those kinds of, you'd never get the venture returns. You can't invest in things when the valuations are already nine digits or 10 digits. And you think you're going to, a small portfolio that's not the kind of game I want to play. So I'm glad that we have well positioned in all these companies that have real good product market fit that came in at the right valuations that we can really help and make big change and deliver painkillers. And we'll let everybody else over there play. So that's what's exciting to me. Oh man. There's this quote that I used the other day on a different podcast that I think applies to you. It's a quote from the Bible that you were made for a time like this. It feels like all the things are converging around the things that you have been doing for so long. And the technology is finally getting exactly as described to actually something amazing. Same thing happened to General Magic, right? General Magic, iPhone too early. And then I just kept adding that and then doing the iPhone. So you just stick with it. There are too many people who chase their tail and chase whatever the hottest thing is when it's already hot. It's already too late to be in it. For people that don't know what you do these days, you've talked about all these companies you work with, help people understand what it is you spend your time on in case they may want to try to work with you on this stuff. I think the first thing to know is that I invest in deep technology. So that could be hardware. It could be software, software plus hardware. It could be chemical, could be all kinds of different stuff. But remember we talked earlier about what's the pain and is there new technology that comes out to solve that pain in a new way or, and so what we do is I've learned that I invest in the deep technologies that are going to unseat the incumbents because it's going to change the market or the product in such a dramatic way that customers will choose this. So we're not just feature competing on features or better marketing or whatever. We're fundamentally a different product. Now it might take longer to get the market to shift to it, but it's fundamentally different. Just like I brought up Grok and Cerebris and these kinds of things, it's fundamentally different. And so at Build, what we do is we invest in those technology companies that can be that seed that can unseat things. And maybe they go the distance or maybe they are the key enabling tech that allows another startup to go the distance, that kind of stuff. And so that's we invest in and we do it in the environment, in societal benefits and health benefits. That's where we focus. And, you know, at times we've had a portfolio of over 200 companies and we do that, but we don't just invest. When we get involved, many of the companies we advise and that we come in helping with product management operations. We help them with financing. We help them with org development. All kinds of different ways that a lot of times in marketing and communications, right? Because we talked about storytelling. Storytelling is really important. And a lot of deep technology people, they're incredible engineers, scientists, researchers, what have you, they have a really good idea, but they don't necessarily know how to form the product around it or form the marketing around the product they're building or help the marketing to inform the product and vice versa. And so we try to encapsulate that and really bring that to bear. So they don't hit it on the fourth version. They try to get very close to the first or second version so they can get on that three-version cycle to get to a great company. And so that's what we do. So we get to have a lot of fun. We get to work, play in all these different places, spaces, health, medicine, drugs, robotics, chips, these kinds of things. So that's what's wonderful to us. And we get to just be kids in the candy store and work with all these incredible smart entrepreneurs and everything. So that's one thing I do. The other thing I do is I'm a designer in residence at MIT. So I just finished up my first year there with the MIT Media Lab in architecture and design and help to give lectures and work with students, amazing smart students with great technology, but help them with the customer journey. Try to make sure that they see this stuff early on in their career, not after 10 years. And then they finally understand, oh, wait a second, what am I really building? Who is it for? Not just what is it I'm building, but why am I building it and for who? And so we're trying to get that into some of the later undergraduate and graduate students so we can watch them change the world more quickly. Incredible. I love just all the levels of [SPEAKER_00] So I just finished up my first year there with the MIT Media Lab in architecture and design and help to give lectures and work with students, amazing, smart students with great technology, but help them with the customer journey. Try to make sure that they see this stuff early on in their career, not after 10 years. And then they finally understand, oh wait a second, what am I really building? Who is it for? Not just what is it I'm building, but why am I building it and for who? And so we're trying to get that into some of the later undergraduate and graduate students so we can watch them change the world more quickly. Incredible. I love just all the levels of ways you are helping people. There's the investing, there's this book, there's MIT, there's these conversations. It's fun. It's just so much fun. Yeah. I love how much fun you're having. Is there anything else you wanted to share that we didn't cover? We should really just talk about ethics and morals and your point of view on that. And as a product manager, as a product designer, you need to really consider these things. I understand we have lots of big questions about AI and is it going to be a disaster for the next generation and for societies and all other stuff. But I think that you really need to be well-grounded and have real principles when you're designing something and don't let those things go astray. Just like you wouldn't go astray with a bad user interface or something. Make sure you're not trying to addict your users. And if anybody is, there's always other jobs and there's always other better companies and don't chase the money for tearing apart the fabric of this society that we built. Obviously there's going to be innovation and there's going to be change. But when you're really doing it and you can see that you're doing it and you're trying to get people hooked or you're thinking, oh, I get more dopamine or whatever. That's when you have to start really looking at things. And a lot of times people are young and they think, oh, that's great. That's what I want. But when you start to have kids and you start to have families and you start to see and you're not just about you, you're not trying to just get out of your family, when you were growing up, I'm an individual and I want what I want. You really need to start thinking systemically about how what the benefit that you're bringing to society as a whole, not just to the business that you're in and trying to bring in whatever revenue you're trying to do. Because at the end of the day, users will feel that. And then I think we'll reward that as we see with Apple with privacy. And people say, oh, they're behind because they're so private and there's this, but it's a double-edged sword. You know, I remember when we had a very pointed discussion when the iTunes music store and when it was turning into video, was being specified and when we were thinking about it and everyone's like, oh, this is going to be great. We're going to do movies. We're going to do TV shows. That's going to all be great. We're going to make a lot of money with this and the studios, everybody's behind it. And then somebody goes, what about porn? Of course, Steve was like, what is that the kind of world you want your kids to grow up in? And Apple is related with that. And Apple's about, is that what we want to do? And it was very clear. It was shut down and we need leaders like that. We need leaders who are very clear, as opposed to I'm going to make a huge service for everyone. And they're all sex chat bots for everyone. I just think when you start normalizing those things and you start telling other generations that's a value and I understand that everyone has their own what's right and what's wrong. And here I am the old guy again. I think we can go a little too far. I'm for individual rights and for everyone to be a thing. But when major companies are doing this in the guise of certain kinds of behaviors they're trying to achieve. When we're selling, we're turning personal connection into a product with AI chatbots and making them really devolve social interaction to the point where I'm going to have a perfect interaction with this thing because the world is so messy. It's like we're losing humanity with that. And we're doing it for gain. So I wish that the other product designers out there really take it to heart. I'm not saying we got to be lily white and be in a church every weekend and Bible bang. I'm not saying that I'm not Maga. I'm not any of that stuff. Just saying, hey, think about it. A lot of people look at the iPhone as this thing now that everyone's hooked on. It's gotten so good. We're just like, it's too good. And there's all this data showing all the impact it has on people and things. Just like, how do you think about that? And the impact the iPhone has had on people? Well, the first thing is the iPhone wasn't set out to be that. You know, there's unintended consequences and the unintended consequence was social media happened and social media. Apple's not a social media company, right? But it does distribute the apps or make available those apps. Right. And so the way I think about it is we have lots of junk food and we have an obese nation or obese world because of all the junk food. And it takes us to regulate our consumption to do that and get healthy tools. And there's nutritional elements on the back of things. And if you want to make a better decision, you can. And I hope AI and these assistants will help people be able to get better control of those kinds of things where our lizard brain is being stimulated in a way that consumes more, consume more of physical food. Right. And now the same thing's happening in digital food, but we have digital food that doesn't have the nutrition labels, doesn't have the warnings, doesn't have the regulation that it needs to have just like we do with our physical food because oh, we can't let innovation slow down. I think there's, I'm not saying again, being a nanny and all the other decision, you can. And I hope AI and these assistants will help people be able to get better control of those kinds of things where our lizard brain is being stimulated in a way that consumes more, consumes more of physical food. Right. And now the same thing's happening in digital food, but we have digital food that doesn't have the nutrition labels, doesn't have the warnings, doesn't have the regulation that it needs to have just like we do with our physical food because we can't let innovation slow down. I think there's—I'm not saying being a nanny and all the other stuff—we've got to have some balance and it's swung too far. And I still think that the platform companies like Google and Apple could be doing a lot more around digital consumption tools and information to help people make better decisions for themselves, for their families and what have you, because your iPhone's just a refrigerator and you can put in junk food or you can put in good food. And even if you put in good food, you could go to the good food every five seconds, right? You have a refrigerator in your kitchen. You can put good food or bad food. You can open it all the time and keep consuming. So we need to learn habits. We need to teach habits. We need to put in regulations. We need information. We need tools to help us monitor and manage that stuff. And they need to be supplied. And we have, just like we have rules around who can buy something when they're 21 or under 21. We need all those kinds of things. And it needs to happen because why? Sure, you could have a short-term game and no customers, but if you make your customers unhealthy, you're not going to have customers. Let me just say for folks that haven't read your book, I just want to communicate how great it is. There's very few books that are both tactically useful that give you like, here's how to do a thing and also just inspire you to build and make great things. And Build does that in such a great way. I think everyone knows about it. I don't know if everyone's read it. So highly encourage you to read it. Two final questions. Where can folks find you online if they want to maybe learn about the stuff you're up to now and how can listeners be useful to you? Well, thanks again. This was a fun interview. I really enjoyed it. I think if you want to interact with us, we're at buildc.com. So Build Collective, but we're Build C, B U I L D C.com. You can go and see the companies we invest in and you can find ways to contact us there. And how can viewers help me, or help us, I think, learn about the companies, see if you can model whatever you're doing in some of the learnings and insights. There's a lot of websites that we helped to create, a lot of the marketing created for deep tech through those investments we made. So you can see some well-done marketing. I hope you like our website for Build C to show you what we think is a really great website that doesn't sell things necessarily, point and click and purchase, but I just get the rebuild and apply. That's the most important thing is rebuild, read other things like that. And really hone your craft, make better products, make a better world because the world only gets better by the things we make and what we bring. And so that to me, that's the most important way to help me is by making other cool products like Flighty or other things that are like, I love this thing. So make great stuff people and don't think the AI as well, use them for the tools that they can help with, but don't have cognitive surrender. Don't allow yours. Don't surrender to the machine. We can use the machines, but don't cognitively surrender and make better stuff, make better stuff than myself or any of the teams that we back can make because we do have better tools now. So please do. Amazing. Tony, thank you so much for being here. [SPEAKER_00] Hey Lenny, that was great. Really appreciate it. Looking forward to seeing what your audience creates. Same. Bye everyone. [SPEAKER_00] Thank you so much for listening. If you found this valuable, you can subscribe to the show on Apple Podcasts, Spotify, or your favorite podcast app. Also, please consider giving us a rating or leaving a review as that really helps other listeners find the podcast. You can find all past episodes or learn more about the show at Lenny's Podcast.com. See you in the next episode. And then if you, and, and at the time, and I'm, and me, I don't, maybe they changed it. Maybe they didn't. But at the time, Dario was saying, you know, 90 to 100% of all our codes written by, you know, our, you know, Claude. And you know, we just monitor it and watch it. And we're like, oh, well, that's really interesting. And then the code leaks. And then if you looked at the code, anybody who looked at the code, who's a real software architect and engineer threw up, they were like, it made what? They're like, this stuff is brittle. Engineers were looking at like, like this should be layered in four or five, you know, actually 12 or 15 different sub functions. This is the main loop of Claude, of, of, of, of, of Anthropics Claude. The main loop, not, not just something off in the, this is the main loop. And people are like, how can you do this? This looks brittle. There's like, it's unreadable. It's un, and they're like, well, the AI knows it. But when you think about it and you have to maintain it, you can have an agent make code for you and it could work and it could test. But is it secure? Is it maintainable? If there's something going wrong, can you roll things back and understand what's going on? Like there's so many other aspects to writing code and delivering a product thing that you still need humans in the loop. And so when I think of product design, I think of software code with AI. And when you look at AI and if it's not architecting things and it's not segmenting things and looking at each of those things, like I was saying, you know, like there's software architects and then there's software optimizers. And then there's just general coders and then there's security reviews. And if you don't have those different mixture 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 laws. And that's, you know, that's called software debt, right? Technical debt. And everybody hates technical debt. So it might be fixing something, but it might, it most likely is giving more technical debt, especially when you're at the high level. So now how does that map to product management? So if you're a product manager and you type this in and you get some results, but you don't have a really good marketer, a really good marketing communications person, a really good sales person, a real good channel sales person, a really good, you know, architect, a really good manufacturing manager, all these different things in this thing that you're getting, you're not going to be able, you might be able to make the first one, but when you go to version five, six, how does that work? You're building on a, a really crusty foundation and people are like, well, my AI is going to be smarter. It's not proven to do that. What's proven is if you properly architected and have code, Claude code go into certain sub segments or have Claude help you build the architecture. You modify, refine it, lock it in and say, just work on these few things. And you know, when these more limited scoped things, yeah, you can make that work. And I think that's the way we have to consider how we use these tools in a product management capability as well. To just say, it's all abstracted away. It's all going to be better. And when you ask specific pointed questions, you want this thing fixed in your marketing thing or whatever, and then they're going to like, well, the AI should just figure that out too. It's like you have given up so much. Like that's to me. Sure. You can write code, but there's going to be the difference between, you know, it's like the difference between H and M and a luxury brand. You can go get certain things that look like that and copies that and like edit, but it doesn't last more than one washing or one season and it's this and you throw it away and it's cheap and blah, blah, blah. Or you go to the luxury thing and you pay more and it's crafted, it's handcrafted, it's did it. And you know, it's going to be around for a while. Like, oh, there is this dichotomy of like fast and throwaway. So, you know, like it's called fast fashion. We got fast software, but software, if you're going to build a real company, can't be throwaway. Maybe it can, but I don't think it can be if you're really going to do this because you get just technical debt and you've got to start over again. So you've got to really understand how you're using these tools. And a lot of these things that these AI coders can do, agent coders can do, can make you incredible prototypes, do more prototypes, do more of those things to help you get that informed gut to say, we're going this direction, architect that in, and then work on the sub segments below it and, and, and, and all the expert systems that expert things that you need in each of those domains. Yeah. And I think what you may also be saying here, which I think is really, really important is that because it's so easy to build, people can just build all these features and additions and the value accrues to build something awesome. And the product mind becomes more important to help push this stuff from just a sloppy, every feature, every checkbox to something awesome that people actually use. Right. Because at the end of the day, if you're building it for yourself, whatever, go have fun. But if you're going to build it and you want to sell it and like, you know, and you only need three key features to sell it to someone, like it's going to have to be boiled down. It's going to be, have to be figured out because you're still selling it to a human who needs to understand it. Now, do you think you could vibe code flighty? Probably. Maybe now that flighty exists, you could. Right. Copy this. Like you could do version two of flighty, maybe vibe coding because you say, look at flighty, but the original flighty, like that's, to me, that's luxury software. Right. It was understood how the pixels are done. So you got to remember, is it version one or is it version two, three, four? Because an opinion based thing on highly innovative, differentiated stuff, it doesn't have a model for that. There's not that stuff in there. You could still need the very version one to be done. So maybe you can prototype with these things. So I just, you know, I could go on for hours, but whatever. That's just one old guy's point of view. I think it's really important. And this insight that as it becomes easier to build, the things that stand out are the things that are really well thought through and great and luxury, almost as you described. And you can feel it. Right. And you go, oh my God. And, you know, I'm like one of the biggest proponents of I'd like telling him flighty, flighty. Cause I, you know, all the people in my, in my sphere, they're all flying all this. I'm like, have you tried it? It's insane. You know? So it's, you know, and then you get the word of mouth and you know, things take up because there has been that level of care and craft to it. And yeah, maybe a lot of the sub functions of flighty could be built and whatever from cloud code or whatever. But the whole thing and the architecture and everything, I don't think so. And if someone hasn't tried flighty, clearly downloaded and play with it. This is, I love that this is the example of an amazing product. That's like a really cool. And it's all software. It's all software. Yeah. Something along these lines, as people hear you talk, clearly you are an amazing storyteller. And in your book, you often come back to the power of storytelling, the value of storytelling for product builders. What's, I guess one is just, why is that so important? Do you think? And two is, what's like one tip you could give people to get better at storytelling? Storytelling, that's how we passed information down or got people to commit to doing something. Like stories are so who we are. We go to the movies for stories. We have books. We have all this stuff. It's just so essential to who we are because we like to be taken on a journey. We like to, you know, and hopefully when you're buying a product or, you know, licensing one or whatever it is. Subscribing. You're taking on a journey that meets your expectations or out, you know, is better than what the expectations were set. It's much, it's outsized that. And so, you know, Dave Chappelle is, he just, you know, when it comes to comedy and storytelling, the way he weaves it, he can weave a story for 20 minutes to get to the punchline. And you're just, you're, you know, just in it. Right. I just love his comedy as opposed to the punchline guys who are just, you know, excuse me, the short ones. It's something in our nature, human nature. You know, we were told stories when we were a kid. You know, we read the same or watched the same movies a hundred times when we were kids. There's something about being taken on that journey that we love. And people love to be educated that way. Right. Your best, your best college professors, high school teachers, whatever. They taught you why you should love, you know, certain math or certain physics or whatever and took you a journey of why it mattered. And you're like, oh, now I get it. You know, you can learn all the basics of, you know, how to do something, but that doesn't really tie it into something that's meaningful. And so when you tie it to something that's human, right, that's when it becomes inaccessible for humans and it's relatable. That's when it goes and it can be for anything. And that's when great marketing, great sales happens, you know, and great story telling through the product design. That's even better. Right. Because it wasn't just perfuming this pig and you put some, you know, on this bad product and you say, oh, yeah, try it. And you're like, oh, and then it doesn't meet the expectations. But when it sings from the depths of the product, like you were bringing up with, you know, the Nest Protect, the thermostat or the smoke detector itself. When we had all that and that you could feel the love and care, that's when people go, oh, I love this and I want more from that brand or from that company or that team. That's what they want. And so to get better at it, I've learned it because I watched my dad. He was in sales. Right. So I watched how he would sell Levi's and I would watch and he would be like and he wasn't always selling to sell. Sometimes he was convincing them not to buy something because that wasn't the best product they had. Buy this one instead. And actually, you go to my competitor down the street because he was building a relationship and storytelling because these people loved what it was. So it sometimes is not just setting expectations and telling a story, but it's also saying, hey, maybe I'm not for you. And that's truth. That's also truth. And so like Steve always said, the best marketing just tells the truth. Now, it might put nice words around it, nice creative and everything, but it's telling the truth. And so when I watched Steve prepare for, and like I said, when we did the two and a half years with the iPhone, he was honing the story of the iPhone every day. He didn't give it to marketing. He knew what that thing was and what those key features were, like we talked about, like and micromanage those features because he knew those were the things the world's going to take notice to. And he would refine the story and then tell other people who were unwashed by, like friends who were really smart and say, I'm going to give you the pitch and give you the pitch. And he would refine, refine, refine. And so when you saw him come on stage, it was just because he had done it, you know, 100,000 times or at least 10,000 times. Right. And he knew it like boom, boom, boom, boom, boom. It just came off. And so I watched and learned from that. And that's what we did for like the Nest Learning Thermostat. That's what we learned, you know, we did for each of those things. It was just that same storytelling over and over. What does it matter? Why does it matter? Why does it matter? And because too many times when we're technology led, we talk about the what. We don't talk about the why. And the why is where the storytelling is. Because you want to take a journey of why it matters to you. And, you know, if you're talking about the what, you're just talking to another geek. Love geeks. No problem. I'm one of them. But, and we can relate on that level. But general, most people who are not in the technology world, they want a story and they want something that, that touches them in some way. One lesson I'm hearing from what you just described is telling the story over and over and over and refining it over time is where the best stuff comes from. Not just here. I just came up with this and it's going to be amazing. Yeah. Oh, absolutely. Because you, you need, and telling it to other people who don't, who don't, it's to see if it resonates. I remember, I remember the number of times I told the Nest story before Nest came out because I was like, this is crazy. This thermostat thing, you know, I'm like, okay, let me set up the virus of doubt, which was, do you know how much you spend on your energy bill every, every year for your heating and cooling? Don't you hate your, you know, thing? Now there's a, there's another way. There's another way to look at the storytelling. And this is, I put this in the book. Oh, no, I didn't put this in the book. I mean, we all have seen infomercials. They exaggerate everything and they show you all the pain points of it. And then they show how wonderful, easy it is to use in this, whatever they're selling. And then it's easy to buy. And then it's easy to return. And it's overly dramatic. And we all know, you know, it's like wrestling. It's all an act and whatever. It's not, you know, there's probably no real this there, but it is storytelling in a way. And if, and not that you should do that because they, they overhype the expectations, but look at the techniques that are used, the psychological techniques, the emotional techniques to get there and then dial it back and go, okay, I'm going to do that. But with truth, and that's when things start to go pop, pop, pop, or at least that's what I've seen. And so I always use that as another metric. And it's not just telling the story over and over. It's what, what story you are telling. And so I try to think of that as well, but not obviously clowny and cheesy and everything else, but it is a caricature of, of doing good marketing. I feel like this is a really interesting lens into the press release first or working backwards ideas, create the infomercial first and just go extreme. Sure. You could know what you don't want to do for sure. But it's like a cool lens to go really far and then kind of pull back the best parts and make it honest. I think we just came up with a really good idea here. Um, I want to come back to the iPhone. So I think it came out like 20 years ago, almost at this point, right? It launched 27, 2007. Yeah, 2007. So it's crazy as people are still trying to build the next iPhone, especially with AI. Everyone's just like, what's this we've had this thing forever. What the hell? Why has nothing changed? I'm curious. I imagine people ask you this question. I'm curious, just like what you think the next iPhone may look like with AI. What's like the device that you think emerges over time? Yeah. Okay. There's the, what it could look like long-term and there's what it could look like soon. And so a lot of people like, okay, there's the long-term thing. And, and when we can trust the models and when they have memory and when they do this stuff, man, then we're still going to need a display. Cause sorry, people, unless we're plugging it into our brain, like a BCI brain computer, or there's some laser thing going into our retina, we're going to need a display. So, so barring those kinds of technologies, we're going to need a display. And so the best display that we have is a smartphone like thing. Okay. It's not going to be this tiny thing. We saw what happened with humane, all that other stuff. So you're going to have some kind of, cause the best way to visualize visual information is with a display. Right? So we're going to have some kind of small slab. Maybe it's foldable like we see today, whatever, so that you can access it. You maybe many things you don't need a display for, but a lot of things you still do. Right? Because you might not be tapping and swiping and all this stuff. So I am of the opinion that long-term, if you look at how a device is layered today, and this is many, many devices and iPhone specifically started this, which was, you know, tapping and swiping. Right? That was, that was the first thing is, you know, you use your finger. Then after that was keyboard. And then after that, the tertiary thing was a voice input. We need to flip it. We need to absolutely flip it. And we have to say, and this is what I always wanted to do at Nest, which is, I want to remove displays and we need to have voice as the number one primary feature. And you build around voice. Then we have keyboard if necessary, and then we have tapping and swiping. Okay. It should go exactly the opposite. And the problem why we know most of us don't go around talking to our phones and everything. And we saw this also happened with cars. There was tactile buttons and then there was the touch screens. And then they also added the voice in, but nobody really uses voice in the car, unless it's some accessibility thing. Right? Because voice was always added at the end because it was always like, well, it sort of works. And it's, it's a gizmo, but it's, you know, it's like, like Alexa was for version 1.0 or Siri was whatever. But when we actually have really good voice input with not just it, understand us like whisper flow or something, cause that's great. What I'm saying is the intelligence behind it with memory and everything else. So it's, then we can start to say, and, and, uh, we can start to use that much more specifically, and then deprecate those other things, but we've always have to have them there as a crutch for voice because voice has never been able to deliver. So that's the long-term thing. So it'll have some kind of display, but it's going to be much more voice primary. And then you're going to have the other things as secondary and tertiary in the middle now, or sometimes soon, it's going to look much, much like this, the smartphone is because we're not going to get away from the all app interface anytime soon. We're not going to get, you know, we're going to remove some things, but we don't trust it yet. It's going to take a while till we trust it. And we are literally turning over a lot to this trusted thing, right? Because tapping and swiping, we know what that is for the most part. We know that we can trust ourselves when we're tapping and keyboarding or whatever. This other thing we don't know. And so it's going to take a lot of time. It reminds me of kind of general magic in a way for us to be able to get on mass to trust it. And we're already seeing this with coding agents and everything else, you know, oh, they deleted my source code. And again, I'm not trying to be an old guy who's saying it's not going to work. Sure. It's going to work in certain things. I'm saying for consumers every day and the things they want and it's cheap enough. So it doesn't cost them a lot. Right. Today, people are like, yeah, I'm going to try chat CPT or whatever. It's $20 a month or $200 a month. That is unsustainable for if you think consumers are going to pay that. There's just no way. Unless it's incredible, but they're not going to, you know what I mean? Like they tried it and now they're getting kind of their Siri. A lot of them are getting their Siri 1.0 with this. Like I paid for it, but it's really not all that yet. And it's like full self-driving. I paid for full self-driving. It's 15 years later. I'm still waiting for full self-driving. So I think we, again, understand what we think we want, but where the technology is and, and, and the social adoption and the social trust that needs to be created around that is going to take a lot of time. It's going to take a lot of iterations to get there, especially, and especially if you're going to have to pay for it. It's really interesting to hear you say that long-term even we're going to need a screen. Cause I think a lot of people are trying to go to just, just like an air pod or like some kind of magical. Sure. And like, how are you going to look at a map? If you want to look at a map, you're going to just, you're going to listen, like put on the voice stuff in your car and never look at the map on your car and say, Oh, turn left in 200 feet, turn left in one or if you're like, shut up, I can't hear you anymore. Like, I just want to glance over. So I, I, I don't buy it. Like, unless you have a jacked in your brain or into your eye or some other way, it's getting into your cortex. That is so interesting. And you're not a fan of like the humane approach. I think it was like a little projection on your hand as a screen replacement, right? Yeah. Why? What? It's just, it, it, it's different, not better. So funny. I guess the advantage obviously is it's like a small little device you could just put somewhere versus like a screen, but yeah. Yeah. And you're like, Oh, it's like, you know, it's like, uh, the, the hologram projections of star Wars or something. You're like, yeah, that's cool. But you still need to, you still need a, you know, uh, uh, a screen or something to you to project on. So it is a screen at the end of the day, you got to still project it onto something. Yeah. It's well, cause everyone keeps saying, how is it possible that the end ideal product is a piece of glass that we look at and you're, what you're sharing here is just like, that's actually maybe the ideal product. Yeah. And like I said, you fold it up, you put it in your thing and it rolls out or whatever else. But I still think there's going to be that thing. If you look at her, if you remember the movie, her, they had, they had glass. There was glass there for certain, for certain things. Wow. I didn't, I completely don't. Yeah. You have to go back and watch the movie. It's there. Oh my God. That movie. I nailed it. Oh man. Go Spike. Spike, Spike Jones, right? Yep. Um, I wanted to ask also just, it's interesting that basically everyone is getting to hardware now. It's like, you've been at this for so long, building hardware in AI and now it's just like the hottest thing. Everyone's building hardware. So funny. Thoughts? I don't know. How does that feel? Look, I was building hardware when it wasn't in vogue in 1995 and 96. Everyone's like Tony, you're in, this was in the valley. Tony, you're crazy. It's all about the internet. We don't need any hardware. And then iPod comes like, and I was pitching new businesses in 99 and 2000. They're like, well, that's the stupidest idea ever. Then the iPod comes out, Tony, you want to leave Apple and start that business you wanted to do with hardware, you know? And then, and then it was like, yeah, okay. Then it was all software, mobile stuff again. Like, okay, we don't need anything. Cause, but we, we can't get to the next level of software if we don't make the next level of hardware and it has to, the revolution has to happen completely. Like you gotta have the mobile network and the mobile network software for the mobile network to work. You had to have the MP3 player and the MP3, you know, format bits to make that work. We're seeing with AI, we gotta have AI plus all the data centers and edge compute to make that work. So, and then over time, the hardware becomes less, it becomes more mundane. Like, okay, it doesn't change as much, but all the software starts to then, you know, great. So I've always just been continually going through the things that I love to do and doing the things that the, the, the, the, the full stack level, because that's where I know is innovation. That's what we had to do at Nest. We had to innovate at the software level, the hardware level, the network level to get the first thermostat out and then the Nest Protect and all that stuff. So if we look now going on, people are like, uh, if you're a SaaS company or if you're a software only company, your software companies do worthless because anyone can vibe code it into the thing. And, and now they're like, we're only funding companies that have atoms in their business plan with software. I'm like, duh, like, like where have you guys been? Like, so it's just, it's just funny to watch these cycles go and happen. And it's like, okay, all right, you guys can go chase your tails. I'm going to just keep here doing these full system kind of products and businesses. Yes. They're a lot harder and yes, they cost more money and yes, they're going to take longer to scale and adopt and blah, blah, blah, but they have staying power for years. Right. And, and they bring, and they bring new, new features that you could have never had if you just did software only. Cause you need, especially let's say in robotics, I mean, you need new sensors and you knew this and knew that what have you. Right. Look at Waymo, you know, it's like, it's an electric car, you know, electric car with tons of sensors and, and everything was, it's a hardware platform. Maybe it doesn't look as streamlined as maybe a smartphone, but it's an incredible hardware platform with an incredible software platform. And that is something that we're going to be able to innovate on. And it'll become a platform for something else. I'm sure, you know, delivery or this or whatever else. When Evan Spiegel is on the podcast, Snapchat founder, he said exactly this. This is why they're, they've spent so much money on these specs. And he's just like, this is the only way to survive in software is you need to have a hardware component now. Yeah. Just very interesting. Everything old is new again. And, and, and, and, you know, I've been in this game 35, 40 years. I just, you just see it and you're like, okay, I was there at 99 when the bottom fell out and, you know, AI is different, but it's, there's a lot of similarities and, you know, we're going to have the gen one companies, the gen two companies. And, you know, when people really understand product instead of selling technology platforms that people have to figure out for themselves. So, you know, it's, it's, it's fun to watch. It's a game. Okay. Maybe one more question before we get to our very exciting lightning round. What are you, what are you most excited about these days in terms of, I don't know, gadgets or hardware or technology that's emerging? Is there anything you're like, oh, pay attention. I've been doing this AI plus hardware thing now, not just at Nest, but in many of the startup companies that we funded at build. And so company like Simbi Robotics, you know, it's Simbi Robotics. We were doing robotics where now it's not a humanoid, but it does inventory, inventory of retail stores. And we've been at it, I don't know, eight years now, seven years. And now it's just taking off. Right. And it does have AI and it has a robotic platform. And it's like, and it really solves real pain points for the retailers of inventory. And the workers hate doing inventory, counting everything on every shelf and all that stuff. So it really works. And like, I love seeing that stuff. You know, I, we're doing the same thing at Great Parrot with AI and, and recycling. Like it's literally figuring out what things should go in this recycling bin versus that, and doing it really fast with cameras and, and all this stuff. It's like, and we've been at that for a few years and we have AI plus textiles, like most textiles, you know, are, have, you know, weaving errors and, and, and, and, and color errors and defects and things like that. And so people still make all of these, these products, but then they have to incinerate them because they're not perfect at the end because we, they don't catch the quality problems early enough in the, in the, in the product, product. And we're doing AI plus cameras to, to spot all this stuff. And again, another thing, and we're doing this, we've been doing AI and drug, drug design now for 10 years at Orionis, and that's taking off. And it's like, so I'm really interested in not just these frontier models and this whole thing is really good AI that you can trust, scoped correctly with this, solving real problems every day, as opposed to pipe dream AGI, you know, okay, you can go solve that. I'm going to go and build all these businesses that really matter right now. And we're finally getting traction because people are like, what AI and, oh, we're robotics and, uh, and now all of a sudden we're in vogue and we've been here really working on our product market fit, working on our marketing, working on version 3.0 of the device and everything. And people are adopting them and that's, what's wonderful to see. And so I'm excited by all that. We have, we have, uh, another one like, uh, AI infusion, you know, and doing that or, or, um, finally doing, um, tons of software with chemical reactions. And now we're, we're turning, we have a agricultural, uh, clean agricultural, uh, fuel and oils company that, uh, is cleaning up farms all around, uh, Central America. So like, and we're almost all Adams plus software in some way. And so it's just nice to be sitting here and, um, and knowing that we made these bets a long time ago and we're doing it now. We're not necessarily, you know, I was early on in Grok that, you know, right. Cause I was like, and it was cheap then. And it was like, yeah, that's the right way to go. And, and, and my friends were in cerebris and I got into that. And then, you know, it's like, but these are long-term plays and they're finally coming to fruition, but we did invested it not when it was hyped and it's, you know, we were doing it back when unicorns valuations were billions of dollars today. If you don't have a $5 billion round raised, you're not anything. It's like, okay, well that doesn't work from a venture perspective. Like with those kinds of, you'd never get the venture returns. You can't invest in things when, when the valuations are already nine digits or 10 digits. And you, you think you're gonna, a small portfolio that's like, uh, uh, that's not the kind of game I want to play. So I, I'm glad that we have well positioned in the, all these companies that have real good product market fit that came in the right valuations that, that we can really help and make big change and deliver painkillers. And we'll let everybody else over there play. So that's, what's exciting to me. Oh man. There's this quote that I used the other day on a different podcast. Um, that I think applies to you. It's a quote from the Bible that you were made for a time like this. It feels like all the things are converging around the things that you have been doing for so long. And the technology is finally getting exactly as described to actually something amazing. Same thing happened to general magic, right? General magic, iPhone too early. And then I just kept adding that and then doing the iPhone. So it's just, you just, you stick with it. Like there's too many people who chase their tail and chase whatever the hottest thing is when it's already hot. It's already too late to be in it. For people that don't know what you do these days, you've talked about all these companies you work with, help people understand what, what it is you spend your time on in case they may want to try to work with you on this stuff. I think the, the first thing to know is that I'm, uh, we invest in, um, deep technology. So that could be hardware. It could be software, software plus hardware. It could be chemical, could be all kinds of different stuff. But remember we talked earlier about what's the pain and is there new technology that comes out to solve that pain in a new way or, and so what, what we do is I've learned that I invest in the deep technologies that are going to unseat the incumbents because it's going to change the market or the product in such a dramatic way that customers will choose this. So we're not, we're not just feature competing on features or better marketing or whatever. We're fundamentally a different product. Now it might take longer to get the market to shift to it, but it's fundamentally different. Just like I brought up Grok and Cerebris and these kinds of things, it's fundamentally different. And so at build, what we do is we invest in those technology companies that can be that seed that can unseat things. And maybe they go the distance or maybe they are the key enabling tech that allows another startup to go to the distance, that kind of stuff. And so that's, we invest in and we do it in, in the environment, in societal benefits and health benefits. That's where we focus. And, you know, at times we've had a portfolio of over 200 companies and we do that, but we don't just invest. When we get involved, many of the companies we advise and that we come in helping with product management operations. We help them with financing. We help them with org development. You know, just all kinds of different ways that a lot of times in marketing and communications, right? Because we talked about storytelling. Storytelling is really important. And a lot of deep technology people, they're incredible, you know, engineers, scientists, researchers, what have you, they have a really good idea, but they don't necessarily know how to form the product around it or form the marketing around the product they're building or help the marketing to inform the product and vice versa. And so we try to encapsulate that and really bring that to bear. So they don't, they don't hit it on the fourth version. They try to get very close to the first or second version so they can get on that three, that three version cycle to get to a great company. And so that's what we do. So we get to have a lot of fun. We get to work, play in all these different places, spaces, health, medicine, drugs, robotics, you know, chips, these kinds of things. So that's what's, that's just what's wonderful to us. And we get to just be kids in the candy store and work with all these incredible smart entrepreneurs and everything. So that's one thing I do. The other thing I do is I'm a designer at residence at MIT. So I just finished up my first year there with the MIT media lab in architecture and design and help to give lectures and work with students, amazing, amazing, smart students with the great technology, technology, but help them with the customer journey. Like try to make sure that they see this stuff early on in their career, not after 10 years. And then they finally understand, oh, wait a second, what am I really building? Who is it for? Not just what is it I'm building, but why am I building it and for who? And so we're trying to get that into the, into some of the later undergraduate and graduate students so we can, you know, watch them change the world more quickly. Incredible. I love just all the levels of ways you are helping people. There's the investing, there's this book, there's MIT, there's these conversations. It's fun. It's just so much fun. Yeah. I love, I love how much fun you're having. Is there anything else you wanted to share that we didn't cover? We should really just talk about ethics and morals and your, your point of view on that. And as a product manager, as a product designer, you need to really consider these things. I understand we have lots of big questions about AI and is it going to be a disaster for the, for the, you know, for the next generation and for societies and all other stuff. But I think that you really need to be well-grounded and have real principles when you're designing something and don't let those things go astray. Just like you wouldn't go astray with a bad user interface or something like that. Make sure you're not trying to addict your users. And if anybody is, there's always other jobs and there's always other better companies and don't chase the money for tearing apart what it is, the fabric of this society that we built. Obviously there's going to be innovation and there's going to be change. And, but when it, you're really doing it and you can see that you're doing it and you're like trying to get people hooked or you're like, oh, I get more dopamine or what have you. That's when, you know, you have to start really looking at things. And a lot of times people are young and they, they think, oh, that's great. That's what I want. But when you start to have kids and you start to have families and you start to see the, and you're not just about you, you're, you're, you're not trying to just get out of your family, you know, uh, out of your, when you were growing up, you know, I'm an individual and I want what I want. You know, you really need to start thinking systemically about how, what the benefit that you're bringing to the society as a whole, not just to the business that you're in and trying to bring in whatever revenue you're trying to do. Um, because at the end of the day, users will feel that. And then I think, and we'll, we'll reward that as we see with Apple, with privacy, right. And people say, oh, they're behind because they're so private and there's this, but it's a double-edged sword. You know, I remember when we had a very pointed discussion, when the iTunes music store and when it was turning into video, um, was being specified and when we were thinking about it and everyone's like, oh, this is going to be great. We're going to do movies. We're going to do TV shows. That's going to all be great. We're going to make a lot of money with this in the studios, everybody's behind it. And then somebody goes out when we should have porn. Of course, Steve was like, what is that the kind of world you want your kids to grow up in? And Apple is related with that. And Apple's about the, is that what we want to do? And it was very clear. It was shut down and we need leaders like that. You know, we need leaders who are very clear, as opposed to, I'm going to make a huge service for everyone. And they're all sex chat, sex chat bots for everyone. I just think, you know, when you start normalizing those things and you start telling other generations, that's a value and you start, and I understand that everyone has their own what's right and what's wrong. And here I am the old guy, you know, again, uh, I, I think we, you know, we can go a little too far. I'm for individual rights and for everyone to be a thing. But when major companies are, are doing this in the guise of certain kinds of behaviors, they're trying to achieve. Um, you know, when we're selling, we're turning, uh, personal connection into a product with AI chat bots and making them really, you know, uh, uh, devolve, uh, you know, social interaction to the point where I'm going to have a perfect interaction with this thing because the world is so messy. It's like, we're, we're losing humanity with that. And we're just for, for, for gain. So I, I, I wish that the other product designers out there really take it to heart. I'm not saying we got to be lily white and, you know, being in the, in a, in a church every weekend and that Bible bang. I'm not saying that I'm not Maga. I'm not any of that stuff. Just saying, Hey, think about it. A lot of people look at the iPhone as this like thing now that everyone's hooked on. It's like gotten, it's so good. We're just like, it's too good. Uh, and there's all this data showing all the impact it has on people and things like that. Just like, how do you think about that? And the impact the iPhone has had on people? Well, the first thing is the iPhone wasn't set out to be that we, you know, there's unintended consequences and the unintended consequence was social, this social media happened and social media. Apple's not a social media company, right? But it does distribute the apps or make available those apps. Right. And so the way I think about it is, you know, we have lots of junk food and we have an obese nation or obese world because of all the junk food. And it takes us to regulate our, our, our, our, our consumption to do that and, and get healthy tools. And, you know, and, and, you know, there's nutritional elements on the back of things. And you, if you want to make a better decision, you can. And I hope AI and these assistants will help people be able to get better control of those kinds of things where our lizard brain is being, you know, stimulated in a way that like, consume more, consume more of physical food. Right. And now the same thing's happening in digital food, but we have digital food that doesn't have the nutrition labels, doesn't have the warnings, doesn't have the regulation that it needs to have just like we do with our physical food because, oh, we can't, you can't let innovation, you know, whatever, uh, you know, beat slow down. I think, I think there's, I'm not saying again, being a nanny and all the other stuff that we got to have some balance and it's just swung too far. And I still think that the platform companies like Google and Apple could be doing a lot more around digital consumption tools and information to help people make better decisions for themselves, for their families and what have you, because, you know, you could go to the refrigerator, get it. iPhone's just a refrigerator and you can put in junk food or you can put in good food. And even if you put in good food, you could go to the good food every five seconds, right? You have a refrigerator in your kitchen. You can put good food or bad food. You can open it all the time and keep consuming. So we need to learn habits. We need to teach habits. We need to put in regulations. We need information. We need tools to help us monitor and manage that stuff. And they need to be supplied. And we have, just like we have rules around, you know, who can buy something when they're 21 or under 21. We need all those kinds of things. And, uh, it needs to happen. Um, because, because why? Sure. You could have a short-term game and no customers, but if you make your customers unhealthy, you're not going to have customers. Let me just say for folks that haven't read your book, I just want to, uh, communicate how great it is. There's very few books that are both tactically useful that give you like, here's how to do a thing and also just inspire you to build and make great things. And build does that in such a great way. Uh, I think everyone knows about it. I don't know if everyone's read it. So highly encourage you to read it. Two final questions. Where can folks find you online if they want to maybe learn about the stuff you're up to now and how can listeners be useful to you? Great. Well, let's see. Well, thanks again. This was fun interview. I really enjoyed it. I think if you want to interact with us, we're at buildc.com. So build collective, but we're build C B U I L D C.com. You can go and see the companies we invest in and you can find ways to contact us there. Um, and how can, uh, viewers help me, um, or help us, I think, learn about the companies, see if you can model whatever you're doing in some of the learn from insights. You know, there's a lot of websites that we helped to create a lot of the marketing created for deep tech through those, through those, those investments we made. So you can see some well done marketing. I hope you like our, our website for build C to show you how, what we think is a really great website that, you know, only doesn't sell things necessarily. You know what I mean? Uh, like, you know, point and click and, and purchase, but, um, uh, I, I, I just, I just get the, get the rebuild and apply. You know, that's the, I think that's the most thing is rebuild, read other things like that. Um, and really hone your craft, make better products, make a better world because the world only gets better by the things we make and how, what we bring. And so that to me, that's the, that's the most important way to help me is by making other cool products like flighty or other things that are like, I love this thing. So make great stuff people and don't think the AI as well, you know, use them for the, the tools that they, they can help with, but don't have cognitive surrender. Don't allow yours. Don't surrender to the machine. We can use the machines, but don't cognitively surrender and make better stuff, make better stuff than myself or any of the teams that we back can make because we do have better tools now. So please do. Amazing. Tony, thank you so much for being here. Hey Lenny, that was great. Really appreciate it. Uh, looking forward to seeing what your, what your audience creates. Same. Bye everyone. Thank you so much for listening. If you found this valuable, you can subscribe to the show on Apple podcasts, Spotify, or your favorite podcast app. Also, please consider giving us a rating or leaving a review as that really helps other listeners find the podcast. You can find all past episodes or learn more about the show at Lenny's podcast.com. See you in the next episode.