Author: Shivam Tiwari

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

    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.


    Book a consult png image
  • Why I’m Tuning In to “In Depth”: Tactical Playbooks for Startup Hiring, Leadership, and Growth

    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.


    Book a consult png image
  • What I Learned from Molly Graham: Hard-Won Management Lessons from Google, Facebook & Quip

    What I Learned from Molly Graham: Hard-Won Management Lessons from Google, Facebook & Quip

    I sat down with Molly Graham, a seasoned exec and builder who particularly excels at helping startups to go not from 0 to 1, but from 1 to 2. She helped build and scale Facebook, Quip, The Chan Zuckerberg Initiative in their early days, and is now the COO of Lambda School. Every time I revisit her playbook, I find fresh, practical insights that resonate with my day-to-day leading product and scaling teams.

    Today, I zero in on management. In my role leading product management at HighLevel, I’ve seen — just as Molly has — how so many startup mistakes come down to general management issues. We unpack the traps that are easy to fall into, how to avoid reactionary leadership, and why deliberate operating mechanisms matter when the team and roadmap are growing fast.

    One counterintuitive practice I double down on: spend more time with your highest — not your lowest — performers. Your top talent sets the quality bar, accelerates product discovery, and protects employee retention at startups; investing in them compounds. I share how I structure 1:1s, goal-setting, and outcomes vs output OKRs so high performers stay aligned, unblocked, and energized.

    We also talk about managers who shaped our philosophies, the messy IC to manager transition, and the cadence that keeps teams focused without stifling autonomy. Expect concrete tactics you can use tomorrow, whether you’re a first-time manager or a seasoned leader scaling from dozens to hundreds.

    Two themes I return to often: codify your culture early, and ‘give away your Legos’. As scope expands, leaders who consciously hand off ownership create more opportunity, reduce bottlenecks, and build a resilient organization. On compensation, I outline a startup compensation strategy and the principles for setting up your first comp system so it’s fair, explainable, and scalable.

    If you’re building from 1 to 2, this conversation is a management field guide: clear mental models, practical rituals, and candid lessons learned from scaling product, people, and culture.


    Inspired by this post on First Round.


    Book a consult png image
  • Going ‘Unreasonably Deep’: Hard-Won Product Lessons with Ayo Omojola from Cash App to Carbon Health

    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.


    Book a consult png image
  • Hard-Won CEO Lessons: Steve El‑Hage on Pivots, Burnout, and Rebuilding After a Revenue Cliff

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

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

    Inspired by this post on First Round.


    Book a consult png image
  • Start With the Story: Leadership Lessons from Drift’s David Cancel I Use to Elevate Teams

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

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

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

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

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

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

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

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

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

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

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

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


    Inspired by this post on First Round.


    Book a consult png image
  • Win-Win Partnerships: Stripe & Notion Lessons to Negotiate Smarter and Scale Faster

    Win-Win Partnerships: Stripe & Notion Lessons to Negotiate Smarter and Scale Faster

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

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

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

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

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

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

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

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


    Inspired by this post on First Round.


    Book a consult png image
  • How Atlassian Scaled Without a Sales Team: Product-Led Growth, Pricing, and Channel Plays

    How Atlassian Scaled Without a Sales Team: Product-Led Growth, Pricing, and Channel Plays

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

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

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

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

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

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

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


    Inspired by this post on First Round.


    Book a consult png image
  • Inside Upstart’s Unlikely Rise: Dave Girouard’s playbook for pivots, speed, and hiring

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

    I recently listened to a deep dive with Dave Girouard, the CEO and co-founder of Upstart, an AI-powered lending platform that recently went public. Before founding Upstart, Dave was President of Google Enterprise, and spent 8 years building Google’s billion dollar cloud apps business. Hearing his operating cadence and decision frameworks through the lens of a public-company founder was a masterclass for anyone leading product and business strategy.

    From a product management leadership perspective, what stood out was how the initial idea evolved into a durable business model. Dave opens up about the early business model pivot and what it took to execute it without fanfare — flying under the radar of Silicon Valley — while staying obsessively focused on product-market fit. His candor about why he “sucked at fundraising” and how his co-founders have stuck together for almost a decade offers rare, unvarnished lessons on founder psychology, trust, and execution.

    I’ve seen how operating outside the spotlight can be a strategic advantage: fewer distractions, faster iteration cycles, and clearer signal on customer value. Pair that with disciplined go-to-market, and you can build momentum the market only recognizes later. Upstart’s path underscores the compounding effect of shipping speed, ruthless prioritization, and a willingness to refactor assumptions when the data demands a pivot.

    I especially appreciated his “Are you Airbnb or Paypal?” test — it’s a crisp way to force clarity on whether a product depends on network effects or transactional trust, which in turn shapes your product discovery, risk controls, and compliance roadmap. His advice to look at your career in landscape mode resonates with how I coach emerging product leaders: zoom out, map the terrain, then choose the next hill deliberately rather than chasing the nearest shiny object.

    Dave also shares three mental models he leans on to manage his psychology as a founder. As operators, we all need systems that keep us calm under asymmetric uncertainty — especially when a business model pivot or fundraising cycle compresses the signal-to-noise ratio. I’ve found that writing down pre-commitments, instrumenting leading indicators, and scheduling deliberate recovery are complementary to the frameworks he describes.

    On operating cadence, his “management by exception” philosophy aligns with how high-leverage leadership teams run: push context, pull exceptions. The practical implications are clear — instrument what matters, set thresholds, and let autonomous teams own outcomes. It’s a blueprint for scaling without bureaucracy, especially when latency between decision and customer impact must be measured in days, not quarters.

    The hiring lesson that hit home: for executive roles, lean on references, not interviews. In my experience, backchannel signals about how a leader performs in ambiguity and aligns a founder-led GTM are far more predictive than a polished interview loop. Combine that with structured trials or outcome-based charters, and you de-risk critical leadership hires while protecting culture.

    There are also transferable insights from what he learned from Google and how he runs his leadership team — tight feedback loops, crisp operating documents, and an insistence on speed as a habit. For AI-powered lending and beyond, the pattern is the same: clarify the decision, collapse the cycle time, and let empirical results, not narrative gravity, determine what scales.

    If you’re building in fintech or any category where trust, risk, and regulation intersect, this conversation is worth studying. It’s a reminder that unconventional trajectories can still compound into category-defining companies — and that the right mental models, operating mechanisms, and hiring heuristics turn volatility into a strategic advantage.


    Inspired by this post on First Round.


    Book a consult png image
  • How Jean-Denis Grèze Builds Ownership-Driven Engineering Teams: My Leadership Playbook

    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.


    Book a consult png image
  • From C‑Suite to Boardroom: Anne Raimondi’s Playbook to Scale Leaders and Build Great Boards

    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.


    Book a consult png image
  • The Game-Changing System Behind Kindle, AWS, and Prime—and How I Apply It Today

    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.


    Book a consult png image