2 ms·
See, that’s what I don’t get. A 2 hour synchronous meeting, to me, is a waste of resources. (side note: If you’re going to destroy an engineer’s morning (or aft
by falcolas 7y ago
See, that’s what I don’t get. A 2 hour synchronous meeting, to me, is a waste of resources. (side note: If you’re going to destroy an engineer’s morning (or afternoon) with a 2 hour meeting, you may as well make it a 4 hour meeting and jam out a POC.)
A day (or week) to review on their own availability, plus the asynchronous feedback during that day (or week) means that the synchronous meeting can conclude in 20-30 minutes (if its necessary at all), with more thought put into it than any two hour review.
In the end, the asynchronous method of syncing state between people may take more overall time, but that time is taken from when an person is naturally not engaged with their current project. A meeting, on the flip side, occurs whether they were in the zone or not.
- pas 7y agoYes and no. In theory the asynchronous mode is more efficient, but then it might mean you never get the ACKs from all the people. If the async mode works, no need for the meeting, after all do it over email or in GDocs. The problem with the sync mode is that inevitably you're wasting someone's time, at best only yours as you wait for others to read.