Author: Shivam Tiwari

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
Treat Operational Debt Like Tech Debt: Inside Elastic’s Distributed Work Playbook

I recently connected with Leah Sutton, SVP of Global HR at Elastic, to unpack how a truly distributed company operates at scale. Elastic’s fully-distributed employee base, which includes over 2,000 spread across 40 countries and 48 states, presents the kind of complex, real-world constraints that product leaders like me think about every day—signal-to-noise in communication, decision speed, and the compounding effects of process design.

What stood out immediately was Elastic’s “distributed by design” company DNA. Leah’s remit spans HR operations, recruiting, and employee engagement, and the way these systems interlock felt remarkably product-like: clear ownership, explicit interfaces, and intentional defaults that remove ambiguity. As I listened, I kept mapping her operating principles to the way we instrument product teams for clarity and velocity.

One of the most practical threads we explored was hiring and leveling for remote leadership—specifically, how to interview for leaders that can manage well remotely. In my experience, the best signals mirror the competencies we prize in product management leadership: written-first communication, outcomes over activity, latency-tolerant decision-making, and the ability to architect rituals (standups, docs, async reviews) that scale across time zones. I’m a fan of structured behavioral interviews that surface these capabilities with work samples and scenario-based prompts rather than abstract hypotheticals.

We also dove into the operational realities of payroll and compensation across regions. The mechanics matter: consistent leveling, location-aware bands, and transparent principles for how currency, cost of labor, and market movement flow into offers and merit cycles. From a startup compensation strategy perspective, I’ve found that publishing your compensation “spec” (philosophy, exceptions policy, refresh cadence) dramatically reduces friction and improves trust—especially when paired with automation for eligibility, approvals, and audit trails.

Elastic has also invested in tactics to mitigate the language and cultural barriers that often trip up global leadership teams. I’ve seen meaningful gains from a few simple, repeatable patterns: default-to-written with concise summaries in plain language, rotating facilitation to balance voices, timezone-inclusive scheduling with recorded context, and cultural onboarding that teaches teams how decisions actually get made. These are small, compounding design choices that preserve speed without sacrificing inclusion.

Zooming out, Leah describes Elastic’s source code as not so much a traditional list of values but more the things that make Elastic, Elastic. That framing resonates with me—values as operating constraints, not wall art. When teams treat culture as an executable spec rather than a slogan, you get fewer surprises, fewer forks, and far more consistent decision quality across the organization.

The concept that most energized me, though, was the push to treat operational debt like technical debt. In product organizations, we maintain backlogs, SLAs, and roadmaps for tech debt because we know it silently taxes every future sprint. Operational debt—fractured tooling, ad hoc onboarding, unclear decision rights, fuzzy compensation rules—creates the same drag. My playbook is to surface operational debt explicitly, size it with impact metrics (time-to-decision, cycle time, error rates, employee retention), assign ownership, and pay it down on a cadence—just like we do with code quality and reliability.

If you’re leading HR, product, or a cross-functional team in a distributed environment, there’s a durable blueprint here: design for async by default, hire for written clarity and systems thinking, codify compensation principles, and manage operational debt with the same rigor you apply to technical debt. Learn more about Elastic’s source code here: https://www.elastic.co/about/our-source-code. You can follow Leah on Twitter at @leahesutton.

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
Unleash Employee Engagement: Proven OKR fixes and manager playbooks for startups

Engaging employees and developing high-quality managers is one of the most reliable ways I know to improve performance, retention, and product velocity. I recently revisited a set of lessons that crystallize what great leadership looks like in practice — especially for startups and product teams under pressure to do more with less.

Consider the arc of Russ Laraway’s career. After starting out in the Marine Corps, Russ made his way into the world of startups, joining Google in 2005 where he led teams for 7 years and was recognized as one of the company’s best managers. Russ then went to Twitter, where he founded and ran the SMB advertising business. Afterwards, he teamed up with Kim Scott to co-found Candor, Inc to help people implement the concepts from Radical Candor and have better relationships at work.

In 2018, he joined Qualtrics as the Chief People Officer, later focusing on helping the company’s customers think differently about employee experience. He also has a book on this topic coming out soon, which I’m eager to dig into because the playbook he’s refined is as practical as it is principled.

Here’s what stands out to me for startup leaders, product managers, and anyone navigating the IC to manager transition: you can systematically drive employee engagement while elevating manager effectiveness. Drawing across roles and company stages, Russ serves up usable wisdom whether you’re a first-time manager or a seasoned leader sharpening your product management leadership muscle.

He starts with the direction-coaching-career framework. In my experience, this trio clarifies why teams stall: unclear direction blurs prioritization, weak coaching slows skill growth, and neglected career conversations erode motivation and employee retention at startups. Pair this with a clean approach to OKRs — too many teams confuse outcomes vs output OKRs — and you get a durable operating system for focus and accountability.

What I appreciate most is how tactical he gets. He shares the typical phrases he relies on when delivering feedback, his go-to questions for soliciting what folks on his team really think, and underrated questions to include in employee engagement surveys. I’ve used similar prompts to create safety in 1:1s, surface hidden risks in roadmaps, and ensure we’re solving the right customer problems — not just burning down a backlog.

Finally, he offers 13 recommendations for leadership reads for managers. I treat this as a compact curriculum: a way to level up how we set direction, coach for performance, and invest in long-term careers across the team. It’s the kind of list I hand to new managers and return to myself during planning cycles and performance reviews.

If you’re leading a product organization or building one inside a startup, the path forward is clear: anchor your rituals around direction-coaching-career, recalibrate OKRs to outcomes, ask the brave questions that reveal what your team really thinks, and keep sharpening your craft with proven leadership reads. Done consistently, these habits compound into higher engagement, stronger execution, and sustainable growth.

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
Build a People-First Org: Data-Driven Empathy, Skip-Levels, and Career Growth with Mark Frein

I recently had a deep-dive conversation with Mark Frein, the Chief People Officer & Head of Alumni Programs at Lambda School. Previously, Mark served as the Chief People Officer at both InVision and Return Path. He also ran his own leadership development consultancy and taught on HR topics as an adjunct professor. As someone who scales product organizations, I was energized by how his people-first principles map directly to product management leadership.

Mark has an invaluable perspective and tons of advice to share after setting up several people orgs in a range of different companies. In our discussion, he shared his approach to the CPO role and his philosophy around the function more generally, including why he thinks at its core, it’s a data and analytical function and how to match the employee experience to your company’s competitive positioning. From my vantage point, that alignment looks like building clear hypotheses, instrumenting the employee journey, and iterating based on signals—exactly how we pursue product-market fit internally.

He also gets incredibly tactical on a wide range of topics, from how to hire with empathy and advice for approaching skip-levels, to gathering employee feedback and driving career conversations. I translate these into playbooks my teams can use: structured, empathy-forward hiring; predictable skip-level rhythms; always-on feedback loops; and career frameworks that make growth expectations explicit.

On hiring with empathy, I lean on behavioral evidence, job simulations, and transparent expectations to reduce bias and improve candidate experience. When we model empathy from the first touchpoint, we accelerate trust, improve close rates, and lay the foundation for employee retention at startups.

For skip-levels, I approach them as discovery interviews—open, curious, and non-defensive. I triangulate themes across teams, synthesize the data, and close the loop publicly so people see action. That transparency compounds trust and gives me the earliest possible signal on risks and opportunities.

When it comes to gathering employee feedback, I blend lightweight pulse surveys with qualitative listening tours and manager office hours. The key is to turn insights into visible change, or we create survey fatigue. We anchor this work to outcomes vs output OKRs so we’re optimizing for impact, not activity.

Driving career conversations requires clarity. I publish ladders, competency matrices, and sample development plans, then coach on the IC to manager transition for those who want to lead. Empathy training for managers helps them ask better questions, calibrate feedback, and co-create growth paths that match both ambition and business needs.

If you’re a founder or early-stage people leader, this approach will help you scale the people function with intention. If you’re a current or aspiring manager, these tools sharpen your leadership and development chops. Most importantly, they weave empathy and data into a single operating system for your culture.

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