Lecture 1-3: Asking Well
목차 31
- Lecture 1-1: Service as a Response to Grace
- Lecture 1-2: Why People Come and Why They Leave
- Lecture 1-3: Asking Well
- Lecture 1-4: Volunteers, Staff and Clergy
- Lecture 1-5: Practice Lab: Why I Began to Serve
- Lecture 2-1: Writing a Role Description
- Lecture 2-2: Listening and Matching
- Lecture 2-3: Screening and Safeguarding for Roles
- Lecture 2-4: Young and Older Volunteers
- Lecture 2-5: Practice Lab: A Role Description in One Page
- Lecture 3-1: The First Month
- Lecture 3-2: Learning Alongside
- Lecture 3-3: The Volunteer Handbook
- Lecture 3-4: Serving in Worship: Liturgical and Free-Church Roles
- Lecture 3-5: Practice Lab: A First-Month Plan
- Lecture 4-1: Rotas, Cover and Rest
- Lecture 4-2: Communication and Digital Boundaries
- Lecture 4-3: Thanks and Recognition
- Lecture 4-4: Money, Expenses and Gifts
- Lecture 4-5: Practice Lab, A Thank-You Said Well
- Lecture 5-1: Recognising Weariness
- Lecture 5-2: When a Volunteer Tells You Something Hard
- Lecture 5-3: Difficult Conversations and Changing a Role
- Lecture 5-4: When Things Go Wrong: Complaints, Misconduct and Concerns
- Lecture 5-5: Practice Lab: What to Say to a Weary Volunteer
A request can be a gift or a trap, and the words may be nearly the same. "Could you possibly help with the children's group this autumn?" can be a respectful question. It can also be a net: the person feels watched, the leader already has the answer in mind, and everyone in the room knows what a "no" would cost.
This lecture is about the moment of asking. It is short in time and long in effect. Many coordinators say that more is decided in that conversation than in any later one: what the person thinks they have agreed to, how large they think it is, and whether they feel free. We will look at the difference between an open door and a named invitation; at what a clear request contains; at what it means to leave a person free to refuse; and at the way requests land differently in different cultures. At the end we will look at a question on which readers disagree: how quickly a new person should be invited to serve.
이 26분으로 얻는 것
- Explain the difference between a public notice and a personal invitation, and say when each is right.
- State the three things a clear request names (what, how much, until when) and say why an open-ended request is harmful.
- Describe what it means to leave a person free to refuse, in four concrete practices.
- Explain how culture can turn a leader's request into an order, and name one way to prevent it.
- State fairly the different views on inviting a new person to serve, and what this course requires whichever view a community holds.
For which of you, desiring to build a tower, doesn’t first sit down and count the cost, to see if he has enough to complete it? Or perhaps, when he has laid a foundation, and is not able to finish, everyone who sees begins to mock him, saying, ‘This man began to build, and wasn’t able to finish.’" — Luke 14:28-30
World English Bible
Therefore though I have all boldness in Christ to command you that which is appropriate, yet for love’s sake I rather beg, being such a one as Paul, the aged, but also a prisoner of Jesus Christ. I beg you for my child, whom I have become the father of in my chains, Onesimus, who once was useless to you, but now is useful to you and to me. I am sending him back. Therefore receive him, that is, my own heart, whom I desired to keep with me, that on your behalf he might serve me in my chains for the Good News. But I was willing to do nothing without your consent, that your goodness would not be as of necessity, but of free will." — Philemon 1:8-14
WEB
Let each man give according as he has determined in his heart; not grudgingly, or under compulsion; for God loves a cheerful giver." — 2 Corinthians 9:7
WEB
Jesus speaks in Luke about counting the cost before beginning. Paul, in Philemon, shows a leader asking for something large while refusing to command it. The verse from 2 Corinthians gives the principle: what is given should be given freely and from the heart.
1. An open door and a named invitation
There are two different kinds of asking, and a community needs both.
A public notice is an open door. It says, in a bulletin, an announcement, a message board or a page on the website: "We need people to help with the Saturday meal. If you would like to join, speak to Maria." It is addressed to everyone, which means it is addressed to no one in particular. It lets people find a place on their own terms. It costs nothing to ignore. It reaches those who are already looking.
A personal invitation is addressed to a person. It says, "Grace, we've noticed how you looked after the new families last month. Would you think about helping with the Saturday meal?" It names the person and, if possible, something about them. It reaches the person who is not looking and would never put themselves forward.
Both are honest. They do different work. The public notice makes sure that nobody is shut out. The personal invitation makes sure that the quiet, the shy, the newly arrived and the modest are not left out because they did not push.
There is a pattern worth keeping in mind. People most often say yes when they are asked by name. That is a general observation made by many coordinators and it should be treated as such; no figure is given here. It has a reason behind it. A notice asks "who will?" A personal invitation asks "will you?" and the second question is the one that most people can answer. A person does not become responsible for a task by reading a bulletin; they become responsible when someone they trust looks at them and asks.
But the strength of the personal invitation is also its danger. When someone looks at you and asks, saying no is hard. The more respect you have for the person asking, the harder it is. A good coordinator knows that a named invitation puts pressure on a person even when no pressure is intended, and builds in room to refuse. That is the third part of this lecture.
2. A clear request
Jesus asks, in Luke 14:28, who among his listeners, wanting to build a tower, would not first sit down and count the cost to see if there was enough to finish. He says this about , but the picture applies to any large undertaking. A person who begins something without knowing its cost may find, in verse 29, that they cannot finish, and be mocked by those who watch. A request that does not state its cost asks a volunteer to build without counting.
A clear request tells the person three things.
What. The actual work, in plain words, as verbs. Not "help with the youth" but "stand at the door of the youth room on Friday evenings, greet each young person, and mark the list." Not "be part of the music" but "play the keyboard at the second service, twice a month, and come to a Thursday rehearsal."
How much. The size of the commitment in hours and days, including what is invisible: preparation, travel, set-up and clearing. A person who is told "an hour on Sunday" and discovers that it means arriving two hours early and staying after to clean will feel misled, even if no one meant to mislead. Coordinators often underestimate the size of what they ask because they know the job so well that its parts have become invisible to them.
Until when. A start and an end. "For the autumn term, until December, and then we will talk again." "Until the end of the school year." "For the three weeks of the summer club." An end date does something important: it makes it possible to say yes. A person who says yes to something with no end has said yes to an unknown future.
The opposite is the open-ended request: "Could you help us out with the kitchen?" It sounds modest. To a conscientious person it can sound like an endless promise. They will hear, "this is yours now" and may be unable to imagine saying "I think I'm finished." A great many people leave the kitchen, the children's room and the sound desk not because they dislike the work but because they could not see a way to put it down. Lecture 2-1 returns to this in detail with the one-page role description. For now, the habit to build is simple: before you ask, know what, how much and until when.
Here is an invented example of the same request, asked badly and asked well.
(An invented example.) Daniel is a retired bus driver who has been attending a small church for a year. The coordinator, Ruth, says after the service, "We're short in the kitchen. You'd be perfect." Daniel, who is a polite man, says, "Of course." By the third week he is washing up every Sunday and several Wednesdays, because nobody told him he could stop and he did not like to say. In the second version, Ruth says, "Daniel, I wonder if I could ask you something. On the first and third Sundays, we need someone to wash up after the shared lunch, about forty minutes. It would be until Easter, and then we'll talk again. You don't need to answer now. If it isn't right for you, that is fine." Daniel says he will think about it, and a week later says yes to the first Sundays only. The work is the same, and the experience is entirely different.
3. The freedom to refuse
Paul's letter to Philemon asks a great deal. It asks Philemon to receive back Onesimus, who, on the traditional reading, was Philemon's slave and who, according to the letter, has become Paul's child in the faith, and to receive him as Paul's own heart. This is not a small request. And Paul puts it in a surprising way. In verse 8 he says that he has all boldness in Christ to command what is appropriate. In verse 9 he says that for love's sake he would rather appeal. In verse 14 he says that he would do nothing without Philemon's consent, "that your goodness would not be as of necessity, but of free will."
Read that again as a statement about leadership. A person with real authority sets it aside because he wants the other to act freely. He does not trust the outcome less; he trusts it more, because a gift that is forced is not a gift. Paul gives a reason, which is the heart of this lecture: the goodness must not be "as of necessity." Compelled goodness is not what he wants. The same principle is stated more generally in 2 Corinthians 9:7: giving should be what a person has decided in the heart, not grudging and not under compulsion, because God loves a cheerful giver. The passage is about money, but the principle applies to time.
(One remark on Philemon. The letter has been read in different ways about slavery, and those debates are not our subject. We use it here only for one thing that is not disputed: Paul chose to ask, not to order, and gave his reason.)
How does a coordinator practise this? Four habits make the difference between an invitation and a net.
No reason demanded. Say, in so many words, "You don't have to tell me why, if the answer is no." A person who must explain a refusal will often invent a reason, or accept a task rather than expose a private situation: an illness, a debt, a family trouble, a quarrel.
Time to think. Do not ask for an answer on the spot. "Take a week. If I don't hear from you, I'll assume it isn't the right time, and that's fine." An answer given at once, under the eyes of the person who asked, is the least free answer.
No pressure. No repeated nudges, no message after message, no mention of how few people are left. Do not tell the person that the work will fail without them. They may be right, and it may be true, but the sentence does a harm: it turns a gift into a rescue, and a refusal into a desertion.
The relationship stays the same. After a no, the coordinator greets the person with the same warmth as before, and does not leave the person off the list of those who are thanked. That is the test of the whole thing: a refusal that costs nothing socially is a real refusal. A refusal that costs the person a place in the community's warmth is not freedom, only a politer form of command.
Notice that none of this makes the request weaker. A coordinator who leaves a person free is not saying "I don't mind if you don't." They are saying "I would like you, and I want you to choose." The first is indifference. The second is respect.
4. When a request is carried by culture
Not every culture treats a request in the same way, and a coordinator who serves in a mixed community must know that.
In some cultures, requests are made directly and answered directly. "Can you do this?" "No, I can't." The answer carries no insult, and the conversation moves on.
In others, requests are made indirectly and refusal is made indirectly too. A person may say "I will try" or "it may be difficult" or "let me see," and everyone present understands that this is a polite no. A direct no may be heard as rude, or even as shameful for both parties. A coordinator who hears "yes, I will try" and writes the name on the rota may be misreading a refusal.
In some communities, a leader's word carries a weight that the leader may not feel. A pastor, a priest, an , a , a senior woman of the parish, a community's founding member: a request from such a person may be heard as a duty. In these places, "would you consider?" from a leader can mean "you will". The leader may be sincere in leaving the person free, and the person may still hear an order, because to refuse such a person would be to dishonour them.
In some cultures, refusal is a shame, and a person who is unable to say no may say yes and then fail to appear. This is not dishonesty; it is the pressure of a situation in which no honourable refusal is available.
What can a coordinator do? No rule fits every place, but these habits help.
- Give a way out that does not require a refusal. For example: "If I do not hear from you by Sunday, I will know the time is not right, and we will speak again after Easter." Silence becomes a safe answer, and no one has to say no aloud.
- Ask through a person who can hear the real answer. In some settings a trusted friend or a coordinator of the same age and background can receive a no that a pastor could not.
- Offer smaller options. "Would you like to help once, to see what it is like?" gives the person a step that is easy to refuse or accept.
- Make the leader's request public in its terms but private in its answer. An announcement states the need, and the answer is given quietly, to someone else, in the person's own time.
- Listen for the "yes" that is really a no. If a person's yes is slow, soft or full of conditions, ask once more, kindly, whether it is a good time.
None of these removes difference between cultures. They keep the central promise: the person should be able to say no without losing face, and the request should not be an order wearing a polite coat.
5. Both kinds of community
In a large cathedral parish, much asking is done by notice: a form in the porch, a table after Mass, an announcement in the weekly newsletter. This is right as far as it goes; it needs to be matched by a personal word to those who would never fill in a form. In a small assembly or house church, almost all asking is personal: a word across the table, a message to a friend. The risk in that setting is the opposite one: every request is personal, and so every refusal is personal too. The remedy is the same: say what, how much and until when, and make the no easy.
6. This is a point where readers will not agree
When should a new person be invited to serve? Some communities hold that belonging comes through serving. A new person who is quickly given something to do, even something small, is helped to feel that they are needed, learns the names of others and finds a way into the community that is not only listening. Those who hold this view point out that many newcomers are shy of asking for a place, and that an early invitation shows that they are wanted. Other communities hold that a newcomer should be given time to receive before they are asked to give. A person who has just arrived, or recently lost someone, or is exploring faith, or is preparing for baptism or reception into the church over a period of months, may need to be welcomed first and asked later. Those who hold this view point out that an immediate request can make a guest feel like labour, and that a person who is still deciding whether they belong should not be given work to decide it.
Both views have strengths. The first sees the loneliness of a newcomer who is never asked. The second sees the pressure on a newcomer who is asked too soon. This course does not decide between them, and it requires less than either: an invitation may be declined, and the new person is not first seen as labour. However quickly or slowly a community asks, it should ask in a way that makes a no easy and that treats the person as a member before a worker. How to welcome the newcomer at all is the subject of LM207E, Welcoming the Newcomer.
Diagram 1. A request card
핵심 요약
- A public notice opens a door for everyone; a personal invitation names a person and reaches those who would never put themselves forward. A community needs both.
- Many coordinators find that people most often say yes when asked by name, which is why a named request needs room to refuse.
- A clear request names what, how much and until when, including unseen preparation and clearing; an open-ended request sounds like an endless promise.
- Paul had authority to command and chose to appeal, so that the goodness would be of free will (Philemon 1:8-14); the same principle applies to time.
- Freedom to refuse means no reason demanded, time to think, no pressure, and a relationship that stays the same.
- Culture can turn a leader's request into an order; give a way out that does not require saying no aloud.
| Front | Back |
|---|---|
| Notice and invitation | A notice opens a door to all; an invitation by name reaches those who would not push themselves forward. |
| A clear request | Names what, how much and until when, including unseen preparation and clearing. |
| Four practices of freedom | No reason demanded; time to think; no pressure; the relationship stays the same. |
| The invitation to a newcomer | It may be declined, and the newcomer is not first seen as labour. |
One sentence to remember Ask a person by name, say what, how much and until when, and make it easy to say no.
This week's action Write the request card for one role you need filled, and read it aloud to yourself, asking: could someone refuse this without losing anything?
스스로 확인해 보세요
읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.
묵상 및 토론
- Recall a time when you were asked by name to do something. How did the way you were asked affect your answer and your later feelings about the task?
- Take a request for volunteers that you know. Can you answer "what, how much and until when"? What is missing?
- In your community, what happens to a person who says no? Is there any change in how they are greeted?
- In your culture, how is a polite refusal expressed? What would a leader need to listen for?
- Paul had authority and chose to appeal. When have you seen a leader do the same? When have you seen a leader do the opposite?
- The lecture describes two views on inviting a new person. Which does your community hold? What would the other view add to it?