Translate the Idea Without Changing the Truth

A librarian wants to keep the branch open one evening a week. Some residents finish work after it closes. She proposes a trial with paid staff, a fixed end date, and a review of attendance and cost.

The director asks where the money will come from. The staff ask who will cover the evening. Residents ask whether the hours will fit their journeys home. Each group is hearing the same proposal through a different decision it must make.

The librarian could answer everyone with her original statement about access. That would preserve her words, but it would leave several questions unanswered. She needs to explain the plan differently to each group. She must also keep it the same plan.

To the director, she can begin with the trial’s budget and the choice about which existing work might be reduced. To staff, she can begin with pay and the proposed rota. To residents, she can describe the service that will be available and ask whether they could use it. Everyone should still hear that the evening is a trial, that it has a cost, and that continuation has not been promised.

This is the work of translation. It makes an idea understandable from another person’s position. It becomes dishonest when the proposal changes quietly as the audience changes.

Begin with the question they must answer

You know why your idea matters to you. The listener needs to know what it means for the choice in front of them.

A director who asks about the budget may support wider access. The budget question does not prove indifference to residents. The director may be responsible for services that will lose funding if the trial expands. An answer that treats the question as a moral defect would avoid a real part of the decision.

Likewise, a staff member asking about the rota may want the trial to succeed. They may also need to know whether their working hours will change. A proposal that respects them should answer that concern before asking them to celebrate the plan.

Begin by learning the actual question. Do not infer it solely from a job title, political label, or age. A director may be most concerned about whether staff can leave safely after closing. A staff member may want evidence that residents will attend. People have more than one interest, and a label cannot tell you which one matters now.

You can ask what they need to know in order to assess the proposal. You can also state your understanding and invite a correction. This small step may change the order of your explanation. It should not change the facts you are prepared to disclose.

There is a difference between starting with a relevant concern and allowing that concern to become the whole account. If the director cares most about cost, begin there. Then show what the spending would provide and who would benefit. A proposal that answers only the listener’s first question may still leave them poorly informed about the full choice.

Translation should widen understanding from a point of entry. It should not trap the proposal inside the narrowest concern in the room.

Keep the promises the same

Before changing your presentation, write down what cannot change between versions. For the library, that includes the proposed hours, the staffing needs, the cost, and the fact that the trial may end. It also includes the evidence for demand and the limits of that evidence.

Suppose the librarian has heard from several residents who want evening access. She can report those requests. She cannot turn them into a claim that most residents want the change. Nor can she call a count of interested people an attendance forecast. Someone can want a service and still be unable to use it on the proposed evening.

The director may receive a budget sheet while residents receive a short notice. The level of detail can differ. A fact that could reasonably change a person’s decision should remain available and visible enough to matter. If the notice makes the hours sound permanent, the short version has removed an important condition.

A useful test is to place the versions beside each other. Would a staff member recognize the plan described to residents? Would the director be surprised by the promises made in the staff meeting? If the groups came together, would the explanation still hold?

You need not say every fact in every sentence. You do need to avoid relying on the groups never comparing accounts.

This applies to uncertainty as well. If you tell the director that attendance is unknown, you should not tell residents that a crowded evening is assured. If you describe a benefit as likely in the long document, do not turn it into a guarantee in the headline. Shorter language still has to preserve the status of the claim.

The same care is needed when you disagree with part of your own proposal. Perhaps you would prefer two evenings but can responsibly fund only one. Say what is being proposed now and why. Do not let the larger hope drift into the description of the approved plan. People should be able to tell a wish from a commitment.

Values are reasons to discuss

Some people will care most about who cannot use the library under the current hours. Others will care about making fuller use of a building the community already maintains. Both are possible reasons for considering the same trial. You can explain either reason if it is honestly connected to the plan.

The ethical problem begins when you borrow a value merely because you think it will secure agreement. You may praise thrift while hiding an added cost, or praise fairness while shifting unpaid work onto the staff. The chosen language then conceals the very thing it appears to respect.

Political experiments offer qualified evidence about the effect of value-based wording. In a preregistered 2023 study recruited through a US probability panel, people read about a hypothetical candidate. Describing a progressive economic platform through values such as loyalty and tradition increased the candidate’s support compared with wording based on values such as equality. The difference was larger among conservatives. The researchers measured stated support and voting intentions, not actual votes. The test supports a possible benefit in that setting, not a formula for every audience.¹

This wording draws on broad moral concerns, often called moral foundations. Later evidence also matters. The published abstract of a 2026 paper by Hawkins and colleagues reports that two independent research teams found no persuasive benefit from moral-foundation messaging across five political issue areas, including the subgroups expected to respond. The full methods were not available for this review, so that result should be treated at the level reported rather than used to settle every dispute about the approach.²

These studies offer no formula for guaranteed agreement. Whatever wording you choose, the case still has to be honest.

For our purposes, the important question is whether the connection can be defended. If you describe evening opening as a better use of public resources, show what use the extra spending would buy. If you describe it as fairer access, explain who the current hours exclude and what the trial might change. The language should lead back to the proposal, where another person can examine it.

Do not tell the audience that their values require your conclusion. They may care about access and judge another service more urgent. They may care about careful spending and believe the trial is worth its cost. Shared values can still produce different judgments because people weigh facts and duties differently.

This is why asking what matters is safer than assigning a person to a type. You are trying to discover their reasons. A list of supposed traits for people like them can get in the way of hearing those reasons.

There is room for moral disagreement too. You may find that an audience wants a benefit reserved for people you think should not receive special preference. Translation does not require endorsing that preference. You can explain your proposal clearly and defend the reason you will not change that part. Being understood is a worthy aim even where agreement remains out of reach.

Make the detail usable

Sometimes the obstacle is a technical word. Sometimes it is a missing explanation of why the technical fact matters.

A budget may distinguish a one-time cost from a continuing one. The terms are simple enough, but the listener needs to know the consequence. Buying a sign once is different from paying for staff each week. If the trial becomes permanent, the weekly expense continues. The proposal should show where that money would come from after the trial ends.

This kind of explanation adds meaning without adding hype. It gives the listener a way to reason about the choice.

A good comparison uses the same basis on both sides. If you compare the cost of evening opening with the cost of the daytime service, say whether you are comparing one hour, one visit, or the whole period. Each comparison answers a different question. Choosing the most flattering one without explaining its basis can mislead even when the arithmetic is correct.

Be equally careful about what a measure leaves out. Cost per visit might be relevant to a budget. It does not by itself tell you whether the visitors had any other time when they could use the library. A visit that becomes possible only because of the new hours raises a question the simple count does not answer. You may still decide that the cost is too high. You should know what your measure can and cannot settle.

The listener does not need every technical detail to understand the main choice. They need the detail on which that choice turns, expressed at the level they can use. Keep the full basis available for checking. Avoid putting an essential condition in an attachment while the main account gives the opposite impression.

A short explanation can be demanding work. You must decide what the reader needs and then preserve the causal steps. If you remove the step that shows why the conclusion follows, you have made the text shorter by making the reader do more of the thinking.

Ask a person unfamiliar with the work to explain it back. Do not ask only whether it is clear. People can agree that a page looks clear while misunderstanding what it allows them to conclude. Their account will show you what survived the translation.

Use a story without hiding the rest

The librarian might describe a resident who finishes work after the branch closes and needs a place to use a computer. That example makes the access problem easier to picture. It does not tell the committee how many residents face it, whether they would attend on the chosen evening, or whether another service could meet the need more effectively.

Keep those questions open. A moving example deserves attention. It should not be made to carry evidence it does not contain.

If the example concerns a real person, represent their situation accurately and protect details they have not agreed to share. If it is imagined, identify it as such. Do not let an illustrative scene quietly become a claimed resident interview or a count of unmet need. The desire to make an idea vivid gives you no right to invent support for it.

An example can also become too convenient. Perhaps the imagined resident has every trait the audience admires, works the hours that best fit the trial, and needs exactly what the library provides. That scene shows why the plan could help someone. It does not test whether the plan is well designed. To do that, consider a person for whom it works poorly.

A resident with an early shift may still be unable to attend. Someone who relies on a bus may need the branch to close before the last service. A worker whose evenings vary may need more than a fixed weekly slot. These cases do not automatically defeat the proposal. They tell you where its benefits stop and what questions remain.

You should be willing to show those limits to people who might approve the plan. Otherwise, you are offering a story arranged to prevent the doubts that good judgment requires.

Some proposals need changing

After listening to residents, the librarian may learn that the proposed evening is the wrong one. After talking with staff, she may learn that the plan depends on duties that cannot be moved. Better language will not solve either problem.

At that point, the proposal itself needs work. Changing it in response to new information is reasonable. What matters is making the change visible to everyone whose decision depends on it.

If the evening moves, update the notice. If the staffing cost rises, revise the budget. If the service offered becomes smaller, tell the residents what will actually be available. Do not preserve earlier support by leaving one group with an outdated version of the plan.

There is a common temptation here: keep explaining until the objection sounds like a failure to understand. But the person may understand perfectly and have found a defect. Ask what would have to be true for their concern to be resolved. Their answer may point to a missing fact, a change you can make, or a genuine conflict that clearer wording will not remove.

A good explanation can expose a weak idea. That is part of its value. You should prefer discovering a flaw before others commit their time or money.

Review the versions of your proposal together. If a sentence works only because the reader will not know what you told the other group, rewrite it. If one version reveals that the proposal lacks evidence, return to the work. There is no need to solve an evidence problem with more persuasive language.

The library trial may be approved. It may be revised or declined. A fair explanation leaves the people involved better able to judge the choice and to see why others reach a different conclusion. That result is worth more than a quick agreement built on accounts that cannot survive comparison.

Once the account is clear, let people consider it. They may need time to check a fact, discuss a cost, or think through what agreeing would mean. More explanation is only helpful if it answers something they still need to know.

Sources and notes