Project delivery in a constantly changing World
The most dangerous word in corporate life right now is transformation. Not because change is wrong — but because it has become the default response to every performance problem, including the ones caused by too much change in the first place. Boeing, Toyota, Microsoft and Amazon all prove the same point. Stability wins.
You’re trusted, you deliver consistently, and your annual reviews are genuinely encouraging and yet when the promotion conversation comes around, someone else gets the nod and you get handed another project. This isn’t bad...
Most organisations don’t fail because people take too many risks. They fail because people stop taking them altogether. By confusing intelligent experimentation with failure, leaders inadvertently discourage innovation, slow AI adoption, and create cultures where good ideas die before they’re tested. The real competitive advantage isn’t technology—it’s learning.
Microsoft’s AI just found 16 critical security flaws in Windows — before any human did. It used a five-stage pipeline with 100+ specialised agents: map, scan, challenge, deduplicate, prove. Sound familiar? It should. It’s everything a great stage gate process is supposed to do. Just faster. And it never gets tired.
We don’t burn out during the sprint. We fracture in the void that follows. The stimulus is gone, but the nervous system hasn’t caught up. That gap — between peak pressure and sudden stillness — is where high-performing teams quietly fracture. The project isn’t complete until the people who delivered it have properly landed and returned to normality.
What if an AI could find critical flaws in your systems that human experts missed for 27 years — for $50? That’s no longer hypothetical. Steve Gibson calls it the biggest shift in security history. Here’s what every leader needs to understand before adversaries get the same capability.
You’re writing dozens of emails a day — to execs, vendors, and your team. Each one carries tone you may not intend. One wrong phrase can collapse a relationship, delay a launch, or signal you’re not in control.
Senior stakeholders don’t reject bad ideas. They reject poorly framed ones. If you’re walking into boardrooms with solid data and still losing the room, the problem isn’t your evidence — it’s how you’re separating fact from opinion. Most PMs never learn the difference.
Anger in complex programmes isn’t a soft-skills problem — it’s a delivery risk. This piece breaks down how senior PMs can manage their own frustration under pressure, de-escalate stakeholders without over-promising, and build environments where people raise problems early enough to fix them.
You hired a strong project manager. In their first year they were exactly what you needed — composed under pressure, trusted by stakeholders, delivering in difficult conditions. Eighteen months later, something has shifted. They’re...
Your lead engineer just got pulled to another project. You’re still on the hook for the deadline. This is the PM’s paradox — responsible for everything, in charge of nothing. But here’s the truth: influence, strategically built, is more durable than any org chart title. Here’s how to wield it.
Project Management Articles Rebel’s Guide to PM Internet of Things (IoT)