Dear Client, Your Design Isn't Working

Introduction

A client hired me to rebuild their e-commerce site. I proposed a modern checkout flow based on conversion research: one-page checkout, guest option, mobile-optimized forms.

The client’s response: “We need a five-page checkout with mandatory account creation. Our old site did it that way, and we’re comfortable with it.”

I showed them data. Cart abandonment on their old site: 78%. Industry average with streamlined checkout: 35%. They didn’t care. “That’s how we’ve always done it.”

I built what they wanted. Their cart abandonment stayed at 76%. Three months later, they blamed me for low conversions.

This article is for developers and designers who’ve been hired for expertise and then had every recommendation ignored. If you’ve never felt the frustration of watching a client sabotage their own success, this isn’t for you.

I’m going to tell you how to handle clients who hire you and then override every decision, when to push back versus when to walk away, and what actually works when expertise conflicts with ego.

Enjoying this? 👉 Tip a coffee and keep posts coming

Here’s who this is for: Freelancers and consultants tired of being treated as code monkeys. In-house developers with micromanaging bosses. Anyone who’s heard “I hired you for your expertise but I want it done my way.”

Not for: People who’ve never worked with difficult clients. Come back after your first project where every decision is overridden.

The question isn’t “how do I convince clients to listen?” It’s “how do I protect my reputation when they don’t?”

The Core Judgment: Document Everything, Deliver What They Ask For, Walk Away Clean

Here’s what most professionals get wrong when clients ignore expertise: they keep fighting battles they can’t win.

You can’t force a client to make good decisions. You can’t convince someone who hired you for validation, not advice. You can’t save a project when the client is determined to fail.

What you can do: document your recommendations, explain the consequences, build what they ask for, and protect your reputation when it fails.

I used to think my job was making clients succeed. It’s not. My job is giving clients the tools to succeed. Whether they use those tools is their choice.

The clients who ignore expertise fall into three categories:

1. The “I Know Better” client - They’ve run their business for 20 years and don’t need some consultant telling them how to do things. They hired you to execute their vision, not challenge it.

2. The “Design by Committee” client - Every decision requires approval from seven stakeholders with conflicting opinions. Nothing ever gets decided. Your recommendations get diluted into useless compromises.

3. The “Previous Developer Trauma” client - They got burned by a developer who oversold and underdelivered. Now they trust no one and question everything. Your expertise is suspect by default.

None of these clients will listen to advice. Fighting them wastes your energy and damages your reputation when you inevitably can’t save their project.

How This Works in the Real World

I had a client who wanted a “modern redesign” of their corporate site. I proposed clean layouts, readable typography, fast loading, mobile-first design.

Every recommendation was rejected.

“Can we make the logo bigger?” Yes, 40% bigger.

“Can we add more animations?” Sure, three auto-playing videos on the homepage.

“Can we use this neon color scheme?” If you insist.

The result: a slow, garish site that looked like a 2005 MySpace page. But it was exactly what they asked for.

What I did right:

I documented every recommendation in writing. “I recommend a maximum video size of 2MB for performance. You’ve requested 15MB of auto-playing video. This will impact load times and mobile users.”

I sent weekly summaries of decisions and their implications. “This week you approved the neon color scheme. Note that this fails WCAG accessibility contrast requirements.”

I built exactly what they approved. No shortcuts. No creative interpretation. They signed off on every wireframe, every mockup, every component.

When the site launched and users complained about performance and readability, I had a paper trail showing I’d warned them about every issue.

They didn’t renew the contract. I didn’t want them to. I’d rather lose a bad client than waste more time fighting losing battles.

A Real Example: The Logo No One Could Read

A startup hired me to build their landing page. They had a logo: white text on a transparent background. I explained this wouldn’t work on all backgrounds and suggested alternatives.

“No, the logo stays as-is. It’s our brand.”

I built the page with their logo. On the hero section’s white background, the white logo was invisible. I used a dark overlay behind it. They rejected the overlay.

“Just make it work.”

I tried drop shadows. “Too much shadow.” I tried stroke outlines. “Looks cheap.” I tried inverting the logo on light backgrounds. “That’s not our brand.”

The solution that worked: I built it their way and included a note in the project handoff: “Logo visibility issues on light backgrounds are a known limitation of the current logo design. Consider redesigning the logo with a background or switching to a version with built-in contrast.”

They launched with an invisible logo. Their investors pointed it out in the first meeting. They redesigned the logo three weeks later.

I didn’t say “I told you so.” I just quietly never worked with them again.

Common Mistakes Professionals Make With Difficult Clients

Fighting every battle. Pick your battles. If it’s a minor preference (“I like blue better than green”), let them have it. Save your energy for decisions that actually matter.

Getting emotionally invested in their success. Your job is delivering what they pay for. Their business success is not your responsibility, especially when they reject your advice.

Taking blame for their decisions. Document recommendations. When the project fails, you have evidence you advised against the approach. Your reputation stays intact.

Working with them again. A client who overrides expertise once will do it again. Fire bad clients. Life’s too short to argue about obvious decisions.

What Breaks When Clients Ignore Expertise

The project fails, and you get blamed. No matter how much you documented, clients will tell others “we hired a developer and the site doesn’t convert.” Your paper trail protects you legally, but not reputationally.

You burn out fighting unwinnable arguments. Every overridden decision drains energy. Eventually, you stop caring. Your work quality drops. Your frustration bleeds into other projects.

You stop trusting your own judgment. After enough clients reject your recommendations, you start second-guessing yourself. “Maybe they’re right. Maybe I don’t know what I’m doing.” You do. They’re wrong. But constant rejection erodes confidence.

The honest cost: One freelancer I know spent six months on a project where every decision was overridden. The client refused to pay the final invoice because “the site doesn’t work.” The freelancer sued. Won. Collected 60% of the invoice after legal fees. Never freelanced again. One bad client killed his career.

Best Practices for Protecting Yourself

Get everything in writing. Email summaries after every call. “Per our conversation today, you’ve decided to proceed with the five-page checkout despite recommendations for a streamlined flow. Noted impact: likely increased cart abandonment.”

Provide two options: your recommendation and their request. Show mockups of both. Let them choose. When they choose poorly, you have visual proof you proposed better.

Build exactly what they approve, nothing more. No creative interpretation. No “I know better.” If they approve a bad design, build that bad design. Your job is execution, not saving them from themselves.

Set boundaries in contracts. Include revision limits. Include decision-making timelines. Include termination clauses. Protect yourself from endless revisions and indecisive stakeholders.

Fire bad clients. After the first project where expertise is consistently ignored, don’t take a second. Politely decline. Your time is worth more than arguing with people who don’t respect your skills.

When to Actually Walk Away

Sometimes you fire a client mid-project. Here’s when:

They’re abusive. If a client yells, insults, or demeans you, terminate the contract immediately. No project is worth that.

They don’t pay on time. One late payment is a mistake. Two late payments is a pattern. Walk away.

They keep changing requirements without budget increases. Scope creep is normal. Unlimited scope creep without compensation is exploitation.

Your reputation is at risk. If the project is going so badly that association with it will hurt your career, offer a refund and exit gracefully.

The honest answer: Most difficult client situations aren’t worth fixing. The energy you spend managing one nightmare client could be spent delivering great work for three good clients.

Conclusion

You can’t force clients to make good decisions. You can only make sure their bad decisions don’t damage your career.

After a decade working with clients, I’ve learned that the most important skill isn’t design or development—it’s knowing which clients to fire.

Good clients hire you for expertise and trust your recommendations. They might question, they might debate, but they ultimately respect your judgment.

Bad clients hire you for execution and override every decision. They want the prestige of hiring an expert without the inconvenience of listening to one.

The future of professional services isn’t “the customer is always right.” It’s “the right customers are the only ones worth having.”

Document your recommendations. Build what they approve. Protect your reputation. And fire clients who don’t respect expertise.

Life’s too short for unwinnable battles.

Frequently Asked Questions (FAQs)

How do you fire a client mid-project?

Be professional, not personal. “After reviewing the project scope and our working relationship, I don’t believe I’m the right fit for this project. I can complete [milestone X] and transition deliverables, or we can terminate now with a prorated refund.”

What if I need the money and can’t afford to fire them?

Finish the project, document everything, and never work with them again. Use the experience as motivation to build a client pipeline where you can be selective.

How do you handle clients who want unlimited revisions?

Include revision limits in your contract (e.g., “3 rounds of revisions included, additional rounds billed at $X per hour”). Enforce it. Clients who don’t respect boundaries will drain you.

Should you ever compromise your expertise?

Yes, on minor preferences. No, on functional or ethical issues. If they want Comic Sans, let them have it. If they want to violate accessibility standards or user privacy, walk away.

How do you rebuild confidence after a difficult client?

Work with a good client who trusts your expertise. One positive project will remind you that you do know what you’re doing, and bad clients are the exception, not the rule.

Your turn: What’s the worst client decision you’ve had to implement, and did you document it?

Enjoying this? 👉 Tip a coffee and keep posts coming