When a client micromanages your design work
By The Onbo team · Updated
Short answer
Redirect detailed instructions back to the goals you agreed, ask what problem each instruction is trying to solve, and explain your process and when feedback is most useful. Most micromanaging comes from anxiety or unclear roles, so agree goals, process, feedback rounds and decision makers in writing at the start of the next project.
Some clients send a hex code for every element, a sketch of exactly where the button goes and a message every hour asking how it’s going. It’s draining, and it rarely produces good work, because you’ve been hired for your judgment and you’re being asked to set it aside. Micromanaging is usually a symptom, though, not a personality. Treat the cause and the behaviour often eases.
Why do clients micromanage?
Mostly from uncertainty. They’re anxious about spending money on something they can’t fully picture. They’ve had a bad experience with a previous designer. They don’t know how a design process works, so they fill the silence with instructions. Or the roles were never agreed: nobody said who decides what, so they assume it’s all on them. Seen this way, micromanaging is often a request for reassurance and structure.
How do you respond in the moment?
Ask about the problem behind each instruction. “You’d like the logo bigger. Is the concern that people won’t notice it, or that it doesn’t feel prominent enough for the brand?” There may be a better solution than the one they’ve prescribed, and asking shows you’re taking them seriously.
Check suggestions against the agreed goals. If the brief says first-time visitors should trust the business enough to book, ask whether a change supports that. It moves the conversation from taste to purpose.
Explain your process and when feedback is most useful. Clients often micromanage because they don’t know they’ll get a chance to comment later. Telling them “you’ll see concepts on Tuesday, and that’s the best moment for big-picture feedback” gives their input a place.
Agree check-in points. Constant updates can be replaced by a short, regular update at an agreed time, which usually reduces the hourly messages.
| Behaviour | Likely cause | Response |
|---|---|---|
| Detailed instructions on every element | Anxiety about the outcome | Ask what problem each one solves |
| Frequent “how’s it going?” messages | No visibility of progress | Agree a regular update time |
| Redesigning your work themselves | Unclear roles | Restate who decides what, per the brief |
| Changing direction often | No agreed goals | Go back to the brief together |
For example, a freelance web designer might have a client sending layout sketches daily. She asks what each sketch is trying to fix, discovers the client is worried visitors won’t find the booking button, and proposes a clearer booking path. She also sets a Friday progress update. The sketches stop, and the client approves the next version with one comment.
How do you prevent it next time?
Most micromanaging is an onboarding gap. Before work starts, agree the goals in writing, explain the process and when feedback happens, define revision rounds, and name who gives feedback and who approves. Our guides on how to prepare a new client for a design project and how to limit design revisions cover each, and the client onboarding questionnaire helps you agree the goals you’ll check work against. Agencies can build the same agreements into the agency project kickoff workflow.
When is it time to part ways?
If you’ve explained your process, offered structure and the client still won’t accept any professional judgment, the project may not be able to succeed. In that case, ending it under your agreement’s terms can be better for both of you. Do it calmly, in writing, with a clear account of what’s been delivered and what’s owed.
How do you stay calm about it?
It helps to remember the client usually wants the same thing you do: a design that works. Keep your replies focused on the goals, and keep your process visible.
A micromanaging-client checklist
- Problem behind each instruction asked about
- Suggestions checked against the agreed goals
- Process and feedback points explained
- Regular update time agreed
- Roles restated: who decides what
- Brief revisited if direction keeps changing
- Everything important kept in writing
- Next time: goals, process and rounds agreed at onboarding
- Approvers named before work starts
- Exit terms in the agreement, if needed
Where Onbo fits
Onbo sets up the structure that prevents micromanaging. Your client accepts the agreement with your process and revision terms, pays the deposit, and answers your questionnaire, where you agree goals and who approves. You get a Markdown hand-off brief to point back to whenever direction drifts. Try it free for 30 days; see pricing.
Questions
How do I handle a client who micromanages the design?
Ask what problem each instruction is solving, check suggestions against the agreed goals, explain when feedback is most useful, and keep communication to agreed points rather than constant check-ins.
Why do some clients micromanage?
Often anxiety about the outcome, a past bad experience, unclear roles, or simply not knowing how a design process works.
When should I walk away from a micromanaging client?
If the client won't accept any process or professional judgment after you've explained it, and the project can't succeed that way, it may be better for both sides to end it under your agreement's terms.