Why Telling the Team What to Do Is Often the Wrong PMP Answer

A team brings you a problem you already know how to solve. You have solved it before, probably twice, and the whole exchange could be over in forty seconds. Answering feels like leadership rather than avoidance, particularly late in the week when three other things are waiting.

Anyone preparing for the PMP exam notices something different, though. Options that begin with the project manager telling the team what to do seldom look like the intended response, and a good deal of preparation material reinforces the impression that facilitating, coaching or asking the team is the safer choice in almost any situation. That impression is useful for about a fortnight. Then a candidate meets a scenario where the team is stuck, the deadline is real and gathering everyone for a workshop would be faintly absurd, and the rule offers nothing, because it was memorised without its reason.

The reason is worth having. It is also more useful on a live project than it is in a question bank.

Where the facilitation habit comes from

Part of the pattern is simply where the exam's attention sits. People accounts for 33 per cent of the questions on the current exam, and within that domain the task covering leading the project team lists both empowering the team and determining an appropriate leadership style among its enablers. That second phrase is easy to read past. The enabler describes selecting a style to suit the situation, not adopting one style and applying it everywhere.

The rest of the pattern comes from the situations these scenarios tend to describe. A team is quietly missing a step. Two specialists disagree about sequencing. A supplier's estimate does not match what the team believes. In most of those cases the project manager does not actually possess the information needed to give a good instruction, and the scenario is written that way because that is what the work usually looks like. Preparation convention then compresses this into "never direct", which is a summary of common cases masquerading as a principle.

Directing spends information you have not collected

Here is the practical version, and it has nothing to do with being nice.

The question a team brings you is almost never the whole situation. It is the part of the situation they have already made sense of, framed in a way that invites a decision. Behind it sits everything they did not mention because they assumed you knew, or assumed it was irrelevant, or have not yet articulated to themselves. The moment you supply an answer, the conversation ends and all of that stays where it is. You have bought forty seconds and lost the constraint that was actually causing the problem.

There is a second cost, slower and more expensive. Teams learn where decisions come from. If the reliable route to a decision is the project manager, people stop forming views and start queuing, and the queue lengthens exactly when the project gets busy enough that you can least afford it. This is what Section 3.8 of The Standard for Project Management is pointing at when it describes building an empowered culture: people contributing, deciding and learning within clear boundaries. Note the boundaries. Empowerment in that sense is not the absence of leadership or governance, and it is not a licence for the project manager to stand back and call it coaching. It is the deliberate placement of decisions where the information already is.

Facilitation, understood this way, is a diagnostic act. You ask because you do not yet know, and because the people in front of you probably do.

When direction is the right response

Several situations invert this, and recognising them quickly is more valuable than any rule about preferred styles.

Direct when the constraint is authority rather than understanding. If the decision exceeds what the team can legitimately commit to, involving a supplier contract, a change to an agreed baseline, a compliance position or another department's resources, then facilitating a discussion about it is not empowerment. It is asking people to spend effort on a decision that will have to be made somewhere else anyway. Take it, or escalate it, and tell them which.

Direct when safety, legal obligation or a regulatory requirement is in play. There is no consultative version of a control that is not optional.

Direct when the cost of the conversation genuinely exceeds the cost of a slightly imperfect decision. Some situations are urgent in a way that makes deliberation the wrong tool. This is a narrower category than it feels like at four o'clock on a Friday, and it is worth being honest with yourself about which of your urgent situations are actually urgent.

Direct when the team is missing information they have no way of obtaining. A new joiner asking how to raise a change request needs an answer, not a coaching question. Asking someone to discover something they cannot discover is a small unkindness dressed as development.

And direct when facilitation has already been tried and the group is deadlocked. Repeatedly returning a decision to a team that has told you it cannot resolve it stops looking like trust and starts looking like avoidance. If you want to work through this kind of judgement with other experienced practitioners rather than against a list of preferred answers, the PMP® Exam Preparation course builds the same habit across the wider syllabus.

Worth saying plainly: directing is not rudeness, and it does not require you to withhold your reasoning. Most of the damage attributed to directive leadership comes from unexplained decisions rather than from decisiveness itself.

Three weeks before cutover, the wrong question

A payments migration is approaching cutover. The agreed process requires the test team to triage defects daily and report severity through the delivery tooling, and for two weeks the reports have arrived late and in a different format. The project manager knows what the process says. Instructing the team to follow it would take one message.

She asks instead, and the answer takes four minutes. The new test tool does not expose the field the triage classification depends on, so the team has been triaging in a spreadsheet and transcribing afterwards, which is why the reports are late and why the format keeps drifting. Nobody raised it because they assumed it was a known limitation of a tool that had been chosen above their level.

The instruction would have produced compliance for perhaps three days, followed by the same drift and a team slightly less willing to explain why. Understanding the constraint produces two decisions instead. The tooling gap becomes a change with an owner and a date. Separately, and this is the part worth noticing, she does direct: the transcribed reports must reach the delivery tooling by the Thursday cut-off until the field is available, because the steering group's cutover decision depends on that data being in one place. She explains why. The team was never resisting the process. They were working around a constraint nobody had asked about.

What this leaves you with

The useful question is not whether to facilitate or direct. It is what kind of constraint you are actually looking at. If the constraint is understanding, a decision from you will be worse than a decision from the people closer to the work, and it will cost you the diagnosis as well. If the constraint is authority, the decision is yours or your sponsor's, and handing it back is an evasion. If the constraint is time, you weigh the value of the conversation against what a wrong answer costs, and you accept that you are trading one for the other.

For a PMP candidate, that is a more durable way to read a scenario than scanning for the option that sounds most collaborative. On a real project it is also the difference between a team that brings you problems early and one that has learned to wait for instructions.

Andre Malowney

Interested in going further?

Reading the constraint correctly under time pressure is a skill that develops through worked situations and discussion rather than through memorised preferences, particularly for practitioners moving between predictive, adaptive and hybrid delivery where the boundaries of team authority differ. Our instructor-led programme spends its time on exactly that kind of judgement.

The Standard's treatment of an empowered culture is short, and reading it directly is a good corrective to the second-hand version that circulates in exam preparation.

Ad · Amazon affiliate link.

References

A041: Empowered Teams Still Need Leadership
A198: When Collaboration Is Better Than Authority in PMP Scenarios
A146: Team Agreements: Small Document, Large Effect
A039: Servant Leadership in PMP: When It Fits and When It Doesn’t
A024: Facilitation as a Core Project Management Skill

PMP and PMBOK are registered marks of the Project Management Institute, Inc.