“JUST”
It's one of the worst four-letter words I know. Whenever I catch myself using it, I stop and apologize. And when I hear it, I hold up my hand and stop the person speaking.
Let me give you some examples from last week…
- “Just put a form up to collect their e-mail…”
- “Just make it so they can login with Facebook…”
- “I'll just throw it in a new database field.”
- “We can just launch a new database server…”
- “Lets just let them post notes, like Twitter does…”
A synonym I often hear is “simply”.
- “Let's simply use Redis for this…”
- “We'll simply spin up another AWS server…”
- “It should be simple to reuse the Atlas library for that.”
If you use the words “just” or “simply”, you might have forgotten how hard the technical details can be. I cover how to fix this in Chapter 2 of my book, 7 Habits that Ruin your Technical Team.
Or, you might be pushing the team too hard, and glossing over the details. That's covered in Chapter 5 of the book.
What if you're not saying it, but you're hearing it?
Then it's time to stop the conversation, and politely ask for the missing details. This used to be hard for me, because it made me feel like I was asking “stupid” questions. For many years I felt that if I asked people to explain what they meant, I'd look dumb. Or unprofessional. Or I'd be wasting their time.
I finally realized that professionals aren't content with generalities or vague requirements. They stop and ask for specifics, even at the risk of looking dumb. They have the confidence to know they aren't dumb, and to not pretend to understand something they don't.
You can use phrases like…
- “Let's pause so I can clarify what you mean. Are you suggesting that we…”
- “Wait, before we continue, can you explain that feature more?”
- “Going back to what you said, can you explain how you would implement that?”
- “I might be a bit slow here, but can you explain?”
Lullaby Language
Gerald Weinberg calls “just” an example of Lullaby Language, which “lulls your mind into a false sense of security, yet remains ambiguous enough to allow for the opposite interpretation.”
He groups it with words like “should”, “soon”, “very” and “trivial”. All perfectly nice words that we see every day, but can carry a lot of hidden ambiguity an assumptions.
How I learned to stop the conversation
My boss, Milind, was great at this. When I was promoted to Team Lead I was brought into a whole new world of meetings and discussions, and I would keep my mouth shut when someone used the word “Just”, or spoke in vague terms. I didn't want someone to think I wasn't fit for the job, or that I was having trouble keeping up. Instead, I nodded and smiled, looking like I was tracking with them.
But Milind knew it was dangerous to accept generalities or misunderstandings. He would simply stop a large group conversation with the phrase, “Maybe I'm missing something here, but can you explain that in more detail?” Everyone would look at him, the speaker would pause, and then back up to cover the “just” part in more detail.
And low and behold, 90% of the time it was revealed that the person who glossed over the details had oversimplified something important. Or, was simply wrong about an assumption. That means 90% of the time we were able to correct the discussion in the moment, and move forward with better information.
And the 10% of the time there wasn't a problem? The explanation simply clarified everyone's understanding and we quickly moved forward. Or, it opened the door to other unspoken questions from the group.
Watching Milind do this made me feel confident enough to try it. Now I do it often, as really understanding what someone is telling me is the most important thing. It allows me to correct misunderstandings and assumptions in the moment, instead of wasting time working in the wrong direction.
Now it's your turn
How often do you hear the word “just” or “simply”, and just nod in agreement?
How could you pause the conversation and change the conversation to move in a different direction?
How often do you use these words, especially when setting expectations or defining requirements?
Oldest comments (31)
I've been guilty of using this kind of phrasing passive aggressively to imply someone was overthinking a problem, while also feeling the sting of hearing it told to me under that context. In most cases, there were other issues at play providing a communication block that we had to overcome instead of slipping in generalizations that can be demeaning.
Thanks for a really illuminating article.
Could you explain some of those communication blocks you mention?
Fantastic article! This is so very true...I've seen it many times, but never realized that the word "just" or "simply" were such reliable red flags of oversimplification. I'm going to be watching how I phrase things, and following your tips in my own job as a Lead Developer. Thank you!
Not too long ago. I heard it countless times in a week from a Data management staff one of my company's clients. He's grossly unaware of a lot of things and believes you can "Just" write code to make things work without taking a lot of things into consideration (He programmed briefly in the past some years ago and feels he knows a lot about software development).
Initially when i joined the company, Like you I'll always nod my head in agreement so i don't look stupid in front of everyone but then i started to realize that "Just" was really hurting me when no one was watching. Most times i'll spend long annoying nights trying to meetup with unreasonable deadlines that i created for myself because i accepted that this was "Just" a new feature that could be implemented "easily".
Now once i hear the word "Just", i do a quick analysis in my brain, If the feature is going to take more time than expected, I waste no time in speaking up and explaining why this isn't "Just" another easy task or new feature.
Glad y'all found it useful. :)
I've been guilty of it, and had it inflicted upon me, more times than I can remember. If you liked this, Chapter 2 of my book 7 Habits that Ruin your Technical Team talks more about this sneaky problem, and other bad habits you might have seen.
I'm glad this is not only me that has a rage about this! My team have gone and created a chat bot called brettbot that has a small rage every time somebody uses the word "Just" on our team hipchat room.
Hadn't heard the term "lullaby words" before, but 💯 – you can make anything sound simple, with the word "just"!
I've managed to almost completely purge "just" from my vocabulary, at this point. And "should", too! I wrote a whole blog post about that journey, when I first started it: blog.entire.life/no-more-shoulding...
I love the idea of stopping conversations to get more clarification when this word is used. I'm gonna start using that technique. 👌🏼
just with the word "just"* :P
Yes! There are quite a few problematic words! 'just', 'actually,' 'easy,' 'real,' 'true,' 'obvious,' even 'deserve.' I dig in here with some ideas for alternatives. :0) blog.scottnonnenberg.com/avoid-the...
I read somewhere that "Just" is a four-letter-word that means, "someone else's job."
"Why can't you just get the color and compare it to one of our 6 brand colors, and if it is, output that brand color on our web page," was an actual thing asked of me. I had a client that wanted to just put a camera outside their HQ, just capture the predominant color that people were wearing, and just turn that color into one of their 6 branded colors that they could just put on a homepage, represented in an animated circle.
And because of that word "just", they thought the animated circle was the hard part. Because I could just compare one of 16 million colors captured in RGB to one of six... because color is just that simple.
"just" seems to be a mask that hides and summarizes a load of technical details. For the non-developer, they're details that are yet to be considered. For the developer, they're details yet to be vetted and validated.
Just is an expression a lot of Clients of Hell use.
Great article "Just" is really a terrible weird when it comes to requirements. Masking complexity is in it's nature.
At first I thought this would be sort of a nitpicky article on how to "communicate absolutely perfectly with your team for hyper-efficient productivity," but it makes really solid points on the role of embarrassment (or perhaps pride? or general unwillingness to interrupt?) in team communication.
I'm currently lucky enough to be part of a team that openly encourages interruption/discussion, but I've been in teams before where asking for clarification gave you the feeling that you were being a bother. This article should be read by everyone.
What a fantastic article! I especially like the phrases we can use when we find ourselves in this situation.
Good post.
I have noticed that I have used this word to belittle what I do/my thoughts. I almost used it while re-tweeting and suggesting a heuristic based on the insights in post and comments.
It's interesting how the usage and intention of the word was changed.
From this:
just
adjective
1.
based on or behaving according to what is morally right and fair.
"a just and democratic society"
synonyms: fair, fair-minded, equitable, even-handed, impartial, unbiased, objective, neutral, disinterested, unprejudiced, open-minded, non-partisan, non-discriminatory, anti-discrimination; More
adverb
1.
exactly.
"that's just what I need"
synonyms: exactly, precisely, absolutely, completely, totally, entirely, perfectly, utterly, wholly, thoroughly, altogether, in every way, in every respect, in all respects, quite; More
2.
very recently; in the immediate past.
"I've just seen the local paper"
synonyms: a moment ago, a second ago, a short time ago, very recently, not long ago, lately, only now
"I just saw him"
To shrugging things, thought and even people around as "That's just somebody..."
Now that I think I've used it also when I tried to explain why I did the thing that went sour - "I just thought that this will be helpful" In blame/shame strong culture this most likely would sound as poor excuse. In healthy environment it could sound more like insecure answer.
(:
I will be more conscious on this one. (:
Now I do wonder how often and with which meaning I use this word.
What you seem to be irritated with is just someone's vision to be later developed. I can actually see nothing bad in using this 4-letter word. It is often an equivalent of picturing that - what a web page, web app, whetever device is supposed to do - should seem so easy and simple to end user.
I admit, sometimes, the word "just" seems to be used in a way as if the speaker claimed to have just found the simplest possible solution among the ramblings and wants to put an eureka end to the discussion and receive all the glory.
At any rate, "just" should only be an introduction to having a more detailed discussion, having the person explain their expectations, perhaps specify preliminary acceptance criteria, and the tech lead should then come back with the expense of "just".
As a front end developer I know that non-techie people tend to think that we have an arsenal of magic buttons that we just keep in our secret vault, and when a "just" comes - we probably JUST copy and paste it into the code.
But usually visionaires don't mean to offend developers or tech leads, and are open to take feedback.
When I sometimes rethink my reactions to this "just"-type of talks, I find my overreacting to actually be a problem in my bad interpretation of someone's intention. I think Milind's way of handling the 4-letter word is perfect as it throws the ball into the right hands at the moment of saying that word.
+1. You should develop this into a full article. I can relate to what Marcus is saying because I've been at the receiving end of the just word, but I also know that not everybody is out to get you by just using just
As a kid I read that John Lennon thought the word "just" was useless, and I've always remembered that and I notice when people use it like that!