Tag: product-market fit lessons

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
How Atlassian Scaled Without a Sales Team: Product-Led Growth, Pricing, and Channel Plays

When I study companies that truly break the mold, Atlassian stands out. In a recent deep dive with Jay Simons — who’s currently a partner at Bond and serves on the boards of Hubspot and Zapier, and previously had a long run as the President of Atlassian — I unpacked the non-consensus moves that propelled products like Jira, Confluence and Trello into the software collaboration canon.

What struck me most were the elements people often misunderstand or overlook: the deliberate choice to build a product that can sell itself, and the discipline to defer short-term openings in favor of more durable long-term opportunity. As a product leader, I see this as a masterclass in product-led growth, go-to-market focus, and product management leadership.

Jay framed Atlassian’s model as a “three-legged stool” of self-service, a global network of channel partners, and eventual enterprise upselling. That structure created compounding advantages: self-service lowered friction and acquisition costs, partners localized value and extended reach, and enterprise upselling unlocked larger ACVs when customers were truly ready. I’ve seen similar dynamics in my own work — when you design for natural adoption first, selling becomes an accelerant rather than a crutch.

We also dug into Atlassian’s pricing strategy and how the team evaluated adjacent product areas. The thinking was intentionally first principles: align price with realized value, protect the user experience, and expand only where the product and the customer journey genuinely intersect. That’s a powerful SaaS pricing lesson — price architecture and packaging should help customers buy the way they want to adopt.

From spinning the flywheels of a remarkable product and a high-velocity self-service funnel, to building a culture that focuses on first principles, the throughline is clarity of intent. In my experience, that clarity keeps teams from chasing vanity metrics or over-rotating to near-term revenue at the expense of product-market fit and durable growth.

This blog post from Intercom has the flywheel graphic that Jay mentioned in the episode. https://www.intercom.com/blog/podcasts/scale-how-atlassian-built-a-20-billion-dollar-company-with-no-sales-team/

If you’re leading go-to-market or revenue, or you’re building at a startup, there’s rich, actionable guidance here: sequence growth levers, keep the buying motion as simple as the product itself, and earn the right to upsell by delivering undeniable value first. That’s the kind of product strategy that compounds.

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
Twilio’s CEO on Peaks, Valleys, and C-Suite Truths: Hard-Won Lessons for Product Leaders

When I study enduring product companies, I look for the inflection points that shaped them. In revisiting the journey of Jeff Lawson, co-founder and CEO of Twilio, I was struck by his longevity and resilience — he’s spent the last 13 years building and running the company, including leading through a successful IPO in 2016. From my product leadership lens, the arc of Twilio’s growth offers a playbook packed with hard-earned lessons for builders at every stage.

One of the early peaks came from defying conventional wisdom. Rather than waiting for perfect product-market fit from a single product, Jeff pushed to launch a second product in Twilio’s early days. I’ve taken a similar stance in my own work: when customer signal is strong and the surface area is adjacent, a thoughtfully scoped second product can accelerate learning, diversify revenue, and strengthen the platform story — as long as you preserve focus with crisp strategy, clear ownership, and a rigorous roadmap.

But no ascent is without valleys. A pivotal low point arrived when one of Twilio’s biggest customers, Uber, significantly scaled back their investment in Twilio’s products. Every product leader knows the sting of concentration risk — when a single customer’s shift reverberates across forecasts, roadmaps, and morale. The real lesson is how you respond: deepen value for the broader customer base, rebalance your portfolio, and institutionalize dependency reviews so one customer’s change doesn’t become an existential threat.

Jeff’s operating system also reflects a powerful inheritance from Amazon: a bias to “write it down.” I share this conviction. Clear, written narratives clarify assumptions, expose trade-offs, and make decisions auditable over time. It’s why “PowerPoint is a terrible decision-making tool.” Slides may persuade; writing forces us to think. In my teams, we prefer narrative memos, PR/FAQ-style artifacts, and decision logs to drive alignment, speed, and accountability.

Inside the C-suite, Jeff instituted practices that many product organizations underutilize. They run post-mortems when things go right — not just when they go wrong. In my experience, reverse-engineering wins reveals the leading indicators and repeatable behaviors that often get lost in celebratory moments. Equally important, Jeff had an “aha” moment that his executive team needed to argue more. Healthy debate is not dysfunction; it’s a prerequisite for durable decisions. The goal is principled dissent, time-boxed contention, and a clear decision owner — then unwavering commitment to execution.

For company-builders across industries and growth stages, these patterns are universally applicable: expand thoughtfully, manage risk before it manages you, privilege writing over slides, study your wins, and cultivate constructive conflict. That’s how you turn peaks and valleys into durable operating rhythms that scale from product-market fit to public markets.

If you want a deeper dive into Jeff’s philosophy on engineering leverage and developer-first cultures, his book “Ask Your Developer: How to Harness the Power of Software Developers and Win in the 21st Century.” is a practical field guide: https://www.amazon.com/Ask-Your-Developer-Software-Developers/dp/0063018292

For a closer look at how Twilio operationalizes company values — including the famous “draw the owl” ethos — explore this overview: https://review.firstround.com/draw-the-owl-and-other-company-values-you-didnt-know-you-should-have

You can follow Jeff on Twitter at @jeffiel.

Inspired by this post on First Round.

October 22, 2025
Inside Tido Carriero’s Playbook: Build World-Class Engineering Orgs and Nail Product/Market Fit

I’m drawn to leaders who’ve built both high-performing engineering organizations and durable products. Tido Carriero, the Chief Product Officer at Segment, a customer data platform which was recently acquired by Twilio, exemplifies that trajectory. Before that, he built out the engineering teams that worked on the core product and the initial business product at Dropbox. Tido started out his career in 2008 as an early member of the Facebook ads engineering team, and went on to become an eng manager on the Pages team — a pivotal IC to leadership transition that resonates with many of us in product and engineering.
What stands out in his journey are pragmatic lessons on building engineering orgs and launching new product lines at several top tech companies. His reflections on the pros and cons of single threaded leadership and the black box analogy for assessing a team’s performance offer concrete ways to interrogate how work actually gets done. In my own practice, I pair these lenses with outcomes vs output OKRs, tight product roadmapping and sprint planning, and a clean operating cadence that links QBRs vs OKRs. Together, these mechanisms create clarity in org design, planning, and execution — and make performance visible without micromanaging.
For new engineering managers and new managers-of-managers, I appreciated the practical “gems of advice.” That IC to manager transition is rarely linear; success hinges on shifting from personal velocity to organizational throughput. I coach first-time managers to build credible operating systems early: explicit decision rights, transparent prioritization, and lightweight feedback loops. One simple ritual I rely on is a weekly narrative update that forces crisp, outcome-focused thinking — a habit that complements any try do consider framework a team may use.
We also explored the path to product/market fit, especially for multi-product strategies — an area where many B2B teams struggle. Tido shares his advice for going from zero to one in a new product, including the simple milestone his teams have to hit before he’ll greenlight a new project, why he prefers iterative approaches over “big bang launches,” and his thoughts on why Dropbox struggled here. My own playbook mirrors this: invest in fast product discovery, define a clear gate tied to must-have user behavior, and resist vanity launches until repeatable pull exists. Small, well-instrumented bets compound; “big bang launches” rarely do.
If you want to go deeper on finding product/market fit in the context of multi-product strategies, Tido shares more of his thinking here: https://segment.com/blog/finding-product-market-fit-again/. It’s a useful companion for leaders calibrating zero-to-one efforts alongside an at-scale core business.
The through line across these lessons is disciplined simplicity. Whether you’re architecting engineering orgs, coaching the IC to manager transition, or charting zero to one in a new product, choose mechanisms that surface reality quickly, reward learning, and keep teams focused on outcomes. That’s how world-class organizations build, ship, and iterate their way to enduring product/market fit.

Inspired by this post on First Round.

October 22, 2025
Inside Product-Led Growth: Self-Serve, Pricing, and Prioritization Lessons from Kate Taylor

I recently sat down with Kate Taylor, who recently joined Notion as their Head of Customer Experience. Previously, Kate spent 8 years at Dropbox, leading their SMB revenue and scaled sales operation before leaving in 2020. Prior to that, she started her career as a sales rep at Salesforce. That trajectory alone offers a rare, end-to-end vantage point across product-led growth, scaled sales, and customer experience — precisely the intersection where modern SaaS wins or loses.
In our conversation, Kate shared a wealth of advice for building out product-led growth and self-serve motions. She shared tons of nuances around going up market, competing with sales and product planning, offering up tactical advice that any founder, product or go-to-market leader can learn from. As someone who has built PLG and hybrid motions, I found her guidance both pragmatic and immediately applicable — especially for teams balancing self-serve efficiency with enterprise demands.
We went deep on product prioritization. At Notion, their system of 700 tags enables a rigorous, multi-dimensional view of customer needs and product work. Hearing specific examples of tradeoffs they’ve had to navigate reminded me how essential it is to pair qualitative signal with quantitative usage data — and to operationalize that insight in product roadmapping and sprint planning. My takeaway: a well-structured tagging and feedback taxonomy is a force multiplier for product discovery and product-market fit lessons.
We also explored pricing and packaging — from specific experiments at Dropbox to why interestingly Notion’s trial isn’t time based. That philosophy reframes trials around value realization and activation, not arbitrary timelines. In my experience shaping SaaS pricing, this approach improves conversion and long-term retention when you align paywalls to “aha” moments and clear outcomes. It’s a call to design pricing alongside onboarding, not after it.
Customer experience was another rich vein. We discussed how to handle a wide range of use cases while building the “front door” customer experience her team envisions. From why customer service shouldn’t be focused on getting customers off the phone faster, to the questions she asks to find more signal in their product feedback, Kate’s perspective elevates support from a cost center to a strategic insight engine. I’ve seen the same: the best CX loops feed product planning, reduce churn, and strengthen go-to-market alignment.
We closed on leadership. Kate unpacked why she hires for curiosity, how she teaches teams to ride the ups and downs of startup life, and how working for three very different CEOs — Marc Benioff, Drew Houston and Ivan Zhao — has impacted her own leadership style. The throughline is deliberate learning: create environments where product managers and operators can test, reflect, and iterate quickly — the same principles that make PLG work at scale.
If you’re building or refining a product-led, self-serve motion — or moving upmarket without breaking what already works — these insights on prioritization, pricing, and customer experience provide a clear blueprint. My advice: operationalize feedback, pressure-test your packaging against value moments, and treat support as your highest-signal discovery channel. That’s how you turn strategy into compounding growth.

Inspired by this post on First Round.

October 22, 2025
From Instacart to Anomalo: Elliot Shmukler’s Zero-to-One Playbook for Product Leaders

As a product leader who obsesses over data quality and founder-led GTM, I’m energized by Elliot Shmukler’s trajectory and the problem he’s tackling at Anomalo — which is a platform that validates and documents all of your data. After leading product and growth teams at Instacart, Wealthfront, LinkedIn, and eBay, Elliot stepped into the founder/CEO role to drive a true zero to one build. That arc offers a grounded blueprint for product management leadership, product-market fit, and disciplined execution.

In this conversation, Elliot’s most recent stop stands out: he was Instacart’s Chief Growth Officer, driving fast and profitable growth and geographic expansion. Before that, he served at Wealthfront as the VP of Product and Growth and as a product leader at LinkedIn and eBay. That context matters because it informs how he now builds Anomalo with an eye for focused experimentation, clear value propositions, and operational excellence.

From my vantage point, the jump from executive to CEO resets the scoreboard. Elliot’s reflections on the zero-to-one phase mirror what I see in early-stage company-building: the need to aggressively prioritize time, protect founder focus, and qualify demand. He underscores a simple but costly trap I’ve witnessed too — wasting cycles on prospects who aren’t actually buyers. My playbook: define disqualification criteria early, insist on access to the economic buyer, require clear problem urgency, and time-box proofs of concept so founder energy fuels real pipeline, not vanity interest. This is classic founder-led GTM discipline and pays compounding dividends.

We also dig into how he picks extraordinary companies to work for. Elliot leans on sharp questions as a candidate and borrows decision-making frameworks from his poker playing. I resonate with that expected-value mindset: when stakes are uncertain, structure decisions around odds, outs, and downside protection. In product discovery, I translate that to staged bets, explicit kill criteria, and A/B tests that quantify lift before we scale. It’s a rigorous way to avoid narrative fallacy and to stay outcomes over output in OKRs.

Another thread that hits home: lessons from the best CEOs he’s worked with. The standout habits are crisp, frequent communication, transparent decision journals, and mechanisms that keep office politics at bay so the best ideas surface. In my teams, we pair written narratives with open metrics dashboards and “disagree-and-commit” rituals to reduce ambiguity and speed alignment. The result is faster feedback loops and clearer ownership across product roadmapping and sprint planning.

If you’re a founder in customer discovery, an executive eyeing your own startup, or an early-career builder trying to spot the next unicorn, there’s practical guidance here. You’ll find tactics for zero to one B2B marketing, qualifying enterprise demand, navigating product-market fit, and sharpening product management leadership skills you can apply today.

You can follow Elliot on Twitter at @eshmu.

To learn more about how Elliot uses A/B testing as a management framework, check out this article on First Round Review: https://review.firstround.com/how-a-b-testing-at-linkedin-wealthfront-and-ebay-made-me-a-better-manager

And check out “The Goal,” which Elliot cited as the most influential management book he’s ever read: https://www.amazon.com/Goal-Process-Ongoing-Improvement/dp/0884271951

Inspired by this post on First Round.

October 22, 2025
From Zero Customers to IPO: Eric Berg’s Hard-Won Playbook for the Messy Middle

I’ve been revisiting the hard-won lessons behind durable product companies, and Eric Berg’s journey is a masterclass. Eric Berg is the CEO of Fauna, which is an adaptive operational database platform. In joining Fauna as its CEO in the summer of 2020, he brought a wealth of experience as a product leader. Most recently, he was the Chief Product Officer at Okta, scaling the company from 10 employees and zero customers to its eventual IPO in 2017. He started his career in product at Intel, working under the legendary Andy Grove, as well as a five-year stint as a product leader at Microsoft.

From a product management leadership lens, the earliest chapters at Okta are a blueprint for zero to one B2B marketing and founder-led GTM. I break down his early go-to-market lessons and the keys to honing in on an ICP to get Okta off the ground, highlighting how tight product discovery, crisp problem statements, and ruthless prioritization turn ambiguity into product-market fit.

What stands out is the often-maligned “messy middle” — the stretch when traction exists but entropy expands. Eric’s moves on “moving upmarket” and evolving a “pricing and packaging model” are reminders that, when done well, takes a company to new heights. For SaaS pricing, I lean on value metrics tied to critical jobs-to-be-done, clear guardrails for discounting, and a win–loss feedback loop owned jointly by product and sales.

We then switch gears to team building and company building. The cultural patterns that stick with me: hire “folks up and down the org chart with the right ego to talent ratio” and operationalize a “disagree and commit” value so it’s not just a long-forgotten team motto. Practically, that means defining decision types (one-way vs. two-way doors), naming a DRI and approver for every call, time-boxing debate, and documenting the rationale so execution never stalls.

On execution mechanics, I’ve found that outcomes vs output OKRs paired with QBRs vs OKRs alignment creates a healthy cadence from strategy to delivery. When you layer in forward deployed engineers and structured customer advisory boards, feedback cycles compress without sacrificing focus — a powerful pattern in both product roadmapping and sprint planning.

Finally, the perspective shifts “as he approaches one year of sitting in the CEO seat” underscore the difference between building products and building a business. Capital strategy, talent density, and narrative become first-class product surfaces. As a product creator, I translate this into designing org APIs, setting explicit burn-to-learn budgets, and treating pricing, packaging, and GTM as core parts of the product.

If you’re navigating product-market fit lessons, wrestling with “moving upmarket,” or recalibrating SaaS pricing, this playbook maps the trade-offs from 0 customers through the “messy middle” and beyond. It’s a grounded field guide for product folks and operators who want to scale with clarity, strengthen culture, and accelerate learning without losing the thread.

Inspired by this post on First Round.

October 22, 2025
Ask Why It Won’t Work: Hard-Won 0→1 Lessons, Pre-Mortems, and Founder-Led GTM from Persona

I recently sat down with Rick Song, the co-founder and CEO of Persona, a platform that enables companies to create the ideal identity verification experience for their customers. Before founding Persona in 2018, Rick was an engineer at Square for 5 years, and an early team member at Square Capital. As someone who leads product teams and thinks deeply about product-market fit and go-to-market, I was eager to unpack the 0 to 1 thinking behind Persona’s trajectory.

Rick is at an exciting inflection point in his journey of building from zero to one — just last week, Persona shared that they’ve raised a $50 million Series B round. The company plans to double the team this year to keep up with revenue that’s surged more than 10x and a customer base that’s grown to include big logos like Square, Postmates, and Gusto. For anyone operating in B2B SaaS, that’s the kind of signal you can’t ignore.

In our conversation, one theme stood out: Rick is somewhat obsessed with the idea of pre-mortems, or figuring out why things might not work out. From all the ways a candidate might fail, to why a customer won’t want a product, to how a commonly-used framework might not be a good fit, he brings this mindset to every aspect of running Persona. I share that instinct — when we anchor on “why it won’t work” early, we surface edge cases, stress-test assumptions, and prioritize outcomes over output. It’s a product discovery discipline that keeps teams honest and accelerates product-market fit lessons.

Rick also shared counterintuitive practices that resonated with my own founder-led GTM experiences. His engineers sell and cold-email prospects, and he doesn’t try to convince candidates that Persona is a company that will change the world. That may sound unconventional, but it’s exactly the clarity zero-to-one companies need: tight customer feedback loops, direct exposure to objections, and authentic hiring that screens for fit over hype. In my experience, these choices reduce handoffs, sharpen messaging, and create a culture that learns faster than the market moves.

There’s a broader leadership lesson here for product management: treat pre-mortems as a muscle, not a meeting. I apply this to hiring scorecards, roadmap bets, and go-to-market plays — explicitly listing failure modes, customer objections, and “anti-personas” who won’t buy. When we teach engineers to engage customers directly, we’re effectively building forward deployed engineers who carry context from discovery to delivery to launch, closing the feedback loop and improving zero to one B2B marketing execution.

For founders, engineering leaders, and hiring managers, the takeaways are practical: start with the “won’t,” design for objections, and let builders meet buyers early. Pair this with a clear definition of success metrics and a bias for candid, frequent iteration. The result is a stronger compass for product management leadership and a far more resilient go-to-market motion.

You can follow Rick on Twitter at @rickcsong and learn more about Persona at https://withpersona.com/

Inspired by this post on First Round.

October 22, 2025
From Slack’s ‘Where Work Happens’ to CEO: Inside the Product Strategy That Scales

I’m drawn to leaders who bridge marketing excellence with rigorous product management. Kelly Watkins, CEO of Abstract, exemplifies this. Abstract is a platform for structure and transparency in the design process. What makes her journey distinctive is the transition from a marketing background into the CEO seat — a path that demands both narrative mastery and operational discipline.

Reflecting on her first year as CEO, what stood out to me was her alternative to yearly planning, borrowing from famed military strategist John Boyd. I’ve wrestled with annual planning cycles myself, and this approach resonates with how I guide product roadmapping and sprint planning — shorter feedback loops, tighter decision cycles, and a bias for learning over lengthy forecasts. It’s a pragmatic way to keep teams focused on the right problems at the right time.

Her walkthrough of Abstract’s most recent product launch crystallized a leadership stance I value deeply: constantly optimize for trade-offs, rather than chasing clear-cut right and wrong. In my experience, framing decisions as explicit trade-offs elevates cross-functional collaboration, aligns product discovery with realistic constraints, and encourages outcomes over output. It’s the difference between shipping features and shipping meaningful progress.

Drawing on a storied marketing career at Slack, Github, and Bugsnag, she underscores a jobs-to-be-done approach for crafting a product story when there’s loads of competition. I’ve seen JTBD unlock clarity when teams get lost in feature parity — it centers the product on the customer’s progress, not our roadmap. When the market is noisy, a crisp jobs-based narrative becomes a durable strategic asset.

The behind-the-scenes look at developing Slack’s “where work happens” tagline is a powerful reminder that great positioning anchors to the job, not the jargon. Moving from a passionate early adopter base to a ubiquitous product requires more than demand gen — it requires crossing the chasm with a value story that scales. I’ve found that the leap from early signals to broad adoption hinges on consistent messaging, intentional onboarding, and instrumentation that proves product-market fit beyond the initial cohort.

This conversation isn’t just a must-listen for marketing folks; it’s a primer for any leader seeking to collaborate more effectively across the org. The art and science of marketing become a force multiplier when paired with disciplined product management leadership. For teams navigating zero to one B2B marketing, these lessons translate directly into sharper execution and clearer decision-making.

My takeaways are straightforward: plan in adaptable cycles, not rigid annual cadences; embrace trade-offs as a core leadership tool; use the jobs-to-be-done framework to tell a product story that cuts through competition; ground your tagline in the customer’s real job; and design your path from early adopters to the mainstream with intention. Applied together, these principles turn strategy into momentum and momentum into enduring growth.

Inspired by this post on First Round.

October 22, 2025