You listened to the problem, separated the causes, worked out a way forward and even built a tracker. Then you sent it over and heard nothing. At the next meeting, the same problem comes up again, along with a request to “come up with some ideas.”
What wears you down is not just the time spent on the document. It is the question left behind: did any of that thinking count? The spreadsheet still exists, but the work that went into it seems to have disappeared.
A proposal stalling does not, by itself, tell you how capable its author is. What happens next depends on the idea, how it is explained, the recipient’s time and authority, and the organisation’s priorities. Before rewriting the explanation, it helps to ask a more specific question: what decision is needed now, and who needs to make it?
What does it tell you when the same idea makes sense to someone else?
Suppose a proposal to help reduce employee turnover gets no response. Later, someone responsible for part of that work asks where to begin. You use the same proposal to explain a first step, and the conversation moves forward. The following is a fictional example, intended to show how the way a proposal is handed over can make a difference.
The original message said only, “Here is the employee retention tracker. Please review.” In the later conversation, you first ask where the person is getting stuck, then explain:
“Let’s start with one instance where work has stalled. We’ll separate changes the team can make itself from decisions that need a manager. This tracker is there to make sure we don’t lose sight of the decisions we’re waiting for.”
The person replies, “That gives me something specific to ask about in the next check-in.”
What this establishes is limited but useful: part of the thinking helped someone identify their next action. It does not prove that the whole proposal is right, or that it will reduce turnover. It does, however, give you a reason to question the conclusion that nobody could use what you produced.
A different recipient brings different concerns, information, time and responsibilities. Changing the order of your explanation during the conversation may also have helped. Rather than settling on “the first person wasn’t interested,” note what made the proposal usable this time. That is something you can take into the next handover.
Replace “they work differently” with conditions you can check
When responses vary that much, it is tempting to say that people run on different operating systems. The metaphor can be useful. But if it turns into a diagnosis of someone’s personality, it can leave you with fewer practical options.
To understand how work is received, check four things:
- Is the request clear? Are they being asked to read, choose between options, or authorise a trial?
- Do they have the authority to decide? If not, whose decision is needed?
- Do they have the information they need? What is missing about cost, workload or risk?
- Is there time and priority for this now? If it needs to wait, when will it be reconsidered?
“I haven’t had time to look,” “I can’t decide without a cost estimate” and “I can’t approve this” can all look like silence from the outside. They need different responses. Sometimes you need a shorter explanation. Sometimes you need a smaller trial. Sometimes you need a different decision-maker.
You can rewrite a document three times and still get stuck in exactly the same place if nobody is responsible for approving it. Changing the colours on the slides does not add decision-making authority.
Turn “improve employee retention” into one concrete next step
A broad goal is hard to act on as it stands. “Improve employee retention” can involve working arrangements, workload, staffing, pay and relationships, each requiring different decisions.
Instead, the first discussion might focus on one situation: work stalls during a handover because nobody knows whom to ask for clarification. This, too, is a fictional example of how to approach the work, not a claim that turnover has one particular cause.
The person doing the work identifies the task and the information that was missing. The decision-maker, perhaps a manager, names a point of contact or makes time available for the people involved. After a trial, the team checks whether less time was spent waiting for clarification and whether the change simply shifted the burden to someone else.
If a tracker would help, its fields should support that sequence: “work that stalled,” “decision needed,” “decision-maker” and “next follow-up date.” If the same information is already maintained elsewhere, check whether you can use that source before creating another sheet that someone will have to keep copying data into.
There is no need to put details of someone’s private life, health or opinions about other people into a shared tracker just because they came up in a check-in. Keep it to facts needed for the work. Handle individual circumstances through the organisation’s designated support channels and within the appropriate sharing limits. A sheet that becomes a scoring system for “people likely to leave” can make it harder for people to speak openly.
The useful outcome is more than a finished spreadsheet. It is someone understanding the problem, taking responsibility for the necessary decision and making a next step possible.
Add an answerable question to “please review”
When you hand over a proposal, include a question the recipient can actually answer.
“This proposal would establish one point of contact for handover questions. Please decide by Friday whether we can trial it next week on one stage of the process. If you need more information to make that decision, please tell me what is missing.”
This is sample wording. The deadline and scope of the trial need to fit the actual authority and schedules involved. If no answer comes back, do not immediately rewrite the whole proposal. First try to establish one reason why it has stalled.
- If information is missing, ask which details are needed.
- If it is a lower priority, agree how long to leave it on hold or what would trigger a review.
- If the recipient lacks authority, establish how to reach the appropriate decision-maker.
- If the proposal will not proceed, record the reason and close the current review.
If the deadline passes without a response, briefly set out when you submitted the proposal, the decision you requested and the work that remains blocked. Follow up through the agreed communication route. “Submitted” and “approved” are different states. Do not treat silence as consent and start implementing the change on your own.
Issues involving safety, legal compliance or a serious impact on customers need to be handled separately from routine response-chasing, through the organisation’s established reporting channels.
Making things clear is work. It does not make you responsible for everything
Listening, separating issues, putting them in an understandable order and reducing them to something someone can tackle tomorrow are all work. That work starts before you open a spreadsheet.
You turn “we need to review the whole process” into “let’s first decide who can answer this question.” That can help the other person choose their own next move. When reflecting on your contribution, record more than the fact that somebody praised you: note what you clarified and which decision or action it supported. This makes your strengths more concrete. Keep ideas that have not yet been implemented separate from completed results.
Helping on one occasion is not the same as accepting permanent responsibility for running the process.
“I’ll organise the issues for this proposal. The responsible manager needs to decide whether to run a trial, and we should also agree who will review it afterwards.”
Make explicit who prepares the work, who decides, who uses it and who reviews it. Those roles vary between workplaces, so do not rely on job titles alone. Confirm what each person is taking on for this particular piece of work. Giving useful advice should not quietly turn you into the owner of every step.
Give the rethinking a stopping point, too
When a proposal is left unanswered, the meeting can carry on in your head after you get home: was it something about the way I explained it? If you revisit the work, start by separating “things I can improve,” “things I need to ask” and “things awaiting someone else’s decision.”
Once you have made your changes, sent the questions and set a date to revisit the proposal, draw a line under that day’s review. The worry may return, but without new information you do not need to reopen the same document every time. A notification on your phone does not require you to start a meeting in every app.
That does not mean switching off the feeling will be easy. This is not a way to erase emotion. It is a way to keep track of the next practical step.
What needs changing next: the document or the handover?
When an improvement proposal goes nowhere, review the substance and the explanation. At the same time, check whether the recipient had the time, information and authority to act. Treating either side as the only possible cause makes it easier to get stuck in the same place again.
Start with one proposal and put the decision into words: who needs to decide what, and by when? If any part of that sentence is blank, you have found something to clarify before producing more documents.
The value of your thinking does not have to depend entirely on whether someone replies. Recognise the work you did to make an idea usable, improve what you can, and pass the next decision to someone who can make it. You do not have to carry that responsibility alone.
