Tag: product roadmapping and sprint planning

From Dropbox to Loom: Hard-Won, Sales-Driven Product Lessons for Competitive Markets

I recently sat down with Sam Taylor, VP of Sales and Success at Loom. Previously, Sam was Dropbox’s first enterprise sales rep, and also served as Quip’s first sales leader. As a product leader, I’m always looking for the connective tissue between sales insights and product strategy, and Sam’s journey offers a rich playbook for product-led growth, enterprise sales, and go-to-market execution.

We started with his earliest experience at Dropbox, and I was struck by his aha moment that sales is an insight driver. That framing resonates deeply with how I run discovery and roadmap governance: when sales becomes a structured listening post, it sharpens pricing and packaging decisions and helps prioritize the feature roadmap as Dropbox moved up market. In practice, that means operationalizing feedback loops, pairing usage telemetry with win–loss analysis, and iterating packaging to match how customers actually buy and expand.

Reflecting on his time at Quip, Sam shared what sticks with him from working closely with its CEO Bret Taylor and COO Molly Graham. He also walked through tested tactics for selling in a competitive market where you’re going up against plenty of established players, like Google and Microsoft. My takeaway for product teams: differentiation must be engineered, not just messaged. Equip champions with crisp value proof, remove switching friction in the product, and align your roadmap to moments that neutralize incumbent advantages. In other words, design the product to win the deal before the demo even starts.

Turning to his current role at Loom, Sam is threading all of those experiences together. He emphasized his partnership with Loom’s product leaders, and how they’re teaming up to achieve what he jokingly calls “total Loom domination.” I loved the practicality here: a tight sales–product cadence, shared metrics for activation and expansion, and packaging that scales from self-serve to enterprise without creating friction. “Everyone wants a silver bullet,” but the real edge comes from compounding small, well-orchestrated decisions across pricing, roadmap, and enablement.

If you’re in sales, Sam’s path reinforces how to translate field signals into product change that moves pipeline and retention. And if you work in a product-led growth company, you’ll come away with a clearer understanding of how sales fits in: establish a reliable voice-of-customer loop, treat SaaS pricing and packaging as a product, and use product roadmapping to align with the most material customer problems. That’s how you turn insights into impact—and how product and sales win together in competitive markets.

Inspired by this post on First Round.

October 21, 2025
Inside the Engineering Cultures of Microsoft, Reddit, Looker & Twitter: Hard-Won Lessons

I’m endlessly fascinated by how engineering culture shapes product velocity, quality, and leadership outcomes. Drawing on lessons from Nick Caldwell’s journey, I’ve distilled the practices that consistently produce performance, clarity, and cohesion across teams. These are the ideas I reference when coaching product and engineering leaders, building org structures that scale, and aligning teams around outcomes.

Nick Caldwell, VP of Engineering at Twitter. Previously, Nick was at Microsoft for 15 years, eventually becoming GM of Power BI. Nick has also held roles as Reddit’s VP of Engineering and Looker’s Chief Product and Engineering Officer.

Across Microsoft, Reddit, Looker, and Twitter, the cultural contrasts are stark—and incredibly instructive. I focus on how each environment sharpened a different leadership muscle: designing resilient organizations, navigating high-context communities, aligning product and engineering at scale, and translating mission into execution. The net effect is a practical playbook for product management leadership, manager development, and cross-functional collaboration.

From Microsoft, I take to heart what Nick believes is a massively underrated approach to organizational design. The company’s disciplined cadence of regular pruning and shaping the org chart keeps accountability crisp and prevents drift. Their management training and talent development systems create durable leadership pipelines, while what Nick calls the fairest performance review system he’s seen sets a predictable bar for growth. In my own practice, I mirror these principles with explicit role charters, outcomes vs output OKRs, and routine structure audits that keep teams mission-aligned.

Transitioning from a 15-year tour at Microsoft to Reddit came with a steep learning curve—and that resonates deeply with anyone making a big career move or an IC to manager transition. Nick’s advice maps closely to what I coach: re-anchor on the company’s narrative, over-communicate intent, and recalibrate decision speed to the culture. At Reddit, the mission-driven culture isn’t just branding; it informs how influence is earned and how leaders show up. That lens carries forward to leadership at Twitter, where connecting daily execution to mission keeps product and engineering grounded and resilient through change.

Looker offered a rare vantage point: leading both product and engineering. The result is a masterclass in reducing friction between two orgs that are often at odds. The insights I apply: define a single operating rhythm for product roadmapping and sprint planning, eliminate ambiguous ownership, and measure joint outcomes rather than siloed outputs. When product strategy, discovery, and delivery operate on one shared cadence, you unlock faster decisions, fewer handoffs, and cleaner accountability.

For managers looking to level up, these lessons are actionable: invest in management training, make performance systems transparent, prune org complexity before it compounds, and tie every roadmap bet to mission and measurable outcomes. For engineers eyeing leadership, study how culture sets the rules of engagement—then learn to translate that into decision frameworks, communication habits, and hiring signals that reinforce your product and engineering alignment.

This is a wide-reaching set of takeaways because the problems are universal: how to design organizations that scale, grow leaders systematically, and build cultures where product and engineering don’t just coexist—they compound each other’s strengths. If you’re rethinking your org chart, refining your OKRs, or preparing for your next leadership transition, these practices will give you a durable edge.

Inspired by this post on First Round.

October 21, 2025
Confidently Validate Product-Market Fit Before You Build: Inside UserLeap’s Playbook

I’m obsessed with validating product-market fit before writing a single line of code. Studying Ryan Glasgow’s journey as founder and CEO of UserLeap — a product research platform that helps PMs, user researchers, and growth marketers launch microsurveys to uncover customer insights faster — sharpened my own playbook for testing demand early and de-risking execution.

Before founding UserLeap in 2018, Ryan was a PM and early team member at Weebly (which was acquired by Square) and Vurb (which was acquired by Snapchat). That operating rigor shows up in how he navigated the pre-build phase — a period I pay particular attention to when coaching teams through product discovery.

I rewind the clock to the 6-month period before launch, when I’m validating the idea and assessing a crowded market. This is where segmentation and early customer conversations do the heavy lifting. I make the target user painfully specific, probe for desired outcomes, and pressure-test willingness to pay. Just as importantly, I avoid common product/market fit mistakes: over-indexing on feature requests, conflating enthusiasm with intent, and skipping a clear hypothesis about the job-to-be-done.

From there, I frame the first version of the product as the smallest coherent solution that proves the value thesis. I outline how to think about adding new features — through evidence-based prioritization, not wishlist drift — and how UserLeap’s 3 product principles can guide day-to-day product decisions so the roadmap compounds rather than sprawls.

As a self-described “product guy,” I taught myself founder-led sales, including the specific tactics that made the biggest difference and how I’ve refined my approach into a repeatable playbook. That means running tightly scoped discovery calls, qualifying ruthlessly, using problem-centric demos, and turning every objection into a testable learning.

There’s also a simple question I always ask in customer meetings that unlocks clarity: “What would make this an absolute no-brainer for you in the next 30 days?” It anchors the conversation in outcomes, timelines, and trade-offs — the raw material for reliable product-market fit signals.

For the curious builders, here are the books that have most influenced my approach to product discovery, roadmapping, and founder-led GTM: What Customers Want: Using Outcome-Driven Innovation to Create Breakthrough Products and Services by Anthony Ulwick; You Can’t Teach a Kid to Ride a Bike at a Seminar by David Sandler; and User Story Mapping: Discover the Whole Story, Build the Right Product by Jeff Patton.

You can follow Ryan on Twitter at @ryanglasgow.

If you’re navigating product-market fit right now, use these tactics to sharpen segmentation, run higher-signal customer conversations, and build a first version that earns traction fast — then scale with a repeatable founder-led GTM motion.

Inspired by this post on First Round.

October 21, 2025
No UX Research Team? Proven Playbook to Validate Problems, Prototype Smart, and Nail Pricing

I recently sat down with Jane Davis, the Director of UX Research and UX Writing at Zoom. She previously led UX Research and Content Design at Zapier, and managed the growth research team at Dropbox. I set out to distill a practical playbook any product team can apply — even if you don’t have a formal UX research function.

Jane tackles the thorniest customer development questions and walks through an end-to-end research process that works in the real world: clarifying your goals, asking the right questions, selecting participants, and synthesizing insights. I translate these steps into repeatable product discovery rituals that drive better decisions and faster product-market fit.

We start by applying her playbook in the early-stage startup context — when you’re shipping the first version of your product and don’t yet have the resources to invest in a full research team. I share how I scope lean studies, use founder-led GTM interviews to deeply understand the problem we’re solving, and shape hypotheses for competitive versus greenfield markets, including how to size demand and figure out willingness to pay for SaaS pricing.

We also dig into best practices for prototyping and iterating. I show how I pair lightweight prototypes with clear research questions, time-box sprints, and convert insights into product roadmapping and sprint planning that truly move the needle.

Later, we confront common roadblocks: building for multiple users, aligning personas, and what to do when people aren’t excited about your product or using it frequently. I outline tactics to diagnose the gap — value proposition, onboarding, activation, and retention — then adjust the solution, messaging, or usage triggers to rebuild momentum.

If you want to go deeper, here’s the book Jane referenced: Just Enough Research by Erica Hall. I also recommend her article: What’s the point of a UX research team?

Whether you’re talking to potential customers before you start a company or looking to get better feedback from your current users, this conversation is packed with field-tested practices for founders, product-builders, and design folks alike. Use it as your starting point to run credible UX research, de-risk decisions, and accelerate product-market fit without a dedicated team.

Inspired by this post on First Round.

October 21, 2025
Product Lessons from KiwiCo: Scaling Physical Products, Toddler Feedback, and Manager Training

I sat down with Sandra Oh Lin, founder and CEO of KiwiCo, which creates hands-on learning kits for children. After executive roles at PayPal and eBay, she started KiwiCo over ten years ago to give her own kids more hands-on projects to exercise their creativity — a spark that led to entrepreneurship. Today, KiwiCo has expanded to include 8 different lines of crates that are shipped out monthly. As a product creator, I was eager to unpack how she turned a personal need into a scalable, beloved physical product line.

We dug into the thornier challenges of building physical products and her biggest aha moments as a first-time founder. She described creating the first KiwiCo crate — from the product development process to spinning up a supply chain and shipping department. We discussed how KiwiCo approaches new product lines, particularly in the last year when KiwiCo demand skyrocketed. She also shared how the team gathers quality consumer feedback when your customer is often a toddler — an audience that demands observational research, short feedback loops, and thoughtful proxies through parents and caregivers.

From a product discovery perspective, I found KiwiCo’s approach refreshingly pragmatic: iterative prototyping, tight learning cycles, and early validation that inform product roadmapping and sprint planning. When demand surges, operational excellence becomes a product feature — and Sandra’s experience reinforced that product-market fit lessons don’t end at the moment of traction; they expand into forecasting, inventory strategy, and resilience across partners. The throughline is an outcomes-over-output mindset that keeps the team anchored on value delivered to families rather than feature velocity.

We then shifted to culture — the often overlooked engine behind durable execution. Sandra is a strong believer in manager training for everyone, from folks that manage just one person to executives that have been managing for decades. She outlined the specific management training modules they leverage at KiwiCo and made the case for having everyone at the company fill out a motivations spreadsheet. For leaders navigating the IC to manager transition, these guardrails accelerate consistency, empathy, and decision quality across teams.

Finally, we explored how she creates a feedback-rich environment for herself as a CEO. I appreciated the intentionality — structured forums, explicit invitations for critique, and clear norms that make feedback safer and more actionable. Whether you’re shipping crates or software, the lesson holds: sustained product management leadership depends on mechanisms that convert diverse signals into aligned action. If you’re building physical products or scaling a product organization, these practices offer a blueprint for learning faster, de-risking complexity, and keeping customers — even the tiniest ones — at the center.

Inspired by this post on First Round.

October 21, 2025
From Good to Great: 3 Design Pillars, GTM Savvy, Hiring Loops, and Onboarding Rituals

I recently sat down with Hareem Mannan, who was a product design leader at Segment for nearly four years, and joined Twilio as a Senior Director of Product, Enablement & Design following the company’s acquisition of Segment. As I reflected on the conversation through the lens of product management leadership, I saw clear patterns any design org can use to go from good to great. We dug into her three pillars of what makes a great designer: a product quality ambassador, serve as the glue across product areas, and intricately understand the go-to-market motion. I break down why each pillar matters, along with practical ways I’ve coached designers and PMs to build these capabilities without slowing momentum. First, being a product quality ambassador isn’t just about visual polish—it’s about product discovery rigor, clarity of problem definition, and crisp acceptance criteria that translate seamlessly into engineering execution. I look for designers who raise the bar in design reviews, connect craft to outcomes, and protect user experience end-to-end, not just at the surface layer. Second, serving as the glue across product areas is the multiplier. The best designers broker alignment among product, engineering, marketing, sales, and support. They see around corners, anticipate dependencies, and drive coherence across journeys. In practice, this shows up in cross-functional collaboration during product roadmapping and sprint planning, where designers orchestrate trade-offs to maintain a cohesive experience. Third, great designers intricately understand the go-to-market motion. When designers internalize how pricing, packaging, positioning, enablement, and adoption tie back to the product, they make higher-leverage decisions. I encourage teams to sit in on customer calls, shadow sales and support, and map product workflows to GTM milestones so the work lands with real users and real revenue. We also discussed hiring. She takes me through her hiring loop and how she probes for core competencies in each of these three areas. I’ve found structured work samples, system-thinking challenges, and a cross-functional collaboration exercise to be strong predictors. She also flags some of her own mistakes she’s learned from as a hiring manager—such as over-indexing on visual craft at the expense of product sense, or underweighting GTM empathy. My adjustments: calibrate rubrics to value problem framing and decision quality, not just artifacts; include partners from engineering and solutions in the loop; and debrief on signals tied to these pillars. On onboarding, her favorite rituals resonated with me. Pairing new designers with a solutions engineer accelerates context, builds credibility with customer-facing teams, and shortens the path to impact. Similarly, crowd-sourcing a “Dear New Designer” document captures tribal knowledge, expectations, and responsive norms in one living artifact—an elegant way to transmit culture and standards at scale. We then turned to leading a high-impact design org. She unpacks the aha moment that her fear of micromanaging had unintended consequences. I’ve seen this too—hands-off leadership can drift into ambiguity and uneven quality. The antidote is intentional structure: office hours for fast feedback, lightweight checkpoints for consistent quality, and team bonding events that reinforce shared taste and high standards. Done well, these rituals create autonomy with alignment—and a consistently elevated bar for design quality. To learn more about the “Dear New Designer” onboarding document, visit Hareem’s Medium page: https://medium.com/segment-design/dear-new-designer-1fd006fc7390 You can follow Hareem on Twitter at @hareemmannan.

October 21, 2025
Behind the Scenes of Canva’s Meteoric Rise: Zach Kitschke’s Battle-Tested Playbook

I’ve been reflecting on the story of Zach Kitschke, CMO of Canva, an online design and publishing tool. Since launching in 2013, Canva has grown from an Australian startup to a global company, with 60 million monthly active users, over 2,000 employees, and a $40 billion valuation. As a product leader, that trajectory is a masterclass in product management leadership, product-market fit lessons, and deliberate go-to-market execution.

Zach was one of Canva’s first employees, leading comms efforts around their initial launch and fundraise. But since then, he’s done everything from answering support tickets and cooking the team lunch, to serving as a product lead and spinning up the people function. That range resonates with my own experience in high-growth environments: early operators wear many hats to unblock the work and accelerate learning loops.

This career history gives Zach a unique vantage point on why Canva worked. I zero in on the early days — from unpacking all the work that went into their launch, to how they improved the early product and focused on the use case for social media managers and content creators. To me, the insight is simple and powerful: obsess over a clear initial ICP, deliver undeniable value for content creators, and let word-of-mouth amplify your early wins. That’s product discovery in action, supported by tight product roadmapping and sprint planning that prioritizes outcomes over output.

Next, I dig into supporting and scaling the team during hypergrowth. Canva has several unique practices around onboarding, learning and development, and keeping the team connected — from vision decks, strategy docs and a specific skills framework, to their ‘chaos to clarity’ spectrum and ‘season opener’ ritual for making company planning more fun. These practices make culture operational: they align teams on strategy, reduce ambiguity, and create repeatable rituals that sustain speed without burning people out.

From a leadership lens, I appreciate how these mechanisms turn tacit knowledge into shareable playbooks. Vision decks codify narrative; strategy docs create traceability; the skills framework clarifies expectations for IC to manager transition; and the ‘chaos to clarity’ spectrum gives product teams a shared language to navigate uncertainty. This is the scaffolding great product organizations rely on to scale quality, autonomy, and accountability.

Zach also shares what he figured out personally along the different chapters in his career at Canva, including how to leverage advisors and when to bring someone else in to take over your role. I’ve found those two moves to be force multipliers: advisors compress time to insight, and timely succession unlocks what the business needs next. Whether you’re a marketer, a founder, a people leader, or a product manager, there are tons of helpful takeaways for everyone here.

You can follow Zach on Twitter at @zachkitschke.

Inspired by this post on First Round.

October 21, 2025
Scale Smarter: Buy vs Build, Core Focus vs Innovation—Hard-Won Insights with Zendesk’s CTO

I recently sat down with Adrian McDermott, CTO of Zendesk, for a candid conversation on how to scale product and engineering without losing the essence of what makes the product great.

Adrian started at the company back in 2010, when they were only 50 employees. Since then, he’s led product management and engineering teams as the company has gone public and scaled to over 5000 employees. I’ve long admired how that trajectory blends product management leadership with operational rigor, and I wanted to unpack the systems behind it.

We began with the classic scaling fork in the road: double down on what’s working or make a change. In my experience, this decision rarely fits a simple binary, and I asked how he navigates it in practice. He went much deeper than the “what got you here won’t get you there” advice you hear all the time in startups, outlining how to read momentum, market signals, and organizational readiness before flipping a switch.

Next, we explored the tension between venturing into new product areas and keeping the central product brilliant. He shared how they use the zone to win frameworks at Zendesk. I contrasted that with my own approach to product discovery and product roadmapping and sprint planning: protect core experience quality with clear guardrails while allocating explicit capacity for bets that expand the addressable problem space.

We then dug into the evergreen dilemma of whether to build or to buy. He walked through the origin stories of several Zendesk products, from the wins to the lessons learned. His take on the role of competition in product strategy and his definition of a truly great product resonated with me. For my teams, I evaluate buy vs build decisions through a simple lens: strategic differentiation, speed to validated learning, total cost of ownership, and ecosystem leverage; if the capability isn’t core to our unique advantage, I bias to buy and integrate, then instrument relentlessly.

In the back half of our conversation, he shared what he’s learned leading both product and engineering teams, along with practical go-to-market lessons that shape how features actually land with customers. We ended on team building and recruiting. Adrian’s interviewed more than a thousand engineers, and I appreciated the way he adapts hiring profiles and loops to the phase of scale—tight generalists early, then rigor around outcomes vs output as the organization matures.

If you’re scaling a SaaS product, you’ll find actionable insights here: how to avoid false trade-offs, decide when to preserve the core versus explore, operationalize zone to win frameworks, and make smarter buy vs build calls that accelerate learning and customer impact.

As a product leader, these lessons reaffirm a simple truth: sustainable growth comes from deliberate portfolio choices, clear go-to-market alignment, and consistent, values-based hiring that raises the quality bar with every new teammate.

Inspired by this post on First Round.

October 21, 2025
My Proven Product Strategy Playbook: From Mission to NCTs That Align Teams and Drive Growth

I’ve spent years building and scaling products, and I continue to see one pattern derail even the most talented teams: a disconnect between product strategy and what product teams actually work on day-to-day. In this deep dive, I share how I bridge that gap with a practical, battle-tested playbook I’ve used to align teams, accelerate impact, and power growth at scale.

I start by getting brutally clear on the real work my teams are doing versus the outcomes we’re aiming for. Too often, teams are busy shipping features that don’t ladder up to strategy. The fix isn’t more process—it’s sharpening the connective tissue between strategy, planning, and execution so every sprint advances a clear, long-term narrative.

At the core of my approach is the product strategy stack: company mission, company strategy, product strategy, product roadmap, and product goals. When each layer is explicit and connected, prioritization becomes straightforward, trade-offs are defensible, and the team understands not only what we’re doing—but why it matters. I treat this stack as a system, not a document, and I revisit it frequently with my leads to ensure decisions remain aligned.

Here’s how I operationalize it. I anchor every planning cycle in the company mission and company strategy, then translate that into a crisp product strategy that defines where we will play and how we will win. From there, the product roadmap becomes a sequencing tool for outcomes, not a wishlist of features. Finally, I define product goals that are specific, measurable, and clearly tied back to the strategy—so everyone can see the throughline from mission to metrics.

When it comes to goal-setting, I prefer an alternative to traditional OKRs: NCTs. Outlining narratives, commitments, and tasks sidesteps some of the most common headaches when it comes to OKRs. The narrative clarifies the why, the commitments define the measurable outcomes we’re on the hook to achieve, and the tasks capture the critical work we believe will get us there. To implement NCTs, I pilot them with a single squad, ensure each narrative maps to the product strategy, pressure-test commitments against leading indicators, and keep tasks flexible as we learn.

Strategy is often misunderstood and has come to mean all sorts of different things. I’ve found that clarity around terms like “mission” and “vision” changes everything. Mission is enduring and customer-centered; vision is a vivid, time-bound picture of the future we’re building. When teams grasp the difference, alignment snaps into place. I’ve seen this playbook resonate across industries and company stages—from category leaders like Tinder and TripAdvisor to fast-growing startups—because it turns abstract strategy into concrete choices and accountable execution.

If you’re looking to uplevel product management leadership and bring more focus to product discovery and delivery, start by assessing your product strategy stack, then pilot NCTs in your next quarterly planning cycle. Tie every roadmap item to a narrative, stress-test commitments with real metrics, and empower teams to adapt tasks as insights emerge. The result is a more resilient roadmap, tighter alignment, and a team that consistently ships what moves the needle.

October 21, 2025
Mastering International Expansion: My Product Playbook Inspired by Faire’s CEO Max Rhodes

International expansion can be a powerful growth lever — or an expensive distraction. Through my product leadership lens, I’m always looking for patterns that separate the former from the latter. Recently, I reflected on insights from Max Rhodes to distill a practical, founder-friendly playbook for going global without losing focus.
Max Rhodes is the co-founder and CEO of Faire, an online wholesale marketplace that connects independent retailers and brands. His vantage point is especially useful for product leaders scaling multi-sided marketplaces and navigating complex cross-border dynamics.
Prior to starting Faire in 2017, Max spent several years at Square, where he was a founding member of Square Capital, the first product manager on Square Cash, and a Director of Consumer Product for Caviar.
In today’s conversation, we dive deep into how startups can get international expansion right. After launching in the U.K. and Netherlands in March 2021, Faire company expanded into countries like France, Germany, Italy and the Nordic region. They’re now in 15 markets, with over 700 employees in 10 offices around the world.
After sharing the company’s origin story and initial strategy, Max offers a helpful analogy that helped him decide when to go international, and details some lessons he learned from other companies like DoorDash and Airbnb. I found his decision framework refreshingly practical — a blend of timing, readiness, and strategic focus that maps well to the realities of product-market fit, capital efficiency, and operational maturity. I’ve used similar mental models to pressure-test when our roadmap should shift from depth in one market to breadth across many.
Next, Max takes us through the nuts and bolts of how the Faire team approached their first international launch, from staffing and operations, to how they thought about local competitors. Max also walks us through the operating cadence and strategic planning process that powered Faire’s international growth. We also talk about the human side of scaling internationally, and the growing pains that come along with it. What resonated with me was the balance between a disciplined operating rhythm — clear goals, tight feedback loops, and cross-functional ownership — and a nuanced, market-by-market go-to-market strategy that respects local competitors and customer behaviors.
To help mitigate the effects, Max shares how he’s implemented the concepts from the First Round Review article on “Giving away your Legos.” Read the article here: https://review.firstround.com/give-away-your-legos-and-other-commandments-for-scaling-startups I’ve leaned on this mindset during hypergrowth — encouraging PMs, GMs, and functional leaders to continually redesign their roles so we can scale scope without calcifying decision-making. The emotional lift is real, but the payoff is a more resilient organization that can execute across time zones and product surfaces.
Here’s how I translate these lessons into an actionable international expansion checklist for product leaders: validate pull (authentic customer demand and repeatable GTM motion), ensure supply and liquidity for marketplaces, map the competitive landscape by customer jobs (not features), stand up a clear operating cadence with measurable outcomes (not just output-based OKRs), hire for local context and cross-functional ownership, and define a fast, lightweight process for localizing product, pricing, and support. When those pieces click, international expansion compounds rather than distracts.
You can follow Max on Twitter at @MaxRhodesOK.

Inspired by this post on First Round.

October 21, 2025
How I Build Highly Technical Enterprise Products: Hard-Won Lessons from CockroachDB and Nate Stewart

Building a highly technical enterprise product is as much about disciplined focus as it is about engineering excellence. When the stakes include mission-critical uptime, data integrity, and scale, the product decisions we make today compound for years. That’s why I’m constantly looking for patterns that help my team make fewer, better choices.

Recently, I sat down with Nate Stewart, CPO of Cockroach Labs, the creator of database product CockroachDB. Our conversation crystallized a number of principles that I’ve seen work in my own practice and that I believe every enterprise product leader should internalize.

First, focus starts with a brutally specific use case. Nate walked through how the Cockroach team narrowed the aperture on where their database would be irreplaceable, not just incrementally better. That clarity anchored the go-forward plan — which meant saying no to a lot of customers who didn’t align with the product roadmap. In my experience, this is the hardest muscle to build. I’ve found it helpful to articulate a one-sentence “non-negotiable” use case, followed by a short list of adjacent use cases we’ll explicitly defer.

Second, treat over-commitment as a structural risk. Nate dives into the tactical ways to avoid taking on too many customer commitments, which he calls tech debt for product teams. I track this debt explicitly: a ledger of promises, effort estimates, and the strategic rationale for each commitment. We cap the total “commitment points” per quarter, require a written business case for any exception, and sunset low-impact promises with transparent communication. This keeps the roadmap credible and prevents well-intentioned deals from silently hijacking strategy.

Design partnerships are the force multiplier in deeply technical categories — especially when working with conservative enterprise clients. Nate outlined different types of design partners and why you should have all of those represented in the early days of your startup. I map partners along two axes: ambition (visionary to conservative) and environment (startup to regulated enterprise). A healthy portfolio includes at least one of each: a visionary who pushes the frontier, a pragmatic mid-market partner who validates repeatability, and a regulated enterprise that stress-tests compliance, security, and operability.

To make design partnerships work, I rely on a simple operating contract: shared problem statement, measurable outcomes, and mutually agreed constraints. We align on exit criteria before we start, time-box pilots, and avoid bespoke code unless it is clearly on the critical path to the broader product-market fit. Executive alignment on both sides and weekly joint reviews keep momentum high and surprise low.

For product leaders stepping into a new role, nothing matters more than building a rock-solid partnership with a CEO as the first head of product. I’ve found three habits indispensable: a shared narrative (why we win), a living strategy doc (how we win), and a predictable cadence (when we decide). I send pre-reads before our 1:1, frame trade-offs in terms of risk and reversibility, and use disagree-and-commit to keep the organization moving. This creates trust, speeds decisions, and shields teams from thrash.

Finally, I’m intentional about how I solicit honest feedback across the executive team. I rotate a “red team” to stress-test critical bets, run brief anonymous pulses after major launches, and host cross-functional postmortems that focus on outcomes vs output. I also schedule regular skip-level interviews to uncover operational friction that might never surface in leadership meetings. These mechanisms create a continuous learning loop without slowing down the business.

In sum, the craft of enterprise product management lives at the intersection of clarity, constraint, and collaboration. Define a use case so sharp it excludes most opportunities. Manage customer promises like a portfolio of risk. Build a diverse, intentional set of design partners. And invest early in executive alignment and feedback channels that scale with your ambitions. That’s how we turn technical excellence into durable enterprise value.

October 21, 2025
From PM to VP: Proven Tactics to Accelerate Your Product Career and Lead with Confidence

I’ve spent my career growing product teams and coaching product managers, and I’m continually drawn to leaders whose playbooks translate across company stages. One standout is Jiaona Zhang (she goes by JZ), whose journey offers an especially clear roadmap for moving from individual contributor to executive product leadership.
JZ is the VP of Product at Webflow. Before that, she was the Senior Director of Product Management at WeWork, a Product Lead at Airbnb, and a PM at Dropbox and at Pocket Gems. She teaches product at Stanford and mentors rising product leaders. You may also know her for the widely shared article, “Don’t Serve Burnt Pizza (And Other Lessons in Building Minimum Lovable Products).”
What resonates most with me is her framing of the product career path. Instead of a linear ladder, think of three distinct phases: contributing as a PM, managing PMs, and leading the function. I’ve used a similar model to guide my own teams, and I’ll walk through how I apply this framework in practice.
Phase 1 — The PM role: When you’re breaking into product, focus on environments that will compound your learning. I look for signs of strong product discovery, clear ownership of product roadmapping and sprint planning, and a culture that values outcomes vs output. In interviews, I ask how success is measured (OKRs, customer outcomes, adoption) and how PMs partner with engineering and design. Early mistakes are common: trying to own decisions without owning the problem, shipping features without a minimum lovable product mindset, and confusing velocity with value. To avoid these traps, anchor your work in customer problems, link every roadmap item to measurable outcomes, and practice crisp storytelling that connects strategy to execution.
Phase 2 — The managing phase: The IC to manager transition is a shift from doing the work to building the system that does the work. As you become more senior, zoom out from features to portfolios, from experiments to strategy. When hiring, I look for complementary archetypes across the team — the product creator who thrives in zero-to-one, the operator who scales repeatable playbooks, the analyst who brings rigor to prioritization, and the evangelist who aligns stakeholders. For first-time managers, my advice is to establish clear decision rights, define the bar for product quality, and coach toward autonomy. Balance mentoring with mechanisms: weekly product reviews, outcomes-driven OKRs, and lightweight rituals that reinforce clarity without micromanaging.
Phase 3 — The executive phase: At this stage, I treat the product organization itself as a product. Define a vision, clarify the customer (your CEO, exec peers, board, and of course end users), and build feedback loops. With the CEO, align on the narrative, business model bets, and the handful of company-level outcomes that matter most. With peers on the exec team, drive cross-functional planning so GTM, finance, and product are synchronized around impact, not just output. With the board, translate strategy into measurable progress and risk mitigation. The goal is to ship strategy: clear choices, intentional sequencing, and a portfolio that advances product-market fit and durable growth.
Whether you’re trying to break into product, grow into management, or step into the executive arena, this three-phase arc is a reliable compass. Invest in product discovery, tie work to outcomes, and develop the operating cadence that turns intent into impact. That’s how you accelerate from PM to VP — and lead with confidence at every step.

Inspired by this post on First Round.

October 21, 2025