Go async-first with your team.
If you and your team wish to work async-first and you’re not sure which practices to adopt, you've reached the right place. This method stack offers ideas for small changes you can implement on your team to go async-first, one step at a time. The launch video on this page (from a few years back) offers a quick overview.
Use the filters below to find async-first methods that are relevant to your team. For detailed articles, check out the blog.
Festina lente
There’s an expression in Latin - festina lente. It means “make haste slowly”. We optimise for speed in software development. Deep work is often the casualty in this quest for speed. Slowing things down through writing has several benefits.
Accountability partner
Advocate for a pair programming pattern where two developers act as each other’s accountability partners.
Create autonomous pods
Create smaller decentralised pods inside the team to devolve responsibilities. Pods operate autonomously and make their own decisions.
Introduce specialised tools
To make remote pairing work, the tools involved play a big role. Make sue you have specialised tools that serve the purpose.
Go solo to take a break
Take a break by going solo on simple coding activities that won’t benefit from the intense code review of pair programming.
Baton pass pairing
Use the flexibility of remote work to work out your “pairing” hours. Get into the practice of writing good commit messages and pass on the baton.