A co-worker told me a while ago that at his previous job, he had an average of 33 hours of regular, recurring meetings on his work calendar every week. That's beyond nuts. He finally gave an ultimatum - either let him choose which meetings to attend, or wipe out all his defined development goals for the year and replace them with "Attend all scheduled meetings." And he also started to schedule his assignments based on a 17 hour work week (33+17=50 hours, which is what he would spend).
"That next assignment is expected to take two months? OK, then at 17 hours per week, I'll commit to a 5 month completion date." After a couple of those, they let him choose the meetings to attend.
For our next mtg could you put together a brief presentation to roll out a collaborative process for reducing our meeting times? Be sure to circulate your initial concept among stakeholders prior to the presentation so we can get some informed feedback at the meeting. We'll see how things go from there but be prepared to meet offline with interested stakeholders and bring back a refined product for consideration by the whole team at a future meeting. K, thx.
No problem! I'll just pull together some second-level stakeholders to brainstorm ideas before we deploy the collaborative process. However, as per Process Document PRM063 I will need to solicit consent from targeted resources that they wish to be stakeholders, which necessarily means I cannot have the feedback in my pocket by the next meeting. I will set up a pre-meeting to outline the concept and bring the PRM063 Stakeholder Agreement form so they can complete it there.
Facebook
Twitter