We’re publishing some of my earlier discussions with authors… I was still learning some interview basics, but the ideas were great nonetheless!
In this episode of Glaringly Obvious, I spoke with Pragati Sinha about why most project failures start from poor beginnings. With years of experience parachuting into troubled projects, Pragati has seen the same pattern repeat. Teams think they are aligned, but important details stay buried. That early drift becomes scope creep, delays, and painful rework.
Here are some of the big ideas:
- Most failures start at the beginning, not the end
- Shallow discovery leads to hidden risks
- A shared evidence source builds real alignment
- AI can support tasks but not replace human judgment
- You need to stress test before you invest
Here’s her framework that got us talking:
Pragati’s Scope Check approach helps teams push past surface-level discovery and get to the truth early. Instead of racing into tasks, she focuses teams on the low-confidence areas that cause confusion later.
One idea that stayed with me is her view on “resetting when you are already in trouble.” Many teams call her after a project is already drifting off a cliff.
Her first move is simple: reset the boundaries. Bring everyone back to what is known, what is unclear, and what evidence is missing. Once the team shares the same facts, progress becomes possible again.
We also talked about where AI fits. Pragati sees AI as useful for pattern recognition and execution, but not for the political, cultural, and contextual nuance that real project work requires. Leaders still have to bring discernment.
Stress test before you invest. She suggests asking harder questions, defining success and failure early, and making sure the team has real proof before committing time, energy, and money.
an important piece to emphasize.