Group processing and planning tools
Brainstorming and Refining Process
- You get as many ideas as possible up on a white board or large sheet of paper. Don't judge or commment the ideas at this point, to keep creativity flowing ...
- Make a firm end to the this phase when you have had enough.
- Try to refine ideas. (use a different colour or lots of colours etc.)
- Cross out the hopeless ideas
- Group similar ideas
- Keep this process going and reduce until you have close to a final solution
- Similar to a brainstorm except you are looking at an existing situation or ministry or even your personal life.
- Divide your paper in 4 with the headings: STRENGTHS, WEAKNESSES, OPPORTUNITIES, THREATS
- Brainstorm or assess for each heading
- Refine the results and take them on for further planning etc.
- Similar to the SWOT test but you want to look for the Gaps in what you are doing or where nothing is happening yet so that you can address the deficit.
- e.g. What is happening in this city? What are the areas where nothing is happening?
- e.g. What areas of knowledge have we already captured on this KnowledgeBase. What areas of knowledge are missing or required?
4 Into 4 Into 4
(Don't know the right name for this but I learned it from Steve.)
This is a good processing tool to boil down a large amount of experiences into a shared summary of experiences. For example answering the question: What have I learnt on this course?
- Group people in two's with a piece of paper
- Ask them to make a list of just 4 items that are the most important answers to your question.
- Group the pairs into a large group.
- Ask them to make a new list containing just 4 items of top importance from the answers they already have.
- Give people the freedom to dispute and argue!
- Group into a larger group or bring them all together
- Work with the group to make a new list of just 4 items of top importance.
- Ask a range of people the same set of questions.
- e.g. How are we doing in terms of community life?
- e.g. How rapid is our response to enquiries?
- Ask them to grade it on a scale for example (1-10)
- It is often more useful to compare and contrast change over a time period. Get people to place a second mark for how they would have asked the question 12 months ago.
- When reading the results back it is helpful to see where there is a clear sense of improvement or decline. This can be useful to measure the effectiveness of a course of action or leadership decision.
- An example audit: YWAM Base Audit.
This is a new tool that can help us to manage change well and help us to bring the best of the past into the future.
Appreciative Inquiry utilizes a 4-stage process focusing on:
- DISCOVER: The identification of organizational processes that work well.
- DREAM: The envisioning of processes that would work well in the future.
- DESIGN: Planning and prioritizing processes that would work well.
- DESTINY (or DELIVER): The implementation (execution) of the proposed design
(From the Wikipedia article Appreciative Inquiry)
More info: Appreciative Inquiry
Group Strategy Planning
- Have general principles in mind or goals or values as a seed to start the process off
- Work together to plan in details and to make sure you have together covered all the goals. Useful for discovering creative ways to achieve goals.
Making Vision and Mission Statements
- Make sure you can tell the difference between a Vision statement and a Mission statement: a vision statement is specific and time related. A mission statement is general and expresses why a group exists and the general range of activities.
- When working on Vision and Mission statements make sure you adhere to a strict definition - if you are vague in what you set out to create the result will not satisfy or help!
- Keep revising it.
Creating a Best Practice Document
- Work with lots of people together to get the broadest breadth of knowledge
- Use some of the tools above to agree what you want to agree on
- Use a wordprocessor, versioning it to make sure that the what, who and why of the modifications are clear, for example by using a Wiki like this one or even this Wiki! (You may use your own User page and subpages of it for your own projects...) (Or just put a summary table of modifications at the beginning of the document, and backup some versions from time to time.)
- Try to reduce and reduce and reduce
- Example best practice document created with this method (sadly before the invention of the Wiki)