What Happened with the Communication Domain in the PMBOK® Guide 8th Edition?
In this episode, Ricardo discusses a key change in the PMBOK® Guide 8th edition: the relationship between stakeholders and communication. In previous editions, communication was a separate knowledge area, but now it is considered part of stakeholder management. This shift is significant because communication only exists when there are stakeholders with different needs. If a project had no stakeholders besides yourself, communication would be unnecessary. Therefore, communication is a tool to support stakeholder engagement. In the new PMBOK® structure, stakeholders remain a performance domain that includes planning, execution, and control activities. Ricardo encourages PMI members to download the PMBOK® Guide PDF and explore these updates to improve project value and delivery.
Listen to the podcast to learn more!
--------
3:05
--------
3:05
My First Impressions about the PMBOK® Guide 8th Edition
In this episode, Ricardo discusses the new edition of PMBOK 8, which brings important changes more aligned with the real work of project managers. Based on nearly 48,000 data points and two rounds of global feedback, it has become more practical, clear, and value-oriented. The old 12 principles have been condensed into six more focused ones, while maintaining good project practices. The traditional five process groups return and now apply to predictive, agile, and hybrid projects. The old knowledge areas have evolved into seven performance domains: governance, scope, schedule, finance, stakeholders, resources, and risks. This edition also features 40 updated processes with integrated ITTOs and reinforces tailoring with practical examples, making the guide more applicable and balanced.
Listen to the podcast to learn more!
--------
5:43
--------
5:43
Luck, Probability, and Risk: What Is Really Under Your Control in Projects
In this episode, Ricardo discusses the role of luck and probability in project management. He explains that while luck can influence outcomes, it favors those who are prepared. Probability, he says, is not a prediction but a decision-making tool that helps manage uncertainty. Effective project managers turn randomness into results through preparation: identifying risks, creating contingency plans, defining triggers, and building buffers. Ricardo also warns against hindsight bias, which makes us underestimate luck after success. He recommends modeling uncertainty with scenarios, using simulations for high-risk decisions, protecting the critical path with buffers, and designing flexibility into projects. True management, he concludes, is not about eliminating luck but shaping how it affects outcomes—turning uncertainty into smarter choices and opportunities.
Listen to the podcast to learn more!
--------
5:34
--------
5:34
Executives Who Don’t Understand Projects Can’t Deliver Results
In this episode, Ricardo explains why executives need to understand the logic of project management to make informed strategic decisions. Projects drive organizational changes, such as digital transformation, new products, entry into new markets, and mergers. Without understanding how projects add value and manage risk, leaders may fail to connect strategy to execution. Many focus only on "normal functioning," but the future depends on "business as change." By understanding the dynamics of projects, executives ask better questions, support teams effectively, and build a results-oriented culture. This knowledge helps them keep pace with the organization, prioritize efficiently, and see failures as learning opportunities. True leadership requires learning to think like a project, not like tools, but like governance, critical thinking, and value creation.
Listen to the podcast to learn more!
--------
3:31
--------
3:31
The Invisible Loop: Why Your Schedule Never Balances Out
In this episode, Ricardo discusses activity loops, which occur when tasks become predecessors and successors to each other, creating cycles that make schedule calculations difficult. Although schedules are designed for linear flows, engineering and innovation projects are often iterative, with constant revisions and feedback. Looping isn't a mistake, but it needs to be represented correctly. Ricardo suggests some ways to avoid this problem, such as creating successive versions (elaboration 1, 2, final), using intermediate milestones, or delayed start-start relationships. When interdependence is unavoidable, he recommends using the Design Structure Matrix (DSM), which maps circular relationships and helps plan blocks of iterative activities. The important thing is to choose the model that best represents the project's reality.
Listen to the podcast to learn more!
Since 2007, Ricardo Vargas publishes the 5 Minutes Podcast where he addresses in a quick and practical way the main topics on project, portfolio and risk management.
Brasil