3 ms·
Typically a 6 Pager is: 1 Page of Press Release and FAQ 2 pages of arch overview 2 pages of business justification 1-2 pages of appendix Or some mix thereo
by grogenaut 7y ago
Typically a 6 Pager is:
1 Page of Press Release and FAQ
2 pages of arch overview
2 pages of business justification
1-2 pages of appendix
Or some mix thereof. 20 minutes is a bit short but doable. Generally at 20 minutes the person running asks "need more time" and it can go longer.
For a design review I ask for at least 2 hours for the meeting. Or more.
Doing everything in the meeting greatly respects everyone's time. It's a thing I'm trying to get evenly applied at the subsidiary I work at as often we don't as people have trouble scheduling the meeting.
- falcolas 7y agoSee, 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.