The Four Difficult Stakeholder Archetypes

After enough years of this work, almost every difficult stakeholder starts to look like a variation on one of four patterns, and the mistake most BAs make is running the same script against all of them. Diagnosing which one you are dealing with, using the Iceberg framework from yesterday, changes everything about how you approach the conversation. Here are the four, what actually drives each one, and the specific opening move that works.

The Blocker

The Blocker says no to almost everything, often before they have finished reading the proposal. Underneath, this is rarely about the specific ask. It is about control, or safety, or a past experience where saying yes cost them something. The Blocker has usually been burned before by a change that was sold as simple and turned out not to be.

The instinct is to bring a stronger case. That rarely works, because the Blocker is not evaluating your case on its merits. They are evaluating whether saying yes is safe. The move that actually works is making the yes smaller and more reversible.

This does not require them to trust the whole plan. It only requires them to trust a small, safe, reversible version of it, which is a much easier yes to give, and it usually earns you the data you need to make the bigger case later.

The Ghost

The Ghost agrees enthusiastically in every meeting and then goes silent the moment a decision actually needs to be made. Emails go unanswered. Sign-offs sit in an inbox for weeks. Underneath, the Ghost is usually avoiding a conflict they do not want to own, often because saying no out loud feels riskier to them than simply not responding.

Chasing a Ghost harder rarely works, because more messages just give them more to ignore. What works is removing the option to stay silent by building a visible default into the process.

This is not a threat, it is a default. Ghosts often respond to a deadline with a visible consequence far better than they respond to an open-ended request, because silence is no longer a way to avoid the decision. It just makes the decision for them.

The Scope-Creeper

The Scope-Creeper adds one more small thing almost every week, each addition reasonable on its own, the accumulated total quietly doubling the original scope by the time anyone notices. Underneath, this is rarely bad faith. It is usually that nobody ever drew a visible line the Scope-Creeper could see themselves crossing.

Refusing each request individually creates friction without solving the pattern. What works is making the line visible once, in writing, so every future request is measured against something concrete rather than against your patience.

This reframes the conversation from you being difficult to the scope document doing the work of being difficult for you. It is far easier for a Scope-Creeper to negotiate against a visible line than against your personal resistance.

The Escalator

The Escalator skips you and goes straight to your manager or theirs the moment something does not go their way. This one stings the most, because it can feel like a personal vote of no confidence. Underneath, the Escalator usually does not trust the process to produce an outcome without applying pressure, often because escalation has worked for them before.

Getting defensive after the fact rarely repairs anything. What works is addressing it directly, once, calmly, and offering a version of the process they can actually trust going forward.

This is not a scolding, and it should not read as one. It is a direct, unemotional invitation back into a process, which is usually more effective than either ignoring the escalation or matching it with one of your own.

One person, more than one archetype

A useful caution: the same stakeholder can be a Blocker on one topic and a Ghost on another, depending on what they are protecting in each situation. The archetype is not a permanent label for the person. It is a diagnosis for this particular conflict, and it can change the next time you sit down with them.

It is also common for a stakeholder to start as one archetype and become another once the first issue is resolved. A Blocker who finally agrees to the small, reversible pilot from the script above often becomes a Scope-Creeper three weeks later, once the pilot succeeds and they start asking for just one more thing to be added before the wider rollout. This is not inconsistency on their part, it is simply a new interest surfacing once the old fear has been addressed. Re-run the diagnosis rather than assuming yesterday's label still applies.

The biggest mistake to make

Across all four patterns, one mistake compounds every one of them: discussing the archetype, even informally, with other people on the project. Calling someone a Blocker or a Ghost in a side conversation, even sympathetically, tends to leak, and once a stakeholder senses they have been categorised rather than heard, every one of the scripts above becomes far less effective, because they are now responding to being labelled rather than to the actual proposal. Use these patterns privately, as your own diagnostic tool, and keep the conversation with the stakeholder itself entirely about the specific situation in front of you.

Go out and be successful.

Oluwatosin Ogunkoya | Flotog BA Insights  |  www.flotogbainsights.com

TOMORROW

The SAID Framework for the Conversation You're Dreading - A four-part structure for the hard conversation itself, with a full worked script.