Skip to main content

Tag: communication

I’ll take it slow today

It’s one of the trends that came with WFH being more accepted (hello, COVID, my (old) friend) in the workplace.

People will often show up online and say something like, “I’ll take it slow today,” “I’m not 100%, but I’ll try to do something,” or they will just put a battery icon with almost depleted energy as their status, followed by some text along the lines I mentioned previously. It’s supposed to mean that even though the person is not feeling great, they’re not feeling that bad, so they can’t do their work. The only caveat is – that no one knows for sure what it means.

Have you noticed the trend? Are you one of the “I’ll take it slow today” people? Don’t worry; I’m not judging. I want to tell you why this may not be a great idea. Even though it’s probably used with the greatest intentions, the whole “taking it slowly” thing is disruptive for both sides—the one taking it slowly and all the others who usually interact with that person.

Here are some reasons against it:

  1. Expectations are not clear. What does your status mean? Should people not contact you or set new meetings with you? How long will it take you to respond to the messages? Can your coworkers still count on your pre-agreed workload being finished while you’re taking it slowly?
  2. You’re creating an unhealthy culture. By sending out a message that you’re working while not feeling well, you’re normalizing working while being sick. It’s even worse if you hold a more senior position in the company. Remember the “lead by example” motto.
  3. The evaluation period is not divided into slow and regular days. There’s no “working slowly” option in the management’s calendar. No one will adjust your evaluation to account for you not being 100%. Even worse, you risk making mistakes when you’re not feeling well. It’s a lose-lose situation for your career progression.
  4. You make others feel guilty. People see your status, and they evaluate whether their request is important enough to bother you while you’re not feeling well.

If you’re not feeling well enough to work, don’t. Focus on recovery and return to work when you can handle your tasks as you would regularly. If you decide to work even though you’re under the weather, clarify your availability and scope of work. If you choose to follow that path, here’s an example of how to handle that communication.

“Hello [team, person]. I’m not feeling that great today, but I’m OK enough to take the meeting with our stakeholders, as it’s a big pain to reschedule. I will be online from 11:30 to 13:00 to see that through and create the meeting notes. After that, I’ll take time to recover, and I’ll be offline. I’ll keep you updated on my status!”


When it comes to communication in the workplace, try to be as precise as possible. Also, take care of your health, mental and physical.

Considerate Digital Communication

Considerate Digital Communication is the practice of using digital communication tools in a respectful and mindful manner that prioritizes the time, attention, and well-being of others. It aims to reduce digital noise, prevent spam-like behaviors, and promote a more efficient exchange of information.

You probably recognized several patterns of non-considerate communication in your day-to-day work. It’s a big part of why we must use “mute buttons” and suppress notifications in our instant communication tools such as Slack, MS Teams, etc.

There are many examples of abusing and misusing communication tools that make our lives a bit noisier than they should be. Maybe you’re also the culprit, and you’re not even aware of it.

Here are four guidelines for being more considerate of people’s time regarding how you communicate digitally.

Note to readers: I coined the phrase “Considerate Digital Communication” as an umbrella term for anything fitting the definition at the beginning of the article. If you have any input or ideas for more guidelines, I’d love to hear those. The best way to contact me is by email, which you can find on the homepage.

One message ought to be enough

If you send someone an email, tag them in the project management app, tag them in another channel, etc., DON’T immediately send them another message that you did so. If you created any action that resulted in the notification for the receiver, don’t double it, reminding them about it immediately. It creates noise and it’s spammy behavior.

Maybe you’re frustrated that people are not paying attention or ignoring crucial messages, but you’re not doing anyone favors by nannying your colleagues. Everyone is responsible for doing their work and following up on the work they’re responsible for. If that’s not working out, that’s a topic for another conversation (and a serious one). That behavior is never fixed by repeatedly messaging someone about the same thing.

Courteous, properly spaced reminders are, of course, fine. A good example of this would be reminding a group of meeting attendees about checking their prep work before the event that was scheduled some time ago.

Discourage the stream-of-consciousness writing

Definition: Stream of consciousness is a narrative style that tries to capture a character’s thought process realistically.

Here’s a hypothetical example of stream-of-consciousness writing about a problem John is trying to relay to Tom:

10:23 AM John: hey, Tom
10:23 AM John: two users called this morning to say that our shop is really slow
10:26 AM John: I don’t know what’s going on
10:28 AM John: can you help me find the problem
10:29 AM John: I tried to contact Sarah, but she’s offline
10:32 AM John: one user just sent me an email that everything is working fine now, but
11:13 AM John: hey, I checked the logging information for the database
11:18 AM John: I think it’s something about the regular maintenance on our provider’s side
11:21 AM John: ah, it’s not, it’s something from our side
11:23 AM John: I’m trying to think if I actually changed something, hmmm weird
11:41 AM John: ah, to hell with it; it’s all okay now

This type of communication is overly time-consuming and confusing. Let’s say that Tom opened the chat at 10:23 AM. He would stare at the screen, looking at the “user is writing…” indicator, waiting for the next message of revelation from John just to be disappointed by receiving another bit of John’s incoherent rambling.

Instead of writing a stream of short messages (generating multiple notifications in some apps), take the time to write a self-contained message. Add as much context as you can and wait for the response. If something is urgent, there are probably other (and better) ways to escalate.

Use cross-posting sparingly

There’s nothing wrong with cross-posting, but some people tend to do it excessively. Before cross-posting, think about the people that make up the channels you’re cross-posting to.

Many companies will have dedicated channels for announcements and general discussions where people are usually added on their first day of work. If you post something there, there’s little value in posting the same thing on other channels.

Cross-posts make sense if an announcement is applicable to two or more teams that lead their discussions in different channels. Companies with many cross-posts on their communication platform could benefit from better channel organization and communication strategy.

If you’re on the receiving end of many of the same messages that were cross-posted, raise that with your manager (or anyone able to help improve the processes in the company). Maybe you can investigate the root cause and hopefully make some improvements!

Avoid direct messaging people in off-hours

One of the advantages of the modern workplace is the flexibility. A lot of work can be done nowadays from anywhere, and what’s more important for this section – anytime. That means that our digital communication spaces are occupied and used 24/7.

There’s nothing wrong with that fact, but it inadvertently brings that FoMO (Fear of missing out) phenomenon with some people. Even if the workplace relentlessly works on telling its employees they shouldn’t check the work tools in the off hours, FoMO can often kick in. That’s why we can and should be considerate to each other by scheduling the messages if possible.

Most, if not all, instant messengers can schedule a message in some way. If you need to message someone directly or tag them (anything that will trigger the notification) in some channels and you’re working at a different time, schedule that message for the company’s regular working time.

By doing that, you’re also helping create a culture that respects the work-life balance and doesn’t add unnecessary pressure.

Tell me when I suck

I recently read a short blog post titled Saying the Difficult Things. It was trending on HackerNews and spawned an interesting discussion.

People wrote that certain cultures are more direct than others, mentioning Dutch as an example of directness. Some said that being direct and unfiltered is a way to go, while others showed more appreciation for the somewhat filtered and more nuanced type of critique.

When it comes to receiving critique, I would choose directness and rawness all day long. That doesn’t mean I want to deal with assholes and sadists though.

If you comment on something I’ve done with “This is complete shit!”, without backing that up with at least one “why”, I will label you as an asshole, but…

If you comment on something I’ve done with “This is complete shit because x/y/z!”, I will thank you for your feedback. Hell, if that “x/y/z” is detailed and you put some thought into it, I’ll buy you a beer!

I’m not saying you should start your critiques with words like “This is complete shit”, and I think that you should always be polite and considerate towards people. Not just while giving them a critique, but always.

What I’m saying is that when you work with me specifically, you can be brutally direct and honest. You can even use adjectives that society deems unacceptable. You don’t have to sugarcoat it, and you don’t need to start with something positive pulled out of thin air only to ease me into the shit part. Just tell me what exactly is the part that’s shit and why.

PS. I wrote this so I can share it with all the people I’ll be working with in the future.