I used to think involving clients closely was good service. I'd send options for them to weigh, check in at every juncture, explain my reasoning at length, and invite input wherever there was a decision to be made — because that seemed collaborative, transparent, and respectful of the fact that it was their project. What I eventually noticed was that the clients who came back most reliably weren't the ones I'd involved most. They were the ones whose projects had taken up the least of their attention.
The assumption underneath the collaborative instinct is that clients want to be involved. Sometimes they do. But for a large share of client work, the actual motivation for hiring someone is the opposite: this is a problem they don't want to spend their attention on, and paying you is how they stop having to. Every decision you hand back to them, every option you present for their consideration, every check-in that requires a thoughtful response, is a small withdrawal from the exact account they were trying to protect.
This runs against how the industry talks about itself. The language of client work is full of partnership, collaboration, and close involvement, all presented as premium service — and for some clients and some projects it genuinely is. But for many, "we'll involve you at every stage" describes a cost rather than a benefit. They hear more meetings, more decisions, more of a project they were hoping to delegate, and the promise of deep collaboration lands as a warning about how much of their week this will consume.
The important distinction, and the one that keeps this from becoming an argument for shutting clients out, is between informing and involving. Keeping someone informed reduces their uncertainty and costs them nothing — it's reassurance. Involving them requires their attention, judgment, and time — it's a tax. Good service tends to maximise the first and minimise the second, and the reason so many providers get this backwards is that both look like communication from the outside. Here's the difference and why it matters.
Key Takeaways
- Many clients hire you to stop thinking about the problem. Involvement is often the thing they were paying to avoid, not a benefit you're providing.
- Informing and involving are opposites in cost. Updates reduce a client's uncertainty for free; decisions and options consume the attention they were protecting.
- Options are work you've handed back. Presenting three directions asks the client to do the judging they hired you to do.
- "We'll involve you at every stage" can read as a warning. For a busy client, deep collaboration means more meetings and more decisions, not better service.
- Some clients genuinely want involvement. The error isn't collaborating — it's assuming, rather than finding out which kind of client you have.
What They're Actually Buying
Start with the motivation for hiring someone at all. A client engaging a provider usually has a problem they can't or don't want to solve themselves, and a substantial part of what they're purchasing is the removal of that problem from their attention. They have their own work, their own priorities, and a finite amount of thinking available in a week — and handing something to a specialist is how they get it dealt with without spending that.
Seen this way, a provider who requires constant input hasn't fully delivered the thing they were hired for. The work may be excellent, but if getting it took twelve decisions, four meetings, and a series of considered responses from the client, then a meaningful portion of the problem stayed with them. Whereas a provider who takes the brief, handles it, and returns with something good has actually removed the burden — which is what the money was for.
This is why the experience of working with someone weighs so heavily in whether they're rehired, and why it's frequently more decisive than the quality of the output. Clients remember whether a project sat lightly or consumed them, and low-attention providers get invited back because working with them costs so little beyond the fee. It's the same underlying reason that dependability outperforms brilliance in ongoing relationships: both are ways of reducing what the client has to carry. [BACKLINK PLACEHOLDER → suggestion: internal link to article #97, why clients rehire the reliable, not the talented / reducing what a client has to manage is much of the value]
Informing Costs Them Nothing; Involving Costs Them Attention
The distinction that makes this actionable is between communication that reduces a client's uncertainty and communication that requires their input. These look similar and behave completely differently.
Informing is telling someone what's happening: a brief update that the work is on track, a note that a stage is complete, an early flag that something has shifted. This costs the client almost nothing to receive — it's read in seconds and requires no response — while removing the low-level anxiety of not knowing, which is a real service. Under-informing is one of the most common ways providers make projects feel stressful, because a silent project is one the client has to wonder about, and wondering is itself a form of attention. [BACKLINK PLACEHOLDER → suggestion: internal link to article #105, what to do when a client goes silent / silence makes people fill the gap with worry]
Involving is asking someone to decide, choose, review, or weigh in. This requires their judgment and time, which is precisely the resource they were trying to conserve — so every instance should be genuinely necessary. Some are: decisions that are properly theirs, matters of business strategy, things only they have the information to settle. Many aren't, and are simply decisions you could have made and chose to pass along.
So the useful rule is to over-inform and under-involve. Tell them everything; ask them as little as possible. Providers frequently do the reverse — going quiet for long stretches and then arriving with a set of questions — which manages to be both anxiety-inducing and demanding at once, and is a large part of why some projects feel heavy to clients regardless of how the work turns out.
Options Are Decisions You've Handed Back
The clearest example of unnecessary involvement is presenting options. It feels generous and respectful — here are three directions, which do you prefer — and from the client's side it's a request to do the evaluative work they engaged you for. They now have to weigh alternatives in a field where they lack your expertise, which is uncomfortable as well as time-consuming, and the discomfort is exactly why so many clients respond slowly or non-committally to a set of choices.
A clear recommendation is nearly always more useful: this is what I think you should do, and here's why. It gives them something to accept or question rather than something to solve, converting a demanding task into a quick judgment. It also demonstrates the expertise they're paying for, since a view backed by reasoning is evidence of professional judgment while a menu is evidence only that you can generate alternatives. [BACKLINK PLACEHOLDER → suggestion: internal link to article #55, clients don't want options, they want a recommendation / a menu hands the decision back]
The same logic applies to explanation. Detailed accounts of your process and reasoning feel like transparency and often function as homework — a long message about methodology is one more thing to read and understand, delivered to someone who wanted the outcome rather than the account of how it was produced. Explain enough to build confidence and justify a recommendation, and stop there. The instinct to demonstrate rigour through volume is understandable and mostly serves the provider's need to be seen working, not the client's need to have something handled.
🎬 Embed a short comparison of a project run with frequent updates and few decisions, versus one with sparse updates and many decisions, and how each feels to the client.
The Cases Where This Is Wrong
This argument has real limits, and applying it indiscriminately would be its own failure. Some clients genuinely want deep involvement — because the work matters enormously to them, because they enjoy the process, because they have strong views and expertise of their own, or because their role requires them to be across the detail. For these clients, close collaboration is exactly the service they want, and reducing their involvement would feel like being shut out of their own project.
Certain kinds of work also genuinely require it. Anything depending on information only the client holds, anything with significant business or strategic implications, anything where their preferences are the actual subject — these can't be handled by a provider working alone, and pretending otherwise produces work that misses. Decisions that are properly the client's remain the client's regardless of how much attention they'd rather not spend.
So the real error isn't collaboration; it's assumption. Providers who assume clients want involvement over-involve them, and providers who assume the opposite exclude people who wanted to be part of it. The fix is to find out, early and explicitly: ask how involved they want to be, how they prefer decisions to be handled, and how much they want to see along the way. It's a simple question, it takes moments, and it's rarely asked — which is why so many providers are guessing about the single variable that most shapes how the relationship feels. [BACKLINK PLACEHOLDER → suggestion: internal link to article #84, what to ask a new client before you start / asking how they want to work is as important as asking what they want]
