You are on page 1of 11

The Science of Asynchronous

Collaboration
How to optimize the cognitive delivery path

Herve Roussel
Co-Founder at Quod AI

#remotedev @quod_ai
Slack + Zoom solved remote ... right 😅?
“Group chat is an all-day meeting with random people and no agenda.

Jason Fried, Co-Founder at Basecamp

“Don't take someone from their work (if you don't have to).

The Remote Manifesto, Sid Sijbrandij, Co-Founder & CEO GitLab

“Disruptions increases frustrations and tensions in dev teams.

The Daily Life of Software Developers, Meyer, Barr, Bird, and Zimmermann, Microsoft & IEEE

#remotedev @quod_ai
Synchronous Asynchronous
8am

9am

10am
❌ Interruption & context switch ✅ Deep work
11am

12pm

1pm ❌ Knee jerk response ✅ Quality response


2pm
VS
3pm

4pm
❌ Information scatter ✅ Recorded answer
5pm

6pm

7pm
Thoughtful written
communication

#remotedev @quod_ai
74.5%
Badly written doc
HackerRank Developer Skills Report (2019)

“High cognitive load would likely translate to slow learning & poor
code quality
Dr. Mikhail Filippov, Chief Scientist at Quod AI,
Honorary Research Fellow at UCL Dept. of Neuroscience.

#remotedev @quod_ai
4 pitfalls of dev comm.

New information ❌ Unclear problem

❌ Non adaptive path

❌ Lack of context
Current
understanding ❌ Distractions
Extraneous Germane

#remotedev @quod_ai
Unclear problem

⬆️Extraneous load 🤯 Shock

#remotedev @quod_ai
Non adaptive path

⬇️Germane load 📛 Personalize

#remotedev @quod_ai
Lack of context
?
?

It’s not
working

? ?
⬇️Germane load 📍Contextualize

#remotedev @quod_ai
Distractions

⬆️Extraneous load ‍ Focus


♀️

#remotedev @quod_ai
How to get the most out of async?

🤯 Shock

📛 Personalize

📍Contextualize

‍ Focus
♀️
Thank you
@hvroussel
herve@quod.ai

#remotedev @quod_ai

You might also like