Tag: product discovery

Master the Purpose of Prototypes: Proven Product Discovery Tactics for Breakthrough Results

Note: This is part of the product creator series of articles, based on the overview article, The Era of the Product Creator.

As a VP of Product Management at HighLevel, Inc., I’m constantly reminded that prototypes aren’t deliverables—they’re decisions. I recently revisited “The Purpose of Prototypes” from Silicon Valley Product Group, and it reinforced a belief I hold deeply: we prototype to learn faster than risk compounds. In product discovery, the right prototype at the right moment helps us surface assumptions, test them quickly, and focus our teams on evidence over opinions.

When I frame the purpose of a prototype, I anchor on four core risks: value (will anyone care?), usability (can they figure it out?), feasibility (can we build it with our constraints?), and viability (does the business model work?). Each prototype exists to retire a specific risk, not to approximate the final product. If we can’t name the risk and the assumption, we’re not ready to build anything—not even a prototype.

Here’s how I choose: I start with the lightest-weight artifact that can answer the next most important question. If I’m unsure about value, I’ll run a simple landing page, ad test, fake door, or concierge experience. If usability is unclear, I’ll move to paper sketches or a Figma click-through. If feasibility is in doubt, I’ll commission a quick engineering spike, an API mock, or a data model prototype. If viability is the concern, I’ll test pricing, packaging, or acquisition economics before writing a single production line of code.

In our practice, ai-based prototyping and gen ai are accelerants. We use AI to generate realistic UI states, draft microcopy, create test data, simulate edge cases, and scaffold throwaway services for feasibility spikes. This shortens cycles dramatically, especially when paired with disciplined product discovery methods and clear success criteria.

I’ve found that forward deployed engineers working hand-in-hand with design and product lead to our fastest learning loops. We timebox aggressively (often 24–72 hours), instrument every prototype for the signal we need, and refuse to promote ideas to the roadmap until the relevant risk is retired. The result is more confidence, less waste, and momentum that teams can feel.

One recent example: a deceptively simple pricing and messaging test revealed that what we thought was a killer feature didn’t drive willingness to pay—but the workflow time-savings did. A one-day value prototype saved us three sprints of build and a painful launch reversal. That’s the power of purposeful prototyping.

My operating cadence is straightforward: articulate the assumption, select the minimum viable prototype, define what success (and failure) looks like, run the test with the right users, then decide—proceed, pivot, or pause. Repeat until the key value, usability, feasibility, and viability risks are de-risked. Only then do we invest in production.

For product creators, this mindset is liberating. Prototypes are not about polish; they’re about progress. If you’re navigating the transition described in “The Era of the Product Creator,” leaning into focused, risk-targeted prototypes will transform your product discovery velocity and your product management leadership impact.

Inspired by this post on SVPG.

October 22, 2025
From $2M to $100M ARR: Inside fal’s Explosive Pivot and the Future of Generative Media

Generative media is no longer a curiosity on the edges of product roadmaps—it’s fast becoming a core capability. Watching one company sprint from uncertainty to undeniable traction reminded me how much a decisive pivot, a developer-first brand, and ruthless focus can bend a growth curve. This is a story about finding product-market fit in real time, scaling with intention, and staying lean while the category accelerates beneath your feet.
Gorkem Yurtseven is the co-founder and CEO of fal, the generative media platform powering the next wave of image, video, and audio applications. In less than two years, fal has scaled from $2M to over $100M in ARR, serving over 2 million developers and more than 300 enterprises, including Adobe, Canva, and Shopify. In this conversation, Gorkem shares the inside story of fal’s pivot into explosive growth, the technical and cultural philosophies driving its success, and his predictions for the future of AI-generated media.
What stood out to me first was the clarity of the pivot: “How fal pivoted from data infrastructure to generative inference.” The hardest decisions often feel like abandonment—of code, roadmap, and even identity—but the right pivot reframes everything around a higher-signal customer need. That decision, described as “The hardest decision that saved the company,” unlocked a new trajectory and set a crisp north star for the team.
Equally important was the market intuition. As they put it, “Why ‘generative media’ is a greenfield new market.” Greenfield means pattern-breaking strategy: prioritize outcomes over parity, embrace new workflows rather than retrofit old ones, and measure value in quality, latency, and unit economics—not just features. In my experience, this is where product teams win or lose: you either build the new default or get trapped perfecting the old one.
fal’s “explosive year” wasn’t luck; it was systems thinking applied to a developer platform. The team stayed small—”lean <50-person team” and “Staying nimble as a 45-person company”—and built a brand that feels genuinely for builders: “Building a brand that resonates with developers.” That shows up in everything from docs and SDKs to the cultural quirks that scale signal, like “Why fal has 500 Slack channels.” Velocity and clarity compound when communication is designed for ownership.
Early traction came from sharp use cases and fast feedback loops. I loved the transition arc from “The early adopters of the first fal product” to “The transition from toy to tool.” In a new category, the fastest path to durable usage is making something delightful and then relentlessly hardening it for production: uptime targets, deterministic APIs, transparent pricing, and repeatable performance. That’s how you move from demos to dependable workflows.
The timing call is bold and specific: “Why 2025 is the year of AI-generated video” and “Predicting AI-generated film in 2027.” If you build in gen AI, this matters. Video will force teams to optimize for cost per second, temporal coherence, and developer ergonomics across long-running jobs. The winners will combine model choice (OpenAI, Anthropic, Google DeepMind, Stability AI; “Stable Diffusion XL (SDXL)”, “Sora”, “DALL-E”, “LLaMA”) with world-class inference, smart caching, and autoscaling that feels invisible to the developer.
On the go-to-market side, I see a masterclass in founder-led GTM and developer evangelism. “Competing in a fast-moving, fragmented market” requires sharp messaging and distinctive ideas. The story behind “GPU Rich / GPU Poor” is a perfect example: a memorable narrative that encodes a real infrastructure advantage. Pair that with “fal’s greatest optimization wins” and you get a brand promise rooted in measurable performance, not just clever copy.
Culture and team design are the force multipliers. “How to build a world-class team” and “fal’s unique hiring philosophy” emphasize high-slope talent, ownership, and speed over headcount. The result is a product org that ships, learns, and iterates without bureaucratic drag. For technical founders, “Learning sales as a technical founder” is a reminder that the best sales motion often emerges from the same instincts as great product discovery: ask better questions, observe real workflows, and sell through outcomes.
Here’s how I translate these lessons into a practical playbook for product leaders working in gen ai and developer platforms: double down on developer experience (time-to-first-output, clear pricing, robust SDKs), make latency and reliability your product features, sequence the roadmap from delightful demos to dependable production tools, and stay lean enough to pivot as models and use cases evolve. Above all, treat “Why generative media is a greenfield market” as a call to invent the defaults others will copy.
Looking ahead, the path is clear: as AI-generated video normalizes in 2025 and professional-grade content follows by 2027, the products that win will combine inference excellence with a brand developers trust. If you’re building in this space, now is the moment to ship fast, optimize relentlessly, and meet creators and developers where they already work.

October 22, 2025
Moments That Changed Us: Teresa Torres & Petra Wille on Leadership, Loyalty, and Product Discovery

Some conversations stay with you because they surface the hard-earned truths that quietly shape our judgment as product leaders. This episode of All Things Product with Teresa Torres and Petra Wille is one of those. As I listened, I found myself revisiting my own inflection points—times when prioritization became survival, when loyalty met reality, and when user research humbled my assumptions. What follows are the moments and mindsets I believe every product creator and product management leader can learn from.

Listen to this episode on: Spotify | Apple Podcasts

In this episode, Teresa and Petra swap the stories that shaped their careers. From navigating the fallout of the 2008 recession as a startup CEO, to realizing the company won’t love you back no matter how loyal you are, to the first user interviews that cracked open a new way of seeing product work—these are the pivotal (and sometimes funny) moments that changed everything. As I reflected, I connected these stories to practical patterns we all face: capacity limits that force clarity, leadership under uncertainty, and the discipline of product discovery.

At [02:30], Teresa’s crash course as a startup CEO during the 2008 recession reminded me that there are seasons in product where perfect information doesn’t exist—only direction and conviction. I’ve been there. In those moments, we earn trust by making the next best decision, communicating trade-offs clearly, and moving. That’s leadership when the stakes are real.

By [11:20], the conversation reframed prioritization as survival, not just a backlog exercise. I’ve learned the same lesson: hitting the limits of your own capacity reshapes how you prioritize. It’s not about doing more—it’s about deciding what not to do. In practice, that means aligning roadmaps to outcomes, not output, and letting OKRs focus the team on the few bets that matter now.

At [18:45], Teresa shares the insight that unlocked her agency as a leader: “No one knows the answer.” That line is liberating. When we stop searching for the mythical right answer, we create space for informed bets, time-boxed experiments, and evolving product strategy. I’ve seen teams accelerate the moment they internalize this.

At [29:10], Petra’s story—why the company doesn’t love you back—hits close to home. Loyalty is admirable, but without boundaries it becomes burnout. As leaders, we protect both people and outcomes by setting explicit expectations, designing sustainable on-call and delivery cadences, and recognizing impact early—long before a too-late pay raise tries to fix a deeper problem.

The [42:05] moment about the pay raise that came too late is a textbook example of how retention is a lagging indicator. Compensation, growth paths, and recognition must be proactive. If you wait for exit interviews to learn, you’ve already lost institutional knowledge and momentum.

At [50:15], Marty Cagan and Petra’s first user interviews at Starbucks show how humble, early customer conversations transform practice. Product discovery is not a ceremony; it’s a habit. Even scrappy interviews, when paired with a clear research objective and rapid synthesis, can change a roadmap. I encourage teams to start with simple, recurring conversations and make insights visible in sprint planning.

By [01:02:00], the funny research fail—“close the window” taken literally—delivers the humbling reminder that you are not your user. Language is loaded. Tasks must be unambiguous. And when in doubt, ask one more clarifying question. Every usability study I’ve run has revealed at least one assumption I didn’t know I was making.

Here’s what I took away as a leader and operator: capacity constraints are a gift if we let them focus us; uncertainty is the job, not a blocker; boundaries prevent burnout and build better products; and early, continuous user interviews keep us honest about outcomes over output. If your roadmap isn’t informed by real user context every week, it’s time to change your operating rhythm.

Follow Teresa Torres: https://ProductTalk.org

Follow Petra Wille: https://Petra-Wille.com

Mentioned in this episode: The True Story of Struggles and Success Of A Startup CEO with Teresa Torres by Barry O’Reilly: https://barryoreilly.com/explore/podcast/the-true-story-of-struggles-and-success-of-a-startup-ceo-with-teresa-torres/?ref=producttalk.org

Mentioned in this episode: Petra’s work on coaching product leaders: https://www.petra-wille.com/?ref=producttalk.org

Mentioned in this episode: Marty Cagan: https://www.svpg.com/team/marty-cagan/?ref=producttalk.org

Mentioned in this episode: iPAQ: https://en.wikipedia.org/wiki/IPAQ?ref=producttalk.org

Have thoughts on this episode? I’d love to hear which moment resonated most with you and how it’s shaping your product practice. Share your perspective and let’s learn from each other.

Inspired by this post on Product Talk.

October 22, 2025
Why I’m Tuning In to “In Depth”: Tactical Playbooks for Startup Hiring, Leadership, and Growth

When I first heard, “Welcome to In Depth, a new podcast from First Round Review that’s dedicated to surfacing the tactical advice founders and startup leaders need to grow their teams, their companies and themselves,” I immediately thought: this is the kind of operating wisdom I reach for every week. As a product leader who obsesses over product management leadership and the realities of scaling teams, I’m drawn to resources that move beyond inspiration and deliver concrete playbooks I can put to work on Monday.

The promise here is refreshingly pragmatic: “We’ll cover a lot of ground and a wide range of topics, from hiring executives and becoming a better manager, to the importance of storytelling inside of your organization. But every interview will hit the level of tactical depth where the very best advice is found.” That’s exactly where the hard problems get solved—whether you’re navigating the IC to manager transition, tuning your approach to product discovery, or tackling employee retention at startups when growth forces you to rewrite the org playbook.

From my vantage point, the most valuable conversations unpack the patterns behind great executive hiring, the cadence of outcomes vs output OKRs, and how storytelling shapes alignment across product, engineering, and go-to-market. I’m eager for insights that translate directly into product roadmapping and sprint planning, lessons on product-market fit that stand up under scale, and founder-led GTM tactics that keep teams focused on what matters.

I’m all in for discussions that get specific—what to ask in a VP interview, how to structure a 30/60/90 for new leaders, and the rituals that keep quality high without slowing velocity. If you’re building, leading, or leveling up your craft, this is time well spent.

I hope you’ll join us. Subscribe to “In Depth” now and learn more at firstround.com

Inspired by this post on First Round.

October 22, 2025
Going ‘Unreasonably Deep’: Hard-Won Product Lessons with Ayo Omojola from Cash App to Carbon Health

I sat down with Ayo Omojola, VP of Product at Carbon Health, to unpack the craft behind building in regulated industries and the discipline of choosing the right problems. Previously, he was the founding product manager on the banking team for Cash App at Square, where he co-created the Cash Card and helped build out Square’s technical banking infrastructure. He’s also a former founder of a Y Combinator-backed startup and an active angel investor, which gives him a unique lens into finding and evaluating startup ideas.

As we explored his time across healthcare and financial services, I was struck by how methodically he untangles regulation to reveal “the opportunities where it’s easy to stop.” That mindset—paired with his insistence on going “unreasonably deep” when building early products—mirrors the rigor I expect from high-performing product teams. It’s a reminder that in complex domains, product discovery starts with understanding constraints so thoroughly that they become catalysts for innovation.

Ayo thinks a lot about problem selection and makes the case for putting more effort into choosing what to work on. I couldn’t agree more. In my experience, a clear and deliberate bet at the outset compounds through product discovery, roadmapping, and execution—reducing thrash and sharpening the signal on product-market fit. The best product outcomes often stem from the discipline to say no until the “why now” and “why us” are undeniable.

If you’re thinking about starting a company someday, or you’re a product leader who hopes to help a new product take shape, this conversation will resonate. We talk about balancing speed with diligence, aligning teams around crisp context, and turning ambiguity into tractable work without losing sight of the customer. These are the muscles that separate good product management from product management leadership.

Even if company-building isn’t your immediate goal, there’s a lot to learn from the frameworks Ayo absorbed from exceptional operators. We dig into how to get better at process, how to set context so decisions scale, and why “optimizing for the outstanding” creates leverage across hiring, execution, and outcomes. I share where I’ve seen these approaches pay off in practice—especially during zero-to-one product discovery and early product roadmapping and sprint planning.

We also cover his management and hiring philosophy, including why he loves to hire former founders. I’ve seen the same pattern: ex-founders bring end-to-end ownership, a bias for outcomes over output, and a resilience that’s invaluable when the path is unclear. In fast-moving environments, those traits accelerate learning loops and raise the bar for the entire team.

You can follow Ayo on Twitter at @ay_o. For reference, the leaders he gave a shout out to in the episode include Robert Andersen (the founding designer at Square), Dhanji Prasanna (who led engineering for Cash App), Jim Esposito (Operations Lead for Cash App) and Emily Chiu (who led strategic development efforts for Cash App).

Inspired by this post on First Round.

October 22, 2025
Hard-Won CEO Lessons: Steve El‑Hage on Pivots, Burnout, and Rebuilding After a Revenue Cliff

I recently connected with Steve El-Hage, co-founder and CEO of Drop, an electronics company that creates products powered by feedback by a massive community of enthusiasts and experts. As I listened, I put on both my product management leadership hat and my operator lens to unpack what other product creators and founders can take into their own journeys. Reflecting on his 8-year, heads-down grind since becoming a first-time founder at 22, Steve shares the lessons that he figured out the hard way, from revenue dropping off a cliff and painful pivots, to hiring blunders and severe burnout. When I hear “revenue dropping off a cliff,” I immediately think about product-market fit lessons and the mechanics of founder-led GTM. In my experience, these moments are brutal but clarifying: they force a ruthless reordering of priorities, sharper customer segmentation, and tighter feedback loops. I’ve learned to ask two simple questions in crises like this: Which customers are truly pulling the product? What’s the smallest, fastest test that can validate our next bet without mortgaging the roadmap? The phrase “painful pivots” resonates because high-quality pivots are really about excellent product discovery under pressure. I anchor teams on outcomes vs output OKRs to avoid thrash, ensuring we change direction with purpose rather than panic. For me, the discipline is simple: re-state the problem in customer language, identify the leading indicator that proves we’re moving the needle, and then run small, compoundable experiments until the signal is undeniable. Hiring blunders are equally instructive. Early-stage teams often over-index on resumes and under-weight learning velocity, values alignment, and ownership. I’ve corrected this by designing hiring loops that test real work, not theater, and by being explicit about the IC to manager transition expectations from day one. Strong onboarding and clear career paths improve employee retention at startups, but it starts with hiring for trajectory, not just pedigree. Severe burnout is the tax we pay when pace outruns process. I’ve found that setting non-negotiable operating cadences—weekly priorities, monthly retros, and quarterly business reviews alongside OKRs (QBRs vs OKRs)—creates healthy pressure without chronic overload. Protecting maker time, limiting work-in-progress, and celebrating disciplined “no’s” are not luxuries; they are system-level safeguards that keep teams creative and resilient. What Steve’s journey underscores for me is both humbling and practical: the hardest-earned lessons become your operating advantages. If you’re navigating a pivot, rebuilding after a revenue cliff, or evolving your team through growth, lean on customer-validated insights, tighten your feedback loops, and operationalize focus. That’s how you turn hard ways learned into repeatable wins.

Inspired by this post on First Round.

October 22, 2025
Start With the Story: Leadership Lessons from Drift’s David Cancel I Use to Elevate Teams

“Start with the story” isn’t a slogan for me—it’s a daily operating principle. As I guide product strategy and align go-to-market with product discovery, I’ve seen how a clear narrative unlocks focus, speeds decisions, and lifts execution. That’s why David Cancel’s perspective resonates so strongly: when you build from the story, you build momentum.

David has been a CEO and founder of multiple different companies throughout his career. He’s also been a software engineer, a serial CTO, and the Chief Product Officer at Hubspot, giving him a unique lens into company building and leadership at different levels. That combination of product, engineering, and executive leadership creates the kind of pattern recognition I rely on when coaching PMs and shaping product management leadership practices across teams.

In my experience, the fastest way to align product, marketing, and sales is to anchor everyone in the same narrative. David’s framing around storytelling at Drift, a conversational marketing and sales platform, crystallizes this. From screenplay writing inspiration, to how storytelling training is part of their onboarding, David shares how they teach storytelling and drive narrative internally at Drift. I’ve adopted a similar approach—story-first onboarding for product creators and PMs, so every spec, roadmap, and customer interaction reinforces the same promise and positioning.

The leadership muscle here isn’t just crafting a compelling story—it’s keeping altitude discipline. He also shares tactical advice for engaging with exec teams and getting better at zooming in and out as CEO, as well as some really tactical frameworks, including Charlie Munger’s practice of inversion, the weekly rituals Drift relies on, and how they use asynchronous video communication. I use these same moves: inversion to pressure-test roadmaps and risks, weekly rituals to reinforce priorities, and async video to scale clear, human communication without meeting sprawl.

On my teams, inversion clarifies trade-offs: before we pursue a bet, we ask, “If this fails, what will have been the likely causes?” That simple prompt improves product discovery, sharpens founder-led GTM motions, and accelerates product-market fit lessons. When we meet, we start with a crisp narrative—who the customer is, what their struggle looks like, and why our solution is the inevitable next step. Outcomes replace output, and teams rally around impact.

I’ve also found that storytelling is a coachable skill, not an innate talent. We run lightweight workshops where PMs deconstruct great narratives (including screenplay structures) and rebuild their own. The effect is immediate: clearer problem statements, tighter product roadmapping and sprint planning, and better executive readouts that move decisions forward instead of sideways.

If you want to dive deeper into David’s perspective, you’ll find practical resources worth bookmarking. You can follow David on Twitter at @dcancel. He also pens a popular newsletter called “The One Thing,” and hosts a great podcast called “Seeking Wisdom.” For reference, the books he mentioned in the episode include Jon Kabat-Zinn’s work on mindful meditation, and “The Passion Paradox” by Brad Stulberg.

To learn more about how Drift approaches storytelling, check out this article David wrote for Inc:

https://www.inc.com/david-cancel/five-storytelling-tips-to-better-communicate-your-brand-message.html

To learn more about Charlie Munger’s concept of inversion that David mentioned, check out this Farnam Street post: https://fs.blog/2013/10/inversion/

If you’re leading teams, think of story as a system: a shared language for product, marketing, and sales; a filter for priorities; and a mechanism for speed. It’s a must-listen for current founders and CEOs, and anyone looking to level up their leadership skills. When we start with the story, we don’t just communicate better—we build better.

Inspired by this post on First Round.

October 22, 2025
Win-Win Partnerships: Stripe & Notion Lessons to Negotiate Smarter and Scale Faster

I’m always searching for practical, battle-tested strategies to build platform ecosystems and business development motions that actually move the needle. Cristina Cordova, Notion’s Head of Platform & Partnerships, brings exactly that kind of rigor. Previously, she was the 28th employee and the first partnerships hire at Stripe, where she cultivated partnerships with companies like Shopify, Squarespace and Apple, built out the BD org, and led their new Corporate Card effort.

After a decade in partnerships, Cristina has bagged big deals, honed her negotiation skills, built out teams — and made plenty of mistakes she hopes others can learn from. Her candor resonates with the realities I see leading product and platform work — the high-leverage wins, the inevitable trade-offs, and the importance of structured decision-making.

In today’s conversation, Cristina pulls from across her career to share the inside scoop on deals that had an unexpected outsized impact — as well as the ones that went sideways. Hearing how she navigated both reaffirmed a core principle I hold: partner success starts with a clear mutual value narrative and disciplined execution across product, GTM, and ops.

She also shares her playbook for being a startup’s first partnership hire, including the three critical areas to focus on first, and the common traps to avoid. It’s also full of actionable tactics on everything from dealing with partners trying to push you around, to how to hire for partnerships roles and structure the org chart.

What stood out to me is how transferable these lessons are to product management leadership. The best partnership strategies are product strategies: prioritizing integrations that deepen product-market fit, sequencing launches to maximize learning, and aligning incentives so partners champion adoption, not just sign paper.

On negotiation, I’ve seen the same patterns Cristina highlights. Win-win deals come from clarity on your non-negotiables, crisp success metrics, and a shared plan for activation — not oversized concessions. I coach teams to pre-wire decisions, define BATNA early, and document a mutual success plan that ties product roadmapping and sprint planning directly to GTM milestones.

Hiring and org design matter just as much as the deals themselves. Great partnership talent blends product discovery instincts with zero to one B2B marketing chops and the discipline of outcomes vs output OKRs. Structure the BD and platform teams so ownership is unambiguous: who drives integration quality, who owns co-marketing, and who runs partner QBRs vs OKRs alignment across the business.

Whether you’re building your first platform integration, leveling up a partner-led GTM motion, or refining how product and BD collaborate, the tactics here can accelerate your path. The stories of how Stripe and Notion scaled offer a rare, practical lens you can apply immediately — from selecting the right lighthouse partners to operationalizing the learnings across your roadmap.

Inspired by this post on First Round.

October 22, 2025
Inside Upstart’s Unlikely Rise: Dave Girouard’s playbook for pivots, speed, and hiring

I recently listened to a deep dive with Dave Girouard, the CEO and co-founder of Upstart, an AI-powered lending platform that recently went public. Before founding Upstart, Dave was President of Google Enterprise, and spent 8 years building Google’s billion dollar cloud apps business. Hearing his operating cadence and decision frameworks through the lens of a public-company founder was a masterclass for anyone leading product and business strategy.
From a product management leadership perspective, what stood out was how the initial idea evolved into a durable business model. Dave opens up about the early business model pivot and what it took to execute it without fanfare — flying under the radar of Silicon Valley — while staying obsessively focused on product-market fit. His candor about why he “sucked at fundraising” and how his co-founders have stuck together for almost a decade offers rare, unvarnished lessons on founder psychology, trust, and execution.
I’ve seen how operating outside the spotlight can be a strategic advantage: fewer distractions, faster iteration cycles, and clearer signal on customer value. Pair that with disciplined go-to-market, and you can build momentum the market only recognizes later. Upstart’s path underscores the compounding effect of shipping speed, ruthless prioritization, and a willingness to refactor assumptions when the data demands a pivot.
I especially appreciated his “Are you Airbnb or Paypal?” test — it’s a crisp way to force clarity on whether a product depends on network effects or transactional trust, which in turn shapes your product discovery, risk controls, and compliance roadmap. His advice to look at your career in landscape mode resonates with how I coach emerging product leaders: zoom out, map the terrain, then choose the next hill deliberately rather than chasing the nearest shiny object.
Dave also shares three mental models he leans on to manage his psychology as a founder. As operators, we all need systems that keep us calm under asymmetric uncertainty — especially when a business model pivot or fundraising cycle compresses the signal-to-noise ratio. I’ve found that writing down pre-commitments, instrumenting leading indicators, and scheduling deliberate recovery are complementary to the frameworks he describes.
On operating cadence, his “management by exception” philosophy aligns with how high-leverage leadership teams run: push context, pull exceptions. The practical implications are clear — instrument what matters, set thresholds, and let autonomous teams own outcomes. It’s a blueprint for scaling without bureaucracy, especially when latency between decision and customer impact must be measured in days, not quarters.
The hiring lesson that hit home: for executive roles, lean on references, not interviews. In my experience, backchannel signals about how a leader performs in ambiguity and aligns a founder-led GTM are far more predictive than a polished interview loop. Combine that with structured trials or outcome-based charters, and you de-risk critical leadership hires while protecting culture.
There are also transferable insights from what he learned from Google and how he runs his leadership team — tight feedback loops, crisp operating documents, and an insistence on speed as a habit. For AI-powered lending and beyond, the pattern is the same: clarify the decision, collapse the cycle time, and let empirical results, not narrative gravity, determine what scales.
If you’re building in fintech or any category where trust, risk, and regulation intersect, this conversation is worth studying. It’s a reminder that unconventional trajectories can still compound into category-defining companies — and that the right mental models, operating mechanisms, and hiring heuristics turn volatility into a strategic advantage.

Inspired by this post on First Round.

October 22, 2025
The Game-Changing System Behind Kindle, AWS, and Prime—and How I Apply It Today

I’m constantly looking for systems that outlast leaders and market cycles. When I picked up “Working Backwards,” which provides an inside look at the leadership principles and business processes that have made the company so successful, I recognized a playbook product teams can trust when the stakes are high and ambiguity is higher.

Bill Carr and Colin Bryar bring rare operator credibility to the topic. Bill started at Amazon in 1999, and went on to launch and run the Prime Video, Amazon Studios, and Amazon Music businesses before he left the company in 2014. Colin joined Amazon in 1998, as the Director for Amazon Associates and Amazon Web Services Programs. He also spent two years as Jeff Bezos’ technical advisor or “shadow,” and later served as the COO for IMDb.com.

Their stories illuminate Amazon’s culture of innovation and the origin stories of the Kindle, AWS, and Prime businesses. From granular details about the “working backwards” process, to an inside look at how players like Jeff Bezos and incoming CEO Andy Jassy operated up close, the lessons sharpen what “dive deep” and operational excellence look like in practice.

Several ideas have become mantras for my product management leadership practice: why innovation can’t be a part-time job, the perils of taking a “skills-forward” approach to exploring new opportunities, and why mechanisms are more important than good intentions. These principles reinforce the shift from outputs to outcomes and bring needed rigor to outcomes vs output OKRs.

At HighLevel, we apply a working-backwards mindset to product discovery: we start from the customer benefit, pressure-test the narrative with real users, and map success metrics before we write a line of code. This discipline accelerates product-market fit lessons, reduces thrash in product roadmapping and sprint planning, and clarifies trade-offs when timelines and resources are tight.

Mechanisms turn intent into results. For us, that means single-threaded ownership for critical bets, decision logs that preserve context, lightweight written narratives that force clear thinking, and weekly business reviews that highlight leading indicators. These habits create the tight feedback loops needed to dive deep, course-correct quickly, and scale operational excellence.

If you’re a founder, product creator, or operator scaling a SaaS platform, the throughline is simple: make innovation a full-time commitment, resist “skills-forward” biases when exploring new opportunities, and demand mechanisms that institutionalize good judgment. That’s how durable systems outlast any single leader.

Learn more about “Working Backwards” here.

Inspired by this post on First Round.

October 22, 2025
From Bump to a Billion Users: My Hard‑Won Product Lessons from David Lieb and Google Photos

I rarely get to trace a consumer product’s journey from a blank slate to one billion users, end to end. In reflecting on my conversation with David Lieb, Director of Google Photos, I was struck by how deliberate product discovery, clear problem framing, and thoughtful org design compounded into outsized impact.

David’s arc is instructive. Previously, he was the founder/CEO of Bump, an app that allowed users to swap contact information by physically bumping phones. Bump was acquired by Google in 2013, and formed the basis for the design of Google Photos, which launched in 2015 and passed the 1 billion users mark in 2019.

He walked me through building a consumer product from scratch and scaling it to over a billion users in just four years. What resonated most was the candid recounting of early mistakes at Bump, the realities of navigating big company politics at Google, and the methodical way the team pinpointed the core problem in the photo-sharing space.

The rigor of product discovery stood out. From the precise questions they asked in user interviews, to how they stack ranked for the canonical users, the team built conviction by prioritizing the right people and the right jobs to be done. I’ve seen too many teams spread thin across edge cases; this approach forces clarity on who you serve first and what you ship next.

We also dug into what it takes to operate at Google’s scale: planning discipline, org design that minimizes cognitive overhead, and mechanisms that keep outcomes ahead of output. For me, the difference between motion and progress is how crisply goals are defined and how tightly execution aligns to them—especially when the stakes and surface area grow.

On org design, I appreciated the practical nods to models like the Spotify “squads’ model, emphasizing cross-functional accountability and autonomy calibrated for speed without sacrificing cohesion. The key is empowering teams to ship independently while keeping a shared strategy and metrics that ladder up.

My playbook takeaways are direct. Narrow the problem statement until it becomes unambiguous. Use user interviews to validate the problem, not to seek applause for your solution. Stack rank canonical users and ruthlessly prioritize. Translate that focus into product roadmapping and sprint planning tied to measurable outcomes—not vanity metrics. And as you scale, evolve the structure so teams can move fast while the product narrative stays singular.

Whether you’re an early product builder or leading a mature platform, this blend of founder scrappiness and big-company craftsmanship is a blueprint. The path to one billion users isn’t a growth hack; it’s clarity of problem, empathy for users, and organizational design that compounds over time.

Inspired by this post on First Round.

October 22, 2025
Build Scalable Startup Systems: My Take on Kevin Fishner’s Writing-First, KPI-Driven Playbook

When I think about building enduring startups, one principle guides my approach: treat the company itself as the product. That mindset came into sharp focus as I studied the operating systems behind Kevin Fishner, Chief of Staff at HashiCorp. The rigor and clarity of his approach offer a blueprint any product management leader can adapt to scale with speed and integrity.

As the first business hire at the cloud infrastructure automation company, he previously built out the sales, marketing and product management teams. That trajectory matters: it’s rare to see one leader connect go-to-market, product management, and operational cadence so cohesively. The result is a system that aligns strategy, execution, and learning loops without creating organizational drag.

Now as chief of staff, he’s focused on building a strong foundation of company-wide systems, now that the team has grown to over 1000 people. This is where great product management leadership shines—codifying how decisions are made, how work moves, and how teams align around outcomes as headcount and complexity expand.

In today’s conversation, Kevin shares a detailed look at how they run meetings, set and track progress toward goals, and make decisions through writing at HashiCorp. I’m a strong proponent of a writing-first culture as the backbone of a scalable operating cadence: crisp memos reduce meetings, strengthen decision quality, and preserve context. Combined with clear meeting charters, owner-defined agendas, and time-boxed decision-making, this turns process into a lever for speed—without sacrificing rigor.

He also shares incredibly tactical advice for making annual planning more effective, including the unique business simulation they run, their scorecard system, and the weekly and quarterly meetings that help them stay focused on important KPIs. My lens: anchor annual planning in outcomes vs output OKRs, then connect those outcomes directly to product roadmapping and sprint planning. Use QBRs vs OKRs thoughtfully—QBRs to pressure-test business performance and assumptions, OKRs to lock in the next set of measurable bets. The scorecard becomes the single source of truth for progress and trade-offs, while the business simulation stress-tests priorities before they hit roadmaps.

Whether you’re a chief of staff, a founder spinning up a company from scratch, or a manager scaling a team, you’ll find practical takeaways here to make your organization more effective. I’ve distilled templates, prompts, and visuals to help you adopt a writing-first decision model, stand up a repeatable meeting rhythm, and operationalize goal tracking so KPIs stay front and center—not buried in dashboards.

If you’re serious about building startup systems that scale, adapt these practices: align on a few critical outcomes, document decisions in writing, instrument scorecards that ladder to KPIs, and commit to weekly and quarterly cadences that turn strategy into execution. That’s how you build an organization that learns faster than it grows.

Inspired by this post on First Round.

October 22, 2025