Since 2007, Ricardo Vargas has been publishing the 5 Minutes Podcast, where he addresses in a quick and practical way the main topics on project management, business agility, risk and crisis management, among other topics.
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.
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.
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.
In this episode, Ricardo discusses the common rush to start acting before fully understanding a project’s problem. Action creates a sense of progress, while thinking may seem like wasted time. However, teams can work intensely and still move quickly in the wrong direction. Ricardo emphasizes that speed should not be confused with impulsiveness.
In this episode, Ricardo discusses rework, one of the most damaging yet invisible costs in projects. Rework occurs when presentations, software, proposals, plans, or decisions must be redone because expectations, requirements, or responsibilities were unclear. Although teams appear busy, they may simply be returning to a point they believed they had already reached—paying multiple times for a result.
In this episode, Ricardo explains that projects are promises about a future often experienced by people other than those who originally approved or delivered them. He argues that organizations tend to exaggerate benefits, minimize long-term costs, and focus on schedules, budgets, scope, and acceptance instead of verifying whether promised outcomes materialize.
In this episode, Ricardo reflects on reactions to his newsletter about project management in the age of AI. He stresses that he is not predicting the future but encouraging professionals to question assumptions and prepare for rapid change. Although some readers considered his views alarmist, he argues that learning AI carries little downside: even if its impact is smaller than expected, new skills remain valuable.
In this episode, Ricardo reflects on how many project managers have shifted from managing projects to merely reacting to urgent matters. Their daily routines are consumed by meetings, messages, emails, and immediate issues, creating a sense of heavy workload but little actual progress. According to him, managing projects means reducing uncertainty, whereas managing anxiety amounts to nothing more than reacting to chaos.
In this episode, Ricardo discusses the new PMP certification exam. He explains that updating the exam is a natural progression, as project management has evolved with artificial intelligence, agile methods, distributed teams, and new challenges. He highlights that the PMP exam has always prioritized the ability to analyze situations, make decisions, lead teams, and deliver value, rather than simply memorizing concepts.
In this podcast, Ricardo argues that many projects are not actually late; instead, their schedules were unrealistic from the beginning. He explains that organizations often approve aggressive timelines to satisfy executives, budgets, or customer expectations, only to blame the project team when those plans fail.
Read Ricardo's reviews of some of the best technical books published.
View recommendations Powered by