What Acting on Your Idea Might Cost

A new booking system would make the office easier to run. At least that is what the person proposing it believes. People would stop calling twice to confirm an appointment. Staff could find the schedule in one place. The old paper diary would finally retire.

The person responsible for the front desk is less excited. She asks what happens when the internet goes down. She asks who will enter the old appointments. She asks how a caller who cannot use the website will book a visit.

The proposer hears reluctance. The woman at the desk hears work being assigned to her without anyone having counted it.

Either could be wrong about the system. Yet they are considering different versions of the proposal. One sees the finished arrangement. The other sees the first Monday.

A proposal can describe the finished service while leaving out the work needed to start it. If someone else must do that work, their objections may expose costs the proposal has missed.

Before asking how to make your idea attractive, ask what acting on it would require from the person you hope to persuade. Include the unpleasant parts. Include the things you have assumed will somehow get done. An idea becomes more credible when the work underneath it is visible.

Who will do the first Monday

Try following a proposal through an ordinary day. Avoid the grand promise for a moment. Follow the actual steps.

A community group wants to hold more evening events in a shared hall. More people could attend. That is a real benefit. Who opens the building? Who stays to lock it? Does the last bus leave before the event ends? Is the person expected to clean the room paid for the extra hours? If the group has not answered these questions, its enthusiasm is partly being financed by unnamed labor.

This does not mean the events should be abandoned. It means the proposal is unfinished.

There is a tendency to reserve the word realistic for whoever says no. That gives refusal too much credit. A person can reject a workable plan because they do not want to make an effort. But the reverse error is also common: we call a person negative when they are the first to explain what the effort actually involves.

The worker asking about the keys may be doing more to make the event possible than the person praising its importance.

To find the difference, separate a constraint from a preference. A constraint limits what can happen under the present conditions. A preference describes what someone would rather happen. Both deserve attention, but they can be addressed differently. If the building must close at nine, the group can shorten the event or ask the proper person about a later closing time. If a member simply prefers afternoons, that preference belongs in the discussion without being presented as an unavoidable rule.

Do not assume the first description is complete. Ask what makes the limit a limit. A staff member may say there is no money when they mean there is no money in their budget. Another department may hold funds for exactly this purpose. Or there may truly be no money, and the next step is to reduce the plan rather than dress it in more inspiring words.

Questions of this kind can sound hostile when their purpose is to expose someone as an obstacle. They become constructive when the purpose is to discover what must change. You are asking for the conditions under which a responsible yes could exist.

The same discipline applies at home. A plan to visit relatives may look simple to the person who needs only to pack a bag. It looks different to the person who must arrange care, change a shift, prepare food, and manage the return. If you want agreement, bring those tasks into the proposal. Better still, take a fair share of them.

The cost of being the one who agrees

Some costs appear only after a person says yes. A manager may be asked to explain the decision to a board. A teacher may have to offer the same change to every student. A volunteer may be making a promise on behalf of people who have not been consulted.

This is why a good reason for doing something is not always enough reason for a particular person to approve it. Their role may require them to consider duties you do not carry.

We should be careful here. People sometimes hide their preferences behind a role. They say their hands are tied when they have simply chosen to keep them still. But you will be better placed to challenge that claim if you understand the actual duty. Which decision can they make? Which needs another person’s approval? What can they recommend even if they cannot authorize it?

Suppose you want a school to let students borrow equipment over a holiday. The head of department agrees that it would help. She is also responsible for replacing lost equipment from a budget that barely covers repairs. Telling her that she should care about students does not answer the problem. A plan for lending, return, damage, and access does. You may still disagree about how much risk is acceptable, but at least the disagreement has reached the real decision.

There is also the cost of appearing disloyal. Someone may believe you have identified a genuine fault, yet fear that supporting your proposal will be treated as an attack on a colleague. Sometimes a private conversation can clear up this fear. Sometimes it reveals a culture where agreement must follow rank. That is a larger problem than an awkward presentation.

Try not to make yourself the expert on someone else’s fear. You can ask whether the proposal creates a difficulty they have not named. You can offer a way to discuss it privately. You cannot infer an entire hidden motive from a pause, a folded arm, or an unread message. Observing a reaction gives you a reason to inquire. It does not give you access to another person’s mind.

Eyal, Steffel, and Epley tested the difference between imagining another person’s view and obtaining it. Across 25 experiments, instructions to take another’s perspective did not consistently improve accuracy. Only the final experiment directly tested asking: among 104 romantic couples, discussing opinions improved predictions mainly for the opinions discussed. Asking supplied information; it did not reveal an unseen mind.¹

This restraint protects the conversation from an especially irritating form of false insight. Few things make discussion harder than being told what you really fear by a person who has not bothered to ask what your job involves.

A useful warning from a novel

In chapter eighteen of George Eliot’s Middlemarch, the doctor Lydgate must help choose a hospital chaplain. He likes Farebrother, one candidate, while the influential banker Bulstrode supports the other. Lydgate also needs a place for his medical work. His judgment is caught among personal regard, doubts about the candidates, and the support on which his ambitions depend. He votes for Bulstrode’s candidate and recognizes that indirect pressure has affected him.²

Eliot lets us see a person who can explain his choice to himself without fully escaping its pressures. The scene is a warning about the stories we tell when our good purpose depends on pleasing someone powerful.

Think of the ordinary version. You want an excellent project to proceed. A sponsor favors a supplier you do not trust. You begin by telling yourself that the supplier is a small detail. Soon the project has become the reason to stop asking about the detail.

Understanding that pressure should make us more careful with the people we hope to influence. It should also make us more careful with ourselves. You may be able to get agreement by attaching it to something the other person badly needs. That does not make the agreement sound. A person can comply because the alternative is too expensive, while privately judging the proposal to be wrong.

If you control the needed resource, do not call this enthusiasm. Ask whether the decision would look different if the person could disagree without losing unrelated support. That question may be uncomfortable precisely because it reveals how much of your apparent persuasive skill came from your position.

A sponsor who welcomes scrutiny before providing support gives the work a better chance to remain honest. They can still set proper conditions. They should be able to explain how those conditions serve the work rather than their vanity.

Do not erase the people outside the room

It is possible to understand your listener very well and still make a bad proposal. The two of you may agree because someone else will pay.

A supervisor and a customer can settle a rushed deadline by assigning an employee to work late. A neighborhood committee can solve a parking problem by moving it to the next street. Two siblings can arrange a convenient family visit by assuming that a third will host everyone. The agreement is real. So is the missing person.

An ethical account of influence has to include these people before we congratulate ourselves on finding common ground.

When a plan becomes easier after a particular cost disappears from the conversation, trace where the cost went. Did a new method remove it? Did someone freely agree to bear it? Or was it merely transferred to a person who had less opportunity to object?

This is a practical question, not a demand to predict every possible consequence. You can start with the people who will do the work, lose access, bear risk, or have fewer choices after the decision. If you cannot include them directly, say what you do not yet know. Do not borrow their consent by saying they will probably understand.

The booking-system proposal becomes better when it includes a route for people who cannot book online. That route has a cost, and the cost should be funded rather than quietly added to the front desk’s workload. The proposal may become less impressive on a slide. It becomes more honest in use.

This is also where persuasion and problem-solving can pull apart. A cleaner story might be easier to sell. A fuller story might reveal that the idea needs revision. If your purpose is to improve the office, you should prefer the revision. If your purpose is to be the person whose idea wins, the missing cost becomes an inconvenience you would rather not mention.

You have to decide which purpose is governing you.

Offer a test that someone can safely learn from

When the uncertainty is real, a limited test can help. The word limited must refer to an actual limit, not merely a reassuring label.

What will be tried? Who will take part? How long will it last? What will count as improvement? What would cause the test to stop? Who has the authority and the resources to restore the old arrangement if needed?

For the booking system, a small test might use one kind of appointment while retaining the paper record. Staff would record missing or duplicated bookings and the time needed to fix them. People who book by phone would keep that option. At the end, the office would examine whether the promised gain appeared and what extra work it created.

This is an example of how to make uncertainty visible. It is not a claim that this exact test suits every office. Some systems handle sensitive information or important services and need more formal review. A trial should not expose people to serious harm simply because its organizers hope to learn from it.

Reversibility also deserves inspection. You may be able to cancel a piece of software, yet unable to recover the hours people spent learning it. You may be able to reverse a schedule, yet unable to repair every disruption it caused. Saying that something can be undone does not make its first attempt free.

Include these costs in the offer. If the people doing the test need time, arrange time. If they need training, provide it. If you want them to report problems, make it clear that reporting a problem will not be treated as disloyalty to the experiment.

A person may then say yes because the test answers their concerns. They may say no because even the test asks too much. Either answer tells you more than a vague promise that everything will work out.

Let the answer change the proposal

There is a hollow version of listening in which you collect objections only to prepare better rebuttals. The meeting looks open, but nothing said in it can alter the plan. People are invited to contribute words and denied any influence over the result.

If you ask what the proposal will cost, let the answer matter.

The front-desk worker explains that entering the old appointments will take time the office does not have. The proposer could dismiss this as a temporary inconvenience. Or he could remove unnecessary data from the transfer, postpone the launch, and arrange help. The concern has now changed the work. The worker has reason to believe that raising the next concern may be worth the effort.

This is how the listener can become a partner in making the idea viable. You do not need to surrender the purpose. You need to give up the assumption that your first design fully serves it.

There will still be occasions when interests conflict. One person wants quiet evenings in the hall, and another wants more events. A compromise may leave both disappointed. You should not promise that proper understanding dissolves every conflict. Understanding allows the conflict to be described honestly, so that a fair decision can be made through whatever process the people have agreed to use.

When you next meet a quick no, resist the urge to diagnose the person before you have examined the proposal. Ask which part creates the difficulty. Ask who would have to act. Ask what is missing from your account of the cost. Then decide whether the objection deserves a change, a reply, or a challenge.

The question is no longer simply whether your idea sounds good. It is whether other people can act on it without being asked to ignore what they know or quietly pay for what you have left out.

Sources and notes