Why Projects Fail
Notas do episódio
We've all worked on those technical projects that felt doomed from the start.
In this episode, we're joined by Eyvonne Sharp and Mike Bushong to dig into what actually derails technical projects, and why the root cause is usually people, not packets.
We unpack:
- Why 80–90% of project failures aren’t technical
- What “executive sponsorship” is supposed to mean (and why most teams never use it)
- The real reason timelines feel arbitrary: information asymmetry
- What “healthy escalation” looks like (and how to avoid the courtroom vibe)
- How to deliver bad news to leaders: few words, calm tone, clear next step, clear ask
- The leadership move that instantly lowers the temperature: removing blame
- Why informal networks matter, including a legendary security-incident save powered by… cheesecake
If you’ve ever felt stuck in status-call theater, pressured to keep the project's status green, or unsure how to talk to leadership when reality hits, this episode is your playbook.
Full show notes, transcript and links: https://artofnetworkengineering.com/episodes/why-projects-fail
For everything AONE: https://artofnetworkengineering.com/