Tag: IC to manager transition

  • Why I Bet on First-Time Executives: Inside Figma’s Playbook for AI, IPO Readiness, and Scale

    Founders should bet on first-time executives. I’ve seen it pay off repeatedly, and a recent deep dive with Praveer Melwani, CFO at Figma, reinforced exactly why. Praveer joined Figma in 2017 as the company’s first business operations and finance hire—when the team was around 30 people and not yet charging for the product—and stepped into the CFO seat in 2022, helping to lead the company’s IPO in 2025. His journey from IC to CFO isn’t just a career arc; it’s a blueprint for scaling leadership capacity in high-velocity environments.

    What struck me first was the clarity of the step functions that took him from operator to “whole-company” leader. Early on, he optimized for doing the work—building driver trees, stress-testing go-to-market assumptions, and putting the basics of board management in place. As the business matured, he shifted from answering questions to defining them, owning capital allocation, and shaping the operating cadence. That evolution—from execution to orchestration—is exactly the arc I look for when I’m hiring first-time VPs.

    Another takeaway: Figma started acting like a public company three years before its IPO. That wasn’t optics; it was operating discipline. Quarterly rhythms, tight controls, an audit-proof close, and forward-looking narrative management helped the company move faster, not slower. In my experience, this kind of public-company readiness clarifies trade-offs, compresses decision cycles, and strengthens cross-functional trust—especially between product, finance, and go-to-market leadership.

    We also unpacked what separates world-class finance leaders from a traffic-cop CFO. The latter enforces rules and guards budgets; the former uses first principles decision making to direct resources toward asymmetric upside. World-class CFOs help the company understand risk in a post-ChatGPT world, design SaaS pricing that matches product reality, and build reliable instrumentation for outcomes—not just outputs. They’re partners in product strategy as much as stewards of the balance sheet.

    On pricing, I appreciated the courage behind selling the exec team on AI consumption pricing. Consumption SaaS pricing introduces variance, but it also aligns value with usage and accelerates time-to-value—especially for AI-driven features whose unit economics evolve rapidly. It requires tight stakeholder management, robust telemetry, and a crisp value proposition, but when executed well it can unlock both growth and discipline.

    One of the boldest moves: Figma intentionally cut its 90% gross margin to invest in AI. That’s a masterclass in capital allocation. The reflex to protect margins is strong, but durable advantage often comes from compounding learning loops, not short-term optics. Framed correctly, AI Strategy isn’t a cost center—it’s an option on multiple future S-curves. The key is to define decision guardrails, instrument usage, and keep a living risk register for AI risk management.

    I was also intrigued by how AI is changing the CFO craft itself. Tools like Claude Code are now part of the financial leader’s toolbox—useful for scenario modeling, policy drafting, and exploring new domains without slowing down the team. Paired with strong data governance and controls, this is where FinOps meets executive leverage: faster cycles, tighter experiments, and better communication with product and engineering.

    Leadership transitions can catalyze phase shifts. When a COO leaves or a company re-architects its operating model, great executives don’t just fill gaps—they redesign the system. That’s when clarity about swimlanes, escalation paths, and decision rights matters most. The lesson for founders: hire for adaptability, not just pedigree, and look for people who can turn ambiguity into momentum.

    Hiring leaders in functions you don’t deeply understand is a common founder challenge. The best antidote is a first-principles test for hiring VPs: can the candidate map the business model, define success metrics, and explain trade-offs in plain language? Do they show how they’d build the team, not just run it? Can they teach you something new in 30 minutes? I use this pattern across executive hiring because it scales better than relying on domain buzzwords.

    Another practice I recommend: build an internal board of peer CFOs and operators. Regular, no-agenda check-ins create a community of practice that shortens feedback loops and surfaces non-obvious risks. It’s one of the most efficient ways to de-risk capital allocation and sharpen strategic narratives ahead of real board meetings.

    We talked about scope versus depth: how deeply in the details should a CFO be? My view aligns with what I heard here—be in the details often enough to validate the model and coach the team, but not so deep that you become the bottleneck. The executive job is to raise the quality of decisions at scale, not to personally make every decision.

    There were personal lessons, too—from the nine-year working relationship with Dylan Field to foundational team-building insights from time at Dropbox. Strong teams are built on crisp roles, tight feedback loops, and a bias for writing things down. That muscle—organizational development through clarity—is what separates resilient companies from merely lucky ones.

    If you’re a founder weighing whether to back a rising operator or recruit a “proven” exec, this story tips the scale toward the former. Bet on slope, not just intercept. Create the scaffolding—public-company behaviors early, transparent metrics, and a culture that rewards learning—and your first-time executives will scale with the business. Done right, it’s the highest-LEVERAGE people decision you can make.


    Book a consult png image
  • Mastering 30,000-Foot Vision and Ground-Level Execution: Systems That Decide Without You

    Mastering 30,000-Foot Vision and Ground-Level Execution: Systems That Decide Without You

    Executive function, for me, is the art and discipline of building systems that make high-quality decisions without my constant involvement. The real unlock isn’t personal heroics; it’s institutionalizing judgment. When I do my job well, teams move faster, ambiguity shrinks, and the organization compounds learning even when I’m not in the room.

    Operating simultaneously at 30,000 feet and ground level is the defining muscle of executive leadership. I deliberately switch altitudes. At 30,000 feet, I obsess over strategy, architecture, and resourcing. On the ground, I validate core assumptions with firsthand data, listen for weak signals, and spot process cracks before they widen. Altitude changes are not random; they’re triggered by variance from plan, critical customer moments, or leading indicators that deviate from expected ranges.

    The leap from frontline manager to manager of managers is where many rising leaders stall. As a manager of managers, my primary value shifts from personal execution to system design. I move from answering questions to installing mechanisms that ensure questions get answered well by others. This includes clear decision rights, shared metrics, and repeatable, lightweight rituals that scale across teams.

    What is an executive actually accountable for? Outcomes over output, talent density, and the clarity of the operating system. That means defining strategy, aligning resources, creating a cadence of review that exposes truth, and ensuring incentives reward the behaviors we want. My barometer: if I step away, do priorities hold, do metrics behave as expected, and do tradeoffs land where I would have landed?

    Knowing when to dive deep versus when to step back is a craft. I dive deep when risks are existential, when metrics have no credible owner, or when narrative and numbers diverge. I step back when leaders demonstrate consistent judgment, metrics sit inside control limits, and learnings are documented. The principle I return to again and again: context is everything. Senior leaders operate on context, not control.

    To scale judgment, I teach people how I think. I externalize my mental models: how I construct decision trees, how I stress-test assumptions, and how I weigh time horizons. I rely heavily on driver trees for metrics because they force causal clarity. If we can’t map how a top-line goal decomposes into controllable levers, we’re managing by hope, not design.

    Creating a shared language across the business is a force multiplier. I standardize definitions for our core metrics, codify what “good” looks like, and make it easy to repeat the system. We align around outcomes versus output, and we use cadences like MBRs and QBRs to unify narrative and numbers. Shared language makes decisions legible across functions and reduces rework.

    My COO playbook emphasizes owning the full customer experience end to end. When marketing rolls up under a COO in certain stages, the upside is coherence: one narrative from awareness to activation to expansion, one set of metrics, one growth engine. The point isn’t org charts; it’s removing seams customers can feel.

    Demanding and supportive is not a contradiction. I set ambitious, unambiguous bars and back them with coaching, resourcing, and fast feedback. The combination builds trust: expectations are clear, and help is immediate. I expect leaders to bring problems paired with proposed solutions and to escalate early, not perfectly.

    Inside my executive interview process, I’m assessing altitude agility, operating cadence, and taste in metrics. I use structured interviews and live case workshops to see how candidates frame ambiguous problems, build driver trees, and prioritize tradeoffs. The best prompts are simple and revealing: design the operating system for a 3x scale scenario; diagnose a broken funnel with incomplete data; align two teams with conflicting incentives. The workshop prompts that reveal everything surface thinking speed, humility, and the instinct to make context legible.

    The common thread in failed executive hires is a mismatch between the company’s operating system and the leader’s default mode. Some leaders can’t stop doing the work themselves. Others stay too abstract and never build mechanisms. I look for demonstrated ability to change systems, not just run them—leaders who can both author and evolve the playbook.

    On metrics, I practice the driver tree philosophy. I begin with the North Star, decompose it into controllable levers, instrument each node, and assign single-threaded owners. We design review cadences where deviations trigger targeted diagnostics, not thrash. Each tree has documented assumptions, data sources, and thresholds that prompt action. This is how teams learn to anticipate, not react.

    High-functioning executive teams are visibly collaborative. We clarify decision rights, disagree and commit quickly, and conduct post-decisions to harvest learnings without blame. My favorite litmus test is simple: can 30 people operate as one team when it matters? When we get this right, information flows, execution accelerates, and customers feel consistency.

    One of the most counterintuitive leadership lessons is working yourself out of a job. If the system cannot run without you, you have a key-man risk, not a leadership strength. I aim to build successors, codify judgment, and design mechanisms that make good decisions the default state. That’s how you create durable, compounding advantage.

    And the review feedback you can’t unhear? Mine was brutally honest: my bar was high, but my mechanisms were implicit. Once I wrote them down—how I decide, what I expect, where I dive deep—the organization moved faster, and I actually became less central. If there’s a throughline to extraordinary leadership, it’s this: make your judgment teachable and your systems inevitable.


    Book a consult png image
  • From Code to Roadmaps: My Proven Playbook for Engineers Becoming Product Managers

    From Code to Roadmaps: My Proven Playbook for Engineers Becoming Product Managers

    "From code commits to boardrooms. Here are real stories of software engineers who swapped bugs for roadmaps on the road to product manager." I’ve made that leap myself and helped many engineers do the same. In this piece, I share the playbook I use to guide high-potential ICs into impactful product management roles—without losing the engineering rigor that makes them special.

    Engineers make exceptional product managers because we’re trained to decompose complex systems, debug ambiguity, and reason from first principles. The transition isn’t about abandoning code; it’s about expanding your scope from implementation details to customer outcomes, market context, and business impact.

    The first shift is mental: move from shipping outputs to driving outcomes. Features are a means; value is the end. I anchor this change with outcomes vs output OKRs, ensuring every roadmap item ties to a measurable user or business result rather than a checklist of tickets.

    Next, upskill deliberately in three areas: product discovery, product positioning, and stakeholder management. Learn to design unbiased customer interviews, synthesize patterns from qualitative and quantitative signals, and craft crisp value propositions that resonate with real segments. Then practice executive-ready communication—clear decisions, concise narratives, and no jargon crutches.

    Here’s the practical, low-risk way to get PM experience without changing your title: form a product trios working group (design, engineering, product) around a real problem. Lead discovery with a weekly cadence, run lightweight experiments, and translate insights into a draft product roadmapping and sprint planning artifact. Ship small, learn fast, and narrate the learning.

    Build a simple portfolio that proves product judgment. Include one-page problem briefs, discovery notes, customer quotes, prioritized opportunity trees, and a before/after roadmap snapshot. For each artifact, quantify the impact: activation lift, support ticket reduction, conversion improvement—whatever outcome your work influenced.

    If you want to pivot internally, propose a 90-day experiment. Volunteer to own a well-bounded problem, commit to an outcomes dashboard, and set a weekly stakeholder update. Keep a minimal engineering contribution during the trial to de-risk the transition for your team while you demonstrate PM leverage across the squad.

    If you’re interviewing externally, prepare two deep case studies: one discovery-led (how you reduced uncertainty) and one delivery-led (how you aligned stakeholders and shipped). Be explicit about trade-offs, risks you retired, metrics you moved, and lessons learned. The best signals of product sense are clarity under constraints and an ability to say “no” for good reasons.

    Once you land the role, use a 30-60-90 plan. In the first 30 days, map users, workflows, metrics, and decision rhythms; in 60, run a focused discovery sprint and align on your hypothesis-led roadmap; by 90, deliver a thin slice that proves value and establishes credibility with empowered product teams. Keep your communication tight, your dashboards honest, and your customers close.

    Common pitfalls: translating directly from solution space to roadmap without validating problems; equating stakeholder satisfaction with customer value; and mistaking velocity for progress. Avoid them by running small tests early, revisiting segment-specific value propositions, and anchoring trade-offs to product-market fit lessons.

    If you’re standing at the edge of this transition, start where you are: choose one user pain, one measurable outcome, and one small bet. Treat it like a product: define success, experiment thoughtfully, and learn in public. The road from engineer to product manager isn’t a title change—it’s a shift in how you create value.


    Inspired by this post on Product School.


    Book a consult png image
  • 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
  • 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
  • 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
  • Inside Tido Carriero’s Playbook: Build World-Class Engineering Orgs and Nail Product/Market Fit

    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.


    Book a consult png image
  • Build a People-First Org: Data-Driven Empathy, Skip-Levels, and Career Growth with Mark Frein

    Build a People-First Org: Data-Driven Empathy, Skip-Levels, and Career Growth with Mark Frein

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

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

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

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

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

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

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

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


    Inspired by this post on First Round.


    Book a consult png image
  • From Dozens to Thousands: The People-First Playbooks and Pitfalls I’ve Learned to Avoid

    From Dozens to Thousands: The People-First Playbooks and Pitfalls I’ve Learned to Avoid

    I recently sat down with McKenna Quint, who was most recently the Head of People at Plaid and also built and led the people team at Cruise Automation. Currently, she’s co-founder and general partner at Quint Capital, a seed-stage fund. As someone who has scaled product and go-to-market organizations, I wanted to surface the real-world playbooks and pitfalls that shape employee retention at startups.

    We focused on the people challenges that inevitably crop up when you’re going from a couple dozen employees to a couple thousand. We compared the moments to draw from established playbooks in the people space versus the moments to start from first principles. I especially appreciated how she brings a data mindset to the people space, including designing a sophisticated attrition model—a discipline I’ve found invaluable for aligning capacity planning, product roadmaps, and outcomes vs output OKRs.

    Next, we tackled the questions I hear most from startup founders and product leaders alike: whether the company should introduce levels, what to look for in your first people leadership hire, and how to approach performance reviews. I shared where I’ve seen levels unlock clarity for IC to manager transition, and where premature structure can slow execution. We aligned on making performance reviews a continuous, signal-rich system that strengthens product management leadership and retention, rather than a once-a-year formality.

    We also explored the broader role companies play in today’s employee experience—from the company cultures that most inspire her, to the evolution of uncomfortable conversations in the workplace, and what pieces of the Google cultural revolution she’s ready to leave behind. My takeaway: culture is a product you ship every day, and your early decisions about norms, accountability, and transparency compound as you scale from dozens to thousands.

    If you’re building or leading teams, this conversation is a practical field guide. It’s relevant for HR leaders, founders, and cross-functional partners in product, engineering, and go-to-market who want an inside look at what’s top of mind for people leaders today—and the systems behind the scenes that power startups to reach new heights. Expect actionable insights you can apply in weekly rituals, hiring loops, startup compensation strategy decisions, and org design.

    Let My People Go Surfing: https://www.amazon.com/Let-People-Surfing-Education-Businessman/dp/0143037838

    Management Lessons from the Mayo Clinic: https://www.amazon.com/Management-Lessons-Mayo-Clinic-Organizations/dp/1260011836

    Let’s Not Kill Performance Evaluations Yet: https://hbr.org/2016/11/lets-not-kill-performance-evaluations-yet

    You can follow McKenna on Twitter at @mckmoreau


    Inspired by this post on First Round.


    Book a consult png image