Sharpen the Knife: Why Simplicity Wins in Product, Story, and Life

The speaker opens by saying her talk is called “Simplify to Win” partly because she wanted people to pay attention, but the real motivation is what she has learned in more than 20 years of building products at scale. Her central claim is that simplicity is not just a strategy but a superpower: it has helped her build better products and focus on what matters in her life. She wants to share lessons about building simple products, starting with why she is obsessed with simplicity.

She traces that obsession to a joking accusation from her husband that she is naturally lazy and uses simplicity as an excuse to do less work. She concedes that laziness is another word for efficiency, with worse branding. But the more important reason is that simple products are often easier for her and her teams to build, and much more importantly, easier for customers to use.

She uses a physical metaphor: when a great idea is hidden inside a lot more information, the idea gets diffused and requires hard pushing to get across, like mashing potatoes. When the same idea is honed down to just 10 words, it becomes a knife that cuts through effortlessly. She points to the knife as one of the most successful products ever: there is one in every home, it has lasted 2.5 million years, and it works because everything unnecessary has been removed—which is literally what sharpening means.

She frames simplicity as a knife that makes it easier to build something meaningful for other people, whether a meal, a sculpture, or a product. That idea has made hard product questions easier for her, and the talk follows three areas: what to build, how to build and design it, and how to tell the story about it. She draws on lessons from WhatsApp, the largest messaging app in the world.

When she joined WhatsApp, she had many ideas for shiny new features and ways to monetize, which she says is typical when building something new. But until a product or feature is known to work, the full roadmap is not needed and can actually muddy the product. It becomes harder for users to understand what the product is for, and they may feel confused, overwhelmed, or even ashamed that they cannot understand all of it.

She compares unexpected product changes to someone rearranging the furniture in your house in the middle of the night, leaving you to bang your shins into a couch. What worked for WhatsApp was simplicity: instead of changing many things, the team figured out what made the product indispensable and focused there. The goal was to give anyone in the world the feeling of being face to face with friends and family, even when separated by geography or circumstance.

For global users in emerging markets on low-end devices, being present meant one thing: did calls and messages go through for free every time? The team spent its entire roadmap on that and slowed down other grand ideas. She admits it was not always easy to watch other teams build the newest AI models or advanced photo filters, but the focus meant users never had to ask what WhatsApp was for or how to use it. That focus earned the right to add more later.

She turns this into a question for other builders: what is the one thing that makes your product indispensable—not flashy, not innovative, not fun, but indispensable? Does the product need to cut through bone or bread, and can you get that 100% right before building more? She adds a caveat: if you are keeping medical devices humming or planes in the air, do not cut anything, because every edge case matters.

No one walks up to a knife and asks how to use it or where to hold it, she says; even kids can use one. She jokes about giving her three-year-old a knife and putting him on eggplant duty, but the point is that a knife is immediately familiar. The product-design question becomes: what will make this product familiar to my customers?

For global users, the team knew little beyond the fact that they had a phone, so familiarity meant matching what they already knew from that phone. WhatsApp borrowed existing patterns: if Android put a floating action button in the bottom right, WhatsApp put its button there too. It used consistent patterns throughout the app, such as a triangle meaning “send” and an arrow meaning “you can still change your mind.”

She acknowledges that this was limiting, especially when new interaction patterns and gestures were emerging. The team could not use them if they were not already accessible to users, and there are only so many directions in which a message can be swiped. So it prioritized the few most important actions and asked where users would naturally put their thumb, or where their mouse and eyes go in tools like Hotjar recordings. Putting the button there meant users did not have to learn; they could pick up the product and start using it like a knife.

She introduces the standard narrative arc that most stories follow and says it has been bred into people for generations. Because customers already expect that arc, a product story that hooks into it becomes more resonant and powerful. She jokes that she has always wanted to be a high school English teacher and finally has the stage for it.

The temptation is to start with a grand new problem and a grand new technology that has never been seen before. But in her experience, technologies change while underlying human needs stay stable—needs such as connection, safety, and status. Products that plug into those needs make more sense automatically, and the key takeaway is that you do not have to add something brand new. You cannot sharpen a knife by adding more to it; the trick is to remove stuff and understand the story customers are already telling so you can reflect it back.

She finds this by listening to customers. For WhatsApp, a user said, “WhatsApp isn’t really an app, it’s a part of my life,” which became a central metaphor about mirroring physical spaces and face-to-face communication. Everyone already knew how to talk face to face, and that metaphor helped the team decide how to build products.

Disappearing messages could have felt novel, confusing, and different from what users were used to, so the team asked how it works in the physical world. Most mail is recycled, and only truly special items are kept, so disappearing messages automatically delete everything except what someone intentionally marks to keep. When users scroll back through a chat, what remains are the most important moments, like flipping through a scrapbook of favorite messages. The metaphor also made it easier to build because the team shared a sense of what it should feel like, and a sharpened story can hook into something deep and emotional.

When asked how to know whether a customer is cutting through bone or bread, she says the best answer is to understand the customer, which sounds easy but is very hard. The hardest part is patience, because product managers often carry a countdown clock in their heads and ask what the ROI is on every 30-minute slot. Customer empathy is not high ROI in the short term; it can be the opposite, and user research can make you want to jump across the table and point out the button you already built.

Even so, she argues that customer empathy is the highest ROI in the long term because it builds intuition about what to build now and what to build next. One tactic is to hold a weekly calendar slot for something customer-related, such as Friday afternoon when other work is unlikely to get done. That slot can be used to use the product, read and watch reviews, read support tickets, watch Hotjar recordings, or visit customers; at Faire, a marketplace for local independent retailers, she can walk into neighborhood stores and ask where they get their products.

She recalls a customer who was a nursing director at a hospital and said Faire changed her life because it let her run a small gift shop in the labor and delivery ward. New families could get what they needed before going home, making their first weeks—when they are most vulnerable—easier. The speaker, who has three children, says they both cried, and now she asks whether whatever she is building is simple enough for Nancy to use in the five minutes she has between delivering babies and restocking cozy baby blankets.

Her goal when talking to customers is to find someone who says the product changed their life, because that is when she knows her knife is sharp and she knows what to build. She will push for the right product even when it feels like going out on a limb, because she is advocating for the customer. That shared customer story gives her team urgency and accountability, and it slices through disagreements with cross-functional partners because everyone has heard the same thing.

She offers cold, hard numbers for WhatsApp: globally it has 2 billion users, 100 billion messages a day, and 1 billion calls a day. Even though the app was designed for anyone in the world to use, it worked well for everyone, and WhatsApp crossed 100 million users in the US last summer. Her lesson is that making something simple and predictable reduces cognitive load for everyone.

She anticipates the objection that WhatsApp is an outlier with a massive network effect and a large acquirer, then points to other companies built on simplicity. PayPal won by making it simple to send payments with just an email address instead of full credit card details; Nest used a simple turnable dial instead of a difficult programmable thermostat; and Square brought simplicity to point of sale. She also cites products that simplified and became more successful, such as Spotify after a relaunch that cut products and Instagram after it stripped away functionality to focus on photo sharing, and she admits with a joke that Claude and GPT supplied these examples the night before.

At Faire, a marketplace connecting local independent retailers with brands, the team applied the same lessons to a notoriously complicated business with two sides and complex unit economics. Instead of 50 priorities that were all equally important, it simplified to the top eight that stacked into an indispensable product, and it simplified core flows from sign-up through browsing and checkout. Customers described Faire as a 24/7 trade show, so marketing now talks about a 24/7 trade show and the company increasingly organizes around customer jobs to be done, including in top priorities and team structure.

The results matter: at a time when consumer spending is down and most global marketplaces have declining growth rates, Faire’s growth rate has doubled because customers are getting more value and the company is getting more efficient at providing it. She jokes that a strategically cropped chart can be totally accurate while telling you absolutely nothing, which is why labels matter. The chart is a reminder that simplifying priorities can produce measurable growth, not just a cleaner interface.

She recaps her lessons: build what makes the product indispensable, make it familiar so users can pick it up and go, and discover the story customers are already telling so you can reflect it back and explain how the product solves their problems. When unsure, the customer should be the guide. She says that even after more than 20 years of loving simplicity, it is still a fight.

The reason is that product managers have many interesting problems to think about: order alignment, keeping a manager happy, keeping cross-functional partners happy, and always having a 2x2 to show everyone. She jokes that this may be too spicy for the conference, but says these activities are distractions and temptations away from the core problem of building something indispensable for customers. She calls a product manager without a way to create impact the most dangerous thing in a tech company, and says generating new ideas just to add to the product is a recipe for complexity.

She pushes back on the pride sometimes attached to building something new and complicated. Even as underlying technology gets better and more life-changing, she argues there is enormous value in building products on top of it that are simple and familiar, because that is how everyone in the world will get the benefits. These principles have helped her channel energy into products and problems that help customers from day one.

She also applies the principles to her life and career, saying she has invested so much in them that she might as well get maximum ROI. She describes the industry pressure to have everything figured out—the next big job, the next company, what your LLM will predict, or what your ice-plunge routine should be—and says it helps to remember that doing a little less can make what you are creating clearer and more powerful. That gives her space to ask what is really indispensable right now, whether a mission in her career or time with her children, and she accepts that she may sometimes discover she has been using a bread knife when she should have been using a scalpel.