Team
|

Linked: Five Skills That Help You Lead Remotely

I like all of Kevin’s 5 skills, but this one to me is paramount because when I’ve been part of a remote team, every single failure ultimately came back to this:

“Be a flexible communicator

Certainly, leaders must be good communicators. But when your team is spread hither and yon, you must be proficient and comfortable with a wider variety of communication tools (more than face-to-face and email). At least as important is knowing the situations in which each tool is more appropriate and effective. These considerations require a higher and more complex set of communication skills.”

I’ve often described it as needing to over-communicate, because to me it’s not enough to send an email and assume everyone saw it, and read it, though they should do that. There needed to be follow-up, and clarification often. Or, a comment made in the middle of a team meeting needed to be flushed out more fully, with a written communication that could be referred to instead of having that comment be the end all be all of what was being expected.

In short, you must always be vigilant about everyone being on the same page. When something is off, it will take a lot longer to find that out when your team is remote, and a lot longer to get it corrected.

That being said, it’s possible, and Kevin’s list is an excellent way to think about how to do it.

https://blog.kevineikenberry.com/leadership-supervisory-skills/five-skills-lead-remotely/

Similar Posts

  • An Important Balancing Point – Be Professional Always

    I talk a lot about the Great Resignation and employees taking control over their own careers instead of just following along with what the company wants them to do. I stand by it, and like Mark, I am also thrilled that we are seeing a shift in the balance of power as employees start to recognize their value. But, he also raises an important post in the LinkedIn post.

    As long as you are there and getting paid you owe them your best. Be professional, even if the company isn’t. Do your job even if you plan on quitting tomorrow. Commit your best efforts to the project even if you don’t agree with it.

  • This Week’s Links (weekly)

    Brace yourselves for the best WordPress yet tags: Blogging MM Technology Assisted Review – The Gavel Has Sounded tags: LitSupport MM Good Processing Requires a Sound Process – eDiscovery Best Practices tags: LitSupport MM “Big-A-Law — Y U No Collapse Already?” tags: LitSupport MM Courts Struggle With Determining Reasonability of e-Discovery Vendor Bills tags: LitSupport…

  • |

    Linked: Actions of a good boss turning into a bad boss

    It’s true. Our words and actions, especially when things are stressful, undermine what we think we are. You may think you’re being a good boss, and maybe most of the time you are, but those days when you’re stressed and short with people or the days you decide to not deal with a problem, become the days that define you in the eyes of the people who report to you.

    To them, you aren’t just another person having a bad day. You are the person who controls their success at this company for better or worse, so it’s not just you having a bad day, it’s the organization having a bad day, directed at them.

  • Linked – Tell Me Seven Times. No – Make that Three.

    Sometimes communicating effectively feels a lot like over-communicating. Especially if your team is hybrid or remote, go ahead and over-communicate. There’s no telling how much better your team will understand what you were trying to tell them when they hear or see it a number of times.

  • | | | | |

    And The World Keeps Turning….

    Apparently, while 2011 was a year of huge changes for me, the changes just keep coming in 2012. I won’t be relocating again, but I will be switching jobs, and that is going to also impact what I’m doing on this site. I’ve accepted a Litigation Support Trainer position with AccessData. I’ll be based out…

  • Linked – Why public chats are better than direct messages

    But, here it the real world, this doesn’t always work out very well. You really need the culture to be one where everyone is used to working asynchronously and checking the public channel for chances to help out the team. It sounds like that is both the expectation and the reality at this company but for a lot of us the reality is very different. Posting something in a public channel where no one gets a notification that a message is being posted generally means no one sees it. So we go back to using private channels or tagging people in the public channel in order so that we purposefully interrupt them. We haven’t developed a culture where asynchronous communication works and I suspect it’s because we don’t really want it. We want people to respond to us now. We don’t trust them to get back later and, to be fair, we don’t give our peers reason to trust us because we spend all of our time putting out fires and frequently forget to get back to people.

    In many cases, it’s a humblebrag. “Oh I saw your message but then I got involved in important things because I’m an important person and never got back to you”.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Find out more about Webmentions.)