무료

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

PT730E Leading Worship: Music, Art and Media

Lecture 6-1: Looking Back at a Service

목차 31
PT730E Leading Worship: Music, Art and Media
제 0 장 · Introduction: Clearing a Road
  1. Introduction: Clearing a Road
제 1 장 · Week 1: Planning Worship
  1. Lecture 1-1: What Planning Worship Is, and Is Not
  2. Lecture 1-2: Reading the Gathering
  3. Lecture 1-3: Shapes of a Service
  4. Lecture 1-4: Welcome, Transitions and Silence
  5. Lecture 1-5: Practice Lab, Read One Service
제 2 장 · Week 2: Building a Team
  1. Lecture 2-1: Who Serves
  2. Lecture 2-2: Calling, Trying Out and Saying No
  3. Lecture 2-3: Training, Rotas and Rest
  4. Lecture 2-4: Rehearsal and the Week Before Sunday
  5. Lecture 2-5: Practice Lab: Map Your Team
제 3 장 · Week 3: Music and Choosing Songs
  1. Lecture 3-1: Choosing Songs
  2. Lecture 3-2: The Congregation's Voice
  3. Lecture 3-3: Leading Without Performing
  4. Lecture 3-4: Permission to Use Music
  5. Lecture 3-5: Practice Lab, A Month of Songs
제 4 장 · Week 4: Art, Space and Access
  1. Lecture 4-1: Where Traditions Differ on Art
  2. Lecture 4-2: Seeing, Moving, Reading Aloud
  3. Lecture 4-3: The Room
  4. Lecture 4-4: Worship Everyone Can Join
  5. Lecture 4-5: Practice Lab: Walk the Room
제 5 장 · Week 5: Media and Online Worship
  1. Lecture 5-1: Screens, Words and Sound
  2. Lecture 5-2: Recording and Streaming
  3. Lecture 5-3: Those Who Join Online
  4. Lecture 5-4: Testing a Tool
  5. Lecture 5-5: Practice Lab: One Slide, One Broadcast
제 6 장 · Week 6: Care, Review and the Long Run
  1. Lecture 6-1: Looking Back at a Service
  2. Lecture 6-2: Bringing Change
  3. Lecture 6-3: Caring for the Team
  4. Lecture 6-4: Safe Rooms, Safe Equipment
  5. Lecture 6-5: Practice Lab: Three Months Ahead

핵심만 먼저 보기 ↓

21분

A service ends, the room empties, and the people who served go home tired. By the next morning the service has already begun to change in memory. One hard moment grows large. One kind word is forgotten. Three weeks later nobody can say what actually happened, only how it felt.

This course rests on one claim. Leading worship is not standing in front of people. It is clearing a road between God and the gathered people. A person who clears a road has to walk it afterwards and look. The front of the room is a poor place to see the road from. The leader sees the backs of heads, hears their own voice, and is busy. So an honest community builds a small habit of looking back.

This lecture describes that habit: a short review of the service and the work, a way of asking the people without turning them into customers, simple notes, a refusal to chase numbers and comparisons, and a way of receiving both praise and complaint.

이 21분으로 얻는 것

  • Explain why the person at the front is badly placed to judge a service alone.
  • Run a short review that asks about the service and the work, not about a person's worth.
  • Ask the people for their view in a way that reaches quiet voices, and state what a survey cannot tell you.
  • Keep simple notes that show patterns over months and lead to one change at a time.
  • Sort a piece of praise or complaint into what to do with it.

Faithful are the wounds of a friend; although the kisses of an enemy are profuse." — Proverbs 27:6

World English Bible

This I pray, that your love may abound yet more and more in knowledge and all discernment; so that you may approve the things that are excellent; that you may be sincere and without offense to the day of Christ;" — Philippians 1:9-10

WEB

The proverb says that an honest hurt from a friend is more trustworthy than flattery from someone who wants something. Paul prays for love that grows in knowledge and discernment, so that people can tell what matters. Reviewing a service asks for both: friends who will tell the truth, and the discernment to know which truths matter.

1. Why the front is the wrong place to judge from

Think of a person who guides a group across a river by placing stones. While they are placing the stones they cannot see how the walkers are managing. They see the next stone. The walkers know whether the third stone was too far away.

The leader of worship is in the same position. A leader may think the transition after the reading was smooth, because they knew what was coming. A newcomer in the third row may have been lost for two minutes. A leader may think the sound was fine, because the monitor near them was set well. A grandmother at the back may have heard only the drum.

Memory adds a second problem. We remember the mistake that embarrassed us and forget the twenty parts that went well. We also remember the one person who spoke to us at the door, and forget the forty who did not. If a community decides what to change from memory and from the loudest voice, it changes the wrong things.

A review does not need to be formal. In a house church of eight it may be two people talking over a meal. In a parish with a choir and a parish council it may be a standing item on one meeting a month. The point is that someone looks, on purpose, soon after the event, and writes down a few lines.

2. Look at the service and the work, not at the person

The first rule of a good review is about its subject. A review looks at the service and the work. It does not look at the worth of a person.

Compare two notes written after the same Sunday (an invented example).

  • "Maria is not a good singer and should not lead."
  • "The second song was pitched too high for most voices. Many people stopped singing in the last verse."

The first note is a verdict on a person. It cannot be acted on except by removing her. It also teaches the team that a review is a trial. The second note describes what happened to the people. It points to something that can be changed: the key, the song, or how it was introduced. The second note may even be about the same moment. What differs is where it looks.

To keep the review on the work, use four plain questions. They follow the simple frame used for planning in lecture 1-3: gathering, hearing, answering and sending.

  1. Could people arrive and settle? Did a newcomer know where to sit and what to do? Was the welcome clear?
  2. Could people follow what was said and read? Was the sound clear? Could the words be seen? Were the transitions understandable?
  3. Could people answer? Did they sing, pray, respond, keep silence? Where did they stop, and why might they have stopped?
  4. Did the work go as planned, and how is the team? Did people know their parts? Was anyone rushed, tired or left alone?

Notice that the fourth question includes the team. A review that asks only about the congregation forgets the people who carried the service. Lecture 6-3 returns to that.

Notice also what the questions leave out. They do not ask whether the service was "powerful" or whether it "worked." Some people hold that a felt atmosphere is the Spirit's presence, and others hold that feeling and presence must be kept apart (lecture 3-3). A review does not need to settle that. It can ask a question that both can answer: did the people have a clear road to answer God?

3. A short review in ten minutes

A small review can be done in about ten minutes by the people who served. Here is one way (an invented example).

When. Within a few days, not at the door and not when everyone is exhausted. In many communities the day after, or the midweek rehearsal, works well. Do not hold it where the people being reviewed cannot speak freely.

Who. The people who served, and, if possible, one person who only attended and was not in charge of anything. That person sees the road from the other end.

How. One person keeps the time and the page. Begin with facts: what was planned, what happened. Then thanks, said specifically ("the reader paused after each part of the story, and people could follow it"). Then the difficult places. Then one decision.

What is written. One page, three short lists:

Keep Change Ask
What worked and should be repeated One or two things to change next time A question we cannot answer ourselves

The "Ask" column matters. Often a team does not know why people stopped singing. Rather than guess, it writes the question and asks someone.

Keep the number of changes small. A team that changes six things at once cannot tell which change helped. Pick one or two. The others go on a list for later.

4. Asking the people

The congregation sees the road from the other end, so their view is worth having. But asking is a skill, and it can be done badly.

Ask a few specific questions, not "How was it?" The answer to "How was it?" is "Fine." People are polite, and many do not know what you want. Compare: "Could you hear the readings from where you sat?" "Was there a part you could not follow?" "Was there a moment when you felt able to join in?" These can be answered in a sentence.

Ask different voices. The people who speak up are rarely the whole community. Think about who is missing: the child, the older person who hears badly, the second-language speaker, the newcomer, the person who sits at the back, the person who joins online. A short conversation with one of them may teach more than a form handed to everyone. Do this with care. A newcomer asked to criticise a service they have attended twice may feel they are being tested.

Say what will happen with the answers. If you ask and nothing changes, people stop answering. If you ask and promise changes you cannot make, people are disappointed. A sentence such as "we will read all the answers, change one or two things, and tell you what we changed" is honest and small.

Know the limits of a survey. A card or a form is useful, and the course does not forbid it. But be clear about what it cannot do.

  • It reaches only the people who fill it in. They are often the ones with strong views.
  • It cannot reach those who have left, and they may be the people with the most to tell you.
  • It measures what people say about the service, and this is influenced by habit and taste. People often prefer what they know.
  • It cannot tell you whether anyone met God. No count of answers can do that, and a community should not pretend otherwise.

A survey is one lamp among several. Use it together with conversation and with your own notes.

5. Notes that show a pattern

One review tells you about one Sunday. Twenty reviews tell you about a community.

Keep the pages. A simple folder or a shared notebook is enough. Once or twice a year, read the "Change" and "Ask" columns together. Patterns appear that no single week showed. (An invented example.) A team finds that in six reviews out of ten, the same note appears: "the newcomers did not know when to stand." That is not a failure of any one person. It is a gap in how the gathering is guided, and the solution is to write one clear sentence of welcome (lecture 1-4).

Patterns also show what is going well. A team that never writes down its successes begins to think it has none.

Be careful with elegance here. A pattern can feel neat because of how you grouped the notes, not because of what happened. Hold a pattern loosely and test it: ask one person whether it matches what they saw.

6. Not chasing numbers or comparisons

Numbers are tempting because they look certain. How many came, how many sang, how many watched online. Such numbers are information. Attendance may tell you that a room is full and the sound needs care, or that a service time is hard for families. But a number is not a verdict. A small gathering that prays honestly is not failing. A full room is not proof that people were helped to answer God.

Comparison is a quieter temptation. We hear that another community has a larger team, a better sound, a bigger screen. Perhaps it is true. It tells you nothing about whether your people have a clear road. The honest question is the one Paul prays for: what is excellent, in the sense of what truly matters here, for these people, in this room?

A practical guard is to compare a service only with its own past, and only on matters you chose to look at. "Last quarter people were lost at the transition after the reading. This quarter they are not." That is a real improvement.

7. Receiving praise and complaint

A review will bring words from outside the team. Some are praise and some are complaint. Both need a way to be received.

Praise. Say thank you, and do not collect it. Praise is a kindness from one person, and the team can pass it along to everyone who helped. Notice also what the praise says. "That was beautiful" tells you little. "I could follow every word of the reading" tells you something real. If praise is kind but vague, you can ask gently what helped.

Complaint. The wise proverb says that wounds from a friend are faithful. Most complaints contain something true, even if the form is clumsy. Listen to the whole of it before you answer. Do not defend yourself at the door. Say, "Thank you for telling me. Let me think about it." Then sort it. A useful sort has four kinds:

  1. A fact about the room or the work. "I cannot hear the reader." Act on it.
  2. A matter of taste. "I prefer the older songs." This is real and deserves a hearing, but it is not the same as a fault. Lecture 6-2 describes how a community can handle such matters fairly.
  3. A concern about teaching or practice. "I do not think this belongs in a service." Take it to the people responsible for teaching in your community. Do not settle it among the volunteers.
  4. A personal attack, or a complaint about a person's character. This is not material for a service review. It goes, privately, to the responsible leader. If it describes harm, lecture 6-3 says what to do.

Sorting is not a way of dismissing people. It is a way of making sure each concern goes where it can be heard. A person who raises a matter of taste should not be treated as if they had attacked the team, and a person who reports harm should not be told it is a matter of taste.

Finally, remember that none of this measures a person. A team member who hears a complaint about a part of the service they led has not been told they are worthless. A leader should say so out loud, more than once.

8. One caution about time

A review that takes two hours every week will soon be dropped. Choose a rhythm the community can keep: ten minutes weekly, thirty minutes monthly, a longer look twice a year. A review that is small and kept is better than one that is ambitious and abandoned.


Diagram 1. A review loop and a way to sort what you hear

Looking Back: A Loop, and a Sort About the service and the work, never about a person's worth Plan people, order, time Serve the gathering happens Look back ten minutes, a page Change one or two things the loop begins again, with the change written into the next plan When someone speaks to you, sort what you hear 1. A fact "I cannot hear the reader." Act on it. 2. A taste "I prefer the older songs." Hear it fairly (6-2). 3. A teaching "This does not belong in worship." To those responsible. 4. A person a complaint about character or harm Privately to the responsible leader. Not every word needs a change. Every word needs a place to go.

핵심 요약

  • A leader at the front sees only part of the road, and memory favours the loud moment. A short review corrects both.
  • A review looks at the service and the work, never at a person's worth. "The key was too high" can be acted on; "she cannot sing" cannot.
  • Ask the people specific questions, ask quiet voices too, and say what will be done with the answers.
  • A survey reaches only those who answer, cannot reach those who left, and cannot tell whether anyone met God.
  • Numbers inform but do not judge. Compare a service with its own past, not with another community.
  • Sort what you hear into a fact, a taste, a teaching concern or a complaint about a person, and send each where it can be heard.
Front Back
Why review at all The front of the room is a poor place to see the road from, and memory exaggerates one moment.
The three lists on a review page Keep, Change, Ask.
The four ways to sort what you hear A fact, a taste, a teaching concern, a complaint about a person.
What a survey cannot do Reach those who left, escape habit and taste, or tell whether anyone met God.

One sentence to remember A review asks whether the road was clear for the people, and it never asks whether a person is worth less.

This week's action After your next gathering, write one page with three lists, Keep, Change and Ask, and choose only one change.

이 과목 요약 전체 보기 →

스스로 확인해 보세요

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

묵상 및 토론

  • Think of the last service you served at or attended. What one thing could you not have seen from where you stood?
  • Rewrite this note so that it looks at the work and not at the person: "The reader mumbles."
  • Whom in your community do you never ask? What would it take to hear from them with care?
  • What is one thing a survey in your setting could not tell you?
  • Which of the four kinds of complaint is hardest for you to receive calmly? Why?
  • What rhythm of review could your community actually keep for a year?

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

다음 단계

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