Escaping the Low-Impact PM Death Spiral
Low-impact work begets low-impact work until layoffs — break the cycle by proactively claiming high-impact work.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 3
- Confidence
- 95%
LeMay names a self-reinforcing dynamic he has seen in nearly every medium-to-large company: teams take on safe, cosmetic work because it invites less scrutiny, the product accumulates loosely-connected features ('rhinestones on the car'), coordination overhead grows, and doing high-impact work becomes ever harder — pushing teams deeper into low-impact work until the next layoff. The escape is a team choosing to stop incurring the risk of being low-impact.
Origin
Coined by Matt LeMay in 'Impact First Product Teams,' drawn from his consulting across many organizations. The framing is partly a response to Spotify CEO Daniel Ek's 2024 layoff message about 'too many teams doing work around the work.'
Core principles
- 01Low-impact work is chosen because it invites less scrutiny and is less likely to break anything important
- 02Every cosmetic feature adds weight to 'the hood of the car' until you can no longer reach the engine
- 03Coordination layers (program management, reorgs) are symptoms of accumulated low-impact complexity, not cures
- 04Executive attention and cross-team dependencies are signs your work matters — not impediments to route around
- 05Being told to build a low-impact feature is no excuse; you'll get laid off eventually anyway
How to run it
- 1
Recognize the rhinestone reflex
Notice when your team defaults to cosmetic improvements and small features because touching the 'engine' (the commercial core) is risky. Name it out loud.
Pro tip The car analogy: adding rhinestones is visible and safe, but ten teams adding rhinestones make the hood too heavy to open.
Watch out Low-impact work self-justifies — 'what's the worst that could happen, we can always take the paint off' is exactly how the spiral deepens.
- 2
Decide to stop incurring low-impact risk
Have the team explicitly resolve: 'we are not going to incur the risk of being a low-impact team anymore.' Commit to proactively seeking high-impact work.
- 3
Reframe friction as signal
When executives suddenly take a big interest or you must coordinate with many teams, treat those as evidence the work matters, not as reasons to retreat to safe work.
Pro tip Be willing to deliver by subtracting — removing steps and streamlining rarely gets celebrated like a feature launch but often is the high-impact move.
In the wild
During Mailchimp's shift from single-product to platform (pre-Intuit acquisition), VP-then-CPO Natalyia Williams worried the platform push would erode commercial fundamentals, so she set an ambitious org-wide goal: improve the rate of users who successfully send their first email. Most teams were hesitant — it was the 'commercial heart of the business,' and risky. One PM who had worked across the app and on a growth team took it on, ran user research to find where people got stuck before sending, gathered PMs in a room in Atlanta and said 'I am going to haunt all of you in your dreams if you do not take this on.' They fixed it by subtracting steps and streamlining onboarding rather than launching new features.
→ The team hit the goal by making the experience simpler; it made the product better and the business better — a case of one brave team breaking the spiral.
Common mistakes
Hiding behind 'the execs told us to build it'
LeMay is explicit that building a low-impact feature because leadership is excited about it is no protection — 'you're still going to get fired eventually.' Deflecting accountability to whoever assigned the work doesn't remove your exposure.
Solving complexity with more coordination layers
Adding program management and reorgs to manage dependencies ('reorgs fix everything') treats the symptom while the hood keeps getting heavier, making high-impact work even harder and accelerating the spiral.
Is it for you?
Best for
Product teams at maturing or platform-transitioning companies that feel busy but suspect their work isn't moving the commercial engine.
Not ideal for
Early-stage teams where nearly all work is inherently close to the core and the spiral hasn't formed yet.
From the transcript
“the low impact death spiral is the dynamic in which every medium to large company I've ever worked with finds itself in one way or…”
“if you have 10 teams adding rhinestones to a car, eventually the hood of the car is going to be so heavy that you can't…”
“Low impact work begets low impact work. The more low impact work you do, the harder it is to do high impact work”
“We are going to proactively seek out high impact work”
“even if you were told to build a thing that the execs are really excited about, you're still going to get fired eventually”
From the episode
The one question that saves product careers
Matt LeMay