2 ms·

How do you reconcíliate future meetings with future flow states? Unless you have the ability to pospone a meeting when you are flowing I don’t see how to do thi

How do you reconcíliate future meetings with future flow states? Unless you have the ability to pospone a meeting when you are flowing I don’t see how to do this, unless you’re able to build a pattern over time and use that information to preemptively inform the organizer of best suited times to schedule a meeting

rob-d 8y ago
I hadn't really thought this through, but the ability to 'snooze' a meeting sounds like something which could be really useful, especially when I'm on maker's schedule and I'm meeting someone on manager's schedule (terminology from here http://www.paulgraham.com/makersschedule.html http://www.paulgraham.com/makersschedule.html). In fact, on a previous job, this happened a couple of times. I was in flow, finishing something off or pairing and I would forget about my 1-1, showing up 15/30 mins late. I was always really embarrassed, but actually it didn't affect the manager too badly because they had other things to be getting on with. My manager wanted a scheduler which satisfied the condition 'I would like to see all of my team members for at least 30 mins each on Wednesday', but they didn't mind who was seen when. In practice, these appointments were scheduled, by the manager, pretty much randomly I think, and fixed in advance, but something fluid could have worked. Perhaps it is inevitable that all makers want meetings at the beginning / end of the day, but I'm not sure, especially when there are other meetings etc going on. Also, perhaps the short term rearrangement would be so disruptive or unsettling that it wouldn't be practical. My experience in some jobs has been that this was happening anyway with people frequently late to meetings, so they were defacto snoozed anyway. As you say, if nothing else, such a system might surface some interesting data on which meetings were always missed / moved.

rob-d 8y ago

I hadn't really thought this through, but the ability to 'snooze' a meeting sounds like something which could be really useful, especially when I'm on maker's schedule and I'm meeting someone on manager's schedule (terminology from here http://www.paulgraham.com/makersschedule.html http://www.paulgraham.com/makersschedule.html). In fact, on a previous job, this happened a couple of times. I was in flow, finishing something off or pairing and I would forget about my 1-1, showing up 15/30 mins late. I was always really embarrassed, but actually it didn't affect the manager too badly because they had other things to be getting on with. My manager wanted a scheduler which satisfied the condition 'I would like to see all of my team members for at least 30 mins each on Wednesday', but they didn't mind who was seen when. In practice, these appointments were scheduled, by the manager, pretty much randomly I think, and fixed in advance, but something fluid could have worked. Perhaps it is inevitable that all makers want meetings at the beginning / end of the day, but I'm not sure, especially when there are other meetings etc going on. Also, perhaps the short term rearrangement would be so disruptive or unsettling that it wouldn't be practical. My experience in some jobs has been that this was happening anyway with people frequently late to meetings, so they were defacto snoozed anyway. As you say, if nothing else, such a system might surface some interesting data on which meetings were always missed / moved.