[SirLJ]

Here is my advice, based on many years managing a remote ops team across the continent: you do not need another tool!

The good old email and phone is just enough, providing you trust the people you work with (if you don't then this is on you as a manager an no tool will help you)

Ask to be cced on the the important problems/projects and have 1 team meeting for few hours Wednesday afternoon, so everyone can share not only work related stuff, but encourage the team to talk about Life, the Universe and Everything... Get to know the people who work with you, have all hands meeting for few days every year, go out for drinks ...

Have their backs, no netter what, even if you risk yours...

Those simple steps should be enough and have served me well over the years, because, really noting beats working form home...

[Zhyl]

A man passes a builder who is using a hammer to drive screws into a plank of wood.

"You should use a screwdriver for that," says the man. "It's more suited to the job, you will find it easier and you will be more productive as a result."

"Thank you," said the Builder, taking the screwdriver.

The builder then hits the screw as hard as he could with the handle. His results are not impressive. "I think I'll stick to the hammer," he says, throwing the screwdriver away.

[runawaybottle]

Definitely. Good ol’ email is really for amateurs at this point. If you want to do remote right, get with it, your vpn has to be rock solid, your team has to be attuned to explaining ideas via conferencing, you better like Slack-type tools, you better be ready to respond to communication speedily (within reason), good ol’ email isn’t a serious solution.

This space has a ton of room for creativity to make it seamless (for those of you wondering if your dog walking app in cloud needs kubernetes, better shit to think about).

[StaticRedux]

TL;DR; when all you have is a hammer, everything looks like a nail

Although I like your version also. Haven't heard the full story before like that

[Zhyl]

Yeah, I want a complementary version too which would support OP's "Email and phone is sufficient".

Something like Alanis Morisette's "10,000 spoons when all you need is a knife". If you're only opening a tin of paint you could also use a spoon.

[JackPoach]

I respectfully disagree with

>The good old email and phone is just enough

I know a lot of folks at Google and most of their (internal) communications go though email (Gmail). They absolutely hate it and understand that it's totally inadequate. They use Hangout extensively (I think it's called Meet now), but they understand that they are behind Slack or Trello as far as chat and project management goes. In order to collaborate effectively you need 1. Email 2. Videoconferencing 3. Shared workspace 4. Document management 5. CRM (if you work with clients) just to begin with. Designers need whiteboards and online proofing. Some folks need mind maps. Etc. Sorry, email and phone is not enough.

[nogabebop23]

>> have 1 team meeting for few hours Wednesday afternoon

This is really old-school (coming from a 40-plus!) and just doesn't work anymore.

What if I have more than a few direct reports or multiple teams?

When exactly is "Wednesday afternoon" for global teammates?

How do I share this temporal, ad-hoc conversation with team members who can't call in when I decide "n O'Clock on Wednesdays is forced bonding time"?

The overall sentiment is good and I completely agree of about geniunely caring for your team members, but synchronous, in-person communication just doesn't scale for remote teams.

This advice also seriously conflates all the different roles a manager fills into combined interactions. You shouldn't be discussing status reports, career planning, personal issues and shooting the sh!t in the same forum, especially all-hands.

Finally, email is terrible for surfacing actionable steps from meetings. There's no ownership or deadline and you will already be buried under a huge mountain of emails.

Will another tool solve structural issues with your remote team? Absolutely Not.

Do you need another tool to manage remote teams? Maybe; at the very least you need to tweak the tools you already use.

[SirLJ]

How many people you are supporting in the organization you are leading? Do you micromanage them all or you fo you have team leaders/department heads? How about hiring few project managers and forming a PMO office to take care of all the deadlines and actually manage the projects? I am sure there is a new shiny app out there for all this...

[AndrewKemendo]

>The good old email and phone is just enough, providing you trust the people you work with (if you don't then this is on you as a manager an no tool will help you)

This is the crux of things. If you haven't hired people who can be trusted to work remotely, there's nothing you can do to manage/lead them.

[SirLJ]

Thanks, that was the point to be made, but the amateurs got stuck on the phone/email comment and the need to use the best new shiny tool...

[nogabebop23]

OK, but your "people you trust" was one partial sentence out of several recommendations.

I'll go further: if you have entire teams of "people you trust" they will make it work regardless of your tooling and in spite of your management techniques.

This really avoids the challenge though; it's like when you have talented, experienced development teams they can make it work if you use agile, waterfall or little planning at all

Your approach relies on having the rare quality (experience, talent or trust) vs. approaches that try to grow these qualitites over time.

And appreciate the "amateur" shot - is that how you show someone you don't know well how empathetic and caring you are when they disagree with your opinion?

[AndrewKemendo]

My perspective is that if you don't have competent people you can trust, then you might as well just pack it up.

Any technical or non technical person with any skill level can be competent in their role and trustworthy. It doesn't take years to develop that, it's a personality trait.

[SirLJ]

What development teams, please go back and reread my original post, I am talking about operations, not development.

[Ididntdothis]

Totally agree. Most organizations have a ton of problems they know about but instead of addressing them directly they decide to paper over them by creating processes and tools.

[thawaway1837]

I was a phone hater, and always had good reasons why. It’s synchronous, requires meetings to be setup in advance, is cumbersome, and is painful.

But I’ve come to the realization after having the company switch to alternative means (slack) that these issues are its greatest strength. The universal annoyances of setting up a phone call means that people only reach out for it when it’s absolutely necessary. Instant messaging means that others will ping you for the slightest of things. And the expectations around instant message means that if I don’t respond within 15 minutes at most, the assumption is that I’m not actually working at the time.

And email works great for everything else that can be done asynchronously and requires a written record. And email has far fewer expectations about immediate responses (in fact, the spate of email is bad commentary over the past few years means that saying you check your email once an hour is not considered bad), being open means it fits into your workflow with the many clients and tools available for consuming it, and is immensely flexible. Good threading and search capabikities, the fact that each mail contains the entire discussion thread which you can then save as a file allows you to then incorporate that information in any alternative workflow using existing tools everyone is comfortable with.

Compare this to the new email replacements, which instead of fitting into your workflow require you to fit your workflow into them (because you’re limited to their clients to use them), and have expectations of not synchronous but almost immediate responses, and take up a lot of your time.

Some caveats though. If you regularly communicate with sales types, they love being on the phone and are willing to call you for anything. My way to avoid that is to basically insist on a calendar invite that I have accepted to take a phone call. The invite must contain a high level agenda so I can make a decision whether it’s worth taking the call, or can potentially be resolved in an email.

TLDR: I agree phone (not necessarily through phone calls, but usually through Skype or Google Hangouts) + email is easily my preferred universe of work communication tools.

[SirLJ]

Amen!