Lecture 5-2: Reviews That Teach
목차 31
- Lecture 1-1: Is Planning an Act of Faith?
- Lecture 1-2: Mission, Vision and Values: Telling Them Apart
- Lecture 1-3: Discernment in Scripture: Praying, Planning, Being Blocked
- Lecture 1-4: Discerning Together: Who Is in the Room
- Lecture 1-5: Practice Lab: A Draft Calling Statement
- Lecture 2-1: Starting From What You Have
- Lecture 2-2: Listening to Your Neighbours
- Lecture 2-3: Your Story, Your Wounds, Your Limits
- Lecture 2-4: People, Time, Money and Health: Counting Your Capacity
- Lecture 2-5: Practice Lab: A One-Page Picture
- Lecture 3-1: Writing a Vision People Can Say
- Lecture 3-2: Priorities, and What to Stop
- Lecture 3-3: Reaching Agreement in Different Structures
- Lecture 3-4: Counting the Cost and Taking a Risk
- Lecture 3-5: Practice Lab, Three Priorities and One Thing to Stop
- Lecture 4-1: Goals You Can Obey
- Lecture 4-2: Calendar and Rhythm
- Lecture 4-3: Roles, Volunteers and Resources
- Lecture 4-4: Plan and Budget Together
- Lecture 4-5: Practice Lab: A One-Page Year Plan
- Lecture 5-1: What to Count and What Not to Count
- Lecture 5-2: Reviews That Teach
- Lecture 5-3: Honest Reporting
- Lecture 5-4: Evaluating Work Without Judging Persons
- Lecture 5-5: Practice Lab: A Year-End Review
Most communities do some kind of review. It is often one of two kinds, and neither teaches much.
The first is the report-back: someone reads out what was done, people clap or nod, and the meeting ends. Nothing is learned because nothing is asked. The second is the post-mortem after a bad event: something went wrong, tempers are high, and the meeting looks for the person who is to blame. Something is learned, but mostly it is fear.
A good review is neither. It is a calm, regular, shared look back at a season of work, asking what we planned, what happened, why, what we learned and what comes next. It is led with enough honesty to speak of failure and enough kindness that people will do so. It ends with thanks and prayer.
This lecture gives a simple frame for that kind of review, shows how to run it in small and large settings, and deals with the hardest part: speaking of failure without blame and without pretending.
이 20분으로 얻는 것
- Use a five-question frame to review a season of work.
- Explain the difference between a review without blame and a review without honesty.
- Describe how to make it safe to speak of failure, and what a leader must do and not do.
- Keep short, useful records of a review and say who should see them.
- Close a review with thanks and prayer in a way that fits your tradition.
Now therefore this is what Yahweh of Armies says: Consider your ways." — Haggai 1:5
World English Bible
Let us search and try our ways, and turn again to Yahweh." — Lamentations 3:40
WEB
Search me, God, and know my heart. Try me, and know my thoughts." — Psalm 139:23
WEB
Where there is no counsel, plans fail; but in a multitude of counselors they are established." — Proverbs 15:22
WEB
I thank my God whenever I remember you," — Philippians 1:3
WEB
The prophet tells a discouraged people to look at their own path. The poet asks God to search him, not to flatter him. Wise plans are strengthened by many counsellors. And Paul begins a letter with thanks. A good review has all of these: an honest look, an open heart, many voices and gratitude.
1. Why look back at all
Some believers feel that looking back is a lack of trust: God has led, so why examine? But the Bible is full of looking back. Israel is told again and again to remember what the Lord has done, and also to remember where it went wrong. The prophet Haggai asks the people, twice in one short chapter, to consider their ways. The writer of Lamentations calls the community to "search and try our ways" and to turn again to God.
Looking back is not doubt. It is how a community that believes in a God who guides notices where it may have missed the guidance, and where it received more than it knew. It is also how a community learns to plan better the next year without claiming that its plans were perfect.
There is also a plain reason. A community that does not look back will repeat itself. It will do again, with the same effort and the same disappointment, what did not work. And it will forget to give thanks for what did.
2. A review frame with five questions
A frame does not make the review. People do. But a simple frame keeps a review from wandering, and from turning into a list of complaints or a list of praises. Use these five questions in order.
1. What did we plan? Look at the plan you made. Read out what you said you would do. This is not to condemn anyone. It is to start with a shared picture of the intention, since people remember intentions differently.
2. What happened? Say plainly what was done and what was not. Use the evidence from lecture 5-1: counts, observations and stories. Do not argue about causes yet. This step is only for facts.
3. Why? Now ask why things went as they did. What helped us? What got in the way? Some causes will be inside the community (we were too busy, a task had no owner). Some will be outside (a flood, a loss of work in the neighbourhood, a change of rules, illness). Name both. Do not decide the cause is always "our lack of faith", and do not decide it is always "circumstances".
4. What did we learn? Say it in a sentence or two. A lesson is something you could use next time: "Tasks that had a named person got done; tasks assigned to 'the committee' did not." If you cannot say it in a sentence, you have not yet learned it.
5. What next? Decide what changes. Often the answer is small: one task will have an owner; one activity will end; one thing we keep. Write it down and give it to the people who will plan the coming year.
(an invented example) The elders of Hillside Fellowship, a congregation of about two hundred, reviewed their year of home visits. They had planned a visit to every household twice. What happened: about a third of the households had one visit, and a few had none. Why: the visits were assigned to "the elders as a group", nobody kept a list, and two elders were ill for months. What they learned: a group that is responsible is a group that does nothing. What next: each would hold a named list of ten households, and one person would keep a simple record. Notice that nobody was blamed, and everybody could see what to do.
3. Review without blame, not review without honesty
Many leaders say "we do not blame" and then discover that people still stay silent. The reason is that blame is not removed by a rule. It is removed by what the leader does.
Here is a distinction that may help. Blame asks "who is at fault?" in order to punish or shame. Learning asks "what happened, and what in our way of working let it happen?" in order to change. The second question can still find that a person made a mistake. But it looks beyond the person to the system: Was the task clear? Was the person tired, new, or alone? Did we give them what they needed?
This does not mean no one is ever responsible. Some failures involve real wrong: a lie, a misuse of money, harm to a person. These are not matters for a gentle review. They belong to those who hold responsibility for oversight, and in some cases to the law. A review for learning is not a place to bury such things. If something of this kind comes to light, stop the review, protect anyone who may have been harmed, and take the matter to the proper body. Lecture 5-3 and the courses on church order and on safety and compliance say more.
For ordinary failures, those of tiredness, poor planning, overreach and bad luck, the community can say: we are not here to find someone to blame; we are here to find out what to do differently. Say it, and then show it.
4. How a leader makes it safe to speak of failure
People watch the leader. If the leader hides every weakness, others will too. A few practical habits help.
- The leader speaks of their own failures first. "I did not give the youth work the time I promised. Here is why, and here is what I should have done." This costs the leader something, and it opens the door for others.
- Ask questions, do not give verdicts. "What made that hard?" teaches. "Why didn't you finish it?" accuses.
- Thank before you correct. Not as a trick, but because the thanks is true.
- Do not repeat in public what was said in confidence. A review that turns into gossip will not be honest again.
- Listen to the quiet. Ask, "Is there something we have not said?" and wait. Some will speak to a leader afterwards when they would not in a group. Be ready for that.
- Watch your face. A leader who looks hurt or angry teaches everyone to be careful.
The book of Proverbs (28:13) says that those who conceal their sins do not prosper, but those who confess and turn away from them find mercy. A community that is allowed to confess its failures is, in time, able to turn from them. A community that is punished for confessing learns only to hide.
5. Who should be in the room
A review of a season's work needs the people who did the work, since they know what happened. It also needs, in some way, the voice of those the work was for. They may not be able to attend a meeting. A few short conversations beforehand, with consent, can bring their voice in. If the work was with children or vulnerable adults, listen through the proper safeguarding channels, never alone with a child, and never in a way that exposes anyone.
It also helps to have someone not too close to the work. Proverbs 15:22 says plans are established with many counsellors. An outside friend, a neighbouring minister, an older member who has stepped back, or a board member who did not run the programme, can ask the simple questions that insiders have stopped asking.
In a house church of twelve, the review may be an evening meal and a long conversation, with one person noting down the main points. In a large congregation, ministries may review in their own teams first, and then bring a short summary to the leadership; the whole body may hear a shortened version. In a parish, the parish council may review, and the findings can be shared at a general meeting of parishioners. In a mission agency or non-profit, a board may review with staff and, where fitting, with partners. A pointer: how decisions are made in the review, and who has authority to change the plan, belongs to your own order and constitution, which a later course on church order and law discusses.
6. When to review
Do not review only after a crisis. A rhythm is better: a short review at the end of each season or project, and a longer one at year's end. Short reviews catch problems while they are small. The year-end review gathers the short ones and looks at the whole.
Give a review enough time to be useful, but not so much that people dread it. For a small community, an evening. For a larger one, a half-day for leaders and shorter sessions for teams. A review that is held but never leads to any change soon stops being honest.
7. Records
Write down the review. Keep it short: one or two pages. Include the date, who took part, the five answers, and the decisions about what changes. Say who is responsible for each change.
Keep the record where those who need it can find it, and no wider. A review often includes personal details, tiredness, family trouble, a conflict. These are not for every reader. Write down what the community needs in order to learn, and leave out what is private. If someone's name must appear, ask whether it is needed. Where a record holds personal data, keep it safely and check what the law and your own organisation's rules say where you live.
Next year's planners should read last year's review before they plan. That is the whole point of writing it.
8. Thanks and prayer
Paul begins several of his letters with thanks: "I thank my God whenever I remember you." Thanks is not decoration. It is part of seeing truly. A review that finds only the faults is as untrue as one that finds only the successes.
Close the review with thanks that is specific: name the people and the work. Do not thank only the visible leaders. Thank the person who set out chairs for ten years, the one who drove the older members, the one who prayed and told no-one. Then pray. How you pray depends on your tradition: a liturgical prayer, a time of open prayer, a silence, a psalm read together. The Lord's Prayer is one that nearly every tradition shares. What matters is that the review ends before God, with thanks for what was given and a request for guidance on what comes next.
Note carefully what prayer here is not. It is not a way to close an argument that was not resolved, and it is not a way to avoid a hard decision. It follows the honest look; it does not replace it.
Diagram 1. A review in five questions
Diagram 2. What a leader does to make it safe
| The leader does | The leader avoids |
|---|---|
| Names their own failure first | Defending every decision |
| Asks "what made that hard?" | Asking "why didn't you...?" |
| Thanks specifically | Thanking only the visible people |
| Keeps confidences | Repeating what was said in the room |
| Waits for the quiet to speak | Filling every silence |
핵심 요약
- Looking back is not doubt. A community that believes God guides learns where it missed the guidance and what it received.
- Use five questions in order: what we planned, what happened, why, what we learned and what next.
- Blame asks who is at fault in order to shame; learning asks what in our way of working let it happen.
- A leader makes failure safe to speak of by naming their own first, asking questions and keeping confidences.
- Real wrong, such as lies, misused money or harm to a person, is taken to the responsible body and not buried in a gentle review.
- Write a short record, keep it where those who need it can find it, and read it before planning.
- End with specific thanks and prayer, which follow the honest look and do not replace it.
| Front | Back |
|---|---|
| The five questions | What did we plan? What happened? Why? What did we learn? What next? |
| Blame and learning | Blame asks who is at fault; learning asks what in our way of working let it happen. |
| Making failure safe to speak of | The leader names their own failure first, asks questions, thanks specifically and keeps confidences. |
| When a review must stop | When it uncovers lies, misused money or harm to a person: protect anyone harmed and go to the responsible body. |
One sentence to remember A review is for learning together, so it needs enough honesty to say what happened and enough kindness that people will.
This week's action Choose one project from the last year and answer the five questions about it on one page, with one change you will make.
스스로 확인해 보세요
읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.
묵상 및 토론
- Think of the last review your community held. Was it more like a report-back, a post-mortem, or a review that taught? What would have made it better?
- Choose one thing your community did last year. Try the five questions on it, in a few sentences each.
- What is the difference between "we do not blame" as a rule and "we do not blame" as something people feel? What would you need to see from a leader to believe it?
- Who is missing from your reviews: the people served, the quiet, the young, the outsider? How could they be heard?
- How does your tradition close a time of looking back? What does it do well and what might it hide?