You suggest a different way to handle recurring requests, and the response comes before you have explained the idea: “We’ve never done it that way.” The proposal seems simple to you, but someone else may see extra work, uncertainty, or an unfamiliar process. The problem may not be the idea itself, but what you have—and haven’t—managed to explain about it.
Coming up with new solutions is only part of the challenge. You also need to connect an unfamiliar idea to a situation the other person recognizes, make its limits clear, and leave room for questions. The aim is to help people judge the proposal on its actual merits, rather than on their first impression.
Start by explaining the problem your idea is meant to solve
People with new ideas often lead with the most exciting part: an unusual tool, an unexpected combination, or an original process. But the listener may not yet see why anything should change. Without that connection, even a good proposal can sound like an unnecessary experiment.
Set the solution aside for a moment and describe a specific frustration the other person already recognizes. Instead of saying, “Let’s build a completely new communication system,” try: “We record the same questions in three different places, then have to search for the latest answer.” The second statement gives you a shared starting point.
Before the conversation, answer these three questions:
- What isn’t working today? Describe an observable situation, not a judgment about people or the entire system.
- Who is affected? Identify who loses time, repeats work, or has to wait.
- What should improve? Name one expected difference that can be checked.
If you can’t identify a problem the idea would solve, that doesn’t necessarily mean it has no value. It might be a game, an artistic experiment, or an exploration of possibilities. In that case, present it honestly on those terms. Don’t promise practical benefits just to make an original idea sound more persuasive.
Separate the core idea from its boldest version
Imagination can bring together things that don’t seem related at first. But when you explain an idea, understanding can suffer if you immediately explore every possible variation. One person may picture a simple adjustment, another an expensive technology, and a third a complete change to the rules. They may be discussing the same idea, but imagining different versions of it.
First, define the smallest change that captures your intention. Once the other person understands it, you can explain further possibilities. For example, a “room that changes according to how it’s used” might initially mean only movable tables and lights with several settings. Automated walls and other technology aren’t needed to understand the basic idea.
Adapt your explanation to the person you’re speaking with
The same proposal can matter to different people for different reasons. Someone who will use it may wonder how difficult it is. The person responsible for it will probably consider the risks. Someone affected by the change indirectly may want to know what will stay the same.
This doesn’t mean telling everyone a different story. The facts and limits of the proposal must stay consistent; only the order and level of detail should change. This overview can help:
| Who you’re presenting it to | What they need to know first | A useful question |
|---|---|---|
| Someone who will use the process | What they’ll do differently and how much effort it will take | What would be the biggest obstacle for you when trying this? |
| Someone who decides how resources are used | What the trial will cost and when it can be stopped | What cost limit must we stay within? |
| Someone affected by the change | What will change for them and what will remain the same | Which part of the current process matters to you? |
The same principle applies in everyday life. If you suggest a new way to plan household responsibilities, you don’t need to start with an app or spreadsheet. First ask whether others are bothered by forgotten agreements, an uneven division of tasks, or something else entirely. Then you can shape the proposal around the real problem instead of pushing a tool you happen to like.
Use a short structure instead of a long, enthusiastic explanation
If you tend to think in images, alternatives, and connections, it can be hard to decide what to say first. A little preparation helps you keep the original thinking without overwhelming the other person with tangents. Start with four sentences in this order:
- The current situation: “When a customer asks about a request, we search through several messages for the answer.”
- One proposed change: “Let’s try keeping a brief status for each request in one shared place.”
- The expected benefit: “We may spend less time working out who has the latest information.”
- A small next step: “I suggest trying it with ten requests, without replacing the current process.”
A hypothetical example of an idea that met resistance
Consider a hypothetical situation in a small office. Lucia notices frequent misunderstandings when tasks are handed over. She suggests replacing informal messages with short cards listing the task, the person responsible, and the next step. She calls it a “new communication system.”
A colleague objects that they don’t want another system. Lucia starts describing all the options, colours, and automations she might add later. The resistance grows because the colleague mainly hears “more recording.” Lucia is confusing the future vision with the first change that’s actually needed.
In their next conversation, she starts differently: “Last week, two tasks were handed over without saying who should take them forward. I don’t want to change our whole way of working. Let’s try adding just the responsible person and one next step to five tasks. If it takes more time than it saves, we won’t continue.”
Now the colleague can respond to a specific proposal. They ask who will fill in the information. Lucia admits she hasn’t worked that out yet. They agree that, during the trial, the person handing over a task will record it. Only then will they know whether this actually reduces misunderstandings and whether recording the details takes too much time.
Acknowledge uncertainty and propose a small-scale test
A new solution often rests on an assumption that hasn’t been tested. You might expect the work to get faster, for example, but not yet know whether the new process will create extra work elsewhere in the team. If you hide that uncertainty, the proposal may seem convincing only until the first objection comes up.
Make three kinds of statements distinct: what you’ve observed, what you assume, and what you want to test. “We often have to search for answers” describes the problem. “A shared space will save us time” is an expectation. “We’ll compare how often we have to search during a small trial” describes how to get better information for a decision.
A good trial has a limited scope, a clear endpoint, and a criterion for deciding whether to continue. But if a change affects safety, privacy, money, or other people’s rights, enthusiasm and a small trial aren’t enough. Appropriate permissions, safeguards, or expert assessment may be needed before testing begins.
If an idea can’t be tested safely, you can use a sketch, simulation, conversations with the people affected, or another way to check your assumptions. Deciding not to put anything into practice yet can also be the result of sound judgment.
Ask whether people understand, not just whether they agree
After presenting an idea, people often ask, “Do you like it?” The answers tend to be brief and not very useful for what comes next. Someone may agree to be polite; someone else may reject an idea that differs from what you actually meant. It’s more useful to find out how the listener understood the proposal.
Questions like these can reveal what remains unclear:
- “What do you think would change first if we introduced this?”
- “Which part seems impractical or too demanding?”
- “What should stay the same for this process to work for you?”
- “What problem might we accidentally create with this proposal?”
If you get a critical response, you don’t have to immediately prove the other person wrong. First, check that you understand their concern. A point about cost, unclear responsibility, or disrupting a useful habit may be a condition the proposal needs to meet to be workable. On the other hand, not every objection is proof that the idea should be abandoned. What matters is the reason behind it and whether that reason can be tested.
When a better explanation isn’t enough
Not every objection comes from poor communication. Sometimes an idea really does address a secondary problem, shifts costs onto someone else, or depends on cooperation the other person doesn’t have time for. Better wording won’t fix those shortcomings.
Look out for three signs: you repeatedly can’t explain the benefit to the user; the person expected to carry out the proposal warns that the workload would be unmanageable; or the expected result can’t be meaningfully distinguished from what already works. In those cases, go back to the problem and reduce or revise the solution.
Prepare before you present your next idea
Choose one idea you’ve been thinking about but haven’t yet been able to explain clearly. Write down five brief answers: What is the current problem? Who is affected? What is the smallest change that might improve it? What don’t you know yet? What would a safe first test look like?
Then practise explaining it aloud, as if the other person knows nothing about your earlier thinking. If you’re still describing interesting possibilities after a minute, return to the purpose. If you can explain the problem, the change, and its limits, you’re ready for a conversation—not just a presentation.
A practical outcome doesn’t have to be immediate acceptance of your idea. It’s enough to turn a vague “That’s strange” into a specific question, an agreement to try something small, or a clear decision about why you’re not proceeding yet.
