5 Minutes Podcast with Ricardo Vargas

Trailer – 5 Minutes Podcast

The Hiding Hand: What If Underestimating Your Project Is a Good Thing?

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!

The Project Where Nobody Asks Anybody Anything

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!

PM Goal: Fifteen Years of Experience, or One Year Repeated Fifteen Times?

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!

Chesterton's Fence: The "Useless" Control That May Be Saving Your Project

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!

Your Project Didn't Break Overnight: It Got Used to Being Wrong

In this podcast, Ricardo explains the normalization of deviance: repeated small failures that, because they cause no immediate consequences, become accepted as normal. Drawing on Diane Vaughan’s studies of the Challenger disaster, he shows how delays, skipped tests, recurring risks, and postponed meetings can make problems invisible. To avoid this trap, he recommends examining trends instead of isolated events, establishing rules before pressure arises, and documenting exceptions with an owner and an end date. He also stresses the importance of protecting people who challenge improper practices and listening to outsiders or newcomers, who can notice deviations the team has normalized. Ricardo invites listeners to review their status report and ask when a problem became considered normal within the project team. Listen to the podcast to learn more!

AI Doesn't Want Anything. And That Is Why We Are Irreplaceable

In this podcast, Ricardo explores what makes people irreplaceable in an age of artificial intelligence. Rather than asking which tasks AI cannot perform, he suggests asking what AI does not have: desire, responsibility, and something at stake. AI can analyze risks, prepare schedules, summarize contracts, and recommend decisions, but it does not care whether a project succeeds or fails. People give projects purpose because they want outcomes and accept responsibility for the consequences. Drawing on his humanitarian work at the UN, Ricardo explains that legitimate decisions require someone willing to face the affected community afterward. He concludes that professionals become difficult to replace when they care, question incorrect recommendations, defend outcomes, and put their names and reputations behind those choices. Listen to the podcast to learn more!

Your AI Pilot Was Cheap. The Bill Won't Be

In this episode, Ricardo warns that artificial intelligence is often approved as a project cost, but after implementation, it becomes an ongoing operational expense. Unlike traditional licenses, its cost varies according to consumption: the greater the adoption, the higher the bill. He also highlights frequently ignored expenses such as data preparation, systems integration, human review, price changes, model replacement, and new testing. Ricardo recommends presenting recurring costs per unit, projecting growth scenarios, identifying who will assume the expense after the project ends, and proactively assessing exit costs. For him, advancing with AI is essential, but it requires financial discipline. Without knowing the cost, the responsible party, and the value generated, there is no complete and sustainable business case. Listen to the podcast to learn more!

Your January Plan Is Already Dead. Nobody Told You

In this episode, Ricardo warns about the risk of resuming January’s projects at midyear. According to him, the context has changed: budgets, suppliers, technology, markets, regulations, and priorities may now be different. Before following the original plan, he recommends three actions: recalculate the project using current information, assess external changes, and reevaluate the portfolio, prioritizing what truly matters. Ricardo emphasizes that replanning does not represent failure; instead, it shows awareness of the transformations that have occurred. He suggests setting aside two hours, gathering people who understand the project’s reality, and asking whether it would still be approved today with the same structure, scope, team, and cost. This reflection reveals whether the project will meet the organization’s needs in December. Listen to the podcast to learn more!

If It's Not a Partnership, It's Just an Invoice: Leading the People Who Don't Work for You

In this episode, Ricardo explains that modern projects depend heavily on external suppliers, contractors, partners, and AI vendors whose teams do not report directly to the project manager. He argues that leading these people has become a core project management skill. He emphasizes that contracts and service-level agreements define obligations and penalties but do not create trust, commitment, or guarantee success. Ricardo also warns that supplier risk should be treated as a major project risk. He recommends involving partners in planning, explaining the project’s purpose, addressing problems early, and speaking directly with leaders who can reallocate resources. Finally, he encourages managers to identify their three most critical external organizations and build genuine relationships with their senior decision-makers. Listen to the podcast to learn more!