Communicating and leading, one lesson a day

Imagine you are the treasurer of a neighborhood choir. Rehearsal has just ended after a demanding week. As people pack their music, another volunteer asks whether you can help with the spring fundraiser. You like the person, you care about the choir, and you want to be useful. Before you know what the help involves, you say, “Of course. Just tell me when.”

The next morning a folder arrives. The request is not a short budget check. It includes choosing a ticket service, comparing three venues, writing sponsor letters, and joining two evening calls. Your friendly answer has turned into an open container, and someone else has started filling it.

Today's lesson is not about becoming less generous. It is about finding out what you are agreeing to before you agree.

William Ury, known for his work on negotiation, wrote about the power of a positive no. His central idea is that a useful no begins with a clear yes: the value, responsibility, or priority you are protecting. If you do not know what your yes is for, every new request appears to cost nothing. The cost becomes visible only after your calendar fills.

When the choir treasurer says “just tell me when,” he means, “I care about this group and I want to support you.” The fundraiser lead may hear, “My time is open, and the size of the task does not matter.” Neither person is being dishonest. The sentence simply hides the edges that would let them plan together.

Research by Vanessa Bohns and Francis Flynn helps explain why this happens. People consistently underestimate how difficult it is for others to refuse a direct request. Saying no carries a social cost. We worry about looking selfish, cold, or uncooperative, so we often agree even when the request is inconvenient. The person asking may not see that pressure at all.

This cuts both ways. When you ask someone for help, their yes may contain more strain than you realize. When someone asks you, they may assume you will set a boundary if you need one. Both sides can leave the exchange believing the other had perfect information. Usually neither did.

Then the planning fallacy makes the promise larger. Roger Buehler, Dale Griffin, and Michael Ross studied how people estimate completion times. Even people's cautious estimates often proved too optimistic. When we picture a task, we imagine the task itself. We leave out interruptions, dependencies, setup, recovery, and the other promises sharing the same week.

The treasurer hears “help with the fundraiser” and pictures an hour with a spreadsheet. He does not picture gathering missing venue prices, creating accounts on ticket sites, revising a sponsor letter, or answering messages between rehearsals. He is not deliberately minimizing the work. He is forecasting from a picture with most of the background removed.

There is a leadership cost to being too agreeable as well as being too forceful. Research by Daniel Ames and Francis Flynn found that assertiveness does not work like a volume knob where more is always better. Too little and too much can both hurt. Overly forceful people often receive feedback because their impact is visible. Under-assertive people may hear nothing because the cost lands quietly on their own time and unfinished work.

So the practice is not “say no more often.” The practice is “do not say yes before the request has a shape.” Use three moves.

First, replace immediate agreement with a question. Ask, “What result do you need from me?” or “Which part are you hoping I will own?” or “How much work have you already scoped?” A question is not a refusal. It gives both people the information required for a real agreement.

In the choir example, the fundraiser lead might say, “I mainly need you to compare the ticket fees and recommend one service by next Thursday.” That is smaller than the folder suggested. Or she might say, “I need a co-lead for the entire event.” That is larger. Either answer is better than letting each person imagine a different promise.

Second, name your shape before offering a time. “I can give this one hour on Saturday, and I need to finish the quarterly accounts first.” Or, “I can review the numbers, but I cannot co-lead the venue search.” This gives the request something real to meet. It also tells the other person what your yes protects rather than making them guess.

A boundary does not need an apology attached. You are describing capacity, not confessing a fault. A clear hour is more useful than an unlimited promise that becomes late, resentful, or incomplete.

Third, for a real project, agree to the next step rather than the entire unknown. “Send me the venue quotes and I will review them before we schedule a call.” That is a genuine yes. It moves the work forward while preserving a chance to reassess when more facts exist. The next step is usually the part you can estimate with some honesty.

Avoid three habits. Do not offer an empty calendar phrase when your day has edges. Do not apologize for protecting existing work. And do not reject a vague request before asking what it means. Some requests that sound enormous become easy once clarified. Some requests that sound tiny reveal themselves as projects. The question tells you which one you are holding.

This works at home and in volunteer groups as well as at work. A family member asking for “help with the move” may mean carrying two shelves or managing an entire weekend. A club member asking you to “look at the website” may want a five-minute opinion or a rebuild. The kind move is not automatic agreement. It is shared clarity.

Try this with the next request you receive. Before answering, ask one question about the result, the part they want you to own, or the expected amount of work. Then state the real shape of your availability. If the request is still uncertain, agree only to the next information-gathering step.

If you are the one asking, return the favor. Name the result, the likely effort, and the deadline. Make it easy for the other person to give a truthful answer instead of a socially safe one.

That is lesson forty eight. Generosity works best when both people can see its edges. Ask what the work is, name the shape you can give, and then make a promise you can keep.

Sources for today include William Ury's work on the positive no; Francis Flynn and Vanessa Bohns on compliance with requests for help; Roger Buehler, Dale Griffin, and Michael Ross on the planning fallacy; and Daniel Ames and Francis Flynn on assertiveness and leadership.