Text has its place

• Pay attention to signs text isn’t working
• Don’t be afraid to move the conversation
• Meetings don’t solve miscommunications

Cover Photo by Fabian Møller on Unsplash

You only need two. Two comments, two messages, two notes, revisions, replies, only two attempts to create a shared understanding by text before you need a better way to communicate.

Some things are easy by text. A message to a colleague to remind them about a task, a reply to a meeting invite to say you’re bringing someone, a quick screenshot of a funny conversation with another team member. These are all things you already share understanding for.

Text is an easy way to quickly give feedback or ask a question when you’re between meetings or in the middle of something but don’t want to forget. There is a sad reality though. We all know using text is a troublesome way to share ideas sometimes unless you put in serious effort to construct it flawlessly, we always think “this is pretty simple, they’ll understand it” and hit send only to regret the next 4 hours of back and forth messaging and the frustrated organization of a meeting with 5 people to make sure everyone is on the same page because sadly that miscommunication from that one quick message wore away at the trust you each had that you understood each other or that anyone understood what was going on.

While I have you! I'll soon be offering career and code coaching for programmers or people considering a career change into tech. If you're interested send me an email or check out all the experience you could benefit from on my LinkedIn

The rule of 2

Photo by Joanna Kosinska on Unsplash

My rule is two. You get one message from you sharing an idea, and one reply from the person you shared it with. With that, you will either be able to tell if they’re on the same page as you or not. If they’re not, time to call or meet at each other’s desks. This goes for emails, replies to code reviews, messages on Slack or Teams, any form of back and forth via text.

The rule of 2 applies only to sharing an idea. If you're just having a fun conversation or doing some kind of basic administration chat over team chat that's fine. It's when there's a concept that may have more than one layer of learning required to understand it that it becomes an issue.

Meetings spread ideas and don't solve miscommunications

Photo by Alexis Brown on Unsplash

The second part of this rule is no meetings. It’s hard enough getting one person on the same page, let alone 5, or 10, or 13. After that second message, you find time for a quick talk one on one to get on the same page. After sharing the idea in a way that one person has understood it, the second, third, and any other number of times you have to share that idea will be easy. Just repeat the one sentence that likely made it click for that first person, or the one detail you shared that soothed a concern they had that you hadn’t thought about.

Two messages and a 5-minute call could be all the preparation you need to know the key points and be prepared to share again with anyone.

If you’re the one replying, if you’re the one having an idea shared with you, and you don’t feel you’re on the same page, take responsibility for that one on one conversation too.

Level up your career with me

I've been working as a programmer, programming teacher, writer, and coach for over 15 years and soon I'll be offering one on one career and code coaching for anyone looking to level up their programming skills, get a path to that next raise or promotion, or looking to enter a new career in tech.

If you want to work with me send me an email or check out all the experience you could benefit from on my LinkedIn.