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!

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!

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!

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!

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!

In this episode, Ricardo explains that projects don’t really fail — they reveal the truth about an organization. Projects act as mirrors, exposing hidden cultural flaws like poor alignment, weak leadership, and political decisions. When pressure from deadlines and budgets increases, the organization’s true nature surfaces: silos, egos, and fear replacing collaboration. A troubled project is not a failure but an X-ray showing what is broken and who has the courage to fix it. Crises test maturity and trust, revealing whether teams can speak honestly or stay silent. The real mistake is ignoring these lessons and repeating errors. Ricardo explains that learning from failing projects leads to real growth and invites listeners to explore his new course on recovering troubled projects. Listen to the podcast to learn more!

In this episode, Ricardo discusses AI washing, a growing trend where organizations falsely claim to use artificial intelligence. Similar to greenwashing, AI washing occurs when companies exaggerate their AI capabilities to attract investors or appear innovative. In reality, many so-called AI systems are just basic automation or rule-based tools. This practice creates serious risks, including loss of credibility, legal issues, and project failure. Vargas highlights warning signs: flashy storytelling over science, unrealistic promises, lack of true AI experts, neglect of data quality, and poor governance. He explains that real AI projects require transparency, solid data, ethics, and humility—reminding project managers to avoid overpromising and to focus on genuine, data-driven value instead of hype. Listen to the podcast to learn more!

In this episode, Ricardo announces the release of the second global research on AI in project management, co-authored with Antonio Nieto-Rodriguez. Compared to their first study two years ago, AI has moved from experimentation to mainstream adoption. The 2025 report, based on insights from 870 professionals in 97 countries, shows that AI familiarity has doubled, and over two-thirds now use AI tools daily. Nearly half of organizations report cost reductions, and 25% achieved over $250,000 ROI. The greatest benefits appear in scaling, risk management, and forecasting. Barriers have shifted from technical to cultural and ethical. By 2028, 42% of organizations expect AI copilots to manage most projects. AI won’t replace humans but enhance leadership and decision-making. Download the free report at pmairevolution.com. Listen to the podcast to learn more!

In this episode, Ricardo introduces the concept of nano projects: ultra-short, highly focused initiatives lasting just a few days, designed to generate value quickly. Unlike megaprojects, which require months or years, nano projects respond to the need for speed and adaptation in a fast-paced world. Examples include testing a marketing channel in five days, redesigning hospital processes in a week, or running rapid pilots in the public sector. Their advantages include low risk, rapid learning, and greater team engagement, as results are quickly seen. However, they require a well-defined scope, discipline, and attention to quality. Ricardo emphasizes that they complement traditional models, helping to reduce uncertainty and stimulate innovation in short cycles. Listen to the podcast to learn more!

In this episode, Ricardo questions whether Agile is still sufficient in the face of the speed of artificial intelligence. Created in 2001, the Agile Manifesto introduced short iterations and continuous learning to address the unpredictability of software development. However, today, tools become obsolete in days, raising questions about the relevance of 2- to 4-week cycles or a quarterly backlog. Vargas doesn't criticize Agile—on the contrary, he recognizes its essential role for organizations in dealing with volatility. The point is to reflect on how to apply it intelligently in the face of the rapidity of AI: smaller microcycles? More discipline? An "Agile 2.0" that includes governance, ethics, and social responsibility? The challenge is adapting to the current intensity of change. Listen to the podcast to learn more!