My biggest takeaways from @stewart: 1. Product design is about creating understanding, not removing friction. Teams obsess over reducing friction and removing steps, but 70% to 80% of product design challenges are actually about helping people *understand* what your product does and what to do next. Users arrive barely interested and confused about what you offer. If they can’t quickly grasp what they’re looking at, they’ll leave. Making confusing things faster just gets users to the exit quicker. The mantra should be “Don’t make me think,” not “reduce friction.” 2. You’re not selling features—you’re selling outcomes. Nobody wants a saddle; they want to go horseback riding. Nobody wants a hammer; they want something built. People understand cars and beer without explanation, but new software needs an explanation of both what it is and why people should want it. Slack wasn’t selling messaging features—it was selling better team coordination and reduced email chaos. If you can’t articulate the transformation your product creates in people’s lives, you’re just listing features. 3. Organizations naturally fill with fake work that looks exactly like real work, what Stewart calls “hyper-realistic work-like activities.” Meetings to preview deck slides, analysis of tiny feature differences, elaborate processes around insignificant decisions. People aren’t stupid or lazy; they’re responding to having more workers than valuable work to do. Leaders must continuously ensure there’s enough clearly valuable work and explicitly say no to projects that can’t possibly generate meaningful impact. 4. The value of a feature exists on a "utility curve." There’s the initial flat zone where a feature is too weak to matter, then a steep rise where it brings users to the "aha" moment, then the value levels off where improvements don’t matter much anymore. Teams often give up in the first flat zone or waste resources in the third. The key question isn’t whether you have a feature, but whether you’ve invested enough to reach the steep part of the curve where it becomes genuinely valuable. 5. Small conveniences create emotional connections that drive word-of-mouth growth. No one switches products because of a good time-zone picker or smooth password recovery, but these details make users love or hate your product. Slack grew largely because people who used it at one company would join a new company and advocate strongly for adopting it. That advocacy came from accumulated small delights, not major features. 6. The “owner’s delusion” explains why bad experiences persist everywhere. Restaurant owners create terrible websites even though they’ve experienced the frustration of visiting other terrible restaurant websites. Business owners assume visitors care deeply about their product, when in reality people arrive distracted, in a hurry, just above the threshold of caring at all. The solution is to regularly step back, pretend you’re a normal person with limited time and patience, and honestly evaluate if your product makes sense. 7. Only pivot after exhausting all reasonable ideas. The right time to pivot isn’t when things get hard—it’s when you’ve genuinely tried every non-ridiculous approach and can coldly, rationally assess that the expected value has dropped below alternatives. Pivoting is humiliating because you’ve convinced investors, employees, and users of a vision you’re now abandoning. That emotional cost means most people either pivot too quickly or wait until they run out of money. 8. Treating customers and employees with extraordinary generosity creates a competitive advantage. Slack pioneered fair billing (not charging for unused seats), gave free credits during Covid, and automatically refunded customers for downtime without their asking. This wasn’t just ethics—it helped attract better employees, created positive stories, and built long-term customer loyalty. The mantra was “In the long run, the measure of our success will be the amount of value we create for customers.”