A project can deliver its final output and still not be formally closed.

Closing consists of the actions performed to formally complete or close a project, phase, contract, or, in some cases, to terminate a project before completion. That includes verifying that specific actions from the other focus areas are actually finished before anything gets declared complete — not just checking that the deliverable shipped, but confirming the surrounding work is done too.

The Close Project or Phase process spells out what that actually involves: finalizing all activities related to the project, whether it succeeded or didn't, archiving information, releasing resources, and confirming the extent to which value — or the capability to deliver value — was achieved. None of that happens automatically once the last task gets checked off.

Table of Contents

• What closure actually requires

• What gets lost when closure gets shortchanged

• What actually helps

• The bigger point

What closure actually requires

For predictive work, satisfying exit criteria means confirming documents and deliverables are updated, issues are resolved, measurable value was delivered with a plan to sustain it, and the customer has formally accepted the work. Beyond that: project accounts close, personnel get reassigned or released, and equipment and facilities get reallocated.

Contracts follow their own sequence, and it starts with an acceptance step that functions as the sign-off: confirming formal acceptance of the external source's work. Only after that can the rest proceed — finalizing any open claims or warranties, updating records with final results, ensuring invoices are paid, archiving the records, and resolving any disputes. If acceptance hasn't happened, or a claim, invoice, or warranty is still open, the contract isn't ready to close — no matter how finished the deliverable looks.

A third layer is easy to skip because it doesn't feel urgent: auditing project records, assessing success or failure, documenting lessons learned, measuring stakeholder satisfaction, and verifying regulatory and legal obligations were actually met.

Adaptive approaches close just as deliberately, differently. Closing an iteration means confirming backlog items meet acceptance criteria, getting stakeholder sign-off, and checking nothing's outstanding. Retrospectives capture lessons before the team disperses, and any unresolved risk gets explicitly carried forward — accepted, or handed to the next iteration or operations — rather than left to disappear.

What gets lost when closure gets shortchanged

Skip the process-defined closure activities, and specific, identifiable things go missing:

• Lessons learned never make it into the register, so the next project starts without them.

• Resources — people, equipment, facilities — stay allocated to a project that's effectively already over.

• Contractual obligations go unverified, leaving exposure nobody's actively tracking.

• Stakeholder satisfaction never gets measured, so there's no confirmed answer to whether the project actually met expectations.

• Outstanding risks never get a clear owner. The project's gone, but what it produced isn't — someone still needs to be watching for a risk that only shows up once the deliverable is actually in use.

What actually helps

• Treat the closure list as work to finish, not a box to tick. Exit criteria, contract closeout, and the other closure tasks are three separate jobs — each needs its own check, not one sign-off covering everything.

• Get formal acceptance before calling a contract closed. It comes first for a reason — everything after it assumes the work has already been accepted.

• Schedule time for lessons learned and retrospectives, don't leave them to the end. By the time a project actually finishes, people forget the details that made the lesson worth capturing.

• Decide what happens to every unresolved risk before the project ends. Don't let it just disappear with the team — either accept it, or hand it to whoever's taking over next.

The bigger point

Closing doesn't mean nothing's happening at the end of a project. It has its own defined process, with its own steps and outputs — just as deliberate as initiating or planning a project in the first place. It gets skipped not because it's optional, but because no deadline is pushing it forward the way one pushed everything before it.

The projects that close properly aren't the lucky ones. They're the ones where someone actually did the work, instead of leaving it half-finished because nobody was checking.

P.S. Know someone who wants to get better at project management? Share this with them.

And if you haven't already, subscribe to get practical project management insight in your inbox every Saturday: https://vandersonbaril.com/newsletter/

Thank you for reading, and see you next Saturday.

Most PMP candidates study risk management like it only has one direction: down.

You learn to spot threats. You learn to avoid, mitigate, transfer, or accept them. You build a mental model where "risk" means "something bad that might happen."

Then the exam hands you a scenario where the correct answer is to pursue the risk, not defend against it. And half the room freezes.

Table of Contents

• The misconception

• What PMBOK actually says

• Why this matters for the exam

• How to study this without wasting time

• The takeaway

The misconception

Here's the habit that costs candidates points: treating risk as a synonym for danger.

In predictive, agile, and hybrid project delivery alike, a risk is simply an uncertain event that could affect objectives — and that effect can be positive or negative. PMBOK is explicit about this. A risk isn't automatically bad news. It's unresolved information.

The habit runs deep because most day-to-day PM conversation defaults to threat language — "what could go wrong," "what's our exposure." Opportunity gets far less airtime in practice, so it gets far less airtime in preparation too. On exam day, when a question describes a scenario where things might go better than planned, the pattern-matching breaks down.

What PMBOK actually says

There are five strategies for threats and five for opportunities. Each one has a counterpart on the other side — which is the whole point.

For threats:

• Escalate — hand it to someone with the authority to own it

• Avoid — eliminate the cause entirely

• Transfer — shift ownership to a third party (often at a cost)

• Mitigate — reduce probability or impact

• Accept — acknowledge it and reserve time, cost, or resources if it happens

For opportunities:

• Escalate — same idea, upward, when it's above your authority

• Exploit — take deliberate action to make sure it happens

• Share — bring in a partner better positioned to capture the benefit

• Enhance — increase the probability or impact of the upside

• Accept — acknowledge it; either reserve time, cost, or resources to capture it if it happens (active), or take no action beyond periodic review (passive)

Five strategies, two directions. That's the whole model.

If you've only memorized the threat-side list, you're carrying half a framework into the exam room.

Why this matters for the exam

Situational questions rarely say the word "opportunity" outright. They describe a scenario — a vendor offering to finish early if given more resources, a technology upgrade that could cut both cost and duration — and expect you to recognize it as positive risk before choosing a response.

Pick a threat-strategy word for an opportunity scenario, and you've answered a different question than the one being asked. This is a recurring trap in ECO 2026-aligned questions: the scenario tests whether you can classify the risk correctly before you respond to it.

It also connects to something bigger than terminology. A project lead who only defends against downside and never acts on upside is missing half the job. Exam writers know this, and they write questions specifically to catch candidates who think defensively by default.

How to study this without wasting time

• When you review a threat strategy, pair it with its opportunity counterpart. Study them together, not as two separate lists.

• When you hit a practice question, pause and ask: is this event working for the project or against it? Classify before you respond.

• Build two or three real scenarios from your own work — one threat, one opportunity — and force yourself to name which of the five strategies fits. Recall built from your own experience survives exam pressure better than recall built from flashcards.

• If you're short on time, prioritize the paired strategies (mitigate/enhance, transfer/share, avoid/exploit) over memorizing definitions in isolation. Three pairs are easier to retain than ten separate terms.

The takeaway

Risk management on this exam isn't about pessimism. It's about accuracy. A project lead who reflexively treats every uncertain event as a threat isn't being cautious — they're missing information that could shorten a schedule, cut a cost, or improve an outcome.

Study both sides of the list. The exam will ask about both.

P.S. Planning your PMP study plan? The PMP Study Plan Calculator breaks it down by domain weights and available study time. Free and takes under a minute.

https://vandersonbaril.com/products/pmp-study-calculator/

Know a colleague sitting the PMP exam? Share this with them.

That's it for this week—thank you for reading, and see you next Saturday.

Ten years running projects. No PMP.

Now compare that person with a PMP holder who has half the experience.

Who’s the stronger project manager?

Most people answer based on the letters after the name.

The real answer is more useful than that — because experience and certification demonstrate different things.

Table of Contents

• What the experienced PM without PMP already has

• What that same PM may be missing

• The gap that's easy to miss: what happens after ce …

• The honest takeaway

What the experienced PM without PMP already has

A PM with ten years of real delivery experience has probably developed strong instincts:

• They can read a difficult stakeholder before the meeting even starts.

• They’ve made real trade-offs under real deadline pressure — not hypothetical ones.

• They’ve dealt with scope changes, difficult contractors, budget pressure and project failures.

• They’ve learned lessons that no exam can fully simulate.

That experience is real and valuable.

No certification can replicate it.

What that same PM may be missing

Here’s the gap that often matters: structure and professional language.

Experience teaches you what works. It doesn’t always teach you why it works, or give you a common framework for explaining it to others.

A PMP-certified PM may be able to describe the thinking behind a decision using recognised project management concepts:

• Is this a risk response?

• Is this a stakeholder engagement issue?

• Is this a governance decision?

• Is this a scope or change-control issue?

• Does this require escalation?

That vocabulary becomes useful when working with a PMO, reporting to senior leadership, negotiating with a sponsor, or moving into a larger organisation where people don't already know your track record.

Experience demonstrates what you’ve done. PMP provides a recognised framework and language for describing how you approach project delivery.

The gap that's easy to miss: what happens after certification

This is where many comparisons stop.

Passing the PMP isn't the finish line.

To maintain the certification, PMP holders must earn 60 PDUs every three years, covering three areas:

• Ways of Working — predictive, agile, hybrid and emerging approaches

• Power Skills — communication, leadership, collaboration, empathy and influence

• Business Acumen — understanding how projects connect to organisational strategy and business decisions

That ongoing requirement creates something an experienced but uncertified PM doesn't necessarily have:

external pressure to keep learning.

The uncertified PM can continue developing — and many do.

But there is no certification cycle requiring them to demonstrate ongoing professional development.

For the PMP holder, the clock keeps running.

And importantly, the learning isn't limited to project delivery methods. It also includes the people and business capabilities that become increasingly important as your responsibilities grow.

The honest takeaway

Experience without PMP can build excellent judgment and strong delivery instincts — but it doesn't automatically create a structured framework for continuing development.

PMP without substantial experience can provide vocabulary, structure and a common professional framework — but it still needs real-world experience to develop judgment.

The strongest project managers eventually have both.

Experience teaches you how to navigate reality.

PMP gives you a structured way to understand, communicate and continue developing that experience.

And the ongoing learning requirement isn't just a chore to tolerate.

It can be a useful mechanism for making sure ten years of experience doesn't quietly become ten years of doing things the same way.

That's the real value of combining experience + structured learning.

P.S. Not sure if you're eligible to sit the PMP yet? My free eligibility checker walks you through the requirements in under a minute → https://vandersonbaril.com/products/pmp-eligibility-checker/

If you know someone who’s considering the PMP or could benefit from this perspective, please share this with them.

That's it for this week — thank you for reading, and see you next Saturday.

You get promoted to project lead. Congratulations.

Nobody hands you a manual.

Most new project leads make the same mistake in month one. They keep doing the job that got them promoted — the technical work, the hands-on fixing, the “let me just do it myself” instinct. And they wonder why the team isn’t performing, why stakeholders are frustrated, why everything still runs through them.

Table of Contents

• The mistake: leading by doing

• Why this trips people up

• Where this shows up on exam day

• What to actually do about it

• The takeaway

The mistake: leading by doing

As an individual contributor, your value was measured by output. You solved the problem. You wrote the code, ran the analysis, built the drawing.

As a project lead, your value is measured by outcomes delivered through other people. That is a completely different game.

New leads often struggle here because nobody told them the rules changed. They keep solving problems the team should be solving. They keep making decisions the team should be making. It feels productive. It is actually a bottleneck — and it’s the fastest way to burn yourself out while your team quietly disengages.

The PMP exam blueprint puts this exact shift front and center. One of its core people-focused tasks is simply: lead the project team. Not “do the team’s work.” Lead it.

That task breaks down into things most new leads never think to do deliberately:

• Establish expectations at the team level

• Empower the team to own their piece of the work

• Solve problems with the team, not instead of them

• Represent the team’s voice upward

• Determine the leadership style the moment actually calls for

• Set clear roles and responsibilities so nobody is guessing

Notice what’s missing from that list. “Do the technical work yourself” isn’t on it.

Why this trips people up

Here’s the part that catches even experienced professionals off guard.

Technical competence built your credibility. Naturally, you assume more technical control equals more credibility. But the moment you’re leading a team, control and credibility start to pull in opposite directions.

The PMBOK Guide frames this as building an empowered culture — team members trust one another, adapt to change, and feel genuinely empowered because the leader recognizes their contributions instead of absorbing all the decisions. That’s not soft language. It’s a direct predictor of whether a team performs under pressure or collapses under it.

The other shift is authority versus accountability. As an IC, you were accountable for your own output. As a lead, you’re accountable for outcomes you don’t fully control — which means your job becomes creating the conditions for other people to succeed, not doing their job for them.

Where this shows up on exam day

This transition isn’t just a career theme. It’s tested constantly, and it’s tested through situational judgment, not definitions.

A typical scenario: a team member comes to you with a technical problem you personally know how to solve in ten minutes. The exam wants you to recognize that solving it yourself isn’t leadership — it’s a missed coaching moment. The stronger answer usually involves guiding the team member to the solution, or determining whether this is a one-off or a signal of a broader skills gap.

Another pattern: a team is underperforming and the “obvious” answer is tighter oversight. The better answer is usually diagnosing why — unclear roles, no shared expectations, no ground rules — before reaching for control.

If you’re studying and every “correct” answer feels like it favors coaching over commanding, that’s not a coincidence. That’s the exam mirroring what actually works.

What to actually do about it

For busy professionals studying while working full-time, this is good news — you don’t need new theory, you need to notice what you’re already doing on the job:

• Audit your week. How many hours did you spend doing versus enabling? Be honest.

• Delegate one decision you’d normally make yourself. Notice what happens.

• Write down team expectations explicitly, even if they feel obvious. Most conflict starts with an assumption that was never actually agreed on.

• Ask your team what they need from you, not what you think they need. The gap is usually bigger than expected.

Study the “Lead the project team” and “Build an Empowered Culture” concepts side by side. They reinforce the same shift from two different angles — one from the exam outline, one from the guide — and seeing both makes the pattern much easier to remember under pressure.

The takeaway

Getting promoted proves you were good at the old job. Succeeding in the new one requires letting go of most of what made you good at it.

The professionals who make this shift early — deliberately, not accidentally — are the ones who pass the exam and become genuinely effective leads. The ones who don’t tend to plateau, exhausted, wondering why doing more is producing less.

Leading isn’t doing more. It’s making sure the right things get done by the right people, for the right reasons.

P.S. Wondering if you qualify for the PMP? The rules are stricter than most people think. Check in under a minute → https://vandersonbaril.com/products/pmp-eligibility-checker/

Know a colleague who just stepped into a leadership role and is finding the transition harder than expected? Share this with them.

That’s it for this week—thank you for reading, and see you next Saturday.

Most PMP candidates think of a lessons learned register as a closing activity. Something you fill out at the end of a project, mostly for show.

That assumption alone can cost you points on exam day.

Table of Contents

• The common mistake

• Why this trips candidates up

• What this means for the exam

• The takeaway

The common mistake

Ask a room full of experienced project managers when a lessons learned register gets used, and most will say the same thing: at project closure.

It makes sense. In real life, "lessons learned" often does happen in a wrap-up meeting nobody wants to attend. A quick retro, a shared document, then everyone moves on.

But the exam isn't testing what happens in most offices. It's testing what the standard actually says. And the standard treats the lessons learned register as a living document, not a farewell letter.

Why this trips candidates up

According to the PMBOK 8th Edition, the lessons learned register is created early — as an output of the knowledge management activity near the start of a project. From that point, it gets used and updated more than once, at different moments across the project, not just at the end.

For example:

• Risk: when a risk plays out differently than expected, the risk register gets updated with the new status — but the insight behind it (what caused it, what worked) goes into the lessons learned register.

• Stakeholder engagement: if an engagement approach isn't working, the stakeholder register tracks the change in status — but what the team learned from it goes into the lessons learned register.

• Communications: if stakeholders need different information than planned, the communications plan may be adjusted — but the reason why, and what was learned, goes into the lessons learned register.

It isn't sitting untouched in a folder until the project ends. It's being read and added to continuously, by the people doing the work — captured in whatever form is efficient, including notes, photos, or recordings.

What this means for the exam

Questions built around the lessons learned register are really questions about mindset. They're checking whether you see project knowledge as something to capture and use immediately, or something to file away for later.

The exam rewards the first mindset. When a question makes you choose between capturing knowledge now or waiting to document it later, "now" almost always wins.

This same logic extends to other documents candidates tend to mentally park at closing — the issue log, the risk register, the stakeholder register. All of them get updated repeatedly across processes throughout the project, not just at the end.

The takeaway

The lessons learned register isn't a closing formality. It's a working document that shapes decisions while the project is still in motion.

Once you see it that way, a whole category of exam questions gets easier — because you stop looking for the "closing" answer and start looking for the "right now" answer.

That shift, more than any formula or acronym, is what separates candidates who pass from candidates who almost do.

P.S. If you're preparing for the PMP, connect with me on LinkedIn if you haven't already — I'd love to hear where you are in your study: https://www.linkedin.com/in/vandersonbaril/

I would also be interested to hear where you are in your own PMP journey. While I may not be able to respond to every message, I do read all replies.

Thanks for reading, and see you next Saturday.

Ask a stakeholder how the budget looks, and you'll get one of two questions back. Either "how much will this cost in total?" or "how much more do we need?"

Those are not the same question. And on the PMP exam, picking the wrong one costs you the point — even if your math is perfect.

Table of Contents

• Two different questions

• The abbreviations

• The four EAC formulas

• How they connect

• A realistic scenario

• How to prepare for this

• The takeaway

Two different questions

• EAC (Estimate at Completion) — total project cost, forecast to the end.

• ETC (Estimate to Complete) — cost of the work still remaining, from today forward.

Get the question wrong, and you'll answer with the wrong number even if every calculation along the way is correct.

The abbreviations

The formulas below use five variables. Keep these straight before anything else:

• PV — Planned Value. The budget authorized for the work planned to be completed to a point in time — usually the data date, meaning the specific day project performance is being measured.

• EV — Earned Value. The budgeted value of the work completed to the data date.

• AC — Actual Cost. What was actually spent on the work completed to the data date.

• BAC — Budget at Completion. The sum of all budgets for the work to be performed. This total is also known as the project's cost baseline.

• CPI — Cost Performance Index. EV / AC — how efficiently money is being spent.

The four EAC formulas

EAC isn't one formula. It's four, each tied to a different assumption about what happens next:

The exam signals which one applies through wording, not through a formula prompt. "CPI expected to stay the same" points to BAC/CPI. "No longer valid" points to bottom-up ETC. Miss the phrase, and you'll reach for the wrong equation.

How they connect

Once EAC is set, ETC follows directly:

ETC = EAC − AC

That's the standard relationship — assuming work continues as planned. But when the original baseline no longer holds, ETC gets re-estimated one task at a time instead. That's the same trigger that drives the third EAC formula above. The two aren't calculated independently — a bottom-up ETC feeds directly into EAC.

A realistic scenario

BAC is $500,000. At the midpoint, EV is $200,000, AC is $250,000. Cost performance is expected to continue at the current rate.

"Expected to continue" is the signal — use EAC = BAC / CPI.

CPI = EV / AC = 200,000 / 250,000 = 0.8 EAC = 500,000 / 0.8 = $625,000 ETC = EAC − AC = 625,000 − 250,000 = $375,000

Change the scenario to "the original estimate is no longer considered valid," and both numbers shift — EAC now comes from a bottom-up ETC instead. Same project, different assumption, different answer.

How to prepare for this

• Read the scenario for the assumption first — name the formula before touching a calculator

• Practice the relationship, not just the arithmetic: EAC first, ETC follows

The takeaway

EAC and ETC aren't two formulas to memorize. They're two questions a stakeholder is actually asking. Know which one is being asked, and the right formula — and the right number — follows on its own.

P.S. Planning your ECO 2026 study plan? The PMP Study Plan Calculator breaks it down by domain weights and available study time: https://vandersonbaril.com/products/pmp-study-calculator/

I would also be interested to hear where you are in your own PMP journey. While I may not be able to respond to every message, I do read all replies.

Thanks for reading, and see you next Saturday.

You can recite the five risk response strategies from memory. Avoid, transfer, mitigate, accept, escalate.

Then a situational question puts two of them in front of you as answer choices, both technically valid, and you freeze. That freeze isn't a knowledge gap. It's a judgment gap — and it's one of the most common reasons capable, experienced professionals lose marks they shouldn't.

Table of Contents

• The misconception

• What each strategy actually signals

• Where candidates go wrong

• How to actually study this

• The takeaway

The misconception

Most candidates study risk response strategies as a list of definitions. They can tell you what "mitigate" means. What they can't always do is tell you why mitigate is correct in one scenario and wrong in the next one that looks almost identical.

The exam isn't testing whether you know the five terms. It's testing whether you can read a scenario and identify which strategy the situation calls for — based on authority, cost, timing, and who owns the consequence if nothing is done.

What each strategy actually signals

Here's the distinction that matters — what each strategy is for, and what it looks like in practice:

• Avoid — best when the threat has a high probability and a large negative impact you can eliminate by changing the plan.

  Scenario: A key vendor has a history of missing deadlines, so you switch vendors before work begins — the threat no longer exists on this project.

• Transfer — best when a third party is better positioned to own the risk and absorb the impact if it happens.

  Scenario: Your project depends on expensive equipment on-site. If it's damaged, repair costs could blow the budget. Instead of absorbing that risk yourself, you purchase an insurance policy on it — so if damage happens, the insurance company pays, not your project.

• Mitigate — best when you can't eliminate the risk but can reduce how likely it is or how bad it would be.

  Scenario: A critical deliverable has a history of quality issues, so you add a second reviewer before release — the error can still happen, but it's far less likely to reach the customer.

• Accept — best when the risk is low-priority or not cost-effective to address any other way.

  Scenario: A minor supplier might be a few days late on a low-cost component, so you either set aside a small contingency reserve (active acceptance) or simply monitor it periodically without acting (passive acceptance).

• Escalate — best when the risk is outside your project's scope or requires authority you don't have.

  Scenario: A new regulation could affect multiple projects across the organization, so you raise it to the program level and stop tracking it yourself — it's no longer your risk to manage.

Read those again. Four of the five are things a project manager does within their own authority. One of them is the project manager recognizing they don't have the authority to act at all — and stepping back once it's handed off.

Where candidates go wrong

The exam's favourite trap works in two directions:

• Escalating when you should mitigate. The scenario gives you a risk that's uncomfortable, but it's still well within your budget authority and your team's control. Escalating it here reads as avoiding ownership — not good judgment.

• Mitigating when you should escalate. The scenario describes a risk tied to a regulatory change, an executive-level dependency, or a cost impact beyond your approved reserve. If you try to manage it yourself, you're answering a "should I act" question with "how do I act" logic. Wrong lens entirely.

Look at the question itself. Anything beyond your budget, your sign-off authority, or your project's boundaries points toward escalation — no matter how solvable it looks. And once escalated, let it go. The exam treats continued monitoring as a sign you never really handed it off.

How to actually study this

Definitions won't carry you through a scenario-heavy exam. Pattern recognition will.

• Stop memorizing the list. Instead, tag scenarios by signal:

  • Outside my authority, handed off for good → escalate

  • Shift the impact elsewhere → transfer

  • Reduce the odds or the damage → mitigate

  • Change the approach entirely → avoid

  • Do nothing (passive) or set aside a reserve (active) → accept

• When you practice questions, don't just check if you got the right answer. Check whether you identified the reason the correct strategy fit — authority, cost, timing, or ownership.

• Build five real scenarios from your own work history, one per strategy. If you've ever passed a decision up the chain because it wasn't yours to make, that's your escalate example. Use it. Real cases stick better than textbook ones.

The takeaway

The five risk response strategies aren't a vocabulary test. They're a test of whether you know where your authority ends and someone else's begins. Understand that boundary, and the correct strategy becomes obvious.

If you've been treating this section as flashcards, it's worth re-approaching it as judgment practice before exam day, not during it.

P.S. Planning your ECO 2026 study plan? The PMP Study Plan Calculator maps domain weights to your study time — free, under a minute: https://vandersonbaril.com/products/pmp-study-calculator/

Know a colleague sitting the PMP exam? Share this with them.

Thanks for reading, and see you next Saturday.

Most PMP candidates can define governance in one sentence. Almost none can tell you where the escalation line sits on their own project. That gap is exactly what this domain tests.

Table of Contents

• What governance actually covers

• Why candidates struggle here

• How this plays out on exam day

• How to prepare for it

• The takeaway

What governance actually covers

Governance is not a policy binder. On the PMP exam, it is a working structure — the rules, reporting lines, and decision authority that tell you who decides what, and at what point a decision stops being yours to make.

This sits inside Business Environment, the smallest of the three domains at 26% of the exam. Smallest does not mean skippable. It carries the tasks candidates most often treat as background reading instead of testable material — governance, compliance, and impediment management.

One task inside it is easy to gloss over: define and establish project governance. Buried in the enablers is a specific, testable skill — outlining escalation paths and thresholds.

Why candidates struggle here

Most study plans treat governance as structural trivia. Learn the org chart, know the sponsor's name, move on.

The exam does not test whether you know governance exists. It tests whether you know when to use it.

That's a judgment call, and judgment calls are where PMP candidates lose points. A schedule slips two days. A budget line runs 3% over. A stakeholder disagrees with a decision you already made. None of these is automatically an escalation. Each one might be, depending on the threshold your governance structure set at the start of the project.

Candidates without a clear threshold in mind default to one of two habits, both wrong:

• Escalate everything, and look like you can't manage without supervision.

• Escalate nothing, and look like you're hiding risk from the people who own it.

The correct habit is neither. It's knowing the threshold before the problem shows up.

How this plays out on exam day

Picture this scenario:

• A vendor delay pushes one deliverable back by a week.

• Your project charter defines schedule variances under two weeks as manageable at the project level.

• A stakeholder emails you directly, asking you to escalate to the steering committee immediately.

The weak answer: escalate right away, because a stakeholder asked and it feels safer to loop in leadership.

The exam-correct answer: check the variance against the defined threshold first. Since it falls within the project manager's authority, resolve it at that level, document the decision, and communicate the outcome to the stakeholder — rather than defaulting to escalation because someone asked.

This is the exact skill the ECO 2026 enabler describes: outlining escalation paths and thresholds before you need them, then applying them without emotion when a real situation shows up.

How to prepare for it

Governance questions are learnable, but not from memorizing definitions. Build the instinct instead:

• For every scenario you study, ask: what threshold would trigger escalation here, and who set it?

• Practice distinguishing a variance from an issue. Not everything off-plan needs a decision above your pay grade.

• Review the governance and change control tasks together. They're tested as a pair more often than candidates expect.

• When a practice question mentions a stakeholder demanding escalation, treat that as a prompt to check the threshold, not an instruction to comply.

The takeaway

Governance on the PMP exam isn't about knowing the structure exists. It's about knowing where your authority ends, and someone else's begins, before you're standing in the moment that tests it. Candidates who study this as a judgment skill, not a definition, walk into that scenario question already knowing the answer.

P.S. Not sure if you qualify for the PMP? Check the free PMP eligibility tool in under a minute: https://vandersonbaril.com/products/pmp-eligibility-checker

If this edition was useful, share it with a colleague who could benefit. It might save them months of second-guessing.

Thanks for reading.

See you next Saturday.

Most people manage stakeholders by instinct. Respond faster to the loud ones. Check in with the ones who ask questions. Assume the quiet ones don't need much.

There's a simple method that replaces that guesswork — and a lot of working professionals have never actually applied it, even after hearing the name.

Table of Contents

• How the method works

• Why it's worth applying, not just knowing

• One thing to watch once you start using it

• Why this shows up on the exam

• How to start using it this week

• The takeaway

How the method works

The idea is simple. You map every stakeholder against two questions:

• Power — how much influence do they have over the project's direction, funding, or approval?

• Interest — how much do they actually care about the outcome?

Plot each stakeholder on those two axes, and four groups emerge:

• High power, high interest → manage closely

• High power, low interest → keep satisfied

• Low power, high interest → keep informed

• Low power, low interest → monitor

The placement drives the effort. A stakeholder in "manage closely" gets regular direct engagement and a seat in key decisions. One in "monitor" gets minimal attention — checking in only if something changes. Get the placement right, and you spend your limited time on the people who can actually affect the project, instead of spreading effort evenly across everyone.

Why it's worth applying, not just knowing

Knowing the four boxes and using them are different things. The value isn't in being able to recite the model — it's in actually sitting down, listing your stakeholders, and placing each one deliberately. Most people skip that step. They keep the model in their head as a concept, then manage stakeholders on instinct anyway.

The moment you write it down, gaps show up. The stakeholder you've been checking in with weekly might actually belong in "keep satisfied," not "manage closely" — meaning you've been over-investing time somewhere it isn't needed. The one you've been ignoring might belong in "keep informed," and their silence isn't disinterest — it's a lack of updates.

One thing to watch once you start using it

Power and interest aren't fixed traits. They're conditions that change with circumstance. A stakeholder with low interest today can become your most vocal voice next month, the moment a decision touches their budget, their team, or their reputation.

So this isn't a one-time exercise once you build it. It's a working tool you check back against as the project moves.

Why this shows up on the exam

This is exactly the kind of concept that turns up in a PMP exam scenario. You'll get a situation describing a stakeholder whose circumstances have clearly shifted, and be asked what to do next. The correct answer usually isn't about the original classification — it's about recognizing that the classification has changed and adjusting the engagement approach accordingly.

If you've only memorized the four quadrants without ever practicing the placement exercise itself, that's the kind of question where instinct tends to default to the wrong answer.

How to start using it this week

• List every stakeholder on your current project — even the ones you've never formally logged

• Place each one honestly on the grid, based on where they sit right now, not where you assume they sit

• Compare that placement to how much time and attention you're actually giving each person

• Revisit the grid at your next phase transition or major decision point

The takeaway

This isn't a complicated model. It's a short exercise that most people know about and skip. The value isn't in understanding it — it's in actually doing it, and doing it again as the project changes.

P.S. Planning your ECO 2026 study plan? The PMP Study Plan Calculator breaks it down by domain weights and available study time. Free and takes under a minute:

https://vandersonbaril.com/products/pmp-study-calculator/

I would also be interested to hear where you are in your own PMP journey. While I may not be able to respond to every message, I do read all replies.

That's it for this week—thank you for reading, and see you next Saturday

You know the material. You've done the practice questions. You could explain earned value management to your cat.

Then you sit the real PMP exam, read a scenario, and every single answer sounds correct.

That's not bad luck. That's the exam working exactly as designed.

Table of Contents

• The mistake almost every candidate makes

• Why this trips people up

• What this means for the exam itself

• How to actually prepare for this

• The takeaway

The mistake almost every candidate makes

Most PMP preparation still treats the exam like a knowledge test. Memorize the ITTOs. Learn the formulas. Recall the definitions.

PMI has confirmed the PMP exam now includes case-or-scenario style questions, where candidates review a detailed situation — sometimes with charts or graphs — then answer a series of questions based on everything provided. Graphic-based and enhanced matching formats have been added, too. None of these reward pure recall. All of them test judgment.

If you're still studying by flashcards, you're preparing for question formats that the exam has moved past.

Why this trips people up

The pattern I see constantly with working professionals prepping for the PMP:

• They study each domain in isolation — stakeholder management on Monday, risk on Tuesday

• They memorize "textbook correct" responses instead of practicing trade-offs

• They assume the most proactive-sounding answer is always the safest bet

That last one is the killer. In real project delivery, over-communicating or escalating early often is smart. On the PMP exam, it can cost you a point — because the question isn't asking what's cautious. It's asking what's appropriate for that specific stakeholder, that specific constraint, that specific moment in the project lifecycle.

The exam isn't testing whether you know project management. It's testing whether you can apply it under ambiguity. That's precisely what the ECO 2026 redesign targets.

What this means for the exam itself

PMI's own domain weighting makes the intent clear. People account for 33% of the exam, Process for 41%, and Business Environment for 26%, and predictive approaches make up roughly 40% of items, with the remaining 60% split between agile/adaptive and hybrid approaches.

Waterfall (predictive), Scrum-based agile, and hybrid delivery all show up — often within the same scenario. You might read about a team running Scrum for development while managing procurement under a fixed-price contract, inside a predictive governance structure. The question isn't "which framework is this." It's "what do you do, given all of it."

That's the part most candidates underestimate: the exam expects you to blend frameworks, not identify one. PMBOK gives you the concepts. The ECO tests whether you can apply several of them at once, in a single messy situation.

How to actually prepare for this

You don't fix a judgment problem by memorizing more facts. Try this instead:

• Study in scenarios, not topics. For every concept you learn, write (or find) a short situational example and decide what you'd do — not what the textbook says.

• Practice eliminating, not just selecting. On situational questions, rule out the two answers that are technically true but wrong for that specific context. That's the real skill being tested.

• Read the stakeholder, not just the problem. Many scenarios hinge on whose expectations matter most right now — sponsor, team, or customer. Servant leadership only works if you can tell who needs support versus who needs a decision.

• Time-box your review sessions. Thirty focused minutes analyzing why an answer is wrong beats two hours re-reading the PMBOK Guide.

If you're working full-time, this approach is also more time-efficient. Isolated facts fade fast without repetition. Applied reasoning tends to stick.

The takeaway

The PMP exam stopped rewarding pure recall a while ago. ECO 2026 confirms it now rewards judgment — the ability to weigh a situation and choose the response that fits it, not just the response that's technically true.

Structure your prep around scenarios and trade-offs, and the exam stops feeling like a memory test. It starts feeling like the job you already do every day.

P.S. Planning your ECO 2026 study plan? The PMP Study Plan Calculator breaks it down by domain weights and available study time. Free and takes under a minute:
https://vandersonbaril.com/products/pmp-study-calculator/

Know a colleague sitting the PMP exam? Share this with them — it could save them a few wasted hours of study.

That's it for this week — thank you for reading, and see you next Saturday.

Work exploded. A project went sideways. Or you were just too tired to open another practice question after a ten-hour day.

Whatever happened, a week of your PMP study plan is gone. And now you're staring at a schedule that assumes you didn't lose it.

Here's the part nobody tells you: how you respond to that lost week matters more than the week itself.

Table of Contents

• The Mistake Almost Everyone Makes

• Why This Backfires

• What This Looks Like in Practice

• How to Recover Without Losing Ground

• The Real Takeaway

The Mistake Almost Everyone Makes

Most candidates try to make up the time.

They doubled next week's study hours. They cram two chapters into one sitting. They tell themselves they'll "catch up on the weekend" — then spend that weekend rushing through content they don't actually absorb.

This feels responsible. It isn't.

Treating a study plan like a debt you owe — hour for hour, topic for topic — assumes every hour of PMP preparation carries equal weight. It doesn't. And that assumption is exactly what gets busy professionals into trouble two weeks before exam day.

Why This Backfires

A PMP study plan built around a calendar treats missed time as a scheduling problem. But the PMP exam isn't testing whether you covered every page in order. It's testing whether you can apply judgment under pressure — the kind of situational thinking PMI builds into scenario-based questions across all three domains.

Cramming works against that. Rushed content produces surface-level recall: you recognise a term, but you can't reason through a scenario that uses it differently than your notes did. On an exam built around applied judgment rather than memorisation, that gap shows up fast.

There's a second problem, less obvious but just as costly: not all study time is created equal.

Under the current PMP ECO, the three domains carry different weights:

• Process — 41% of the exam

• People — 33% of the exam

• Business Environment — 26% of the exam

If your missed week was supposed to cover Business Environment topics, replaying that content at the expense of Process review is a bad trade — even though it "catches you up" on the calendar.

A missed week doesn't cost you equally across the exam. Treating it like it does is the real mistake.

What This Looks Like in Practice

Say your original plan had you studying stakeholder engagement and risk response strategies this past week — both Process and People domain material — and instead, nothing happened.

The instinct is to squeeze both topics into the next available study block, back-to-back, so the calendar looks intact again.

A better move: first check where you actually stand across all three domains. If your last practice set showed you're already solid on stakeholder engagement but shaky on risk response calculations, that tells you where the missed week actually needs to go — not the order it appeared in your original plan.

This is the same logic that applies to agile, predictive, and hybrid approaches. If your gap is in hybrid project delivery specifically, a generic "process review" won't close it. You have to know what you're actually missing before you decide how to spend the time you have left.

How to Recover Without Losing Ground

• Run a short diagnostic before you resume. A 20–30 question practice set across domains tells you exactly where you stand — not where the calendar thinks you should be.

• Reallocate by weight and weakness, not by chronology. Prioritise whichever combination of "high-weight domain" and "known gap" is worst. Skipping ahead in your plan is fine if it means studying the right thing.

• Cap your catch-up sessions. A focused 45-minute session beats a rushed three-hour one. If you're too fatigued to reason through a scenario question properly, you're building false confidence, not knowledge.

• Rebuild your plan around your real pace, not your original one. If you've missed time more than once, the plan itself may be unrealistic for someone working full-time. Adjust the total timeline before you adjust your evenings.

• Protect your practice-question habit above everything else. If you can only do one thing in a short recovery session, do situational questions. They rebuild exam-day thinking faster than passive review does.

The Real Takeaway

A missed week isn't a failure of discipline. It's a normal cost of preparing for a serious exam while working full-time.

What separates candidates who recover well from those who don't isn't willpower — it's whether their study plan was built to bend without breaking. A plan that only works if nothing goes wrong isn't a study plan. It's a best-case scenario.

Build in the assumption that some weeks won't go as planned, and you'll spend less time panicking and more time studying what actually moves the needle.

P.S. Planning your ECO 2026 study plan? The PMP Study Plan Calculator breaks it down by domain weights and available study time. Free and takes under a minute → https://vandersonbaril.com/products/pmp-study-calculator/

If this one helped, send it to a colleague who's studying for the PMP right now. It might save them from a few avoidable wrong answers.

That's it for this week — thank you for reading, and see you next Saturday.

Most project schedules don't fail because of bad luck. They fail because no one planned for what could go wrong.

Table of Contents

• The Pattern Is Always the Same

• What Risk Management Actually Means

• What the Best Project Managers Do Differently

• The Real Cost of Skipping It

• What to Do This Week

The Pattern Is Always the Same

No contingency. No backup plan. No early warning.

The project runs smoothly for the first few weeks. Then week 6 hits. A supplier delays. A key resource leaves the team. Scope changes without a formal process. And the whole schedule falls apart.

The team scrambles. Leadership asks questions. Deadlines are renegotiated.

That's not a project execution problem. That's a planning gap.

What Risk Management Actually Means

Risk management is not about predicting every problem. No one can do that.

It's about being ready when a problem hits — and problems always hit.

Risk management is an ongoing process. It starts before the project kicks off and runs until it closes.

Most teams treat it as a checkbox. They fill out a risk register in week one and never open it again.

That's not risk management. That's documentation.

What the Best Project Managers Do Differently

The project managers who consistently deliver on time do three things:

1. They identify risks upfront

Before the project starts, they map what could go wrong. Dependencies. Resource constraints. Supplier lead times. Scope ambiguity. They don't wait for problems to surface.

2. They plan responses

For each identified risk, they have a documented response. Not a vague idea — a clear plan. Who acts. What the alternative is. What it costs.

3. They build contingency

They allocate contingency time and budget from the start. Not added at the end when pressure mounts. Built in from day one.

These aren't advanced techniques. They're the fundamentals.

Most teams skip them because they feel like overhead when things are going well. They don't feel like overhead in week 6.

The Real Cost of Skipping It

A schedule with no contingency has no room to absorb a setback.

That means every problem becomes a crisis. Every delay hits the deadline directly. Every cost overrun comes straight out of your bottom line.

The time you save by skipping risk planning upfront is paid back — with interest — when the first problem lands.

If your schedule has no room to absorb a setback, it's not a plan. It's a wish.

What to Do This Week

If you're mid-project right now, open your risk register. If you don't have one, build one today.

For each active risk, confirm:

• Is it still relevant?

• Do you have a documented response plan?

• Do you have contingency allocated?

If the answer to any of these is no, fix it before week 6 arrives.

P.S. Not sure if you qualify for the PMP? Check the free PMP eligibility tool in under a minute: https://vandersonbaril.com/products/pmp-eligibility-checker

If this edition was useful, share it with a colleague who could benefit.

Thanks for reading.

See you next Saturday.

Most project managers treat the risk management plan as a formality — written once, filed away, never opened again. That is not risk management. That is paperwork.

The risk management plan is a living component of the project management plan. According to the PMBOK® Guide, 8th Edition, risk management activities are structured and performed across the entire project life cycle.

Here is what it actually contains — and when each part comes into play.

Table of Contents

• 1. Risk Strategy

• 2. Methodology

• 3. Roles and Responsibilities

• 4. Funding

• 5. Timing

• 6. Risk Categories

• 7. Stakeholder Risk Appetite and Thresholds

• 8. Probability and Impact Definitions

• The Point

1. Risk Strategy

The first thing to define is the general approach to managing risk on the project. Is the organisation conservative, moderate, or aggressive in how much uncertainty it will accept?

This sets the tone for every decision that follows.

2. Methodology

The methodology defines the specific approaches, tools, and data sources that will be used. This covers three areas:

• How risks will be identified — brainstorming, SWOT analysis, checklists, interviews, lessons learned

• How risks will be analysed — qualitatively (probability × impact) and quantitatively when the project requires it

• How risks will be responded to — for threats: avoid, transfer, mitigate, accept; for opportunities: exploit, share, enhance, accept

3. Roles and Responsibilities

The plan defines who leads, who supports, and who owns each risk management activity. Without this, risk ownership falls through the gaps.

At minimum: a risk lead, risk owners for individual risks, and a sponsor with authority to approve escalations above the defined threshold.

4. Funding

Risk management costs money. The plan establishes two types of reserve:

• Contingency reserve — covers identified risks. Held within the project budget.

• Management reserve — covers unknown risks (unknown-unknowns). Held above the project budget, released by authorised personnel only.

The plan also defines who can approve the use of each reserve and at what threshold.

5. Timing

This is where most plans fail. The PMBOK® Guide 8th Edition maps six risk processes across the project life cycle:

Risk management is not a planning-phase activity. It runs from conception to close.

6. Risk Categories

The plan organises risks into categories to ensure nothing is missed. The PMBOK® Guide 8th Edition uses a Risk Breakdown Structure (RBS) with four top-level categories:

• Technical — scope, requirements, technology, interfaces

• Management — resourcing, communication, organisational structure

• Commercial — contracts, suppliers, client stability

• External — legislation, weather, site conditions, regulatory

7. Stakeholder Risk Appetite and Thresholds

Risk appetite is the degree of uncertainty an organisation is willing to accept. The plan records each key stakeholder's appetite — expressed as measurable thresholds around project objectives.

For example: a cost threshold of ±5% of budget reflects low appetite — Medium and above risks require an active response. A threshold of ±20% reflects high risk appetite — only Very High risks escalate.

These thresholds drive how risks are scored and when they escalate.

8. Probability and Impact Definitions

The plan defines what probability and impact mean for this project — not in general terms, but specifically. Use a scale like this as a starting point:

Adjust the thresholds to match your project scale and the organisation's risk appetite. The structure stays the same.

The Point

Write it at project conception. Complete it before execution starts. Update it when the project changes. Use it every time you open the risk register.

The document does not manage risk. The discipline of using it does.

P.S. Not sure if you qualify for the PMP? Check the free PMP eligibility tool in under a minute: https://vandersonbaril.com/products/pmp-eligibility-checker

Found this useful? Share it with a colleague. A clear process saves more time than any tool.

Thanks for reading.

See you next Saturday!

This is one of the most common questions in project management:

Which certification should you choose — PMP or PRINCE2?

Both are globally recognised. Both are respected by employers. But they are built for different purposes, and that difference matters when deciding where to invest your time and effort.

Table of Contents

• What each certification is designed to do

• The key difference

• Which one is more valuable for your career?

  • PMP is often the better fit if you:

  • PRINCE2 is often the better fit if you:

• What the data suggests

• Final takeaway

What each certification is designed to do

PMP® (Project Management Professional) is issued by PMI and is a performance-based certification. It validates your ability to lead and direct projects across different environments, including predictive, agile, and hybrid delivery models. The focus is on the project professional's capability — how you apply knowledge and experience in real project situations.

PRINCE2® (Projects IN Controlled Environments) is issued by PeopleCert and is a structured project management framework. It defines a standardised approach to managing projects through principles, processes, roles, and governance controls. The focus is on providing a consistent method for structuring and controlling project delivery.

In simple terms:

• PMP focuses on the project manager’s capability.

• PRINCE2 focuses on the project management method.

The key difference

PMP and PRINCE2 are not competing versions of the same thing. They solve different problems.

Which one is more valuable for your career?

The right choice depends on your role, industry, and where you want to work.

PMP is often the better fit if you:

• Work in engineering, construction, manufacturing, IT, consulting, or large private-sector organisations

• Want a certification recognised across multiple industries and countries

• Are targeting roles in Asia-Pacific, North America, or multinational companies

• Want to demonstrate proven project leadership capability

PRINCE2 is often the better fit if you:

• Work in organisations that already mandate or prefer PRINCE2

• Are targeting UK, European, or government-sector roles

• Want a structured framework you can apply immediately

• Are early in your project management career and building foundational knowledge

What the data suggests

PMI’s research indicates that PMP-certified professionals report higher median salaries compared to non-certified peers across multiple countries.

PeopleCert does not publish equivalent salary comparisons for PRINCE2 certifications.

This does not make one better than the other. It simply reflects that PMP is a performance-based certification, while PRINCE2 is a methodology framework — and they are not directly comparable in financial terms.

Final takeaway

There is no universal “best” certification.

PMP is generally more versatile across industries and regions. PRINCE2 is highly effective in organisations that are built around its framework.

For some professionals, the right answer is not either/or — it is both.

The real question is not which certification is better.

It is the environment you want to operate in next.

P.S. Not sure if you qualify for the PMP? Check the free PMP eligibility tool in under a minute: https://vandersonbaril.com/products/pmp-eligibility-checker

If this edition was useful, share it with a colleague who is weighing up their next certification. It might save them months of second-guessing.

Thanks for reading.

See you next Saturday.

I walked into the PMP exam with 15 years of project delivery experience. I expected it to be straightforward.

It wasn't.

Here is what actually surprised me:

Table of Contents

1. Experience Doesn't Fully Prepare You for How Questions Are Framed

2. Agile Is Non-Negotiable

3. The "Right" Answer Often Feels Less Obvious

4. Situational Judgment Is Harder Than Knowledge Recall

5. Passing Changes How You Interpret Your Experience

6. Final Thought

1. Experience Doesn't Fully Prepare You for How Questions Are Framed

The exam doesn't ask what you would do. It asks what a project manager should do — based on a specific mindset.

Those aren't always the same.

Years of instinct-driven decisions don't automatically translate into PMP-style answers. The exam rewards a structured way of thinking, not just results.

2. Agile Is Non-Negotiable

A significant portion of the exam covers agile and hybrid approaches.

I had the foundation — but applying agile thinking to exam-style scenarios still required deliberate practice. Understanding a concept and applying it under exam conditions are two different skills.

3. The "Right" Answer Often Feels Less Obvious

In real projects, speed matters. In the PMP, multiple answers may seem correct — but you must choose the one aligned with the PMP mindset, even when your instinct suggests otherwise.

The exam tests whether you can slow down and think structurally, not just react efficiently.

4. Situational Judgment Is Harder Than Knowledge Recall

Knowing processes isn't enough. The exam puts you in scenarios where two answers look correct — and the difference comes down to how you think, not what you know.

5. Passing Changes How You Interpret Your Experience

Years of decisions suddenly align under a common framework.

It doesn't just validate experience — it clarifies it. I could look back at past projects and understand them differently: why some decisions worked, where the gaps were, and what I would approach differently today.

Final Thought

The PMP doesn't validate experience. It stresses how you think about it.

If you are preparing for the exam, focus less on memorising and more on understanding the reasoning behind each answer. That is what makes the difference.

P.S. Not sure if you qualify for the PMP? Check the free eligibility tool in under a minute: vandersonbaril.com/products/pmp-eligibility-checker

I'd also love to hear how you're handling structure on your current projects. While I may not be able to respond to every message, I do read all replies.

See you next Saturday.

Two project managers. Same organisation. Same workload.

One ends every week exhausted — inbox full, chasing updates, putting out fires. The other finishes Friday with a clear record of what moved, what is next, and what does not need their attention at all.

Same hours. Different results.

The difference is not effort. It is structured.

Table of Contents

• The Problem with Hustle Culture in Project Managem …

• What Structure Actually Means

• The Hustle PM vs The Structured PM

• Why This Is Hard to Change

• Bottom Line

The Problem with Hustle Culture in Project Management

There is a belief in many organisations that the best project manager is the busiest one. The one who responds fastest. The one who is always across every detail. The one who never seems to stop.

It sounds like dedication. But in practice, it often looks like this:

• Status updates collected manually every week

• The same stakeholder is asking the same question for the third time

• Decisions made from memory instead of a documented baseline

• A project that runs on one person — and slows down the moment that person is unavailable

That is not a high-performing project. That is a project held together by individual effort.

And individual effort is not a system. It is a risk.

What Structure Actually Means

Structure is not bureaucracy. It is not more meetings, more templates, or more documentation for its own sake.

Structure is the set of simple, repeatable habits that remove the need to make the same decision twice.

It looks like this:

Communication cadence → Stakeholders know when they will hear from you. They stop asking because the update is already scheduled.

A single source of truth → The project register, the schedule, the risk log. One place. Everyone knows where to look.

Decision records → When a call is made, it is written down. Who decided, what was decided, and why. No more "I thought we agreed to..." conversations.

A weekly review → 30 minutes, same time every week. Look at what moved, what is blocked, what needs a decision. Not reactive. Deliberate.

None of these is complicated. All of them require consistency.

The Hustle PM vs The Structured PM

Here is what this looks like in practice:

The structured PM is not less busy. They are busy on the right things.

Why This Is Hard to Change

Most project managers know they need better structure. The problem is that building a structure takes time you feel you do not have.

When you are already behind, slowing down to build a system feels like a luxury. So you keep running. And the pattern continues.

The way out is to start small and start with the thing that creates the most friction today.

If you are chasing the same status update every week — set up a standing request that goes out automatically.

If stakeholders keep asking where the project stands, create one shared document and stop answering the same question twice.

If decisions keep getting revisited, start keeping a one-line decision log in your next meeting.

One change. One week. That is enough to start.

Bottom Line

Effort matters. But effort inside a broken system just produces tired people.

If your weeks feel like controlled chaos, the answer is probably not more hours.

It is one clear communication cadence. One single source of truth. One decision record.

Structure is not the reward for getting on top of things. It is how you get on top of things.

P.S. Not sure if you qualify for the PMP yet? The PMP Eligibility Checker walks you through the requirements in under a minute. Free: vandersonbaril.com/products/pmp-eligibility-checker

I would also be interested in hearing how you are handling structure on your current projects. While I may not be able to respond to every message, I do read all replies.

Thank you for reading, and see you next Saturday.

You're not behind. Your study plan just wasn't built for your life.

There are two types of candidates who don't pass the PMP on the first attempt.

Neither of them lacked the ability to pass.

Table of Contents

• The first type studied hard, just in the wrong dir …

• The second type had a plan — then life happened

• Both problems have the same root cause

• What a plan built for your life actually looks lik …

• The professionals who pass on the first attempt ar …

The first type studied hard, just in the wrong direction

They put in the hours. Consistently. For months.

But their effort was spread evenly across everything — treating each domain like it carried equal weight, moving linearly through a study guide that wasn't calibrated to the actual exam.

Under ECO 2026, that pattern is expensive.

Business Environment is now 26% of the exam. People is 33%. Process is 41%. If your study time doesn't roughly reflect those numbers, you're preparing for the exam you assumed existed — not the one that does.

The fix isn't more effort. It's an aligned effort.

The second type had a plan — then life happened

This one is more common than anyone admits.

The first few weeks went well. Then a project escalated at work. A few sessions got skipped. Getting back into it started feeling harder each week — until the plan quietly became a source of guilt instead.

This isn't a discipline problem. It's a design problem.

PMP preparation runs three to six months. That's long enough for real life to disrupt even the most committed candidates. A plan that depends on conditions that don't consistently exist will eventually break down.

The candidates who survive that disruption aren't the most disciplined ones. They're the ones whose plan was built around the hours that actually exist in their week.

Both problems have the same root cause

The plan wasn't built for the person using it.

Generic study plans are written for an average candidate with an average schedule. They don't know you have two evenings and a Saturday morning to work with. They don't know that the Business Environment feels unfamiliar because your organisation doesn't frame it that way. They don't know that you consistently underperform on People domain scenarios, even though you lead teams every day.

A plan that doesn't account for those specifics will produce results that don't account for them either.

What a plan built for your life actually looks like

It starts with honesty.

Not the hours you intend to study. The ones that have reliably been available over the past few weeks. That's your real study budget.

From there:

• Allocate time by domain weight — 33% People, 41% Process, 26% Business Environment

• Let practice data tell you where to focus — weak areas get more time, not less

• Keep sessions high-signal — scenario-based questions over passive reading

• Build a re-entry mechanism — a way back into the plan after a disrupted week without starting from scratch

Disrupted weeks will happen. The plan that survives them is the one that gets you prepared for the exam.

The professionals who pass on the first attempt aren't different from you

They didn't have more time. They didn't find a resource you haven't found.

They built a plan that was honest about their schedule, aligned to the exam's actual structure, and resilient enough to survive real life.

That plan is available to anyone who deliberately builds it.

The only question is whether you build it now — or wish you had

P.S. Planning your ECO 2026 study plan? The PMP Study Plan Calculator builds a domain-weighted schedule from your available hours. Free and takes under a minute:
https://vandersonbaril.com/products/pmp-study-calculator/

I would also be interested to hear where you are in your own PMP journey. While I may not be able to respond to every message, I do read all replies.

That's it for this week — thank you for reading, and see you next Saturday.

Most PMP candidates prepare for the exam from their comfort zone.

If they come from software or digital delivery, they lean heavily into agile and Scrum.

If they work in engineering, construction, manufacturing, or infrastructure, they naturally default to predictive project management.

And that becomes a problem.

Because the PMP exam doesn’t reward loyalty to a methodology.

It rewards judgment.

That’s one of the biggest mindset shifts in PMP ECO 2026.

Table of Contents

• The mistake that quietly costs candidates marks

• Predictive project management is not “outdated”

• What the PMP actually tests in Agile

• Hybrid project management is now central to PMP EC …

• How to study smarter for PMP ECO 2026

• Final thought

The mistake that quietly costs candidates marks

The project management industry has spent years talking about agile transformation, Scrum frameworks, Kanban boards, SAFe, sprint planning, and iterative delivery.

So many candidates assume:

“PMP is basically an agile certification now.”

It isn’t.

The PMP certification still tests:

• Predictive approaches
• Agile approaches
• Hybrid approaches

— all with equal weight.

That’s what makes PMP difficult.

Not memorisation.

Recognising which approach best fits the scenario.

Predictive project management is not “outdated”

Predictive delivery (traditional waterfall) remains dominant in industries like:

• Construction and infrastructure
• Manufacturing and engineering
• Government and defence
• Healthcare and pharmaceuticals
• Energy and utilities

You don’t iteratively build a bridge halfway and “pivot later.”

You need:

• Defined scope
• Procurement planning
• Cost baselines
• Schedule control
• Formal change management
• Regulatory compliance

And PMP still tests all of it heavily.

Candidates who ignore predictive concepts because “everything is agile now” usually discover that mistake during the exam.

What the PMP actually tests in Agile

The PMP exam does not test whether you memorised Scrum terminology.

It tests whether you understand agile decision-making in real project environments.

That includes:

• Servant leadership
• Self-organising teams
• Backlog prioritisation
• Stakeholder collaboration
• Responding to changing requirements
• Sprint planning and retrospectives
• Incremental delivery under uncertainty

The tricky part?

Many agile-native candidates become overconfident and skip practising realistic scenarios.

That’s where PMI-style answers often differ from real-world habits.

Hybrid project management is now central to PMP ECO 2026

This is the part that many study plans still underestimate.

Hybrid delivery is no longer a side topic.

It is embedded throughout PMP ECO 2026.

Most modern projects now combine:

• Predictive governance
• Agile execution
• Fixed milestones
• Iterative delivery
• Structured reporting
• Flexible development cycles

That’s how real organisations operate in 2026.

And that’s exactly how the PMP exam is designed.

Under ECO 2026:

• People — 33%
• Process — 41%
• Business Environment — 26%

…all contain hybrid decision-making elements.

Hybrid questions are often the hardest because there’s no obvious framework pattern to follow.

You must interpret the situation.

How to study smarter for PMP ECO 2026

A few things consistently help candidates improve faster:

• Study by ECO domains, not just methodology
• Practice mixed-scenario PMP questions
• Track weak areas by delivery approach
• Revisit high-difficulty questions repeatedly
• Learn WHY an answer is correct, not just what is correct

The candidates who perform best are usually the ones who stop asking:

“Is this agile or predictive?”

…and start asking:

“What problem is this project trying to solve?”

That’s the PMP mindset.

Final thought

Agile is not the answer.

Predictive is not the answer.

Hybrid is not the answer.

The situation determines the answer.

That’s the entire philosophy behind the PMP exam.

And the earlier candidates understand that, the better their preparation becomes.

P.S. Preparing for PMP ECO 2026? The PMP Study Plan Calculator for Busy Professionals helps you turn your exam timeline into a clear, structured study plan in under a minute.

👉 https://vandersonbaril.com/products/pmp-study-calculator/

I’d also be interested to hear where you are in your PMP journey — studying, scheduling the exam, or already certified.

I read every reply, even if I can’t respond to all of them.

See you next Saturday.

Studying for the PMP without knowing your weak areas is guesswork.

A lot of candidates start with a study guide, go chapter by chapter, and assume that covering everything means they’re ready. Sometimes that works. A lot of the time it doesn’t — and they only find out when they sit the exam.

The issue usually isn’t effort. It’s studying the wrong things for too long.

Table of Contents

• Reading alone won’t get you there

• Start practice questions earlier

• ECO 2026 makes this even more important

• What to do once you find the gaps

• Readiness isn’t based on confidence

Reading alone won’t get you there

The PMP is not really testing how much you can memorise. It’s testing judgment.

You can read an entire section on stakeholder engagement and still get stakeholder questions wrong because the exam is asking you to apply PMI’s way of thinking in a situation, not repeat definitions back.

That’s why practice questions matter so much. They expose the gap between “I’ve seen this topic before” and “I can consistently answer questions on it correctly.”

Start practice questions earlier

One mistake candidates make is waiting until they “feel ready” before attempting practice exams.

In most cases, you should start earlier.

Not because you’ll score well immediately, but because practice questions show you where the problems are:

• which domains feel weak,

• which question types keep catching you out,

• and where your instincts don’t align with PMI’s expected answer.

That’s useful information. It tells you what actually needs attention instead of spending another week reviewing material you already know reasonably well.

ECO 2026 makes this even more important

Under ECO 2026, which takes effect for the PMP exam on 9 July 2026, Business Environment increases from 8% to 26% of the exam.

That’s a major shift.

The domain covers things like governance, strategic alignment, compliance, and value delivery. Most experienced project professionals work around these areas already, but that doesn’t automatically translate into answering PMP scenario questions correctly.

A lot of candidates are probably underestimating how much preparation this domain will require.

What to do once you find the gaps

Once practice identifies a weak area, go back to the related ECO tasks and focus on understanding PMI’s reasoning.

Then do more scenario-based questions specifically tied to that area.

Repeat the cycle:

• practice,

• identify gaps,

• targeted review,

• practice again.

It’s slower than simply reading through a study guide from start to finish, but usually far more effective.

Readiness isn’t based on confidence

A common trap is assuming you’re ready because the material feels familiar.

Familiarity is not the same thing as performance.

The candidates who are genuinely prepared are usually the ones tracking weak areas honestly and working on them until their results consistently improve.

P.S. Curious whether you’re eligible to apply? The PMP Eligibility Checker walks you through the requirements in under a minute — no spreadsheet needed.

https://vandersonbaril.com/products/pmp-eligibility-checker/

I’d also be interested to hear where you are in your PMP journey. I may not be able to reply to every message, but I do read them all.

That’s it for this week — thanks for reading, and see you next Saturday.

The PMP Exam Content Outline (ECO) will be updated on 9 July 2026. While the structure remains based on three domains, the weighting of those domains is changing in a way that will affect how candidates should prepare.

Table of Contents

• What the ECO is

• What Is Changing

• What this shift means

• Important clarification on exam structure

• What this means for exam preparation

• Final takeaway

What the ECO is

The ECO is the official blueprint used by PMI to design the PMP exam. Every question is mapped to defined domains and tasks within this framework.

The exam continues to be structured around three domains:

• People

• Process

• Business Environment

What Is Changing

The domain structure remains the same, but the weighting shifts as follows:

Current ECO

• People — 42%

• Process — 50%

• Business Environment — 8%

ECO effective 9 July 2026

• People — 33%

• Process — 41%

• Business Environment — 26%

The most significant change is the increased emphasis on Business Environment.

What this shift means

The Business Environment domain moves from a relatively small component of the exam to approximately a quarter of the overall content.

This reflects a stronger focus on:

• Alignment between projects and organisational strategy

• Value delivery and benefits realisation

• Understanding external business and environmental factors

• Governance and decision-making at a business level

Rather than focusing purely on execution, candidates are expected to demonstrate awareness of how projects contribute to broader organisational outcomes.

Important clarification on exam structure

PMI does not publish exact question counts per domain. While the exam contains 180 questions, the distribution across domains is based on weighted sampling rather than fixed question numbers.

For example, Business Environment represents 26% of the exam, which is approximately one quarter of the total content, but exact question counts may vary.

What this means for exam preparation

Three practical considerations:

1. Rebalance study focus
Candidates should ensure sufficient coverage of Business Environment, as its weight has increased significantly compared to the current version.

2. Maintain balance across all domains
People and Process remain the majority of the exam and continue to carry substantial weight.

3. Use updated ECO-aligned materials
Study resources should reflect the 2026 ECO structure rather than older exam distributions.

Final takeaway

The PMP exam is not becoming harder—it is becoming more strategically focused.

Candidates who adjust their preparation to reflect the updated domain weights will be better aligned with the exam structure from July 2026 onward.

P.S. Planning your ECO 2026 study plan? The PMP Study Plan Calculator breaks it down by domain weights and available study time. Free and takes under a minute.

I would also be interested to hear where you are in your own PMP journey. While I may not be able to respond to every message, I do read all replies.

That’s it for this week—thank you for reading, and see you next Saturday.