Some workflows require synchronous communications. Meetings, in person or virtual, are great for these.
Other workflows work asynchronously. E-mail, IM and the like are great for these.
Post-War America erred on the side of meetings, forcing asynchronous flows into artificial bottlenecks. Silicon Valley seems to have over-corrected, replacing ten-minute meetings with full-day Slack threads.
Trying to force asynchronous flows into synchronous constructs introduces unnecessary delays, as the slowest process sets the pace. It also increases overhead, since resource C is occupied while A and B sync. Trying to force synchronous flows into asynchronous constructs introduces mistakes through mis-communications. It also increases overhead, since an additional layer of verifying everyone got critical information is introduced.
Insightful. Was thinking about this recently. I find meetings are usually “make a decision”, “give updates”, or “show a demo”. For decision making, have been trying to optimize that workflow with teammates all over the world and not everyone having the time or not loving textual communication.
Seems like a master decision record in confluence, discussing finer points in a private slack channel, and demo and tie-breaking plus sync with busy or non text thinkers with ad hoc video meetings works well together. Another thing is quick prototypes of ux or architecture designs in codesandbox.
These all work well, but it would be great to have less overhead. Even on a small team though there are so many gaps it feels impossible to reconcile without all these.
Anyone have a team decision making workflow for spinning up new projects that is more efficient?
Other workflows work asynchronously. E-mail, IM and the like are great for these.
Post-War America erred on the side of meetings, forcing asynchronous flows into artificial bottlenecks. Silicon Valley seems to have over-corrected, replacing ten-minute meetings with full-day Slack threads.
Trying to force asynchronous flows into synchronous constructs introduces unnecessary delays, as the slowest process sets the pace. It also increases overhead, since resource C is occupied while A and B sync. Trying to force synchronous flows into asynchronous constructs introduces mistakes through mis-communications. It also increases overhead, since an additional layer of verifying everyone got critical information is introduced.