J-U-S-T. Those four characters can be significantly detrimental to a software development process. In this blog post, I’ll describe how the “just keyword” can affect team’s communication and how to avoid misusing it on Slack.
Let’s “just” do it
You’ve probably been there. Your product manager shares his brand new plan on the Slack channel:
“Why don’t we just add this cool new feature to our application?”
or your colleague got the wrong idea about scaling after reading a HackerNews story:
“Let’s just migrate our infrastructure to Kubernetes…“
“Just” is toxic and dangerous. It implicitly suggests that the proposed task is straightforward. It undermines the discussion about the issues that might pop-up during the implementation.
There’s no “just” in software development. Most of the tasks turn out to be more complex than anticipated. “Just tickets” tend to drag, evolve into epics, miss deadlines and hurt the team’s motivation.
How to use Slack to get rid of “Just tickets”
I want to propose a solution to the “Just” problem. Lexically there’s never a need to include the word “just” in a sentence. You can always omit it without altering the core meaning of your message.
You could discourage using the word “just” in communication. Slack offers a simple feature that will let you automate it. Introducing Slackbot triggers:
You can configure Slack to automatically send a custom message whenever a trigger keyword is detected. In settings, go to Customize > Slackbot and enter your desired trigger and response.
It could be pretty spammy to start with, but your team should quickly adjust and stop using the forbidden keyword. If someone does use it, the alert message will be a fun reminder to stop and think twice if the “just” idea is really that simple.
So why won’t you just give this communication experiment a try?
BTW if you’re looking for more creative ways to enhance your communication on Slack, you can check out Abot for anonymous messaging and polls. It’s highly configurable and supports various usage scenarios.