I've been building digital products for a little over eight years; that's long enough to know what works and what doesn't. Along the way, you accumulate what people politely call "experience": the scars, the wins, the misfires, and the hard-won pattern recognition.
Product development is a strange ride of discovery, learning, and failure, usually punctuated by plenty of: "We intended for this to work one way, but users had completely different plans for it." It's the classic OnlyFans trajectory, miles away from what the creator originally set out to build, because the market intervened and redirected the course.
Those nuances and discoveries are why I love building, and why Lenny's Podcast has become a fixture I keep coming back to. A recent episode featured Mark Pincus of Zynga unpacking the hidden patterns behind enduring products. Mark shared decades of trench experience and touched on his book, which draws on both his personal life and career.
I picked it up expecting a few useful frameworks. I got considerably more than I bargained for.
Mark brings readers up to speed with his journey, tracing how his upbringing and playful childhood home shaped his perspective on engagement and play. Long before Zynga, he built, scaled, and exited multiple ventures. Out of the principles and operating frameworks he unpacks, his breakdown of product creation stood out the most.
The Three Pillars of a Product Maker
1. Instincts vs. Ideas
You constantly hear people obsessing over someone stealing their idea. But ideas are just the mechanics of execution, while instincts tap into a deep well of genuine human need. As Mark puts it, people are usually 95% right about their instincts and 75% wrong about their ideas. When folks in the past dreamed of faster horses, the idea was equine speed, but the underlying instinct was getting from point A to point B faster. Staying anchored to the core human instinct gives you the freedom to test, discard, and iterate across dozens of executions until one finally clicks.
Before reading this, I hadn't made that distinction: ideas and instincts felt like the same thing. Now, it has shifted how I look at everything I build. Regardless of where an initial flash of inspiration comes from, the real job is stripping it down to find the raw, underlying human instinct first. Once that foundation is clear, you can afford to play freely with multiple executions until the right idea surfaces.
2. The Proven, Better, New Framework
Early in my career, I did the exact opposite of this. My default reflex was to invent something radically novel from scratch, convinced that novelty alone was the differentiator. But users are inherently averse to change; they crave validated, familiar foundations. Mark's breakdown offers a far saner balance:
- Proven: The baseline patterns and mechanics users already know, trust, and rely on.
- Better: The core flow you optimize so thoroughly that users have an immediate, visceral "hell yeah" reaction to the upgrade.
- New: The single, genuine novelty you introduce, cleanly isolated so it can be tested and validated without breaking the rest of the product.
Like a lot of builders, I used to feel a strange guilt around the idea of "copying." Maybe that traces back to grade school, where individual work is praised and collaboration is labeled cheating. We're conditioned to brainstorm alone and build in a silo. Silicon Valley operates on a completely different truth: when Snapchat pioneered ephemeral Stories, it made zero sense for the rest of the tech world to reinvent the wheel. Your users live in other apps every day, and their muscle memory is already formed. If you force them to unlearn proven patterns, you lose them.
The art is using Proven patterns as your floor, making the core flow Better so the upgrade is instantly felt, and saving New as the deliberate differentiator, the isolated feature that gives your product its edge without confusing anyone.
3. Institutionalizing the "Right Thing"
Great products rarely survive design by committee. Breakthrough products require what Mark calls a "democratic dictatorship." It might make traditional corporate culture uncomfortable, but anyone who has built from zero recognizes the reality: everyone gets a voice and a seat at the table, but the founder retains the wheel. Mark throws out the classic corporate mantra of "disagree and commit" in favor of "disagree and disagree." It's a deliberate stance to keep the product's original soul from dying the slow death of a thousand well-meaning compromises. You listen to the room, debate the nuances, but when it's time to steer, you protect the core vision without apologizing for it.
In early-stage building, complete democracy is just disguised indecision. You want radical honesty and candid input during the debate, but strong products need a single hand on the wheel to maintain conviction.
Beyond the MVP: Atomic Units of Learning
Mark went further to share what I'd call a master playbook of operating principles that guided Zynga's biggest wins.
One core critique centered on Eric Ries's classic Lean Startup concept: the Minimum Viable Product (MVP). Mark's contention is with the word viable. He argues that traditional MVPs have become too slow and expensive for modern product cycles. Instead, he advocates for atomic units of learning through what he calls the Minimum Idea State (MIS).
An MIS isn't a fully built product. It is simply the smallest expression of an idea you can put in front of friends or your target audience to extract directional feedback. That could mean a plain text link, a rough pitch deck, or a quick prototype that breaks after ten clicks. Moving in atomic units drastically reduces the cost of failure, keeping testing velocity high and hit rates even higher.
While Mark's assertion made total sense when engineering costs were prohibitive, our post-AI reality flips the script. With vibe-coding and modern generative tooling, the cost of spinning up a functional, stripped-down product in record time has cratered. In many cases, it now makes more sense to give users an actual, tangible artifact to touch rather than a conceptual MIS. Still, the fundamental lesson holds: competitive advantage is no longer about "Can you build it?" but "Do you know what to build, what to test, and what to kill?"
Bold Beats, OMFG Moments, and the Living Roadmap
Product development is fundamentally an act of aggressive discovery. To deliver a positive disruption in consumer experience, teams must build, test, and discard failing concepts in isolation without destabilizing the core platform. Mark calls these isolated swings Bold Beats. When executed right, they produce an OMFG moment: a rapid, high-impact feature release that ignites immediate consumer engagement.
Most features I've built have tended to be tight extensions of the core product. Reading this made me want to be far more deliberate with Bold Beats. I've seen versions of that OMFG reaction before in user data, but usually by accident rather than through structured, isolated bets.
This is where the Proven, Better, New framework becomes operational through the product roadmap.
The roadmap is where strategy meets execution. It isn't a static quarterly Gantt chart; it's a living document that allocates resources, defines measurable outcomes, sets shipping dates, and dictates the operational heartbeat of the company. Paired with rigorous weekly reviews, it acts as the team's ongoing report card, defining exactly which hills you take, what impact you expect, and what every bet costs. Without that clear accountability, a team is simply building blind.
Staying Close to the Metal
Mark also touched on leadership and culture, stressing that founders must "stay close to the metal": maintaining a direct, hands-on connection with their product, their users, and the core building blocks, whether software code or physical atoms.
This resonated deeply. As products gain traction and teams expand, too many founders drift into pure managerial scale and lose touch with the very craft that made them succeed in the first place. As Mark puts it, a founder's primary job is to be right, and "being right comes from staying close to the metal."
You see this in leaders like Brian Chesky at Airbnb or Evan Spiegel at Snap. Both come from design backgrounds; both remain deeply immersed in the levers, pulleys, and craft of their interfaces. That proximity isn't micromanagement; it's full-stack leadership from builders who know how to get in the trenches.
Internet Treasures
Throughout the book, Mark keeps returning to the concept of Internet Treasures: products and services so essential to everyday life that we can neither remember life before them nor imagine life without them.
The term was coined by venture capitalist John Doerr and Bing Gordon, longtime mentor to Pincus and former Chief Creative Officer at Electronic Arts. They argue that these products represent the highest creative output of modern culture: milestones like Google, the iPhone, Instagram, and now ChatGPT. For Pincus, discovering this concept crystallized his own life's work. He passionately argues that translating foundational human instincts into products that elevate millions of lives is "God's work."
That idea stayed with me long after closing the book. It reframed a question I've been circling for years without naming it clearly: am I building things that matter, or just things that ship? Eight years in, I know how to launch. I know how to iterate. What I'm still learning, what Mark's work made uncomfortably clear, is the difference between a product people use and a product people need. The gap between those two is where the real work lives, and I suspect it always will.