The Growth Reframe
You don’t have to fire anyone. You have to be brave enough to redefine contribution
A couple of posts ago I wrote about an engineer who automated her own team so well that half of it disappeared, and a senior engineer cornered between a shrinking job market and a contract that would not let him build anything else. Both stories were about what happens when leadership only sees people through the narrow lens of the role they are currently performing.
This one is about what happens when someone refuses to look away from that lens.
She was a good project manager. Not the loudest in the room, but the one whose status reports leadership actually trusted, because she flagged risk before it became a crisis rather than after.
When the organisation rolled out AI tools across the delivery function, most PMs treated it the way most people treat a new reporting template. Comply, tick the box, move on. She did something different. She started using AI to model second order risk, not just the obvious blockers sitting on the plan, but the ones two steps downstream. The vendor dependency that would only bite in month four. The resourcing gap that would not show up until the team hit its next milestone.
Her manager noticed. Not because she announced it. Because the retros started sounding different. She was not just reporting what had gone wrong. She was explaining what had not gone wrong yet, and why.
Most managers would have filed that under good PM instincts and left it there. Hers asked a different question. What is she actually doing when she does this. And the honest answer was, she was not managing a project anymore. She was making product judgment calls, the kind a product manager makes, about what mattered and what did not, before anyone had asked her to.
Here is the part that almost did not happen. The organisation was mid restructuring. Efficiency numbers were being reviewed. Her manager could have looked at her project purely through the delivery lens, seen a well run project, moved on, and never asked the deeper question. That is what happened to the engineer in the first story of this series. Nobody looked underneath what she had built. They saw the pipeline, and they saw the headcount it no longer needed.
Her manager looked underneath instead. Not at what the project delivered, but at the kind of thinking that delivered it. And then he did something that took more nerve than spotting the pattern did. He staked something on it before it was proven. He gave her a product problem to solve, months before anyone would have called her a product manager, at a point where if she had struggled, it would have been visible and it would have cost him something too.
She did not struggle. Eight months later her title changed. But the title was the last thing that changed. Everything that mattered had already shifted the day someone decided to test for what she could become, instead of only measuring what she already was.