Lecture 2-2: Listening to a Congregation's Story
목차 31
- Lecture 1-1: The Faith and Its Clothing
- Lecture 1-2: Two Kinds of Problem: Fixing and Learning
- Lecture 1-3: Three Stories of Change in the Bible
- Lecture 1-4: Questions to Ask Before You Propose a Change
- Lecture 1-5: Practice Lab: What We Keep, What We Might Change
- Lecture 2-1: What Change Takes Away
- Lecture 2-2: Listening to a Congregation's Story
- Lecture 2-3: Generations, Languages and Cultures
- Lecture 2-4: Who Is Not in the Room
- Lecture 2-5: Practice Lab, A Change Seen from One Seat
- Lecture 3-1: Who Decides? Polities and Their Roads
- Lecture 3-2: Small Steps and Reversible Changes
- Lecture 3-3: Speaking About Change
- Lecture 3-4: Buildings, Money and Endings
- Lecture 3-5: Practice Lab: A One-Page Proposal
- Lecture 4-1: Conflict Is Not a Failure
- Lecture 4-2: Layers: Facts, Methods, Values, Relationships, Power
- Lecture 4-3: How Conflict Grows
- Lecture 4-4: Conflict or Harm?
- Lecture 4-5: Practice Lab: Drawing a Conflict Map
- Lecture 5-1: Where a Leader Stands
- Lecture 5-2: Running the Meeting
- Lecture 5-3: Calling in Help
- Lecture 5-4: Where Mediation Must Not Go
- Lecture 5-5: Practice Lab: What I Will Say First
Every community that gathers for long enough has a story. It is told at funerals and anniversaries and in the kitchen after a service. It has proud chapters, wounds, heroes, and a few events that no one mentions unless a stranger asks. A leader who proposes a change in the middle of this story, without knowing it, is like someone who walks into the third act of a play and starts rearranging the stage.
This lecture is about listening to that story before, and while, a change is considered. It is a practical lecture: who to ask, how long to take, which questions to put, how to record what is said, and how to report back. It rests on one rule that has to be stated first and stated again. Listening is not agreement. A leader who listens has promised to hear, not to do what each person asks.
이 21분으로 얻는 것
- Explain why a community's story is part of what a change must respect.
- Plan a listening session: who is invited, how large it is, how long it lasts, and what is said at the start.
- Choose open questions that invite a story, not a position.
- Describe how to record what was said and how to report it back honestly.
- State what a listening session does not promise.
Hear my teaching, my people. Turn your ears to the words of my mouth. I will open my mouth in a parable. I will utter dark sayings of old, Which we have heard and known, and our fathers have told us. We will not hide them from their children, telling to the generation to come the praises of Yahweh, his strength, and his wondrous works that he has done. For he established a testimony in Jacob, and appointed a teaching in Israel, which he commanded our fathers, that they should make them known to their children; that the generation to come might know, even the children who should be born; who should arise and tell their children, that they might set their hope in God, and not forget the works of God, but keep his commandments," — Psalm 78:1-7
World English Bible
that this may be a sign among you, that when your children ask in time to come, saying, ‘What do you mean by these stones?’ then you shall tell them, ‘Because the waters of the Jordan were cut off before the ark of the covenant of Yahweh. When it passed over the Jordan, the waters of the Jordan were cut off. These stones shall be for a memorial to the children of Israel forever.’”" — Joshua 4:6-7
WEB
He who gives answer before he hears, that is folly and shame to him." — Proverbs 18:13
WEB
Psalm 78 and Joshua 4 show a people taking care that the story is told, and told to those who come after. Proverbs 18:13 is a short warning to anyone who answers before they have heard. Neither text tells a modern leader how to run a meeting. They show what the people of God valued: remembering, and listening before replying.
1. A congregation has a story
The psalm opens with a vow not to hide from the children what the fathers told. The point is not that the story is flawless; the psalm goes on to tell of rebellion and failure as well as rescue. A story that includes the failures is a truthful story. In Joshua 4 the stones were set up so that when a child asked, "What do you mean by these stones?" there would be something to point to and someone to answer.
A congregation does the same thing with less ceremony. It tells how the first members met in a house, how the roof was paid for, how a pastor or priest or was loved or was hard to love, how a division came, how the building filled one year and emptied the next. The story is not a record of facts. It is a way a group of people say who they are. When a proposed change touches the story, it touches the group's sense of itself.
(An invented example: a congregation was founded by families who came together to share one rented hall after being turned away from others. The story of that first hall is told every year. When a proposal arrives to move the main gathering to a larger, better building, the leaders discuss rent and distance. The older members hear something else: a proposal to leave the place that is the first chapter of who they are.)
The leader who does not know this will give answers to questions that nobody asked.
2. Why a leader should listen before proposing
There is an objection to listening sessions, and it should be put in its strongest form. It says: they take time we do not have. People will say what they want and expect to get it, and a leader will lose control of the process. A leader who already knows what is needed is only delaying. In any case, in most congregations the people who come to a listening session are the people who always come, so the leader hears the same voices again.
Each part of this is partly true. Listening can be used to stall. Sessions are sometimes dominated by a few. And a leader may indeed know what is needed.
But a listening session is not meant to find out what the leader already knows. It is meant to find out what the leader does not know: what the community treasures, what it fears, which wounds are still open, who carries the memory, and what words will carry weight. These cannot be learned from a spreadsheet. A leader who skips this learning may be right about the change and wrong about the road, and the road is where most changes fail. The Bible puts the warning shortly: "He who gives answer before he hears, that is folly and shame to him."
A second reason is respect. People who are asked what they think are treated as members of a body, not as an audience. Even a person who does not get what they asked for will more often accept the outcome when they know they were heard.
3. Say what listening is not
Begin every session with the same short statement, in plain words. For example:
"We are here to listen. Nothing has been decided here today. We are not taking a vote. I cannot promise to do what each person asks, and some of you will ask for things that are opposite. I do promise that I will hear it, write it down, and tell you what I heard."
If this is not said, some people will take the session as a promise, and the leader will later seem to have broken it. If it is said, the session is honest.
4. Who is invited
The aim is to reach the whole community, not only the committed centre. Think in terms of people, not of titles.
- Different ages. If the proposal touches children's ministry, hear the parents and also the children's teachers; if it touches the building, hear those who rely on stairs and those who push prams.
- Different standing. Include long-serving officers and also those who have no office.
- The quiet. Some will not speak in a large circle. Offer a second way: a short conversation one-to-one, a written note, a telephone call.
- Those on the edge. People who come irregularly, who sit at the back, who are new, who arrived from another tradition.
- Different groups. If the community has more than one language or more than one habit of worship, hear each in its own way (lecture 2-3 returns to this).
Hold sessions in small groups, usually six to ten people, so that each person can speak. Where the group is mixed in age or standing, a session by itself for a particular group (the young, the very old, the newcomers) can be useful, because people speak more freely among those they feel close to. It is not a good idea to put the strongest critic and the leader's closest ally at the same table by default; arrange the groups so that no one feels outnumbered.
A leader should ask whoever holds oversight in the community's own arrangement before starting. In some bodies a bishop, a council, a board of elders or a membership meeting needs to know that a listening process is under way. This course does not say who that is; the reader's written constitution does.
5. How long, and where
A session of sixty to ninety minutes is usually enough. Shorter does not allow a story to unfold; longer tires people. Hold it in a place that is not charged with a particular meaning: not the leader's office, not the front of the sanctuary. Offer tea or water. Start and finish on time. If many sessions are held, keep the format the same, so that what is heard in one can fairly be compared with what is heard in another.
6. Questions that invite a story
A question about the proposed change gets a position. A question about the past and the hope gets a story. Questions that tend to work:
- When did this community feel most alive to you? What was happening?
- What would you want someone new to know about this place?
- Who are the people who have carried this community? What did they do?
- What has hurt us as a community? What do we find hard to speak of?
- What do you hope never changes here?
- What do you think we are being asked to learn?
The fifth question deserves particular care. It tells you what the people treasure. Write it down exactly.
Do not begin with: "What do you think of my proposal?" Do not use the session to defend a plan. If a person asks, "Are you going to do X?" the honest answer may be: "I haven't decided. I would like to know what X means to you."
7. The leader listens to hear, not to answer
A listening leader does four things.
Asks, and then is quiet. Silence in a group usually means someone is thinking, not that nothing is being said. Wait.
Asks for the story behind the opinion. "Tell me about the last time that happened" is better than "Why do you think that?"
Repeats back. "Let me check I have understood: you were saying that..." This lets the speaker correct the leader, and it slows the pace.
Does not defend, argue or correct. If a speaker says something the leader thinks is untrue about a past event, the session is not the place to correct it. Note it. Check the facts later.
This is not counselling. Skills for listening to a person in distress are taught in course LM205E, and a session is not the place for them. If someone begins to speak of a harm done to them or to someone else, in this community or elsewhere, particularly abuse, violence or a danger to a child or a vulnerable adult, the leader gently stops the session for that person, thanks them, does not ask for details in front of the group, and afterwards speaks with the person named in the community's written safeguarding policy. Lecture 4-4 returns to this.
8. Recording what is said
Take notes where people can see them. Appoint a second person to write if possible, so that the leader can watch the room. Write what people said in their own words where you can, and mark clearly what is a quotation and what is your summary.
Do not attach names to remarks unless the person has agreed. Most people speak more honestly when they know they will not be quoted by name. Record patterns: how many people said something, and in what words, and whether it came up in more than one group. Record also what was not said, particularly in the quiet groups. Record contradictions; do not smooth them away.
Keep the notes in a place that the community's rules for records allow, and tell people how long they will be kept and who will see them. Follow local law on the keeping of personal information; this course gives no legal advice.
9. Reporting back
A session that is never reported is worse than none. Within a few weeks, tell the people what you heard. Do this in a form that the whole community can see: a short written summary, a talk at a gathering, or both.
A fair report has four parts:
- What we heard as the shared story. The proud chapters, and also the hard ones.
- What people treasure. The things that came up in many mouths.
- Where people disagreed. Honestly. Without naming individuals.
- What will happen next, and what will not. Say plainly if a request will not be met, and why, and what part of it will be.
A report that lists only what the leader wished to hear teaches people not to speak next time.
10. The central claim, once more
The central claim of this course is that conflict is where treasures collide. A listening session is where the treasures are first named, before they have collided. It does not remove disagreement. It does something more modest and more useful: it lets the leader and the community see together what each side holds dear, so that when a decision comes, the discussion is about real things and not about phantoms.
Diagram 1. A congregation's story on one line
Diagram 2. A listening session in order
| Step | What the leader does |
|---|---|
| Before | Asks permission of whoever holds oversight; chooses small groups; invites the quiet and the edge |
| Opening | Says what listening is not: no vote, no promise, nothing decided |
| During | Asks story questions, is quiet, repeats back, does not defend |
| Recording | Writes where all can see; no names without consent; notes patterns and contradictions |
| After | Reports back within a few weeks: shared story, what is treasured, where people differ, what happens next |
핵심 요약
- A congregation has a story, with proud chapters and wounds. A change that touches the story touches the group's sense of itself.
- Listening is not agreement. Begin every session by saying that nothing is decided, there is no vote, and no promise is made except to hear and report.
- Invite across ages and standing, include the quiet and the edge, and hold small groups of six to ten for sixty to ninety minutes.
- Ask questions that invite a story: when were we most alive, what has hurt us, what do you hope never changes.
- Record where people can see, without names unless agreed, and mark contradictions. Report back within a few weeks, including what will not happen.
- If someone speaks of abuse or danger, stop for that person and refer the matter to the written safeguarding policy.
| Front | Back |
|---|---|
| First sentence of a session | "We are here to listen. Nothing is decided. This is not a vote." |
| Who to invite | Different ages and standing, the quiet, the edge, each language group; small groups of six to ten. |
| Story questions | When were we most alive? What has hurt us? What do you hope never changes? |
| Fair report in four parts | Shared story; what is treasured; where people differ; what happens next and what does not. |
One sentence to remember Listening is not agreement, but a change proposed without listening is proposed to a stranger.
This week's action Write down six story questions you could ask in your own community, and the names of the kinds of people (not individuals) who would be least likely to be asked.
스스로 확인해 보세요
읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.
묵상 및 토론
- What is one chapter in the story of a community you belong to that is told often? What does the telling say about who they are?
- Why does the lecture say that a listening session is not a vote? What might go wrong if people thought it was?
- State, in its strongest form, the objection that listening sessions only delay a leader who already knows what is needed. How does the lecture answer it?
- Which people are least likely to come to a listening session in a community you know? What second way could you offer them?
- Why does the lecture warn against attaching names to remarks? When might a name be appropriate?