Saturday, October 13, 2007

Flow chart frenzy! 1week decision feedback





Here is our formatted feedback - double click to view.
Taccers please do a close reading because there are some (mostly minor) discrepancies in understanding between members and it would be good to arrive at an overall consensus.
Can we please also feedback further to the suggestions to resolve how best to use "1-Week Decisions".
p.s. Hope you like your designated colours!

9 comments:

Tom said...

It looks like we are mostly on the same page (literally and figuratively!) when it comes to 1 week decision making. This flow chart is such a great visual representation of our decision making process! I really like it.

Liz said...

Hi Tom - more soon - just trying to get the image sizes right

Melanie Oliver said...

Yes it seems our comments are pretty similar (simple?) and we all enjoyed some flow chart fun.
But I have been thinking about why I was interested in being involved in TAC and what has made me sluggish with my own contributions/ communication. Thinking aloud, apart from the distance and a busy schedule, I am mainly keen to research and talk about ideas related to collaboration and so the organisational aspects of TAC appear mundane even though they are operational research - because it would require more analysis?... My personal approach to things is generally goal driven and so I wondered if anyone else is similar and would like us to move towards another project (such as the publication)? Or if I should start with evaluating more what we have been/ are doing?
Looking forward to hearing other feedback!
xx M

Liz said...

Yep, for sure, our understandings of this decision making process are similar in most aspects - but there are discrepancies which need to be "ironed out" for cleaner use.
I wholeheartedly acknowledge that talking about these kinds of processes at this level of detail becomes abstract and it therefore it becomes difficult to recognise the value or significance of the conversation. It's good to question relevancy.
To talk to that, I would posit that one of the main FAQ's that are lodged at collective enterprises is: "group work, fine - but how do so many people agree on things?". This is, I think, because it is a challenging thing to make decisions collectively.
I like the way Mel phrased this review process as operational research, spot on! I see this discussion (content and process) as generating a resource to use in our future kit-publication process.
Goal driving is a great strength and well put to use for getting the next project moving. In terms of this discussion, our goal is specifically: for every member of tac to have the same understanding of what/why/how to use 1W decision process; and
generally: for every member of tac to understand what our communication issues are and how to solve them.
It would be great if we could put our analysis hats on and dig into this one!

Liz said...

For further clarification these are the discrepancies that I have picked up on. I am sure there are more so please add them into the discussion.

We have differing opinions on/understandings of:
Whether 1WDs require everyones input or whether it is a process that allows for non-participation in operational decision making;
Whether 1WDs should only be used for previously discussed issues;
How email and 1WDs could work together; and
How best to format 1WDs (titles, subject labels, colours).

Paula Booker said...

Thanks for breaking the points down and making it simpler to feedback liz!


QDoes every member need to feed into 1-week decision to make it work?
I think In short, no. I think the point of having a quick decision making function should be to aid speed. TAC members who want to have ongoing input will be sure to get involved. This way varying degrees of commitment currently evident can be accommodated without holding things up.
QWhether or not decisions that can fit into 1 week bracket must be discussed first
I thinkToo hard to discuss everything prior. Granted it is more everyday type decisions
QShould all 1 week discussions be notified by email?
I think Emails are not necessary. Checking the blog’s 1 week decisions link is not too much of a hassle do at least once per week.
QHow should the 1-wk decisions function work/look?
I think A link at the top all by itself would be good. Would be similar to the current active comments portal, but instead of going to a single page, as that currently does, it would take you to all the posts with “1 week decisions” labels.

Unknown said...

Here's a wrap up of where 1 Week Decisions has ended up:

What are they for?

Administrative or operational decisions - ones which don't affect the structure or direction of tac. 1wds can be about things which haven't been discussion prior to posting them.
1wd is a process that allows for members to not participate in admin decisions, this means admin decisions can be made by those who do participate without needing to get others approval.

How do we use it?

Blog: Always write up the thing that needs to be decided about and post it on the blog. Include the words "1 week decision" in title and attach the same as a subject label.
Email: U decide! this is up to the person who makes the post. Some decisions might not warrant an email, or the poster might not be into it, so it will still be useful to visit 1 week decision subject label on the side of the blog - as we have all been doing.

thats all folks
a wrap
in a nutshell
over and out

The Association of Collaboration said...

Hi folks I am just in the admin function - I tried to format a separate linking device for 1wds but no-go sorry. I think it's pretty easy to find in the subject label list so let's just continue using that.
I have left a how-to guide post in the 1wd subject label, which means it will always show 1 entry present.
If you are visiting the blog and see there is a number greater than 1 next to the 1wd subject label then it means there is a decision there to participate in.
liz

Unknown said...

Hi- I know I won't get posted, but wanted to share a link with you. i've been studying collaboration here in Portland, Oregon, and met someone in Melbourne in March named Mark Elliott. he designed the collaborative commons website. he also wrote a dissertation on collaboration. http://eprints.infodiv.unimelb.edu.au/archive/00003977/
pretty dense, but it's nice to have something more thorough than a dictionary definition. best, Katy