Lecture 6-1: The First Days Home: Debriefing and Hearing the Host
Contents 31
- Lecture 1-1: Sent and Welcomed: Scripture and the Long History of Going
- Lecture 1-2: The Honest Argument About Short-Term Trips
- Lecture 1-3: Whose Work Is It? Hosts, Guests, Power and Money
- Lecture 1-4: Kinds of Teams, Kinds of Trips
- Lecture 1-5: Practice Lab: Why We Want to Go
- Lecture 2-1: Beginning With an Invitation
- Lecture 2-2: Designing the Days: What a Visit Leaves Behind
- Lecture 2-3: Teams With Special Skills: Medical, Teaching, Building, Youth
- Lecture 2-4: Near Home and Far Away: Local Trips and Online Teams
- Lecture 2-5: Practice Lab: A Shared Plan With the Host
- Lecture 3-1: Choosing the Team
- Lecture 3-2: Training the Guests
- Lecture 3-3: Health, Safety and Documents: Preparing Without Giving Advice
- Lecture 3-4: Safeguarding Children and Vulnerable People
- Lecture 3-5: Practice Lab: A Code of Conduct
- Lecture 4-1: What a Trip Costs and What It Is Worth
- Lecture 4-2: Raising Support Honestly
- Lecture 4-3: Photographs, Stories and Social Media
- Lecture 4-4: Reports and Testimonies That Tell the Truth
- Lecture 4-5: Practice Lab: Checking a Fundraising Letter and a Post
- Lecture 5-1: The Guest's Posture: Serving Under Local Leadership
- Lecture 5-2: Planning for Crisis and for Withdrawal
- Lecture 5-3: Team Conflict, Tiredness and Spiritual Care
- Lecture 5-4: When Harm Has Happened: Honest Reporting and Accountability
- Lecture 5-5: Practice Lab: A Crisis Scenario
- Lecture 6-1: The First Days Home: Debriefing and Hearing the Host
- Lecture 6-2: What Remains: Continuing, Changing or Ending a Partnership
- Lecture 6-3: Calling, Discernment and the Ones Who Stay Home
- Lecture 6-4: Judging the Programme: Evaluation With Humility
- Lecture 6-5: Practice Lab: A Statement of Principles for Our Church
The plane lands, the bags come round, and the team goes home. For the team it feels like the end. For the host, the visit has been one event in a year that goes on. The cooking has to be paid for. The beds have to be washed. The interpreter goes back to a full-time job. The host pastor has to explain, to people who stayed away, what the guests did and why. The trip is not over. Only the guests' part of it is over.
This lecture is about the first days and weeks after the return. It argues that a trip is not finished when the team arrives home. It is finished when the host has been asked what the visit was like, and has been heard. The same is true of the home church: it needs an honest account, not a celebration only.
This is the first lecture of the last chapter, and it carries the course's central claim. A short-term trip is a humble partnership. In partnership, one side does not decide alone how it went. The claim closes two doors here. One door treats the return as the end of an experience: the team has been changed, and the story is now the team's to tell. The other treats the host as a source of material: warm words, photographs and a story for the church bulletin. The host is neither. The host is a partner who gets the first word about what happened.
The lecture does not say that the team's own feelings are unimportant. A team member who comes home tired, moved, confused or flat needs somewhere to say so. It does not say that a debrief is a kind of treatment. And it gives no medical or mental-health advice: if a person is struggling after a return, the right people to ask are a trusted pastor or priest, the organisation's care contact and a qualified health professional.
What these 32 minutes give you
- Describe a team debrief that has a shared part and a private part, and say what each is for.
- Name the kinds of change a team member may notice after returning, as things others may notice and not as diagnoses, and say where help can be found.
- Ask a host for an honest evaluation in a way that makes an honest answer possible, and receive it without defending.
- Write a thank-you that says something specific and does not ask the host for anything more.
- Explain what a team leaves behind that the host must carry, and what records are kept and discarded.
From there they sailed to Antioch, from where they had been committed to the grace of God for the work which they had fulfilled." — Acts 14:26
World English Bible
When they had arrived, and had gathered the assembly together, they reported all the things that God had done with them, and that he had opened a door of faith to the nations." — Acts 14:27
WEB
Test all things, and hold firmly that which is good." — 1 Thessalonians 5:21
WEB
Paul and Barnabas, at the end of a journey, sail back to the church that sent them, call the whole assembly together, and report. What they report is "what God had done with them", and the opening of a door to others. We read this as a pattern of ordinary return: the people who sent them are told, in public, in an honest way, and the account is about what God did, not about what the travellers achieved. The second verse is a short rule for any review: test what happened, keep what is good, and let go of what is not. We take from it only the permission to examine a trip honestly. It is not an instruction to judge anyone.
1. The trip is not over
A team usually plans its departure in great detail and its return in none. There is a flight home and perhaps a thank-you meeting. After that, everyone is tired and busy, and the matter fades.
That fading has a cost, and it is not the team who pay it. If nobody asks the host how the visit went, the host is left with a set of private judgments (what helped, what was awkward, what must now be repaired) and no one to give them to. If nobody asks the team members what they saw, they hold on to their own judgments, and the picture they carry home gets fixed by the first story they tell. If nobody asks the congregation to look at the trip honestly, the church learns only what the loudest speaker says.
So the return needs a plan, made before departure, as part of the shared plan with the host (lecture 2-1). It has four parts: a debrief for the team, an evaluation from the host, a thank-you, and an account to the church and to donors. This lecture takes the first three. The account to donors and the congregation is the subject of lecture 4-4, and we will touch it again at the end.
2. The debrief: a shared part and a private part
A debrief is a planned conversation, after a trip, in which people say what happened and what they make of it. It is not a party, and it is not a trial. It has a shared part and a private part, and the two do different work.
The shared part is a meeting of the team, with the leader, within a few weeks of the return. A reasonable length is two to three hours; set the time by what the team needs and not by a rule. A plain agenda works well:
- What did we expect, and what did we find?
- What did the host ask of us, and what did we actually do? Where did the two differ?
- What did we learn that we did not know before?
- What went wrong, or came near to going wrong? What would we change?
- What did we leave behind that someone else now has to carry?
- What do we say to the church, and what do we not say?
Two points keep the meeting honest. First, ask what happened before you ask what it meant. A team that jumps at once to meaning ("God showed us...") may skip what actually occurred. Second, the leader speaks last and says what went wrong in the leader's own part. A leader who defends the plan teaches the team that only success may be named.
The private part is a short conversation between each team member and someone who is not the leader or a close friend: a pastor, a priest, a spiritual director, an older member of the church, or a care contact the organisation names. It does not report to the leader. It lets a person say what is hard to say in a room: that they were frightened, that they disliked a member of the team, that something bothered them about how the team treated the hosts, that they came back with doubts about their own faith or about the church's plan. The person who listens does not have to solve anything. The listener's work is to hear, to ask good questions, and to know when to point to someone with more training.
(An invented example.) The Ravenhill Church youth team returned from the town of Kest. At the shared debrief, the leader, Mr Adeyemi, spoke first. "I changed the schedule on the third day without asking Pastor Ilse," he said. "I thought it was a small matter. Looking back, it was not." The team members relaxed. A girl of sixteen then said that she had been uncomfortable when the team took photographs inside a family's home. At the private conversations, which a retired teacher from the church had agreed to hold, another member said he had not been able to pray for the whole of the second week and had told nobody. None of these was a scandal. All of them would have disappeared if the team had only been asked to share "highlights".
3. Coming home: what others may notice
Many people find the first weeks after a return harder than they expected. This is a common experience and not a sign of weakness. Writers on cross-cultural life call it by several names: reverse culture shock, return shock, re-entry. The full course on cross-cultural communication and adjustment treats it properly. Here we give only a team-sized note.
This is not a diagnosis, and nothing in this lecture is medical or mental-health advice. We describe what a team member, a friend or a family member may notice, and say whom to ask.
Things people sometimes notice in the weeks after a trip: tiredness that does not go away with a few nights' sleep; a flatness, or a restlessness, when ordinary life resumes; irritation at home, at shops, at the way people talk about small things; sadness or grief for people left behind; difficulty explaining the trip, or the feeling that nobody wants to hear the whole story; guilt about comfort; a sense that one's own church now looks strange. Some people notice none of these. Some people notice them for a short time and then they pass.
Three notes help. First, ask the person, and listen. A question such as "What has been hard since you came back?" is better than advice. Second, do not read a sign as a verdict. A person who is flat for a week is not "in crisis"; a person who has been struggling for a long time is not "ungrateful". Third, know whom to ask. If a person's difficulty goes on, grows worse, or makes ordinary life hard to manage, the right people are the organisation's care contact, a trusted pastor or priest, and a qualified health professional. If a person is in danger now, call the local emergency number.
One further point belongs here. A team member sometimes comes home angry at the host, or at the team, or at the church that sent them. Anger is information. It may point to something that went wrong and should be heard (lecture 5-3). It may also be a sign of tiredness. The debrief is a better place for it than a social media post.
4. Asking the host, and hearing the answer
The most important piece of the return is the host's evaluation. It is also the one most often left out, for a plain reason: it is hard to ask, and it is harder to hear.
It is hard to ask because the host has been generous, and a question about how it went can seem to sound ungrateful. It is hard for the host to answer because the visitors may be a source of money, introductions or future help, and an honest "that did not help" may seem to put those things at risk. We said in lecture 1-3 that the one who holds the money holds power, even when nobody means to, and that a host may hear any question from the guest as a question from a funder. So asking well takes some care.
Here are the elements of a way of asking that makes an honest answer possible.
Ask early, and ask in advance. At the time of the first agreement (lecture 2-1), say that a review will take place and what it will be used for. A host who knows in advance that the question is coming can think about it.
Ask someone other than the person who hosted you, as well. A host pastor may say "it was wonderful" to guests because that is what a host says. An interpreter, a person from the host church who was not in charge, a local colleague of the organisation, or a person the host himself chooses, may say something else. The host should be told who will be asked and should agree.
Ask in the host's own language, and allow the host to choose the form. Some hosts will write. Some will speak. Some will prefer a conversation with a trusted third person who carries the answer back. Do not require a form.
Ask open questions about what was left, not only about what was good. Plain questions work better than a scale of one to five:
- What helped most? What was hard to carry?
- What did the team do that you wish it had not? What did it not do that you hoped for?
- What are you now doing because of the visit? What are you doing in spite of it?
- What did the visit cost you, in time, in money and in other ways?
- If we came again, what should be different? And do you want us to come again, or to come later, or not at all?
- What shall we say to our church, and what shall we not say?
Make it safe to say no. The last question about coming again matters most. A host should be told, in so many words, that "no", or "later", or "not like this" is a good and welcome answer, and that it will not change the team's friendship or the church's prayers. Whether it will change a gift or a grant is a different matter, and honesty requires that it be said openly: a funder should say beforehand whether any decision about money will depend on the answer, and a body that says "no" will not should keep its word.
Receive the answer without defending. This is the part that is hardest. When the host says something painful, the instinct is to explain: "We only meant...", "In our country...", "Well, the schedule you gave us...". Do not do it. The host has just taken a risk. A good response is short: "Thank you. Say more." Then write it down, in the host's words, and read it back to check it. Defence can come later, in private, with the team, when you decide what you will change.
Here is a short worked example. It is invented.
Before. Coordinator: "Pastor Ilse, I am sure the visit went well. Did you find it useful? We would love to come again next year." Pastor Ilse: "It was a blessing. Of course you must come."
After. Coordinator: "Pastor Ilse, thank you for having us. We would like to hear what it was really like for you, and we will not change our friendship whatever you say. May I ask three questions? What was hard for you to carry? What would you want us to do differently? And is next year a good time, or would you prefer we waited?" Pastor Ilse: "The first week was hard. We had no cook, because Mrs Ovo was away, and my wife did all of it. I did not know how to tell you. Next year, please let us choose the week." Coordinator: "Thank you. I have written that down: a week of your choosing, and we will ask first about meals. Is there more?"
The "before" version invites a polite answer. The "after" version tells the host that there is a safe way to say a difficult thing, and it asks a question to which the answer might be "no".
This is a point where readers will not agree: how openly a team should speak, at home, about the difficulties it saw. Some hold that supporters have a right to know the whole truth, including what went wrong and how hard things were, because they gave money and prayer. Some hold that open reporting can expose hosts, families and local believers, and that a team does not own other people's stories. Some hold that stories of need and difficulty are useful for raising money but bend the picture of the place. All three are describing real dangers. This course requires less than any one of them: the account at home is honest in substance, protective of local people, and never used to pressure givers. Lecture 4-4 sets this out. Here the rule for the debrief is simple: before the team tells any story in public, the team asks the host what may be said, and takes the host's answer.
5. Thanking well
Thanks are owed, and they are easy to do badly. A gift of goodwill that says only "thank you for everything, you are wonderful" says little. A thank-you that has a request tucked in the last line ("we hope we can come again, and perhaps you might help with our visa letter?") turns thanks into business.
A good thank-you is specific, written, and unattached.
- Specific: it names what the host and the host's people did. "Mrs Ovo's cooking on the first Sunday" is better than "your hospitality". Name the interpreter, the driver, the person who gave up a bed.
- Written as well as spoken. A letter or a message can be kept and shown to a family or a congregation. A spoken thanks at the airport is soon forgotten.
- Unattached: no request, no promise of more, no fundraising. A request, if there is one, goes in a separate message on another day.
- Sent to the people, not only to the leader. Where a host church has a committee, write to the committee. Where a family has hosted, write to the family. Where a team member has a personal gift to give, do it through the host leader (lecture 5-1).
A sentence for your own letter: "Thank you for giving us your table, your time and your trust. We came to learn, and you taught us."
6. What we left behind, and what we keep
Every trip leaves something. Some of it is good. Some of it is a weight. Lecture 2-2 asked what a visit leaves behind; here the question comes back after the event. In the debrief, and in conversation with the host, ask:
- Is there anything unfinished that the host must now finish? A wall begun and not completed, a promise of supplies, a class that has lost its teacher?
- Is there equipment, food or a donated item that the host must now keep, repair or pay for?
- Did we raise any hope that we cannot meet? A personal promise made by a team member, a remark about "next year", an unspoken sense of a gift to come?
- Did we leave a cost: unpaid bills for our meals, a team member's damage to property, a strain among local helpers?
If the answer is yes, the team's first duty is to say so, plainly, to the host and to ask what is needed. Do not wait to be asked. Where the team did make a promise, the host leader and the team leader should look at it together and decide what can be kept, what must be renegotiated and what must be honestly withdrawn. A promise that cannot be kept should be taken back with an apology and not left to fade.
7. Records: keep little, protect what you keep
A team gathers records: application forms, health and emergency information, consent forms, photographs, the team's budget and receipts, notes from the debrief, the host's evaluation, and any report of a concern. What should be done with them?
This lecture does not give legal advice, and rules about personal information, storage and retention differ from place to place. The principle is: find out in advance, from the organisation's written policy and the law of the places concerned, what must be kept and for how long, write it down and keep it where it can be reached. Beyond that, four habits help.
Keep little. Personal information that is no longer needed (health details, passport copies, emergency contacts) should be deleted or returned according to the written policy, not kept "just in case".
Keep safely. What is kept is kept in a place with limited access, and the number of people who can open it is small.
Never publish what is sensitive. The names, photographs and places of local believers, workers or families who may be at risk are not posted or shared without their consent (lecture 4-3). A testimony from a person who is vulnerable is held by the leader or the organisation and shared in a general form, if at all.
Keep the record of any concern. If a concern was raised about a person's conduct on the trip, the record goes to the organisation's safeguarding contact according to its policy (lecture 5-4). It is not for the team's private archive and it is not deleted because the trip is over.
8. What to do with the whole thing
A debrief, an evaluation, a thank-you and a clean-up of records are not a ceremony. Their purpose is to give the next decision, about the relationship and about the programme, something true to stand on. Lecture 6-2 takes up what comes next: continuing, changing or ending a partnership.
From the host's side, one point more. A host may be tired too, and may not want a long review right away. A host may have other visitors, a harvest or a funeral. Ask when the host would like to talk, and keep to it. The host's time is not owed to the guests.
And from the sending church's side: many congregations will want a service, a report and a slide show. These are fine, if they are honest and if the host has agreed to what is shown. The test is whether a person from the host church, sitting in the room, would recognise the account as true and respectful.
Diagram 1. The return, in four parts
In short
- The trip is not finished when the team lands. It is finished when the host has been asked how it went and has been heard.
- A debrief has a shared part and a private part. Ask what happened before what it meant, and the leader speaks last.
- Difficulty after a return is something others may notice, not a diagnosis. Ask the person; if it goes on, ask a pastor or priest, the care contact and a health professional.
- Ask the host in the host's form, from more than one voice, and make "no" or "later" a safe answer. Receive it without defending.
- A thank-you is specific, written and unattached. Say plainly what the team left for the host to carry. Keep few records, and keep them safely.
| Front | Back |
|---|---|
| The two parts of a debrief | A shared meeting of the team, with the leader speaking last, and a private talk with a listener who is not the leader. |
| Hearing the host | Ask open questions in the host's form, from more than one voice, say that "no" or "later" is welcome, and receive the answer without defending. |
| A good thank-you | Specific, written, sent to the people who bore the cost, and carrying no request. |
| What a team leaves behind | Unfinished work, goods to keep, hopes raised and costs. Name them to the host, and take back promises that cannot be kept. |
One sentence to remember The trip ends when the host has been asked and heard, not when the team lands.
This week's action Write three questions you would ask a host after a visit, so that "no" or "later" is a safe answer, and read them aloud to one person.
Check yourself
Not "did you read it" but "can you explain it". Ticks are kept on this device only.
Reflection and discussion
- Why does the lecture say that a trip is "not over" when the team lands? Say it once from the host's side and once from the team's side.
- What are the shared part and the private part of a debrief for? What might a team member say in one that they would not say in the other?
- Why is it hard for a host to give an honest evaluation, and what in the way of asking can help? Which of the six questions would be hardest for you to ask?
- In the "before and after" exchange with Pastor Ilse, what changed in the way the question was put? What did the coordinator do when the answer was hard to hear?
- What is a specific, written, unattached thank-you? Think of a thank-you you have received that was not one, and say what was missing.
- What records would your church keep after a trip, and who would decide when to discard them? What must never be shared without the consent of the person?