Posted by & filed under distributed teams, management.

Over the last few years, Liza and I have had the pleasure of building an ever-expanding engineering team. We’ve managed to find great people from across the country and were 100% distributed & office-less until a few folks moved into the new Safari office in Boston two months ago. Because our team was remote by rule rather than by exception, we’ve been forced to develop a culture that exploits new tools whenever they can help us cooperate and collaborate. One particular habit we’re fond of is running meetings through Google Docs.

As is typical with developers, we are not generally fond of meetings, especially recurring meetings, so we have tried to distill them into their productive, fundamental essence1. While our meetings are still far from perfect, I think we’ve developed some conventions worth sharing with other distributed teams.

One minutes to rule them all—in real time

Google Docs sometimes makes it too easy to create and share new documents, so the first lesson is to fight against this: use the same Google Doc for the same meeting week after week and write it during the meeting. This practice is laughably simple, but it removes the biggest threats to useful minutes:

  1. the attendees (claim) to not know where the minutes were/are
  2. the minutes feel worthless because they’ll be ignored forever after
  3. the attendees (wrongly) feel that someone else will write the minutes
  4. the attendees claim the minutes did not accurately capture the discussion

To set this up, just use an extremely clear title for the document (“{Team} {Purpose} Rolling Minutes”) and then add the new minutes at the very top for each meeting. Make it clear from the very first meeting that everyone is expected to help write the minutes in real time (plant some willing collaborators beforehand, if necessary).

It’s worth rotating to a new document every 6–12 months or Google Docs will be crashy.

Collect agenda beforehand (the “Pending” bucket)

Once you’ve established that the same document will be used for each meeting in the series, it is time to start turning the rest-of-the-week time into a lever that makes the meeting itself shorter. We keep an (empty) bulleted list under a Pending heading at the top of every minutes document. The Pending list gets filled by folks as something occurs to them throughout the week. In more extreme cases, the Pending list must be filled beforehand or the meeting itself is summarily canceled (depends on the meeting). Developing the Pending list asynchronously can also make it easier for less outspoken people to make sure their topics get some space in the larger forum.

Establish a repeating structure

While it’s easy to screw up, a carefully crafted meeting structure can help everyone understand when they’ll be actively participating and when the thing is nearly done. The problem is that you have to frequently evaluate the structure to make sure it still actually helps the team communicate rather than being wasteful boilerplate.

Our “big” meeting looks like:

A repeating structure also helps answer questions about who promised what. You just go down far enough to find it in the expected place in the minutes of a previous meeting. While this is a simple act, doing it consistently makes it clear that the minutes serve a purpose and that the each member of the team is accountable.

Force collaboration and attention through humor

The biggest benefit of cloud-based minutes is the opportunity to use a meeting as a way to help the group gel a tiny bit more, week after week. For distributed teams, the chances for true collaboration and team-building are already extremely limited, so we take whatever we get. Specifically, I want to use the minutes as a tool to have the team:

  • see each other actually (visibly) contributing to a shared project
  • laugh with each other
  • pay attention
A screenshot of a Google Docs document with humorous images and silly fonts

To achieve these goals, we need only two things: silly cat pictures, collaborative authoring. When the team knows that their colleagues are humorously defacing/lolcatting their section of the minutes, ignoring the document is nearly impossible (we don’t actually use Comments in minutes as much as you would expect). Juxtaposing the boss’ description of a particularly rough moment in the release process with a sad panda provides a rare moment to let off steam for people who almost never see each other face to face. And watching a document being written and edited by 5–10 people at once is really quite enchanting.

1 Andrew, our CEO, bought a huge stack of these and forced us to read them, before, ahem the next meeting.


7 Responses to “Building Distributed Teams: Driving meetings with Google Docs”

  1. Liza Daly

    I found this meeting style especially helpful back when we were a (distributed) startup. It can be a little embarrassing to read, but looking back over our meeting notes at Threepress is instructive to me in terms of seeing larger trends in how we evaluated potential opportunities/flailed around helplessly. It’s easy to see things in retrospect as all leading up to a single perfect outcome, but the path is always more twisty than that.

  2. Chuck Ha

    I like our meetings. They are usually quite brief, not frequent and often I get a good laugh out of them. The only thing I don’t like is when google docs crashes or someone loses their internet connection and just drop out of the meeting.

  3. Baldur Bjarnason (@fakebaldur)

    This reminds me of the way danc uses Game Design Logs

    Quite a few similarities: the use of gdocs, emphasis on collaboration and realtime conversation, etc.

    What danc’s logs don’t have is your emphasis on humour, which is something that does make a huge difference, at least in my experience.

    I really do wish that the place where I recently started working ran their meetings this way. And that they had fewer of them. And that they were shorter. And that they’d put more stuff in writing rather than assuming that everybody catches everything on a busy conference call.


    • Keith Fahlgren

      I never would have guessed this beforehand, but humor turned out to be the perfect carrot so that people were motivated to actually follow along. Given a big enough group, almost any lame joke will get one person to laugh and if someone is laughing at a joke you didn’t get because you weren’t following along….

  4. Molly Sharp

    I can’t believe how much this style of working has changed us for the better – we’ll never go back to the “old ways” now… Love it.


  1.  This week in marketing operations: the rise of the remote workplace - ProofHQ