Tag: product roadmapping and sprint planning

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
How Jean-Denis Grèze Builds Ownership-Driven Engineering Teams: My Leadership Playbook

I recently reflected on an insightful conversation with Jean-Denis Grèze, Head of Engineering at Plaid, which securely connects your bank to your apps. Before joining Plaid, he served as Director of Engineering at Dropbox, and even has law school and one year as a lawyer under his belt before diving deep into the world of CS. That unconventional path sharpened his perspective on leadership and culture in ways that deeply resonate with how I build product and engineering teams. Jean-Denis calls becoming a lawyer a “four-year detour he probably didn’t need,” yet the discipline and judgment he developed there clearly inform his approach. He strongly favors pragmatism over perfection — a stance I share. In product management leadership, that bias toward outcomes, rapid iteration, and accountability is the backbone of a healthy engineering culture of ownership. What stood out most was his modern playbook for engineering leadership, stitched together from years at Plaid and Dropbox. Ownership starts with clarity: sharp priorities, explicit decision rights, and fast feedback loops that connect product roadmapping and sprint planning to measurable business outcomes. When teams understand the why and can see their impact in the right KPIs, they lean into responsibility rather than waiting for directives. We also dug into org design choices that amplify ownership. His engineering org doesn’t have titles. In my experience, removing titles can reduce ego-driven friction and elevate scope, impact, and outcomes as the true signals of growth. But it requires strong frameworks for leveling, compensation, and the IC to manager transition so people still understand expectations and career paths. I was particularly intrigued by the one question he asks every engineering manager candidate. While the question itself is simple, the signal it seeks is profound: can this leader create clarity, foster accountability, and drive outcomes across ambiguous, cross-functional work? When I hire, I look for the same traits — leaders who translate strategy into outcomes vs output OKRs and consistently raise the team’s bar for execution. We also unpacked the perennial balancing act: prioritizing technical debt and keeping the lights on versus sexy, brand-new projects. My approach mirrors his emphasis on sustainability — dedicate explicit capacity for reliability, security, and platform health, anchor the roadmap to product and engineering KPIs, and make trade-offs transparent. When technical debt is framed as risk mitigation and velocity enablement, it earns its rightful place alongside new customer-facing bets. This conversation is a must-listen for technical leaders or anyone eyeing the engineering leadership track. From motivating a team to tracking the right KPIs, the tactics and stories from Plaid and Dropbox offer practical guidance for cultivating an engineering culture that owns outcomes, moves fast with judgment, and scales without sacrificing quality.

Inspired by this post on First Round.

October 22, 2025
From C‑Suite to Boardroom: Anne Raimondi’s Playbook to Scale Leaders and Build Great Boards

I recently sat down with Anne Raimondi, Chief Customer Officer at Guru, and independent board member at Asana, Gusto and Patreon. Previously, she was part of the founding team at Blue Nile, spent five years in product marketing at eBay, and led marketing as an early employee at SurveyMonkey, before pivoting to operations as an SVP at Zendesk.
Drawing on her arc as a founder, operator, executive and board member, we explored what truly enables top executives to scale across hypergrowth. I probed how she structures her own 30, 60, 90-day plans as a brand-new hire — and we compared notes on the traps that derail otherwise great leaders during executive onboarding.
Her playbook for executive recruiting, interviewing and hiring resonated deeply with my experience building product management leadership benches. We dug into when to mine executive talent internally rather than defaulting to external hires, how to test for C-suite judgment under pressure, and how to align on outcomes before titles.
We also examined her approach to board work, surfacing the essential ingredients for productive, impactful boards across every growth stage — from crisp strategy and clear owner/decider models to operating cadences that keep focus on value creation, not vanity updates.
Here’s how I operationalize these lessons in my own practice: I anchor the first 30 days on discovery and trust-building; days 31–60 on strategy validation, metrics and early wins; and days 61–90 on execution rhythms, hiring plans and cross-functional commitments. In executive searches, I bias toward internal succession when there’s strong product-market context and cultural trust, and I use structured interviews, work samples and reference triangulation to raise the bar.
For boards, I insist on tight pre-reads, decision logs, and a cadence that separates governance from operating reviews. The goal is a board that sharpens thinking, accelerates decisive action, and strengthens the leadership team.
If you’re an executive, founder or board member aiming to elevate your leadership frameworks, the themes we covered deliver practical, repeatable patterns you can apply immediately — from crafting a high-signal executive onboarding plan to building a healthy relationship with your board.

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
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 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