Project Failure Files: Relying on Ad-Hoc Processes

In Episode 65 of the Project Failure Files weekly webcast, our focus was “Running on Random,” in which Sharon and I tackle the deceptively common mistake of running teams without a shared process. We draw a bright line between helpful structure and soul-sucking bureaucracy, arguing that a lightweight, repeatable method—clear roles, simple cadences, right-sized reporting—actually speeds delivery and reduces stress. Culture fit matters: pick a framework people will use, not one they’ll dodge.

Sharon and I dig into the fallout of “winging it”: hero culture, scope drift, reinvented wheels, shaky quality, and onboarding that feels like guesswork. Without portfolio-level priorities and agreed handoffs, every project becomes the #1 emergency and morale tumbles. Small teams are hit hardest; ironically, they benefit most from a minimal operating rhythm.

Finally, we get practical. Our advice is to start with standards and outcomes, then select the lightest rituals and tools to meet them. Over-communicate transparently, balance control with flexibility, and measure what matters—including testing and risk. Try a known framework (Agile, PMO lite, etc.), adapt it to your context, and improve it weekly through team reviews and retrospectives.

Enjoy the episode!

Be sure to tune in next Monday, November 17th at 9am Pacific for a program update on our weekly series. Hope you can join us on our NEW YouTube channel (please subscribe!), or find us on LinkedIn.