Project Management

Random Thoughts

by
Uniting the passion for writing and project management

About this Blog

RSS

Recent Posts

Autonomous vehicles: when 90% done means nowhere near ready

The accidental path to Project Management

What history reveals about AI and the Project Manager profession

When results aren’t enough: Rethinking Leadership

The Sagrada Família: A living Project Management case study

Categories

74-343, Agile, Agile, Artificial Intelligence, basadur, Budget Management, Career Development, Certification, Change Management, Change; Change management; Team management, Chapter, Communications Management, Complexity, conceptualizer, Cost Management, data management, Decision Making, Estimating, Ethics, generator, Giga Projects, Goal Setting, Governance, Human touch, implementer, Leadership, Lessons Learned, machine learning, MS Project 2013, Negotation, New Practitioners, optimizer, Organizational behavior, Organizational Culture, personal growth, pharmaceutical; lifecyle management; agile; waterfall, PMI, Problem solving, Product Owner, Project Communication, Project Management, PSM I, PSPO, Resource Management, Risk Management, Scheduling, Scope Management, Scrum, self-development, Stakeholder management, Strategy, Teams, test, training, Volunteering

Date

The ABC Principle in Project Management

linkedin twitter facebook Request to reuse this  

The ABC principle is often linked to learning fundamentals, as famously sung by the Jackson 5 in ABC. But in project management, ABC stands for Assume nothing, Believe no one, Check everything. This take on ABC highlights the importance of risk mitigation by challenging information. It closely relates to PDCA (Plan, Do, Check, Act), but with a heavier emphasis on skepticism and validation.

Before diving into the ABC Principle in project management, it's important to take this with a grain of salt. These ideas encourage a healthy level of skepticism, but like any approach, they should be balanced with trust, teamwork, and effective communication.

Assume nothing

Every assumption is a potential risk. When unverified assumptions guide a project, it opens the door to disaster. A classic example is NASA’s 1999 Mars Climate Orbiter. The spacecraft was lost because of a simple yet catastrophic error: a failure to convert units. One engineering team used metric units (Newtons) for the spacecraft's thrust data, while another team used imperial units (pounds-force). This mismatch was never corrected, leading the spacecraft to come much closer to Mars than planned—so close that it disintegrated in the planet’s atmosphere. This $125 million failure was a direct result of an unchecked assumption.

In project management, assumptions like this one often fly under the radar, making it crucial to question even the smallest details to avoid colossal mistakes. Many assumptions in project management are tied to communication, which makes it crucial to communicate often and clearly. In one of my early years as a project manager, I encountered this first-hand. I assumed that project sponsorship would transfer from a departing managing director to the incoming one without issues. I went ahead and updated the project documentation to reflect the new sponsor. However, I failed to communicate this change to the incoming managing director. Later, the new sponsor humorously remarked, “Oh, thanks for making me the new sponsor. It would have been nice if you had informed me.” This taught me that assumptions around roles and expectations should always be clearly communicated.

Believe no one

“Believe no one” should be taken with a grain of salt, but even reliable sources need to be cross-examined. Everyone tends to believe what they’re told—especially if it comes from trusted sources. But in project management, relying on verbal assurances without verification can lead to failure. Cross-examination and double-checking are essential to increase the odds of delivering a successful project.

A perfect example is the 2017 Fyre Festival disaster. The organizers believed the assurances of suppliers who lacked the capability to deliver. Even reputable sources can be wrong, and failing to dig deeper can cause significant setbacks.

In today's world, this principle has become increasingly interesting due to the sheer volume of information at our fingertips. The rise of AI is playing a pivotal role here as well. Even AI tools like ChatGPT, which can provide valuable insights, come with a disclaimer that they may make mistakes and suggest verifying the information provided. This reminds us of the importance of skepticism in any project.

Check everything

Being diligent is essential. Always validate that information is up to date and relevant. Boeing’s 737 Max crisis is a stark reminder—outdated assumptions about the aircraft’s MCAS software, and failure to thoroughly check system changes, led to two fatal crashes. Not verifying critical details led to widespread fallout.

"Check everything" loops back to the first two rules. By assuming nothing and believing no one, you are effectively checking everything. But again, what is "everything"? This touches on the concept of WYSIATI—"What You See Is All There Is," a term coined by Daniel Kahneman. It humorously points out that no matter how thorough we think we are, we likely missed something. Funny, isn’t it?

In project management, the ABC rule is as simple yet vital as the Jackson 5 tune. It’s about consistently challenging information, assumptions, and sources to avoid risks and ensure project success.

Posted on: October 22, 2024 05:52 AM | Permalink | Comments (16)
ADVERTISEMENTS
ADVERTISEMENT

Sponsors