PMP disapointment after exam

I finally passed the PMP exam a few months later, scoring Above Target in all domains.

Compared with my first attempt, one major difference was that I used an unofficial simulator and external video preparation instead of relying mostly on the official simulator.

My honest takeaway is that the exam contains two kinds of difficulty. Some of it is valuable: certain questions are subtle in a way that genuinely separates people who really understand PMP methodology from those who do not. But some other subtleties feel artificial and poorly aligned with the real-world judgment expected from an actual project manager.

That can create a frustrating sense of unfairness. Still, it is also part of why passing the certification feels so satisfying: to succeed, you really have to immerse yourself in the mindset and take the preparation seriously.

Personally, I think the exam could remain just as challenging while being more realistic and removing some of the subtleties that feel more like design flaws than true tests of project management ability.

Thank you all for your professionalism, your thoughtful analysis, and the quality of this exchange.

Reading your comments, and reflecting on my own journey, I realized that what I experienced with the PMP exam goes beyond a simple preparation issue. It touches something deeper about how different profiles approach complexity, uncertainty, rules, and decision-making.

Over the years, I have developed a rather systemic way of thinking. It comes from a combination of experiences and studies: military environments, including exposure to special forces selection, intelligence, and psychological operations cultures, where discipline, responsibility, information asymmetry, uncertainty, and decision-making under constraint coexist; project environments, where constraints are concrete and immediate; political science and international relations, which taught me to analyze power structures, institutions and decision systems; and a personal interest in neuroscience, epistemology, and more abstract domains such as quantum physics or relativity.

I do not mention these fields as an argument of authority, nor as an expert claim. I mention them because they raise epistemological questions about perception, uncertainty, models, influence, incentives, and the limits of human understanding. When you spend time engaging with such questions, you become more cautious about obvious answers. You start seeing that reality is often filtered through frameworks, assumptions, institutions, narratives, and incomplete information.

In practice, this often leads to a form of Bayesian thinking: constantly updating one’s judgment based on incomplete information, while remembering that unknown unknowns may still exist. This can be useful in project environments, but it can also make standardized tests more difficult, because the mind naturally explores several possible interpretations before accepting one predefined answer.

I remember, for example, a situation on a construction project where, according to the applicable safety rules, workers were required to wear life jackets because they were operating near a shallow water area. From a compliance standpoint, the rule was understandable. However, in the actual situation, the water level was approximately 10 cm, while the weather conditions were extremely hot.

Applying the rule mechanically would have reduced a theoretical drowning risk, but it was also creating a more immediate and concrete risk: heat stress, fatigue, discomfort, reduced vigilance, and potentially heat-related incidents.

I made the decision not to enforce the rule mechanically.

For me, this illustrates what leadership sometimes means: not hiding behind a procedure when reality clearly requires judgment. A leader must understand the rule, respect its intent, assess the real environment, and take responsibility for a proportionate decision when two risks contradict each other. This is not about rejecting the framework. It is about preserving the purpose of the framework in real conditions.

This kind of situation is especially interesting in a French and continental law context, especially when compared with common law cultures. France has a strong culture of written rules, formal obligations, risk prevention, and legal traceability. This has many advantages: clarity, protection, accountability. But it can also create situations where several legitimate principles collide: compliance with a rule, proportionality, actual risk assessment, duty of care, operational feasibility, and real protection of workers’ health.

In such cases, project leadership cannot only be bureaucratic. It must also be practical, ethical, and accountable.

I encountered a similar pattern when preparing psychometric tests for special forces selection. In some abstract reasoning tests, especially with sequences, patterns, or logic exercises, I sometimes identified several possible answers. The test, however, expected one specific internal logic. Once I understood the “language” of the test, my performance improved significantly.

Before that little training, I was simply not able to think inside the box expected by the test.

I could multiply examples like these — some of them are even quite funny in retrospect — but I think you understand the idea.

This is where I see a parallel with the PMP exam.

The PMP exam does not only test project management knowledge. It also tests the ability to operate within a specific decision model. For experienced or non-linear profiles, the challenge is not always understanding the framework. Sometimes, the challenge is temporarily suspending part of one’s contextual judgment in order to align with the expected PMP logic.

That was probably the most important lesson for me.

Compared with my first attempts, the turning point was not only more effort. It was learning to enter the PMP mindset with discipline. I had to stop answering as “Thomas managing a real project with all its ambiguity” and start answering as a project manager operating inside the PMI decision model.

There is also another important point: systemic profiles need contradiction.

What matters most, in my view, is not always that everyone reaches the same decision. It is the ability to fully justify a decision through the most systemic view possible: rules, risks, context, human factors, operational constraints, ethics, and responsibility.

And fortunately, there are sometimes differences of appreciation between individuals. That is not necessarily a weakness. It can even be one of the most valuable parts of collective decision-making.

There is something very interesting when two different decisions, both legitimate in the way they are constructed, are confronted with each other. This confrontation forces each person to clarify assumptions, test the robustness of their reasoning, and refine the final decision.

A broad, strategic, or non-linear way of thinking can be useful, but it must be confronted with people who are more technical, more focused, and sometimes less global in their approach. This complementarity helps challenge decisions, test feasibility, and avoid both excessive abstraction and purely mechanical solutions.

I experience this very clearly with my current working partner. His approach is more technical and operational, while mine is often more global and systemic. This creates a useful balance: it helps temper decisions without necessarily removing audacity when it is needed.

Four years later, I can honestly say that I am proud to hold the PMP certification.

Today, I no longer see it only as an exam I had to pass. I see it almost as a structured advisor that stays with me when I face complex project situations. It gives me a common language, a disciplined way to frame problems, and a useful decision model when constraints, stakeholders, risks, and uncertainty interact.

It also helped me recently while completing a Global Executive MBA / Master’s degree in management at Sorbonne, in parallel with my full-time professional activity. My final work focused on the strategic analysis of a French public university hospital, as part of a broader personal project to restart medical studies and eventually become a surgeon.

This project is not only analytical for me. It is also a way to reconnect with something more fundamental: being more present, more directly useful to people, and more connected to my immediate human environment. After years of working on complex systems, strategy, and large-scale projects, I feel the need to move closer to direct care and concrete human impact.

In that context, the PMP background helped me far beyond certification. It helped me connect operations with strategy. It gave me a structured way to translate field constraints into strategic analysis.

At the same time, my own pragmatic project experience helped me tailor the framework properly, so that the analysis remained realistic, operational, and grounded in the constraints of a tense environment such as the French public hospital system.

That balance was essential.

A hospital is not an abstract organization. It is a living system, under pressure, with limited resources, human fatigue, regulatory constraints, medical responsibility, public service obligations, and strategic tensions. In such an environment, a purely theoretical analysis would be insufficient. But a purely operational view would also miss the broader strategic picture.

The PMP mindset helped me bridge that gap: from operations to strategy, from constraints to structure, from complexity to decision-making.

This is also why I find the idea of more interactive or contextual PMP questions very interesting. Of course, it may create new challenges. But in principle, it could allow candidates to demonstrate not only that they know the framework, but also how they reason, prioritize, adapt, and make decisions under uncertainty.

In the end, I still believe the PMP has real value. It creates a common language, a structured mindset, and a shared baseline for project management.

But I also believe that the future of project management certification should continue moving closer to what project leadership truly requires: not only applying a model, but navigating reality — where ambiguity, uncertainty, ethics, context, contradiction, and responsibility are always part of the equation.

Thank you again for your insights, and congratulations to everyone for the quality of this discussion.