무료

수료증 무료 발급 — 2027년 3월 31일까지.

PT736E Short-Term Mission Teams: Planning, Sending and Following Up Honestly

Lecture 6-4: Judging the Programme: Evaluation With Humility

목차 31
PT736E Short-Term Mission Teams: Planning, Sending and Following Up Honestly
제 0 장 · Introduction: Sent, Welcomed, Accountable
  1. Lecture 0: Introduction: Sent, Welcomed, Accountable, and What This Course Does Not Teach
제 1 장 · Week 1: Sending and Welcoming: Why We Go and How We Argue About It
  1. Lecture 1-1: Sent and Welcomed: Scripture and the Long History of Going
  2. Lecture 1-2: The Honest Argument About Short-Term Trips
  3. Lecture 1-3: Whose Work Is It? Hosts, Guests, Power and Money
  4. Lecture 1-4: Kinds of Teams, Kinds of Trips
  5. Lecture 1-5: Practice Lab: Why We Want to Go
제 2 장 · Week 2: Planning With the Host
  1. Lecture 2-1: Beginning With an Invitation
  2. Lecture 2-2: Designing the Days: What a Visit Leaves Behind
  3. Lecture 2-3: Teams With Special Skills: Medical, Teaching, Building, Youth
  4. Lecture 2-4: Near Home and Far Away: Local Trips and Online Teams
  5. Lecture 2-5: Practice Lab: A Shared Plan With the Host
제 3 장 · Week 3: Choosing, Preparing and Protecting the Team
  1. Lecture 3-1: Choosing the Team
  2. Lecture 3-2: Training the Guests
  3. Lecture 3-3: Health, Safety and Documents: Preparing Without Giving Advice
  4. Lecture 3-4: Safeguarding Children and Vulnerable People
  5. Lecture 3-5: Practice Lab: A Code of Conduct
제 4 장 · Week 4: Money, Words and Pictures
  1. Lecture 4-1: What a Trip Costs and What It Is Worth
  2. Lecture 4-2: Raising Support Honestly
  3. Lecture 4-3: Photographs, Stories and Social Media
  4. Lecture 4-4: Reports and Testimonies That Tell the Truth
  5. Lecture 4-5: Practice Lab: Checking a Fundraising Letter and a Post
제 5 장 · Week 5: On the Ground and When Things Go Wrong
  1. Lecture 5-1: The Guest's Posture: Serving Under Local Leadership
  2. Lecture 5-2: Planning for Crisis and for Withdrawal
  3. Lecture 5-3: Team Conflict, Tiredness and Spiritual Care
  4. Lecture 5-4: When Harm Has Happened: Honest Reporting and Accountability
  5. Lecture 5-5: Practice Lab: A Crisis Scenario
제 6 장 · Week 6: Coming Home and What Remains
  1. Lecture 6-1: The First Days Home: Debriefing and Hearing the Host
  2. Lecture 6-2: What Remains: Continuing, Changing or Ending a Partnership
  3. Lecture 6-3: Calling, Discernment and the Ones Who Stay Home
  4. Lecture 6-4: Judging the Programme: Evaluation With Humility
  5. Lecture 6-5: Practice Lab: A Statement of Principles for Our Church

핵심만 먼저 보기 ↓

29분

Lecture 6-1 looked at one trip: the debrief, the host's word and the thanks. This lecture looks at the whole programme. A congregation, a youth ministry, a school, a diocese, an order or an agency that sends teams over several years needs to ask, from time to time: Is what we are doing good? For whom? How do we know? Shall we continue, change or stop?

Many sending bodies do this badly, and for an understandable reason. Evaluation is awkward. The people who ask are the same people who ran the programme and who believe in it. The people who could answer best, the hosts, are the people with least freedom to say what they think. The numbers that are easy to count (teams sent, people travelled, money raised) say little about what matters. And a bad result is likely to be taken as a reproach to someone who gave a great deal.

This lecture argues that a programme should be judged by the host's voice first, with claims no larger than the evidence, and by a method that lets the programme change or stop without blaming anyone. It sets out who is asked, what is asked, what is claimed, what cannot be counted, how a decision is made and how a church learns from failure.

It carries the course's central claim. A short-term trip is a humble partnership, and humility includes being willing to be told that the programme is not working. The claim closes two doors. One door makes the programme a product to be marketed: its worth is shown by satisfied travellers and good photographs. The other makes the host a stage on which the sender's good intentions are performed, whose own view of the matter is not part of the data. A programme judged only by those who run it, or only by those who travel, has not been judged.

The lecture does not say that a programme must be measured to be valued. It does not say that stopping is a failure. It gives no financial or legal advice and no particular method of research. It is a guide to asking honest questions.

이 29분으로 얻는 것

  • Say who should be asked in an evaluation, in what order, and why the host comes first.
  • Write the kinds of question that a programme review should ask, and say what a review should not claim.
  • State fairly the three positions on numbers and stories, and say what the course requires of any evaluation.
  • Describe how a body decides to continue, change or stop, and how it learns from failure without blame.
  • Explain the roles of a yearly review, the whole congregation and the budget in keeping a programme honest.

He has shown you, O man, what is good. What does Yahweh require of you, but to act justly, to love mercy, and to walk humbly with your God?" — Micah 6:8

World English Bible

Where there is no counsel, plans fail; but in a multitude of counselors they are established." — Proverbs 15:22

WEB

Even so you also, when you have done all the things that are commanded you, say, ‘We are unworthy servants. We have done our duty.’”" — Luke 17:10

WEB

Micah names three things asked of a people: to act justly, to love mercy and to walk humbly. The last word is the one this lecture leans on: a body that walks humbly does not assume that its work is good because it is its own. Proverbs says that plans survive where there is counsel, and that more counsellors are better than few. For us, this means that those who run a programme should not be the only ones who judge it. Luke records a saying of Jesus about servants who have done what they were told: they do not boast. We use it as a check on claims, not as a reason to take no notice of results. These verses are not about programmes. We take from them only a way of looking: justly, kindly and without boasting.

1. Why programmes go unexamined

A short-term programme is easy to leave alone. It brings energy to a church. It gives young people something to do and older people something to give to. It makes a good story in the church bulletin. Sending bodies have a plan, a date, a budget and a list of people, and these are enough to keep it going. When a trip has been run once, it is likely to be run again, because the arrangements are in place and the people are keen.

So a programme can continue for years without anyone asking whether it is a good one. The questions are not hard to state. They are hard to ask in a church, because the programme is loved, because a question about it can sound like a charge against those who gave their time, and because the host has an interest in being polite.

An evaluation is not a trial. It is a way of seeing more clearly, so that the church can do better or stop. Hold on to that: the programme is being judged, not the people.

2. Who is asked, and in what order

The order matters, because the first voice shapes how the rest are heard.

The host first. The host church, school, clinic or community is asked before the sending side has settled on its own account. For the reasons given in lecture 6-1, this has to be done with care: in the host's own language and form, through someone the host trusts, with more than one voice, with a plain statement that "no" and "later" are good answers, and with a promise about what will not depend on the reply. A host who says "everything was a blessing" may be telling the truth, or may be being polite. A well-made question is one to which politeness is not an answer: "What did the last team cost you, in time and in money? What would you change?"

(An invented example.) The Ironbridge Youth Network ran a programme that sent teams of young people each summer to a village called Ottle. After four years, the committee asked the village church for an evaluation. They sent a form with eight questions, each to be rated from one to five. The returned form said five, five, five, five. The next year, the committee asked a young member who had grown friends in Ottle to visit and ask, in an unhurried way, how the visits were going. The village schoolteacher said, quietly, that the summer visits fell in the exam season, that two of her best pupils had stayed away from revision to help the guests, and that the church was too polite to say so. The committee had asked a polite question and received a polite answer. A different way of asking produced the truth.

The local leaders and workers beside the team. Interpreters, drivers, local colleagues, teachers, nurses and builders who worked alongside the team often see things the pastor does not. They may also be the ones whose work was displaced or whose burden was increased. They should be asked separately and told what will be done with their answers.

The people the programme says it serves, in whatever way is appropriate and safe. Children are not interviewed by strangers. Others may be asked by a local person they trust. Not everyone can or should be asked, and the burden of being asked repeatedly is itself a cost to a host.

The team members and the leaders, who know what they did and what they saw. They are important witnesses but not the only ones.

The senders: the congregation, the board, the donors, the families. They are asked what they have learned and whether the programme has done what they were told it would do.

An outsider, where the body can find one: a person from another church or organisation, with no stake in the programme's continuing, who is asked to read the records and the host's responses and say what they see. This is a gift to a body that might otherwise judge itself too kindly.

3. What is asked

Plain questions, asked with care, are better than long forms. They cluster around a few themes.

The host's side.

  • What did the visits do for you and your community, and what did they cost?
  • Did the team do what you asked? Did it do things you did not ask?
  • Was the time right? Was the size right?
  • What changed, if anything, in your church or community that you can attribute to the visits? What did the visits leave that you must now carry?
  • What would you ask the team and the sending church to do differently?
  • Do you want visits to go on, and in what form?

The programme's own conduct.

  • Did the programme keep its promises to the host, to the team and to donors?
  • Did it follow its own written rules: the shared plan, the code of conduct, safeguarding, the use of money, the reports?
  • Were there any concerns raised (lecture 5-4), and how were they handled? Were there near misses?
  • Was the budget honest and was any surplus used as the donors were told (lecture 4-2)?
  • Did the reports and the photographs tell the truth (lectures 4-3 and 4-4)?

The sending side.

  • What did the congregation learn, and what did it change?
  • Did the programme take more from the church than it gave to the host: money, leaders' time, attention?
  • Did it do good to the young people, the retirees and the families who went, and did it harm any?

The alternatives.

  • What else could the same resources have done, in the host's judgment? Would a gift to the host's own priorities, a visit from the host to the sender, or a different programme have served better?

That last question is a hard one, and it is asked honestly or not at all. It is the one the critics in lecture 1-2 put, and a body that cannot bear to ask it has not looked at the matter.

4. What is claimed, and what cannot be counted

An evaluation ends in a report, and the report makes claims. A rule keeps it honest: claim only what you can show, and show it in the host's words as well as your own.

Here are examples, with a sentence before and a sentence after.

Before. "Our programme has transformed the village of Ottle and reached over four hundred people." After. "In each of the last four years a team of eight to twelve visited Ottle for two weeks. The village church tells us that the repair of the school roof was of use, that the summer English classes were welcome in the first two years and less so in the last two, and that the timing of the visits has been difficult for pupils preparing for examinations. We cannot say what became of the people who attended the classes."

The "before" claims a result that the body cannot show and that only the village could judge. The "after" tells what was done, what the host said and what is not known.

Some things can be counted, and it is honest to count them: how many teams went, how many weeks, what was spent, what came from whom, how many complaints or concerns were received and how they were handled, how many local workers were involved and paid. Counts are useful for honesty about money and conduct.

But counting has limits. The meaning of a visit to a host, a change in someone's faith, a friendship, a refusal to give up, a decision not to emigrate, a fear that was lessened: these cannot be counted and should not be turned into numbers. A body that reports only what is easy to count will drift toward whatever scores well. Be careful with numbers of "decisions", "reached" or "served": they look exact and are often not. Writers on short-term missions disagree about how much can be shown about the long-term effects of short visits, and the findings vary by setting, so be modest. If you are not sure that a number means what it seems to mean, leave it out.

This is a point where readers will not agree: how to evaluate a short-term programme. Some people want measurable results, set before the programme begins and checked afterwards: churches and boards that give money are right to ask what it did, and what cannot be measured is too easily used as an excuse. Others hold that most of what matters cannot be counted and that an effort to count it distorts the work: a visit's worth is in relationships, in encouragement and in slow change, and these are told by stories, not by tables. Still others hold that the only valid verdict is the host's, because the programme exists for the host, and no sending body can judge itself. Each position protects something real: accountability, truth and the host's ownership. This course requires less than any one of them: the host's voice is in the evaluation, nothing is claimed that cannot be shown, and numbers never replace the story of what was left behind. A body may use numbers and stories, together, as long as it does not hide behind either.

5. Continue, change or stop

At the end of an evaluation comes a decision, and the options are the same as for a single partnership (lecture 6-2): continue, change or stop.

Continue if the host says that the programme is of use, the body kept its promises and its rules, and the cost is justified in the host's judgment. Continuing is not the same as repeating: even a good programme should make one or two improvements each year.

Change if the programme has done some good and some harm, or if the host asks for a different form. A change might be a smaller team, a different season, a different kind of work, a change from teams to a single longer visit, more local leadership, a shift of money from travel to the host's own plans, or a closer link to a long-term partner.

Stop if the host asks for it, if the body cannot keep the promises and rules, if safeguarding or conduct has failed in ways that were not repaired, or if the programme serves its senders more than its hosts and cannot be changed. Stopping is not a failure. A programme that ends with honesty and with its debts paid is better than one that goes on as a habit. Ending is taken up in lecture 6-2: tell the host first, say why, keep the promises made, hand over what is owed.

The decision is made in the open, by more than one person, with the host's reply on the table. It is recorded, with its reasons. A decision made by one enthusiastic leader to go on, or by one tired leader to stop, is not an evaluation.

6. Learning from failure without blame

Something will go wrong in any programme. A team member will be hurt, a promise will be broken, a building will be unused, a report will be inflated, a host will be left with a burden. Lecture 5-4 dealt with harm to people: in a case like that the first duty is to those who were hurt, and the matter goes through the proper channels. Here the point is different. When a programme has failed in some way, a good body asks what was wrong in the arrangement, before it asks who was wrong.

A review of a failure has a few rules.

  • Start with what happened, in order, from as many sides as possible. The host's account is in it.
  • Ask what made the failure likely. A promise that was not written down, a role that nobody held, a question that was never asked, a person who was afraid to speak.
  • Separate the lesson from the person. If someone made a poor choice, that is dealt with by the body's proper process. A review that is only a search for a person to blame will teach everyone to hide failures.
  • Write down what will change, who will do it and by when. A lesson that is not written down is lost by the next team.
  • Tell the host and the donors, in plain words, what was learned and what will change.

A failure that is honestly reviewed is often worth more to a programme than a year of unquestioned success. The reverse is also true: an unexamined success can be a failure that nobody has been told about.

7. The whole congregation, the budget and the yearly review

The whole congregation. A programme that belongs to a small enthusiastic group will be judged by that group. A short-term programme should be reported to the whole congregation at least once a year: what was done, what the host said, what was spent, what is proposed. Those who did not go are asked what they think, and are heard. Some of the best questions come from the person who has never travelled and who asks "why?"

The budget and fairness. An evaluation looks at the budget as a moral document. Who paid, who benefited, how much went to travel and how much to the host, how much was spent on things the host did not ask for, and whether the cost of the programme was fair to those who could not pay (lecture 4-1). A programme that can be afforded only by the well-off, or that takes from a church's local ministry to pay for a trip, should ask whether it is honest.

A yearly review, on a calendar. Put the review on a fixed date, with a named person responsible and the host's part scheduled in advance. A review that happens "when we have time" does not happen. A modest review, done every year, is better than an exhaustive one that is done once. In some years the answer will be a plain "continue". Even then the host has been asked, and the church has looked.

No inflated claims. The review's report is written in the same way as other reports (lecture 4-4). It is shared with the host before it is shared at home, and the host is asked whether it is fair.

8. From three sides

For the sender, the hard part is to ask a question whose answer may end a programme that people love. The way through is to remember what the programme is for: it is for the host first, and the host's view is the test.

For the team, the hard part is that the evaluation may seem to deny what they experienced. It does not. What they saw and felt is real. It is one witness among several.

For the host, the hard part is to speak when speaking may have a cost. A host who is asked well and safely, who sees that an honest answer is received without a change in the friendship, and who hears back what was done with the answer, may come to trust the process. A host should also be free to say "this is not worth my time", and a body should be ready to hear that too.


Diagram 1. An evaluation: who, what, and the verdict

Judging a Programme With Humility The programme is judged, not the people 1. Who is asked, in order The host first, in the host's form Local workers beside the team Those served, safely, via a local person Team members and leaders The congregation and donors An outsider with no stake 2. What is asked What did it do, and what did it cost the host? Did we keep our promises and rules? What did the sender learn and change? What else could the same resources have done, in the host's view? 3. What is claimed Only what can be shown In the host's words as well Count money, weeks, concerns Do not count faith or "reached" Numbers never replace the story of what was left behind 4. Decide in the open: Continue, Change or Stop More than one person, the host's reply on the table, reasons recorded, review on a fixed date each year. Where evaluation usually fails A polite host, a form of five-out-of-five, a claim of "transformed", and a search for someone to blame.

핵심 요약

  • A programme is judged, not the people. The host is asked first, in the host's form, with a safe way to say no.
  • Ask what the programme did and cost the host, whether it kept its promises and rules, and what else the resources could have done.
  • Claim only what can be shown, in the host's words as well. Count money, weeks and concerns; do not count faith.
  • Readers differ about numbers, stories and the host's verdict alone. This course requires the host's voice, no unshown claims and the story of what was left.
  • Decide in the open to continue, change or stop. Review each year, learn from failure without blame, and report to the whole congregation.
Front Back
Who is asked, in order The host first, then local workers, those served, team and leaders, senders, and where possible an outsider.
Claim only what can be shown Say what was done, what the host said and what is not known. Avoid "transformed" and "reached".
Three positions on evaluation Measurable results, stories because most of what matters cannot be counted, and the host's verdict alone. The course requires the host's voice and no unshown claims.
Learning from failure Ask what was wrong in the arrangement before who was wrong. Write down what will change, who does it and by when.

One sentence to remember Judge the programme, not the people, by asking the host first and claiming no more than can be shown.

This week's action Write one claim your church or group makes about its mission work, and rewrite it so that it says only what could be shown and what the host has said.

이 과목 요약 전체 보기 →

스스로 확인해 보세요

읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.

묵상 및 토론

  • Why does the lecture say that the host should be asked first? What can a sending body do so that the host's answer is honest and not merely polite?
  • In the story of Ottle, why did the first form say five out of five? What did the second way of asking do differently?
  • State the three positions on numbers and stories in their strongest form. What does the course require whichever you prefer?
  • Choose one claim from a programme you know or can imagine. Rewrite it as a claim that could be shown, in the way of the "before and after" about Ottle.
  • How does a review of a failure ask "what was wrong in the arrangement" before "who was wrong"? Why does this matter?
  • Who in a congregation is rarely asked about its mission programme? What might they add?

로그인하시면 여기에 답을 적고 보관하실 수 있습니다

다음 단계

여기까지가 강의입니다. 아래는 읽은 사람들이 남긴 글입니다.