5 Minutes Podcast with Ricardo Vargas

In this episode, Ricardo challenges the belief that project outcomes depend mostly on luck. While predicting the future is difficult, controlling a project means recognizing early signals and making timely decisions. Based on his experience, Ricardo believes that 60 to 70 percent of project events are within reach of a well-structured team, while only around 30 percent depend on chance. Supplier delays, key-person risks, seasonal weather, and changing requirements often provide warning signs before becoming crises. Strong teams create psychological safety for bad news, establish contingency decisions in advance, and distinguish genuine chance from carelessness. Ricardo encourages listeners to revisit a problem labeled “bad luck” and ask whether signals existed or earlier decisions were possible, reinforcing accountability and continuous learning.

Listen to the podcast to learn more!

In this episode, Ricardo explores Albert Hirschman’s Hiding Hand Principle, which suggests that we often underestimate both the difficulties of a project and our ability to develop creative solutions when problems arise. In contrast, Bent Flyvbjerg’s research identified the Malevolent Hiding Hand, where costs are underestimated, and benefits overestimated, without creativity being enough to rescue the project. Later studies suggest that both situations can occur. Ricardo argues that the key is distinguishing two different moments: when deciding whether to start a project, excessive optimism creates significant risk; during execution, however, confidence, creativity, and adaptability can be essential to overcoming unexpected challenges. He concludes by inviting us to recognize when a difficult project is worth fighting for—and when the bravest decision may actually be to stop.

Listen to the podcast to learn more!

In this episode, Ricardo explores how reliance on artificial intelligence can weaken human connections and knowledge sharing in project management. Inspired by declining participation in professional communities, he highlights how private AI conversations may replace exchanges that build collective learning. Although AI provides quick answers, projects depend on contextual knowledge, shared experiences, and trust developed through relationships. Drawing on Adam Grant’s ideas, Ricardo emphasizes the importance of giving while maintaining boundaries to avoid exhaustion or exploitation. AI should support collaboration without replacing it. He invites listeners to compare how often they consult AI with how often they help others, encouraging them to answer colleagues’ questions, share lessons, and strengthen the human exchanges that sustain teams, especially during difficult project moments.

Listen to the podcast to learn more!

In this episode, Ricardo questions whether years of project experience represent genuine growth or repeated routines. While projects are carefully measured, professional competence often relies on resumes, certifications, and subjective judgments. He explains how artificial intelligence could make competence assessments continuous and accessible. As an example, he introduces PM Goal, a free tool he helped develop that analyzes professional maturity across people, process, and business, suggesting actions for thirty, sixty, and ninety days. Ricardo emphasizes that responsible AI assessments must disclose uncertainty rather than offer misleadingly precise scores. Such evaluations cannot capture courage, judgment, or dedication to a team. Their purpose is to guide development, never define personal worth, encouraging professionals to reflect on and measure their own growth.

Listen to the podcast to learn more!

In this episode, Ricardo presents Chesterton’s Fence, a principle that warns against removing rules, controls, or processes before understanding why they were created. Although simplifying bureaucracy can improve agility, eliminating safeguards without investigating their purpose may revive risks they were designed to prevent. Ricardo recommends four steps: identify who created the process and why; determine which risk it controls; when its purpose remains unclear, test its removal through a reversible pilot; and document why controls exist for future teams. He also encourages humility when judging decisions made by previous teams, since they may have faced unknown constraints. His challenge is: before eliminating anything from a project, ask why it is there. If nobody knows, investigate before tearing down the fence.

Listen to the podcast to learn more!