
Andy Hunt and Dave Thomas’s The Pragmatic Programmer is a bible of sorts when it comes to effective programming. One of the strongest take home points from the book was their advice to gently exceed expectations.
It’s one of those little nuggets of advice that is so subtle that it’s easy to go in one ear and out the other. However, if you follow it, you’ll probably see returns far greater than the effort it takes to achieve. It’s one of the quick wins in life.
In practice
So what’s it all about? Let’s take an example. Say you have a client who wants you to build a contact form. Their requirements are simple: they want their customer to be able to fill in their contact details, press ’send’ and get a response to say the message was sent. Your to-do list on this project might look like this:
- Mark up form
- Design form
- Install code to send email
- Mark up feedback page
- Design feedback page
The client needs it done in a week. Based on the requirements, a week is just fine.
So the expectations are set. Your client expects you to deliver a fully functional, well designed contact form in a week, based on the to-do list above. There are a few possible outcomes in this scenario.
Undesirable outcomes
Let’s look at the worst outcome first. You half ass the whole project. It takes two weeks and even after all that time the form doesn’t work and it looks like shit. No one’s happy. No one wants this. Your client expected you to get the work done. Even if it was a bit late, at least it would work. Their expectations haven’t been near met, and they won’t be working with you in the future.
Alternatively, you could work all night to get the whole thing done in a day. Not only that, but you added a content management system that allows customisation of every element on the page. You even throw in a colour picker, in case your client’s customers don’t like your design. You’re fucking shattered, but when you call your client the next morning, they’re amazed and delighted at your performance. Totally worth it, right?
It’s not that simple. You’ve just greatly exceeded your client’s expectations. Exceeding expectations is the point of this post, but if you go too far, you don’t just exceed them, you change them. The next time your client comes back for more work, not only will they not believe you when you said that you haven’t completed the work in half the time, they’ll be disappointed that you didn’t go to the same effort as before. It’s a vicious, unfair reality.
Meeting expectations
Right in the middle there are two more options: you can choose to meet your client’s expectations, or you can seek to actively, gently exceed them.
Meeting expectations is straightforward: you deliver your work exactly as you said you would. The contact form works and looks as you described and you delivered bang on one week from when you said you would. This is cool. In fact it’s better than cool, it’s very good. Your client will probably come back for more work. You’ll probably get a recommendation.
But there’s something missing. Something of an anti-climax. Your client got what they wanted, but without pizzazz, without any ceremony. You’ve failed to create the happiness that you did when you stayed up all night, killing yourself. There is a better way, almost as effective at creating client happiness, but without the pain.
Gently exceeding expectations
Gently exceeding expectations involves giving your client something that they didn’t ask for, that you know they’ll appreciate. The important thing though is to give them something that won’t cost you very much to implement.
Let’s say you have a couple lines of javascript from a previous project that lets you submit the form via Ajax, with a smooth transition and it’s all gracefully degradable. Your client didn’t ask for it, but you know that it would improve their customers’ experience. It costs you about 10 minutes extra time and effort. Let’s say you’re able to deliver this on the morning of the one week deadline.
Your client sees that the job was done and they have a full day to review it. Not only that, when they review it, they see that it works better than they expected. They’re delighted: They got more than they asked for, even if it’s just a little. More importantly, they know that you’re looking out for them. They know that you care enough to go an extra mile to make them happy, even if you only went an extra inch.
Extras that cost a little gain a lot
You might look at these two small ‘extras’ and say they’re not worth it. Small, simple extras, however, are the kind of things that take you from ‘good’ to ‘great’ in your client’s eyes. They’re the difference between the deli that gives you a free muffin when you buy a sandwich and the one that stiffs you for some butter. The ice cream parlour that lets you taste the ice cream before you buy it. The restaurant that comps your champagne at the start of the meal. They’re the kind of gestures that cost a little, but keep customers coming back again and again.
The next time you’re working on a project, look for ways to exceed your clients’ expectations in small ways that cost you little, but that you know they’ll appreciate. Throw in that feature they’ve been asking for that you know won’t take long. Fix the bug that’s been bugging you, and probably them, but they’ve not got around to contacting you about. Your clients probably won’t know why they’re so much happier working with you, but they sure as hell will be.
10 Comments
Great post Paul - we’re clearly on the same page when it comes to things like this - I put a post up about it a few weeks ago:
http://blog.echolibre.com/2008/12/recession-customer-service-value-for-money/
Posted by Eamon Leonard at 2:16 pm on 16 January, 2009.
Also plays into your availability. “Just because I’m available to help you immediately once, doesn’t mean that I’ll always be able to respond to your issues immediately”. O, I hate that conversation.
Posted by David Barrett at 2:18 pm on 16 January, 2009.
Yup. The trick is to try not and change expectations and to keep the sugar sufficiently small that it doesn’t kill you. It does take a bit of practice.
Posted by Paul Campbell at 2:38 pm on 16 January, 2009.
Nice post Paul,
I read that book sometime back in 2007, but had forgotten about that particular piece of advice in the book.
I’ll put my hands up and admit that I’ve been guilty of greatly exceeding one client’s expectations at the expense of another’! Probably because it just interests me more. I’ll need to try harder to cut that out of my work.
Your post has made me think about reading the book again. It’s the kind of book that should be re-read every couple of years. An absolute must for folks in our industry.
Posted by Iarfhlaith Kelly at 3:42 pm on 16 January, 2009.
That’s a really great post, Paul, well explained. You’re right; it is easy to hear it and not take it in. Your examples made the point perfectly.
I don’t think i really understand what the graph was all about, though. What’s the 0-80 scale all about, and why does it change so much between Thursday and Friday? It doesn’t seem to have much relevance to your post.
Posted by aimee.mychores.co.uk at 7:18 pm on 16 January, 2009.
Aimee, the graph is really only an illustration, not really supposed to say very much. I suppose more to say that the gently exceeding expectations isn’t too far from just meeting them …
Posted by Paul Campbell at 10:24 pm on 16 January, 2009.
Afraid I didn’t understand the graph either, Paul, but I certainly like the concept!
Posted by Breandán at 7:37 pm on 18 January, 2009.
Nice read Paul. I’ve found that especially applicable to turnaround time in the past.
Sometimes I’ll just want to get an update out of the way, so I’ll set other work aside and get it done straight away. But then the next time the client expects you to get it done straight away the next time, when you could be swamped with other work.
Sometimes I’ll hold off making the update ‘live’ for a few days, that way they don’t get used to the quick turnaround.
Posted by Lee Munroe at 10:13 am on 20 January, 2009.
Interesting post.
Thanks
Posted by Dee at 2:23 am on 30 January, 2009.
The graphic makes sense to me. You take someone so high that when you are ordinary next time (who can be god every day), disappointment sets in.
Doesn’t just apply to client work, but applies also to girlfriends and boyfriends. The bell curve is generally much better.
So by gently exceeding expectations, one stays in that happy zone. Even more important with clients than private life, where in principle lots of people are happy enough to get the roller coaster.
Posted by Alec at 4:01 pm on 31 January, 2009.
1 Trackback
[...] Gently exceeding expectations Exceeding expectations is the point of this post, but if you go too far, you don’t just exceed them, you change them. The next time your client comes back for more work, not only will they not believe you when you said that you haven’t completed the work in half the time, they’ll be disappointed that you didn’t go to the same effort as before. It’s a vicious, unfair reality. [...]
Posted by Weekly Digest, 1-18-09 - almost effortless at 7:14 pm on 18 January, 2009