By Peter Bell

Should the Word "Just" Be Banned in Client Communications?!

I first remember coming across this a *long* time ago in Pirsig's "Zen and the Art of Motorcycle Maintenance" back in high school, but it seems particularly applicable to client requests . . .

"I just want you to add another field to the form". "We just need to make sure it works in IE5". "I just need it to work with MySQL as well as Oracle". "We just need to see what admin user made what changes". "We just need people to be able to buy stuff online". "It just needs to integrate with Quickbooks" . . .

How many times have you found your blood boiling as a client makes what to them seems an innocuous request - often towards the end of a long and difficult project? Perhaps they want to change the db engine or the object model the day before launch. Maybe you've just created a sophisticated JS based site and they mention at the end that they do indeed need it to work in IE5 despite previous assurances that IE6+ would be fine.

What is interesting to me is that if you remove the word "just" from any of the above sentences, they are much less annoying. If a client tells you "I need it to work in IE5", you can explain that it's possible, but you'd have to change the entire front end, cut back on the AJAX, double the budget and add two more months to the project. They may say yes or no, but they asked for something and you can explain the implications and make a recommendation. However, when they add the word "just", they are taking the same request and framing it as technically being no big deal to do - an estimation they're usually not capable of making.

Just an observation. Anyone else notice this one? I'll usually just repeat the question back to them without the "just" and pretend they never said the word. Any really good approaches for handling the "just . . ." requests from clients?!

Comments
Hey Peter, you've given me an idea. From now on in all my quotation specs I will charge £100 per usage of the word JUST. In other words every time a stake holder uses that word - they will be invoiced.

Happy writing!

J
# Posted By Jatin Nanda | 10/29/08 3:08 PM
Yeah, that's what I was speaking to before when I mentioned "availability" as one of a variety of cognitive biases that can negatively impact client negotiations. http://en.wikipedia.org/wiki/Availability_heuristi...
# Posted By ike | 10/29/08 3:08 PM
Yes, and the word "etc." is dangerous too. "User accounts will have a first name, last name, e-mail address, phone, address, etc.) " Some clients always have a tendency to come back and fill-in what "etc." means. "Okay, want those and these 500 other fields." Grr...
# Posted By Ryan | 10/29/08 3:21 PM
I've actually told clients - the words 'can't you just', are banned from this meeting. Every time you think 'can't you just', it never is, as it is always more complicated than that'.

It has actually worked a charm... as you get stuff like this happen:

'Can't you just build... oh.. I guess it's not that simple. Hmnnn... well, we would really like a whole social network, how long would that take?'

Which is great.

Client eduction is fun ;)
# Posted By Mark Mandel | 10/29/08 3:27 PM
I also attempt to ban the word "should". How many times has the phrase "It should just work." been tossed around and created no end of head-aches?
# Posted By andy | 10/29/08 4:22 PM
Ha ha, right on Andy. My boss's two favorites were "It shouldn't be that hard" and "It shouldn't take that long." He would literally add one of those two phrases to every feature request. Finally we started calling him on it in a friendly way -- I don't think he realized he was doing it every single time -- and he stopped doing it.
# Posted By Josh Nathanson | 10/30/08 3:21 PM
@Jatin, Sounds like a good idea - let me know how it works out selling that to your clients :-)

@Ryan, We don't ever allow the word etc. We just replace it with a reasonable estimate of what etc means or remove it.

@Mark, I like it. That's pretty much the experience we have too as the clients start to get educated.

@Andy, I guess it depends how the word is used. I sometimes use should to describe use cases "an administrator should be able to xxx". Remove "just" from the phrase and it becomes "it should work". Then at least you can say "why? was it in the specs?!". For me, "just" is the worst.

@Josh, It's something I come close to saying sometimes when I'm passing a project off to someone, but I try pretty hard not to say it any more as I know how annoying it is from the other side.
# Posted By Peter Bell | 10/31/08 8:54 AM
Another to add to the list: whatever:

"Can we set up counters to check transactions each month or whatever?"
# Posted By Julian Halliwell | 11/4/08 3:24 AM
BlogCFC was created by Raymond Camden. This blog is running version 5.005.