Comments on: Reflecting on Team Work http://www.engagedyouth.org/2007/10/25/reflecting-on-team-work/ Just another WordPress weblog Tue, 06 Jan 2009 23:03:56 +0000 http://wordpress.org/?v=2.3.3 By: Lance Bennett http://www.engagedyouth.org/2007/10/25/reflecting-on-team-work/#comment-19 Lance Bennett Mon, 05 Nov 2007 10:44:48 +0000 http://www.engagedyouth.org/2007/10/25/reflecting-on-team-work/#comment-19 I agree that there are pros and cons to each decision process style. What seemed missing from our earlier process (which is clearly less hierarchical and more organic) was a facilitator such as you. It has been really helpful for me to have someone who digests meetings and then returns to frame the issues at a next meeting. This helps clarify concepts and keep the process moving forward. I agree that there are pros and cons to each decision process style. What seemed missing from our earlier process (which is clearly less hierarchical and more organic) was a facilitator such as you. It has been really helpful for me to have someone who digests meetings and then returns to frame the issues at a next meeting. This helps clarify concepts and keep the process moving forward.

]]> By: Deen Freelon http://www.engagedyouth.org/2007/10/25/reflecting-on-team-work/#comment-18 Deen Freelon Thu, 25 Oct 2007 23:46:04 +0000 http://www.engagedyouth.org/2007/10/25/reflecting-on-team-work/#comment-18 Adri, To respond quickly to your last two bullets—I would say that the line between "proposal" and "decision" should be hashed out in those last 5 minutes of each meeting. Each team should ask themselves: Which of the issues discussed today have we resolved? Which will need to be discussed at future meetings? It won't always be clear, but I expect that people will be able to reach consensus most of the time. As for decisions worth blogging, again, always a judgment call. When in doubt, I would say blog it, but you're right, not every little detail needs to be logged. If you think it will be worthwhile for people to remember beyond the next few days, go ahead and post it. When people outside the group will be affected, definitely write it up. Adri,

To respond quickly to your last two bullets—I would say that the line between “proposal” and “decision” should be hashed out in those last 5 minutes of each meeting. Each team should ask themselves: Which of the issues discussed today have we resolved? Which will need to be discussed at future meetings? It won’t always be clear, but I expect that people will be able to reach consensus most of the time.

As for decisions worth blogging, again, always a judgment call. When in doubt, I would say blog it, but you’re right, not every little detail needs to be logged. If you think it will be worthwhile for people to remember beyond the next few days, go ahead and post it. When people outside the group will be affected, definitely write it up.

]]>