Inspired by this post on First Round.
Tag: employee retention at startups
-
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.
-
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.
-
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.
-
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.
-
Treat Operational Debt Like Tech Debt: Inside Elastic’s Distributed Work Playbook
I recently connected with Leah Sutton, SVP of Global HR at Elastic, to unpack how a truly distributed company operates at scale. Elastic’s fully-distributed employee base, which includes over 2,000 spread across 40 countries and 48 states, presents the kind of complex, real-world constraints that product leaders like me think about every day—signal-to-noise in communication, decision speed, and the compounding effects of process design.
What stood out immediately was Elastic’s “distributed by design” company DNA. Leah’s remit spans HR operations, recruiting, and employee engagement, and the way these systems interlock felt remarkably product-like: clear ownership, explicit interfaces, and intentional defaults that remove ambiguity. As I listened, I kept mapping her operating principles to the way we instrument product teams for clarity and velocity.
One of the most practical threads we explored was hiring and leveling for remote leadership—specifically, how to interview for leaders that can manage well remotely. In my experience, the best signals mirror the competencies we prize in product management leadership: written-first communication, outcomes over activity, latency-tolerant decision-making, and the ability to architect rituals (standups, docs, async reviews) that scale across time zones. I’m a fan of structured behavioral interviews that surface these capabilities with work samples and scenario-based prompts rather than abstract hypotheticals.
We also dove into the operational realities of payroll and compensation across regions. The mechanics matter: consistent leveling, location-aware bands, and transparent principles for how currency, cost of labor, and market movement flow into offers and merit cycles. From a startup compensation strategy perspective, I’ve found that publishing your compensation “spec” (philosophy, exceptions policy, refresh cadence) dramatically reduces friction and improves trust—especially when paired with automation for eligibility, approvals, and audit trails.
Elastic has also invested in tactics to mitigate the language and cultural barriers that often trip up global leadership teams. I’ve seen meaningful gains from a few simple, repeatable patterns: default-to-written with concise summaries in plain language, rotating facilitation to balance voices, timezone-inclusive scheduling with recorded context, and cultural onboarding that teaches teams how decisions actually get made. These are small, compounding design choices that preserve speed without sacrificing inclusion.
Zooming out, Leah describes Elastic’s source code as not so much a traditional list of values but more the things that make Elastic, Elastic. That framing resonates with me—values as operating constraints, not wall art. When teams treat culture as an executable spec rather than a slogan, you get fewer surprises, fewer forks, and far more consistent decision quality across the organization.
The concept that most energized me, though, was the push to treat operational debt like technical debt. In product organizations, we maintain backlogs, SLAs, and roadmaps for tech debt because we know it silently taxes every future sprint. Operational debt—fractured tooling, ad hoc onboarding, unclear decision rights, fuzzy compensation rules—creates the same drag. My playbook is to surface operational debt explicitly, size it with impact metrics (time-to-decision, cycle time, error rates, employee retention), assign ownership, and pay it down on a cadence—just like we do with code quality and reliability.
If you’re leading HR, product, or a cross-functional team in a distributed environment, there’s a durable blueprint here: design for async by default, hire for written clarity and systems thinking, codify compensation principles, and manage operational debt with the same rigor you apply to technical debt. Learn more about Elastic’s source code here: https://www.elastic.co/about/our-source-code. You can follow Leah on Twitter at @leahesutton.
Inspired by this post on First Round.
-
Unleash Employee Engagement: Proven OKR fixes and manager playbooks for startups
Engaging employees and developing high-quality managers is one of the most reliable ways I know to improve performance, retention, and product velocity. I recently revisited a set of lessons that crystallize what great leadership looks like in practice — especially for startups and product teams under pressure to do more with less.
Consider the arc of Russ Laraway’s career. After starting out in the Marine Corps, Russ made his way into the world of startups, joining Google in 2005 where he led teams for 7 years and was recognized as one of the company’s best managers. Russ then went to Twitter, where he founded and ran the SMB advertising business. Afterwards, he teamed up with Kim Scott to co-found Candor, Inc to help people implement the concepts from Radical Candor and have better relationships at work.
In 2018, he joined Qualtrics as the Chief People Officer, later focusing on helping the company’s customers think differently about employee experience. He also has a book on this topic coming out soon, which I’m eager to dig into because the playbook he’s refined is as practical as it is principled.
Here’s what stands out to me for startup leaders, product managers, and anyone navigating the IC to manager transition: you can systematically drive employee engagement while elevating manager effectiveness. Drawing across roles and company stages, Russ serves up usable wisdom whether you’re a first-time manager or a seasoned leader sharpening your product management leadership muscle.
He starts with the direction-coaching-career framework. In my experience, this trio clarifies why teams stall: unclear direction blurs prioritization, weak coaching slows skill growth, and neglected career conversations erode motivation and employee retention at startups. Pair this with a clean approach to OKRs — too many teams confuse outcomes vs output OKRs — and you get a durable operating system for focus and accountability.
What I appreciate most is how tactical he gets. He shares the typical phrases he relies on when delivering feedback, his go-to questions for soliciting what folks on his team really think, and underrated questions to include in employee engagement surveys. I’ve used similar prompts to create safety in 1:1s, surface hidden risks in roadmaps, and ensure we’re solving the right customer problems — not just burning down a backlog.
Finally, he offers 13 recommendations for leadership reads for managers. I treat this as a compact curriculum: a way to level up how we set direction, coach for performance, and invest in long-term careers across the team. It’s the kind of list I hand to new managers and return to myself during planning cycles and performance reviews.
If you’re leading a product organization or building one inside a startup, the path forward is clear: anchor your rituals around direction-coaching-career, recalibrate OKRs to outcomes, ask the brave questions that reveal what your team really thinks, and keep sharpening your craft with proven leadership reads. Done consistently, these habits compound into higher engagement, stronger execution, and sustainable growth.
Inspired by this post on First Round.
-
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.
-
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.
-
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.
-
Retaining Startup Talent: Conflict Playbooks and Couples Therapy Tactics I Use
I recently sat down with Alex Buder Shapiro, the Chief People Officer at Flatiron Health, a company that focuses on accelerating cancer research and improving patient care. As someone who leads product management and cares deeply about culture, I wanted to unpack what truly keeps startup employees engaged and growing over the long haul — and how people leaders can partner with product leaders to make that happen.
Alex first joined Flatiron back in 2016, after an 8-year stint on Google’s People Operations team. Before her promotion to Flatiron’s executive team this past March, Alex previously ran the HR business partner and employee relations team as the startup rapidly scaled. That vantage point matters: when HR business partners and product leaders operate as one team, we can proactively design the org, clarify decision rights, and align incentives so people can do the best work of their careers.
We began with conflict resolution at work — a topic that shows up in every scaling startup. Alex talked through patterns she’s seen and why borrowing from couples therapy can be surprisingly effective. I’ve found the same. Techniques like mirroring to ensure each person feels heard, naming feelings before jumping to fixes, and agreeing on shared norms (“assume positive intent,” “disagree and commit,” “no surprises”) defuse tension fast. When I coach PMs and cross-functional leads, I push for structure: time-boxed turn-taking, clear owners for decisions, and a quick retro to repair after conflict. These are the same muscles healthy relationships use — empathy, curiosity, and accountability.
We also dug into the challenge of getting employees to stick around long-term at startups. Retention is rarely about perks; it’s about momentum, meaning, and mastery. From hiring your own boss to navigating tough career conversations, Alex’s playbook resonated with mine. I encourage leaders to draft a “growth contract” with each team member: What capabilities are you building this quarter? What scope will expand if you nail it? What support do you need? When someone hires their own boss, I frame it as a capability accelerator — you’re trading title for a teacher, and the compounding effect on your craft can be huge.
Her own journey — rising through the ranks from IC to exec at Flatiron — offers a blueprint for the IC to manager transition many product folks face. My guidance: don’t rush the leap. First expand scope as an IC (own bigger outcomes, not just features), then practice leadership without authority (drive cross-functional programs), and finally formalize people leadership when the org truly needs it. In product management leadership, that sequencing prevents the common trap of managing without mandate or mission.
Alex has also seen the growing pains of scale up close — and I’ve lived them, too. On day one in a new role, you’re “selling” your new role with an elevator pitch when you first join, because clarity reduces friction. I write a crisp one-liner on why the role exists, the problems it owns, and how success will be measured, then socialize it relentlessly. Just as important is resisting the danger of locking into people processes and frameworks too early. I favor lightweight experiments: pilot a performance ritual with one org, run a compensation calibration dry run, or test a feedback cadence in a single squad before scaling. Evolution beats edict.
Across all of this, the throughline is simple: great people leadership and great product leadership share the same foundation — clear outcomes, frequent feedback, and respect for the human at the center of the work. Whether you lead engineering, design, product, or people, these principles help teams compound trust and results.
Inspired by this post on First Round.