Open jbenet opened 9 years ago
For time optimized meetings, you suggest using Github issues. I've been trying to do that to optimize the meeting we are having for #RebootingWebOfTrust by having pre-readings and asking people to post issues. However, I've had a very difficult time herding cats to get the advance readings up so that people post issues, and so far there has been only one issue posted.
Basically, everyone is too busy, but all agree the meeting will be useful. Any suggestions on how to move the process forward?
x.ai schedules meetings. More "smart" agents to be expected. Until then, there's always Huginn software agents (AI optional).
JRFC 25 - Time Optimized Meetings
Time matters. Mine and yours. Often, more time is wasted scheduling or travelling to meetings than actually meeting. This is absurd. I rather spend time speaking with you than transiting or calendaring. This is worst when physical presense is not substantive. I propose the Time Optimized Meeting protocol. Please schedule meetings with me this way. Contributions welcome. Love, Juan.
TOM Values
Core Principles
Suggestions
Video Calls
I find that ~20min video calls (+Hangouts or Skype) hit the sweet spot of hyper focused and lowest overhead.
Please bear with me if I suggest that we +hangout. I would much prefer to meet in person, but I can be more valuable to you if I meet more often and waste less time.
TOM Scheduling
Scheduling sucks. Optimize it away. The protocol below can help. It doesn't have to be so dry. The exchange below conforms just fine and gives me tears of joy.
Message 1 from [REDACTED]
Message 2 from @jbenet
Message 3 from [REDACTED]
Message 4 from [REDACTED]
Boom. 4 messages. Hyper clear and done.
Tom Scheduling Protocol
Below,
starter
is meeting initiator.participants
are all parties. To avoid confusion,starter
is responsible for attaining consensus in a fault tolerant way. Above all, respect time preferences.starter
sends message to allparticipants
including:participants
respond once:sender
waits for all or most (2/3) or simply keyparticipants
' responses.sender
sends confirmation toparticipants
, including all relevant information.sender
sends a Calendar Invite toparticipants
with all details.sender
sends reminder ~3 days prior. (no "still on?", just a reminder)