-
Notifications
You must be signed in to change notification settings - Fork 6
Basics for making distributed work work
This isn't strictly about the NRRD site, but this site has been entirely built and managed by a distributed team, and we've learned some things in the process. Here's what's been successful for keeping momentum going, even when we aren't all in the same room (or time zone).
Overcommunicate, overcommunicate, overcommunicate. When we're working in the same physical space, we can take communication for granted. Remote teams rely on consistent communication. Don't feel like you're bothering someone by communicating or asking questions: it may save the whole team time and headaches in the long run.
Use tools that make it possible to see the team’s work (like waffle, trello, or mural) as a whole, so that everyone is aware of what each other is working on.
Treat remote meetings the same way you would treat in-person meetings: be at your workspace and focused on only the meeting. [Occasionally it makes sense to take a meeting from transit, etc, but that should be pretty rare, and only for meetings that don’t involve screensharing, remote collaboration, or presentations.]
Show up to meetings on time! The fact that they’re video meetings doesn’t make them less real. If you feel like a conversation would help move something forward, make that conversation happen by asking for a quick video chat or call.
Default to video for most meetings (especially daily standups, collaboration, and coworking). Things move faster because you can rely on nonverbal feedback and cues to keep the conversation moving. They also help build team empathy and avoid alienation.
Invest a little more time into meeting preparation/planning than you might automatically do for in-person meetings. This can help get things moving quickly, get the right tools or documents queued up pre-meeting, and make all meetings feel more productive.
Write it down, whatever it is. When the team makes a decision or decides on a next step, make sure it’s reflected in GitHub, notes documents, or email. If people are storing team information in their heads or notebooks, it makes handoff and collaboration slower.
Treat everyone as remote — as much as possible, avoid having part of the team co-located and part of the team remote. Even if this means having people sitting 15 feet apart, plugged into the same remote meeting, it will help level the playing field and streamline participation.
- Problem statement
- Product vision
- User scenarios
- What we're not trying to do
- Product risks
- Prioritization scale
- Technical overview
- Contributing to code
- Creating a new branch
- How to prepare and review PRs
- Releasing changes
- Database change management
- Tech Solutions
- Data overview
- How to upload monthly data
- How to upload OGOR-B Data
- Troubleshooting for specific datasets
- Goals and metrics
- Analytics
- DAP-GA4 templates & instructions
- DAP-UA templates & instructions
- User research plans & findings
- Joining the team
- Onboarding checklist
- Working as a distributed team
- Planning and organizing our work
- Sample retro doc
- Human centered design process
- User research study process
- Design Standards
- Usability testing process
- User research participant guide
- User research agreement
- Observing user research
- Design and research in the federal government
- Shaping process
- Research wiki
- Data catalog
- Problem statement (2016)
- Hypotheses (2016)
- Outcomes workshop (2017)
- Transition goals (2018)
- Product management training (2018)
- Information architecture
- NRRD-flavored Markdown (Jekyll site)
For information about our other website see our ONRR.gov wiki.