Menu Search
Jump to the content X X
Smashing Conf Barcelona 2016

We use ad-blockers as well, you know. We gotta keep those servers running though. Did you know that we publish useful books and run friendly conferences — crafted for pros like yourself? E.g. upcoming SmashingConf Barcelona, dedicated to smart front-end techniques and design patterns.

Is John The Client Dense or Are You Failing Him?

Meet John the client. John runs a reasonably large website. He is a marketer who considers himself smart, articulate and professional. That said, he doesn’t know much about Web design, and so he needs your help. John comes to you with a clear set of business objectives and asks for a quote. But what happens next leaves John confused, frustrated and extremely unhappy.

Explain Why You Are Asking About Money Link

Before giving John his quote, you ask a little more about the project. After chatting for a few minutes, you ask him about his budget. A fair question, you think. After all, you could approach the project in so many ways. Without knowing the budget, knowing where to begin is impossible. In your mind, building a website is like building a house. Without knowing the budget, you can’t possibly know how many rooms the client can afford or what materials you should use to build.

John, on the other hand, is instantly suspicious. Why would you want to know about his budget? The only reason he can think of is that you want to make sure you don’t charge him less than what he is willing to give. Besides, he doesn’t really know his budget. How the heck is he supposed to know how much a website costs?

Money Grabber
Don’t come across as money-grubbing. (Image credit)

John leaves, determined to find a Web designer who doesn’t want to take advantage of him. Fortunately for you, all of the other designers he speaks with also neglect to explain why they need to know about his budget, and so you manage to win the project after all.

Justify Your Recommendations In Language John Can Understand Link

Once you have won the job, you arrange a kick-off meeting to nail down the specifications. However, John instantly regrets his decision to hire you because his worse fears have been confirmed. In his eyes, you are all of a sudden trying to squeeze more money out of him as you waffle about the importance of usability and accessibility. John doesn’t care about disabled users. He doesn’t expect disabled users to visit his website anyway.

And as for usability, surely the job of the Web designer is to make the website usable. Why do we need expensive usability testing? He is pretty certain that usability testing involves expensive things like cameras, labs and two-way mirrors. You thought you had explained these issues clearly. You spoke of WCAG 2, and you mentioned Jakob Neilsen. You are beginning to wonder if John is a bit thick.

People looking confused
Avoid techno-babble if you expect clients to understand what you’re talking about. (Image credit1)

Perhaps if you had talked about accessibility in terms of assessing search engine rankings and testing usability as a way to increase conversion, then John might have listened. As it is, John puts his foot down and refuses to pay for any of these “unnecessary extras.”

Include John In The Process Link

You walk away from the kick-off meeting pleased to have a signed contract. But that feeling in the pit of your stomach tells you that this might be another one of those projects. Regardless, you try to be optimistic, and you dive into the design process. Almost immediately, you get a phone call from John asking if there is anything for him to see. You explain that it is still early in the process and that you are not ready to present anything. John sounds disappointed but resigned.

A short while later, you are ready to present the design to John. You are pleased with the result. It took you a lot more time than you had budgeted for, but it was worth it. The final design is extremely easy to use and will make for a great portfolio piece.

Person hiding
Stop hiding from your clients. Show them your work early on, and include them in the process. (Image credit2)

When John sees the design, he is horrified. From his perspective, you have entirely missed the point. The design clashes with his offline marketing materials and doesn’t hit the right selling points. Also, he is convinced that his suppliers will hate it and, although they are not his end users, their opinion matters.

After a tense conference call, you feel demoralized but have struck a compromise that hopefully will make John happy. You wonder in hindsight whether showing John some of your initial ideas and sketches would have been better. Perhaps you should have presented a wireframe first.

Educate John About Design Link

After much agonizing and compromise, you are once again ready to present to John. John is much happier with the new design and feels it is heading in the right direction. However, he does have some concerns. For starters, he has to scroll to see most of the content, and yet white space takes up either side of the design. He tells you to move key content into this wasted space. Also, as he thinks about his young male target audience, he realizes that the color scheme is too effeminate, so he tells you to change it to blue.

While John feels somewhat happier, you feel crushed. You feel as though he is trying to do the job for you. The instructions to move this there and change this color to that makes you feel like you have been reduced to pushing pixels.

Teacher teaching maths
Educate your clients so they make more informed decisions. (Image credit)

By this point, you are sure the client is dim, and now you just want him to sign off on a design. At no stage do you think to ask John why he is requesting these changes. Perhaps if you had appreciated his thinking, you could have explained concepts such as screen resolution and suggested an alternative to corporate blue, which is so over-used on the Web.

Instead, you wash your hands of the design and just give John what he wants.

Communicate With John Regularly Link

Now that the design is complete, you turn your attention to building it. John certainly won’t care about your code. Now you can finally do things right.

It’s a big job and takes a lot of time. Even though you put too much time into the design and washed your hands of it, you still have your pride. You are not about to cut corners with the code. After all, other designers might look at it and judge you! You work really hard, putting in more work than you probably should have. John even manages to slip in some extra functionality at the scoping phase, which turns out to be a pain in the butt.

For his part, John is wondering what’s going on. He hasn’t heard from you in weeks. Surely the website must be ready now? He decides to email you to ask how things are progressing. You reply with a short email telling him that everything is progressing smoothly. You never did like project management, and you are sure John would prefer that you spend time building his website instead of writing him detailed reports.

John receives your email and is becoming increasingly frustrated. What does “progressing smoothly” mean? He writes back asking for an expected date of completion, and you reply with a rough estimate.

The date comes and goes without a word from you. After all, it was merely an estimate, and several complications have delayed completion by a few days. John finally loses his temper and calls you. He tells you that he has arranged a marketing campaign to coincide with the launch date, and because he hadn’t heard from you, he presumed everything was on schedule.

Phone with the receiver taped up
Communicate with your client regularly. (Image credit3)

You defend yourself, citing “scope creep” and unanticipated delays. But responding is difficult when John says, “All I needed was a weekly email keeping me up to date on progress.”

Explain John’s Ongoing Role Link

By this stage, the relationship has broken down entirely. You finish your work, and the website finally launches. Begrudgingly, John pays the invoice after delaying it for as long as possible. What amazes you most is John’s pronouncement that he is bitterly disappointed with the result. How can that be when you gave him exactly what he asked for? This guy isn’t just thick: he’s a jerk!

Of course, John sees things differently. He came to you with a list of his business objectives, and the website has failed to meet any of them. He had hoped to launch the website, watch it achieve his objectives and then move on to the next project. Instead, after an initial spike in interest, the number of users and inquiries dropped over time, and the website stagnated.

Seedling being cared for
Ensure that your client understands what kind of ongoing care their website will need. (Image credit)

What John does not realize is that websites need continued love and support. You cannot build a website and then abandon it. John has to nurture it by adding new content, engaging with visitors and planning for ongoing development.

If only someone had told him.

The Moral Of The Story Link

It’s amazing how quick we are to judge our clients.

As Web designers, we communicate and empathize for a living. Our job is to communicate messages to our clients’ users. We create usable websites by putting ourselves in the position of our users, which allows us to design around their needs.

Why, then, do we so often seem to be incapable of empathizing or communicating with our clients? Perhaps it is time for us to apply the skills we have cultivated as Web designers to our own customers.


Footnotes Link

  1. 1
  2. 2
  3. 3
SmashingConf Barcelona 2016

Hold on, Tiger! Thank you for reading the article. Did you know that we also publish printed books and run friendly conferences – crafted for pros like you? Like SmashingConf Barcelona, on October 25–26, with smart design patterns and front-end techniques.

↑ Back to top Tweet itShare on Facebook


Paul Boag is the author of Digital Adaptation and a leader in digital strategy with over 20 years experience. Through consultancy, speaking, writing, training and mentoring he passionately promotes digital best practice.

  1. 1

    You should upload these articles in PDF! Nice post for reading in the bus to a client!

    • 2


      I think this would be a great idea too. But you could always send your client a link to the posting. On top of that image how much bandwidth would be used for everyone downloading PDF postings. May be expensive to do and not worth it in the long run.

    • 3

      Sorry to put it in that way, but I think you missed the point of that article: It is not the client, but your poor communication. So, why would you give this story to a client. Rather, distribute it among your fellow designers and help them avoid misunderstandings.

      Very good article.

      • 4

        I agree. I wouldn’t show this to a client, but pass around to fellow designers. The Designer needs to reference this article and remember to include their clients throughout the process, and that communication is key. It also reminds of a talk that some Web Designers, should partner up with a good Project Manager, that can serve as the client liaison who communicates back and forth with the client to get their feed back, update them on the project’s progress, and gather the client’s requirements. Free lance designers often kill their client retention because they are not designed for client interaction, so they should buddy up if they fall in this category. Otherwise they are going to lose out.

  2. 5

    Maybe also tell John that life is more than money, websites & design…?

    • 6

      good one ! :) yes life is more than money , websites and design…wait what is it about ….oh yes, its about our glorious existence on this planet…and everyday, we need to thank the almighty for it….we should be happy….like robots….for our eyes, ears, hair (your choice of purple, red, blonde, dirty blonde, whatever you want to dye), thankful for the fact that you dont yet have a tail or two pointed horns on your head….

      what a great existence of a great species….wow !

  3. 9

    richard hughes

    February 19, 2010 5:44 am

    thanks for sharing – some common sense stuff here, but make you think of the other sides point of view.

    reminds me of the client Vs graphic designer video –

  4. 10

    All of a sudden I have heard about this web site. This is the first post I have read on. A organized and structured way to manage a prospective client I must say. As though my job responsibility is to manage projects and clients, I will surly apply such methodology.

    Keep it up…

    • 11

      This site is a fantastic resource for all kinds of topics related to our craft.

      • 12

        Yes. Its a site of fun although contain so much useful resources. Any one can mumble jumble with the given techniques. :)

  5. 13

    web design would be fun if it wasn’t for the clients.

    • 14

      No kidding, all of design would be fun if clients weren’t involved :)
      Of course then we wouldn’t get paid either… that’d be a bummer.

    • 16

      Sounds like you missed the point.

    • 17

      Cosmo Raoul K.

      February 25, 2010 5:49 am

      Designing stuff with no clients involved? It’s all there, man. They call it “being an artist”. Hard way to put food on the table, though. It’s our job to make our clients happy even if they’re completely bananas. That being said, clients are the worst people to walk the face of the earth.

  6. 18

    This is one of my absolute favorite non-technical articles I have read on Smashing Magazine. It was entertaining and at the same time tough some very good lessons. I would love to see more business oriented articles like this. Well done!

  7. 19

    This is what I like about Smashing Magazine: Instead of writing articles like “10 ways to do this and that… ” you present an example of how things can go wrong and how to avoid these mistakes in the process. ‘Boagworld’ is fantastic as well.

  8. 20

    Nice post!!! Every web design firm must read this. Good work!!

  9. 21

    Very interesting take on the whole subject. I think it’s important that we, as designers, remember that we are no better than our clients. Just because we understand something better than they do, doesn’t give us the right to just treat them poorly. This simply results in angry clients and lost relationships and income.

    Thanks for sharing.

  10. 22

    Best piece I’ve read on here in a while, cheers Paul.

  11. 23

    Wow. I’ve yet to build an actual client website (well, for pay), but I think this applies to a lot of design areas. It was a very good read, and I could see things going awry–I’ve even used the same rationalizations sometimes, like “Why would he be interested in the code? I’ll just tell him when it works.”

    A very well thought out article, thank you!

  12. 24

    I feel that a more appropriate name for John would be Wayne… :)
    great post!

  13. 25

    Great article, Paul! You just won one more RSS-subscriber on Boagworld ;-)

  14. 26

    Would love to know how you would answer the client when talking to him about his budget:

    “Why would you want to know about his budget? The only reason he can think of is that you want to make sure you don’t charge him less than what he is willing to give. Besides, he doesn’t really know his budget. How the heck is he supposed to know how much a website costs?”

    I’ve come across this a few times with ‘suspicious’ clients, and generally I tell them that I need to know a range so I know which bells & whistles to propose for his site, or how to create his site in a more cost-effective manner. How do you handle it?

    • 27

      This was an article of web design but has many isomorphisms to software engineering.

      I did Software Engineering (SE) in University and we learned about requirements analysis. To be honest a lot of it seemed like academic gibberish and learning of superfluous notation, but one of the ideas that stuck with me was “managing customer expectations”. The client usually doesn’t understand how software is built. Some might thing that it is as simple as lego, snapping blocks together, when the reality is exponentially increasing complexity for every feature he/she wants to add. You have to make them understand the complex implications of their requests. It gets very dangerous when feature creep begins and the project’s scope spirals out of control.

      Often the only way to force the client back into reality is to charge more for every extra feature that was not in the original requirements specification. You, after all, run a business too. One client can’t take up all your time.

  15. 28

    Amazing article Paul.

  16. 29

    sydney web design

    February 19, 2010 6:34 am

    ha ha ha

    sad but true

  17. 30

    Thanks Paul. Great article. My key takeaways from this were:
    1. Asking the client for the budget needs to be explained in the context of what dollars can buy. Using comparisons and familiar analogs helps the client figure out why we need those numbers and what the value of those dollars will be. We often say “when shopping for a house you look at comparative homes. Let’s look at some comparison web sites to see what your money will buy”.
    2. Describe everything through the eyes of the client. For example, when you talk about methodology or usability explain that it’s about “using a step by step process that reduces risk of project failure” or “maximizing conversions from visitors to customers”.
    3. Be inclusive. Over communicate at the beginning and make sure the client feels like they are not just being pushed to sign and then abandoned. There is no such thing as too many emails or phone calls. It reduces stress and churn.
    4. Educate the client. The welcome packets we send out and double-kick-off meetings we do with our clients build comfort and confidence which can only lead to good things. We can all improve this by having frequent workshops for our clients about design and process in general.
    5. Give the client things to do. Almost all our clients want to be part of the process and like having responsibility in getting the work done. Explaining what their roles are and how they can make the project successful is key to them being part of the solution.

    • 31

      Richard, not sure I agree with point #3.
      Over communicating in the beginning, John might think you don’t know what you are doing and may regret signing with you.
      And why just in the beginning? Communication is key throughout the project. If parts of the project take more time…aka are more meticulous and slow showing results… communicating that with the client as well. All milestones of our design and development should be forwarded with the client, whether he likes it or not. If John comes back and says “what is this?” … take a deep breath and communicate more… he is paying you remember.

      Great article SM
      Richard, cheers~ let’s go to the bar and have a drink on John!

  18. 32

    Great post. Dont forget the time wasted waiting for media such as text/logo’s/photo’s and site structure infomation, and that it extends the deadline. Plus having to copy the written material and optimise the images, which is easy I suppose.

  19. 33

    Reminds me of the “How a Web Design Goes Straight to Hell’ from The Oatmeal.

  20. 34

    excellent post. really enjoyed it.


↑ Back to top