When Collaboration Is Better Than Authority in PMP Scenarios

Work through enough practice questions and a pattern starts to appear. Options that involve talking to the team, understanding the situation or bringing the right people together tend to survive. Options that involve deciding on the spot and telling people what will now happen tend not to. Most candidates compress that observation into a rule: when in doubt, collaborate.

It is an understandable summary of what candidates see, and a poor description of what is being examined. It also travels badly onto a real project. A project manager who consults on everything becomes a bottleneck rather than a leader, and some decisions were never the team's to make in the first place.

The more useful question is what collaboration is actually doing in those situations. Once that is clear, the cases where authority is the better instrument stop looking like exceptions to a rule and start looking like a different problem requiring a different tool.

Collaboration, consultation and consensus are three different moves

Much of the confusion comes from treating one word as though it covered three behaviours.

Collaboration means working on a problem jointly with the people who hold parts of it, and arriving at something none of them held at the start. Consultation means gathering views and then deciding yourself; it is often the right move and is frequently mislabelled as collaboration. Consensus means requiring agreement before anything proceeds, which is the most expensive of the three and the least often necessary.

Candidates who read every collaborative-sounding option as the same thing lose the ability to choose between them, and so do project managers. Announcing a consultation and then delivering a decision the team believes they co-authored is worse than either move made honestly. So is convening a group to reach agreement on something that a single accountable person could have settled in ten minutes.

None of the three transfers accountability. Involving the team in a decision does not make the outcome theirs to answer for. This is close to what Section 3.8 of The Standard for Project Management describes in dealing with an empowered culture: people contribute, decide and learn within boundaries that somebody has taken responsibility for setting. Empowerment there is not the removal of leadership. A team handed a decision without the information, the mandate or the boundary it needs has not been empowered, it has been abandoned.

What makes collaboration the stronger instrument

Two gaps, either of which authority is badly suited to closing.

The first is an information gap. The facts needed to decide well sit in more than one head, and no single person in the situation holds the whole picture. Authority is efficient at converting a decision into an instruction. It is not a method for producing information you do not have, and a confident instruction built on a partial picture is simply a faster route to the wrong outcome. Collaboration in these situations is not a gentler way of issuing an instruction. It is a decision to take the problem to where the information already sits, rather than requiring the information to travel to you.

The second is a commitment gap. People can comply with an instruction without committing to it, and on most projects the difference shows up in the discretionary effort: whether someone raises a problem early or waits to be asked, whether they work around an awkward step or flag it. Where delivery depends on that kind of effort, a decision people helped construct outperforms a decision they received, even when the two decisions are identical in content.

Reversibility and time sit underneath both. Where a decision can be revisited cheaply and there is room in the schedule, the cost of involving people is low and the return is usually positive. Where neither is true, the arithmetic changes, and it changes in favour of someone taking the decision and owning it.

When authority is the right instrument

Some boundaries are not open for discussion, and treating them as though they were is a failure of leadership rather than an expression of it.

Safety rules, legal and regulatory obligations, contractual terms and ethical duties are the clearest cases. So are thresholds and baselines that have already been agreed through a governance route, because the point of agreeing them in advance was to remove the need to negotiate them under pressure. Individual performance and conduct matters belong here too, since they cannot be handled in a group without treating one person unfairly. And genuine deadlock, after a real attempt at resolution, eventually needs someone to decide rather than to reconvene.

There is a quieter case that catches experienced project managers as often as candidates. Consulting on something that has already been settled, or that cannot change whatever the team concludes, damages trust faster than deciding openly ever does. People notice, and they stop investing in the next conversation.

The 2026 PMP® Examination Content Outline puts the People domain at 33 per cent of exam items, and among the enablers listed under leading the project team is determining an appropriate leadership style. The word carrying the weight there is appropriate. A single default style, collaborative or otherwise, is not a selection. The same outline notes that roughly 40 per cent of items represent predictive approaches, with the remaining 60 per cent divided between adaptive/agile and hybrid. That distribution helps explain why team-level decision making appears so often in the situations described, though it is a statement about the environments the exam samples rather than about a preferred answer.

A cutover that needed both

A finance system migration is two days from its cutover weekend. The infrastructure lead raises that the agreed sequence will leave month-end reporting unavailable for around four hours longer than the business was told, because a dependency was mapped against the old reporting stack.

The project manager could reorder the steps himself. He has the sequence, he understands the dependency, and he could circulate a revised plan within the hour. He does not, because three people hold different parts of the answer. The infrastructure lead knows what can be moved. The application lead knows what breaks if it is. The service owner knows which four hours the business can actually absorb. Forty minutes in one room produces a sequence none of them would have written alone, and the two leads leave having agreed to something they helped construct.

At 02:40 on the Sunday, a verification step fails twice and the rollback threshold agreed during planning is crossed. Nobody convenes anything. The project manager calls the rollback, tells both teams, and informs the service owner afterwards. The threshold existed precisely so that this decision would not be renegotiated at three in the morning by tired people with partial information.

Same project, same week, two decisions, two instruments. Neither one is a softer or harder version of the other.

The question underneath both is not whether to collaborate. It is what is missing. If what is missing is information or commitment, collaboration is the instrument. If nothing is missing, and what remains is a boundary somebody has to hold, then collaboration is delay dressed as inclusion. This is the kind of distinction we work through case by case during PMP® Exam Preparation, because the cue that separates the two is rarely stated openly in the situation itself.

Under exam conditions the check is quicker than it sounds. Read the situation for what the project manager does not yet know, and for who will have to carry the outcome. Where the scenario has deliberately withheld something, or where the people affected could quietly fail to deliver, the collaborative option is usually doing real work. Where the scenario has already handed you the constraint, in the form of a signed contract, a safety requirement, an agreed threshold or a regulatory deadline, the collaborative option tends to consume time the situation does not have.

The delivery approach shifts the picture less than candidates expect. In predictive environments decision rights are more visibly located in defined roles, change control and approval thresholds, which makes the boundary easier to point at. In adaptive environments more decisions sit with the team by design, within limits somebody has still set. Hybrid delivery asks the harder question of the three, which is which decisions sit where on this particular project. The underlying test does not change.

On live projects the cost of the wrong instrument is asymmetric, and that is worth knowing. Deciding alone when you should have involved people is loud and obvious: someone objects, something is missed, the mistake surfaces quickly. Over-collaborating is quiet and cumulative. Decisions arrive late, accountability spreads until nobody quite holds it, and capable people spend their afternoons co-owning matters they cannot influence. The habit worth building is not a preference for either mode. It is the short check on what is genuinely missing, made before you choose how to proceed.

Andre Malowney

Interested in going further?

Choosing between collaboration and authority improves with exposure to many situations rather than with a single rule, and it is difficult to build from practice questions alone. The PMP® Exam Preparation course works through People-domain situations in a taught setting, where the reasoning behind each choice can be tested and challenged rather than memorised.

The thinking on empowered culture that sits behind this distinction is set out in The Standard for Project Management, published with the PMBOK® Guide Eighth Edition.

Ad · Amazon affiliate link.

References

A042: Why Telling the Team What to Do Is Often the Wrong PMP Answer
A041: Empowered Teams Still Need Leadership
A146: Team Agreements: Small Document, Large Effect
A007: The Standard for Project Management vs the PMBOK Guide
A044: Analyse Before You Act: A Better Way to Read PMP Scenarios

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