3 ms·
The first hurdle isn't tool or tech-related; it's management. They need to buy in. If they don't, remote work won't work. About half my team is remote, and tha
by alistairSH 10y ago
The first hurdle isn't tool or tech-related; it's management. They need to buy in. If they don't, remote work won't work.
About half my team is remote, and that's not uncommon for my division. We use Slack for collaboration. It was rolled out recently - prior to Slack, it a mix of (lots of) email and Skype. We use BlueJeans for larger meetings.
For day-to-day work, this all works well. But, it's also ingrained in the culture - we've had many remotes for a long time.
For new project kick-offs, especially greenfield dev, it makes sense to bring the remotes into the office for a week or more. I've done this three times now over the past 5 years. It fosters a sense of team and also allows easy white-boarding and fast/effective collaboration.
All my remotes are within an hour +/- time zone and a short flight away (office near DC, remotes in Carolinas and Mid-West). Teams spread across continents introduce more problems.