The Art of Managing Up - How to Guide Clients Who Think They Know Best
You know your work. You've done it hundreds of times.
You see a client's idea and you can predict it won't work - it'll confuse users, miss the market, or create technical problems. But telling them "That won't work" kills the relationship.
The tricky part of client work is influencing without overstepping. They're paying you.
You need their buy-in. But you also have a responsibility to warn them when they're headed toward a mistake.
The skill is managing the conversation so they come to the right decision themselves, rather than you telling them what to do. It feels subtle, but it's a completely different dynamic.
Understand Why They Think They Know Best
Before you push back on a client's idea, understand why they're proposing it.
Sometimes they have information you don't. They know their market better than you do. They've heard customer feedback that's shaping their thinking.
Before you dismiss their idea, ask what's driving it. "What's the thinking behind that? Is it something you're hearing from customers?"
Sometimes they're insecure. A new client isn't sure they trust you yet.
So they're micromanaging and telling you how to do your job. This is insecurity, not actual expertise.
Sometimes they're just brainstorming out loud. They're not attached to the idea. They're thinking out loud.
If you immediately reject it, they get defensive. If you explore it, they often come to your conclusion anyway.
Sometimes they're right. Your first instinct might be wrong.
A client who knows their customers might propose something you wouldn't have thought of. Approach it with curiosity, not dismissal.
Understanding their motivation changes how you respond.
The Data-Driven Approach
When you think a client's idea is wrong, the strongest response is data.
"I see what you're going for. Let me show you how this similar approach performed for other companies in your space." Share case studies or data that shows why another approach works better.
"You want X, but research shows Y actually performs better. Here's what the data shows..." Data removes ego. You're not saying "I'm right and you're wrong." You're showing what works.
If you don't have data, run a test. "Let's A/B test your idea against my approach and see what your customers respond to." This gives you both the answer instead of arguing about it.
Data is powerful because it's not about opinion. It's about outcomes.
The Question-Based Approach
Instead of telling them their idea won't work, ask questions that lead them to that conclusion themselves.
Client: "I want the call-to-action to be bright yellow to really stand out."
Wrong response: "Yellow will look cheap and won't convert."
Right response: "I hear you wanting it to stand out. Tell me about your user - what's their goal when they land on this page?
What would catch their attention? Is it the button color, or is it where the button is positioned?"
By asking questions, you're guiding them to think through the idea more deeply. Usually, they'll realize the issue themselves.
This works because they're not defensive - you're not attacking their idea. You're exploring it together.
The Reframing Approach
Sometimes a client's underlying need is right, but their execution is wrong. Reframe to address the need differently.
Client: "I want every service listed on the homepage so people understand everything we do."
Your concern: The page will be cluttered and confusing.
Reframe: "I get it - you want people to understand your full range of services. Instead of listing everything on the homepage, what if we created a clear services menu and a detailed services page? That way people can understand your full range without the homepage being overwhelming."
You're not saying no. You're solving their actual problem (showcasing services) in a better way.
The Risk-Based Approach
When you're concerned about an approach, articulate the specific risk.
"I love the enthusiasm. Here's my concern - if we implement it this way, we're assuming customers will [X], but what if they do [Y] instead?
That would create [negative outcome]. What if we tested it this way first to validate that assumption?"
Concrete risks are easier to discuss than vague concerns. You're not being negative - you're identifying risks and proposing ways to mitigate them.
The Authority Approach
Sometimes you just need to be the expert.
But do it carefully. Lead with your experience, not ego.
"I've done about 50 projects like this. The times we've gone down this road, it's typically resulted in [X problem].
I'd hate to see that happen here. Can I suggest an alternative based on what's worked?"
This positions you as experienced, not bossy. You're sharing hard-won lessons, not insisting you're right.
When to Push Back Harder
Sometimes the client's idea is so problematic that gentle influence isn't enough. You need to push back more directly.
This is especially true if:
- Their idea contradicts the project brief or goals
- Their idea creates liability or risk
- Their idea is based on a misunderstanding about their market
In these cases, be direct but respectful.
"I need to be honest with you. I think this approach is going to hurt your conversion rate, based on what I've seen in similar projects.
I can't recommend this. Here's what I'd suggest instead, and here's why."
This is a strong statement, but it's backed by experience and reasoning. You're not saying "You're wrong." You're saying "I can't recommend this approach based on my experience."
A good client will listen. If they insist anyway, you document that you recommended against it and let them make the choice.
Knowing When to Just Do It
Sometimes you push back, they insist, and you have to decide: do I do it or do I walk away?
If it's not actually wrong - just not what you would do - do it. Let them learn.
Their idea might work. Or it might not, and you'll both see why.
If it's actually risky or damaging, and you can't recommend it, you might need to walk away. But this should be rare.
Document your recommendation. "You asked for X. I recommended Y because [reason].
You're choosing to go with X. I'll execute it professionally, but I want this documented that I recommended against this approach."
This protects you professionally and creates a record.
FAQ
What if the client is the decision-maker and absolutely insists on their approach? You execute it professionally. It's their decision and their outcome. But you can say, "I'll do this, but I want to check in after launch and see if we're hitting your goals. If not, we can adjust."
How do I push back without damaging the relationship? Focus on their goals, not their idea. "Your goal is increasing conversions. My concern with this approach is that it might hurt that goal. Let me suggest an alternative." You're on the same team trying to achieve the same goal.
Is it ever okay to refuse to implement a client's idea? Yes, if it's unethical, illegal, or violates your values. Otherwise, you can express concern, but ultimately it's their decision.
What if I'm wrong and their idea actually works? Great. You learn something. Don't get defensive. Instead, say, "I'm glad that worked. I was concerned it might create X issue, but you were right. That's good to know for future projects."
How do I build trust so clients listen to my recommendations? Consistently delivering good work and being honest about outcomes. Over time, if your recommendations are good, they'll trust you. This happens through reputation, not one conversation.
Should I let them fail to prove my point? No. That's petty. Your job is to deliver the best outcome possible. If you genuinely think an approach will fail, speak up. But after that, you execute professionally.
What if I genuinely don't know if their idea will work? Say so. "I'm not sure about this, but it's interesting. Let's test it" or "Let's build a prototype and see how users respond." You don't have to have all the answers.