Skip to content

Instantly share code, notes, and snippets.

@nkammah
Last active October 11, 2018 14:34
Show Gist options
  • Save nkammah/88eb87301280dc18707e92ab40662a65 to your computer and use it in GitHub Desktop.
Save nkammah/88eb87301280dc18707e92ab40662a65 to your computer and use it in GitHub Desktop.
Remote teams are working better than you: productivity lessons for co-located teams from remotes

What seems to work well for co-located team breaks down once remotes join a team. The local team dials-in the remote to make them feel part of the team, yet remotes still feel disconnected. They don't feel like they have an equal voice in meetings than their local counterparts. They feel like they're missing key conversations from the hallway track. And having an ad-hoc, impromptu conversation, usually requires booking a meeting room. What if we were approaching this problem the wrong way ? What if the issues were not about remotes but rather latent issues exacerbated by being remotes ?

This talk will uncover how to improve your team's productivity by learning from remote team best practices. By approaching team collaboration from a remote-first perspective, you will gain insight into your co-located teams' inefficiencies.

An environment with everyone in close proximity encourages synchronous communication. You will learn how asynchronous communication and systematic documentation offers a far more inclusive environment and more accountability.

An open office makes it easy to break into impromptu brainstorming sessions. You will understand why fostering the distraction-free environment that remotes enjoy can also benefit your co-located team and let them get into the zone.

Last but not least, we will talk about the barrage of seemingly useless meetings that every remote dreads more than you do. By exercising empathy around remote

@elazar
Copy link

elazar commented Oct 11, 2018

The overall concept is good, but both the title and abstract need to be a lot shorter. The abstract is your "elevator pitch" for your prospective audience. You can list a few short specifics about what you'll discuss, but otherwise, try to keep the abstract length minimal and focused on high-level concepts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment