5 Minutes Podcast with Ricardo Vargas

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!

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!

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!

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!

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!