---

title: "Difficult client archetypes: the ghost, the micromanager, and the committee"

module: 12

module_title: "Special Situations"

order: 4

access: "paid"

summary: "Recognize the three classic difficult-client patterns as anxieties with causes rather than personality flaws, and address the cause instead of enduring the symptoms. Covers shrinking asks and default-and-proceed rules for the ghost, proactive visibility for the micromanager, and a named decision-owner for the committee."

related:

• "proactive-communication"
• "managing-conflicting-feedback-from-multiple-stakeholders"
• "the-kickoff-meeting"
• "consistent-communication-cadence"

---

Difficult client archetypes: the ghost, the micromanager, and the committee

Early in my career I thought difficult clients were a personality lottery. Some people are just hard to work with, you draw a bad ticket sometimes, nothing to be done but endure it. Then I noticed something that changed my mind: the same client could be a nightmare with one team and easy with another. The "difficult client" our whole team dreaded became, after we changed how we communicated with her, one of our best long-term relationships.

Difficult client behavior is usually a pattern, and patterns have causes. Once you can name the pattern, you can usually see the anxiety driving it, and once you see the anxiety, you can address the cause instead of enduring the symptoms.

Why archetypes are worth naming

Every experienced agency person knows these characters. The client who vanishes for three weeks and then needs everything urgently. The one who comments on individual button colors at 11pm. The one who is actually six people wearing a trench coat, none of whom agree with each other.

Naming the archetype does two useful things. It depersonalizes the problem, because "we have a committee situation" is a solvable structure, while "this client is impossible" is just despair with extra steps. And it lets you respond to the pattern early, because these patterns are visible in the first month if you know what to look for, and every one of them is cheaper to address early.

One ground rule: archetypes describe behavior under stress, not character. Almost every difficult pattern is a reasonable anxiety expressing itself badly. The micromanager was burned by a vendor who went dark. The ghost is drowning in a job where your project is priority forty. The committee exists because nobody above it made a decision about who decides. Work the cause, not the caricature. And notice when you're the cause: plenty of micromanagers are created by vague status updates, and plenty of ghosts are created by emails that don't contain a clear question.

The ghost

What it looks like: Feedback requests disappear into silence. Approvals that should take two days take three weeks. Meetings get rescheduled twice and then attended by someone unprepared. Then, periodically, the ghost rematerializes with urgent energy and is surprised the project has drifted.

What's usually going on: Not indifference. Overload. Your project is one of many things on their plate, your emails require thinking, and thinking gets deferred. Sometimes there's a second cause: your requests are too big. An email that says "review the attached 30-page document and share your thoughts" is an email designed to be postponed.

What to do: Shrink the asks and attach consequences to the calendar, gently. Make every request answerable in under five minutes, put one question per email, and be explicit about what happens when a date passes.

Mid-project, after the second missed feedback deadline:

"Hey Maria, totally understand things are hectic on your end. Two things to keep us moving. First, I've boiled the open feedback down to three yes/no questions below, should take about three minutes. Second, a process suggestion: for future reviews, if we haven't heard back within five business days, we'll proceed with our recommended option so the timeline holds, and we'll flag anything that would be expensive to reverse later. That way your busy weeks don't stall the project. If that doesn't work for you, happy to find another rhythm."

The micromanager

What it looks like: Daily check-ins about things you discussed yesterday. Feedback at the pixel and comma level, delivered at all hours. Requests to be CC'd on internal threads. A palpable flinch every time something happens that they didn't pre-approve.

What's usually going on: Fear, almost always. Fear from a past vendor who went dark and delivered garbage, or fear of their own boss, to whom they've promised this project will go well. Micromanagement is what "I can't see what's happening and I'm accountable for it" looks like in the wild. The instinct to create distance, slower replies, less detail, guarded updates, reads as evasion and makes everything worse.

What to do: Flood them with the visibility they're starving for, but on your schedule instead of theirs. Overwhelming proactive communication is the cure, because the check-ins aren't the disease, they're the symptom of not knowing.

Three weeks into a new engagement, after the fourth "just checking in" day:

"Ben, I've noticed the check-ins, and I want to make sure you're never in the position of having to ask. Here's what I'd like to try: every day at 5pm you'll get a three-line update from me. What moved today, what's next, anything blocking. Plus you have the live project board, link here, which updates as we work. If a day ever feels off to you, call me directly. I want you walking into your Monday meeting with your boss already knowing everything. Deal?"

The committee

What it looks like: Feedback arrives from five people in four documents, and it conflicts. Decisions get made, then unmade when a new stakeholder appears. Meetings are large and conclusions are rare. Nobody can tell you whose opinion wins, and asking produces uncomfortable laughter.

What's usually going on: A structural vacuum. Nobody with authority has designated a decision-maker, so decisions are being made by ambient consensus, which means they're not really being made at all. This one differs from the other archetypes in an important way: it usually can't be fixed with better communication habits alone. It has to be fixed with process, and the fix has to be explicit.

What to do: Get one throat to choke, kindly. Push for a single feedback channel and a named decision-maker, and frame the request around protecting their budget, because that's what it does.

After the second round of contradictory feedback:

"I want to flag something that's starting to cost you money. On the homepage design, we got feedback from Priya asking for a bolder look, from Tom asking for something more conservative, and from Alex with detailed notes that conflict with both. We can build any of these, but we can't build all of them, and every cycle we spend reconciling feedback is budget not going into the product.

My strong recommendation: pick one person to be the decision-owner for design. Everyone else still gives input, but it flows through that person, and what they send us is final. Most teams your size work this way and it typically saves 10-15% of the budget in avoided rework. Who would be the right person?"

What goes wrong with difficult patterns

Enduring instead of addressing. The most common response to all three archetypes is to quietly absorb the dysfunction and vent internally. Six months of that produces a resentful team, a degraded margin, and a client who has no idea anything is wrong.

Matching the energy. Ghosting the ghost, stonewalling the micromanager, playing committee members against each other. Each feels momentarily fair and makes the pattern worse.

Diagnosing out loud. The archetype vocabulary is for your team's internal thinking, never for the client. "You're micromanaging" is an accusation. "I'd like to get you a daily update so you always know where things stand" is a fix. Same diagnosis, opposite outcomes.

Missing your own contribution. Before labeling the client, audit yourself. Vague updates breed micromanagers. Twelve-question emails breed ghosts. No proposed decision process breeds committees. Sometimes the difficult client is responding rationally to a difficult vendor.

Ignoring the pattern in the sales process. All three archetypes are usually visible before the contract is signed. Slow responses to your proposal, obsessive pre-contract detail questions, six people on the sales calls with no clear lead. You can still take the project. Just price the pattern in and set up the countermeasures on day one.

Getting better at this

Build the countermeasures into your defaults. Every practice above, small single-question asks, proactive update rhythms, one feedback channel, a named decision-maker, silence-handling rules, is just good process. Run them with every client from day one and most archetypes never fully develop. The difficult patterns grow in the space your process leaves undefined.

Do a pattern check at week four. One month in, ask your team: how fast is feedback coming? How many people is it coming from? Is anyone showing anxiety? Week four is early enough that a process adjustment feels like tuning, not confrontation.

Keep a playbook, not a grudge list. When a difficult pattern gets resolved, write down what worked. Over time you get a real playbook: the daily three-liner for anxious clients, the default-and-proceed rule for slow ones, the decision-owner pitch for committees. The next occurrence stops being an ordeal and becomes a known play.

Know your walk-away line. Most difficult patterns respond to structure. A few don't, and the pattern that persists after clear, kind, repeated process fixes is telling you something about the next two years of your life. Pricing a difficult client correctly sometimes means declining the renewal, and that's a legitimate outcome, not a failure.

How this connects

Each archetype maps to skills covered elsewhere in this collection. The ghost is a consistent-cadence and expectations problem. The micromanager is solved with proactive communication and instilling confidence. The committee is a stakeholder-conflict and decision-facilitation problem wearing a scarier costume. And all three are easiest to prevent in the kickoff meeting, where communication rhythms, feedback channels, and decision-makers get established while everything is still easy.

Things to try

• Pick your currently most frustrating client and write down the pattern, not the person: what behavior, how often, triggered by what?
• For a slow-responding client, shrink your next ask to one question answerable in five minutes. See what happens.
• For an anxious client, start an unprompted end-of-day three-line update this week. Watch the check-ins fade.
• For a multi-stakeholder project, count how many people gave feedback on the last deliverable. If it's more than two, propose a decision-owner at the next meeting.
• Audit your own habits against the patterns: are your updates specific enough, your asks small enough, your decision process explicit enough?

That client our whole team dreaded, the one who became a favorite? Nothing about her changed. She had been burned by an agency that missed a launch and hid it from her until the end, and she was never going to extend blind trust again. What changed is that we stopped treating her anxiety as an insult and started treating it as a requirement. Difficult clients are mostly clients whose fears haven't been addressed yet. Address the fear and you'll often find a good client was in there the whole time.

Template: Default-and-Proceed Rule for the Ghost

Use this when: a client keeps missing feedback deadlines and you need to shrink the ask and set a gentle rule so their silence stops stalling the project.

Channel: Email

```template

Subject: Three quick questions + a suggestion to keep us moving

Hi [NAME],

Totally understand things are hectic on your end. Two things to keep [PROJECT] moving without adding to your load.

First, I've boiled the open feedback down to three yes/no questions — should take about three minutes:

1. [QUESTION 1 — answerable yes/no]
2. [QUESTION 2]
3. [QUESTION 3]

Second, a small process suggestion for future reviews: if we haven't heard back within [FIVE] business days, we'll proceed with our recommended option so the timeline holds — and we'll always flag anything that would be expensive to reverse later, so nothing important gets decided by default. That way your busy weeks don't stall the project.

If a different rhythm would work better for you, just say so and we'll adjust.

[YOUR NAME]

```

Template: Daily Update Offer for the Micromanager

Use this when: a client is checking in constantly out of anxiety, and you want to give them more visibility than their check-ins extract — on your schedule, not theirs.

Channel: Email

```template

Subject: A daily update so you always know where things stand

Hi [NAME],

I've noticed the check-ins, and honestly I want to make sure you're never in the position of having to ask.

Here's what I'd like to try: every day at [TIME] you'll get a three-line update from me — what moved today, what's next, and anything blocking us. On top of that, you've got the live project board here ([LINK]), which updates as we work.

If a day ever feels off to you, call me directly — that's always fine.

Mostly, I want you walking into [THEIR HIGH-STAKES MOMENT — e.g. your Monday meeting with your boss] already knowing everything, with no surprises. Sound good?

[YOUR NAME]

```