After a no, the sponsor asks what would change the answer, fixes it, and brings the proposal back at the next good moment, until the objections run out or the people deciding change.
An example
Automating first notice of loss was the proposal a claims operations director at a mid-size property insurer took to the executive committee in 2022. The committee said no: too expensive and too risky during a system migration. She asked the chief financial officer what would make it fundable. The answer was a cheaper first phase and evidence from a carrier of similar size. She cut the proposal to one product line, found two peers who had done it, and came back the following spring. The committee said no again, this time because the chief operating officer worried about the call center. She spent four months with the call center head working out staffing, and brought it back that autumn with his name on it. By then a new chief executive had joined who asked why it had taken so long. It was approved in one meeting.
Why it works
Each round fixes a stated objection, so the proposal looks better and easier to approve every time it returns. A no that came with reasons becomes a list of conditions, and meeting them in the open makes a further no harder to justify. Time helps as well: people, budgets, and priorities change, and a proposal that is ready when they do is first in line. It depends on the sponsor asking for the real reasons, accepting the fixes, and staying patient without looking unable to take an answer.
The thinking behind it
Debra E. Meyerson Tempered Radicals: How People Use Difference to Inspire Change at Work (2001) describes people who want to succeed inside an organization and also change it, working through persistent, low-key moves and small wins. Meyerson calls one of their habits variable-term opportunism: staying ready to seize short-term openings while working toward longer-term change. Patient resubmission is that habit applied to a single proposal: fix what the last no named, and bring it back when the opening comes.
When it fits
Proposals with lasting value that lost on fixable grounds are the candidates: cost, timing, an unready partner, an unanswered risk. You need enough standing to bring an idea back without being dismissed as stubborn, the patience of a year or more, and the ability to keep doing your day job well in the meantime.
How to use it well
Take the no well. Thank the people who decided, and ask each one, privately, what would change their answer.
- Write down every objection and treat each as a condition to meet.
- Fix what you can: a smaller first phase, better evidence, a partner who was missing.
- Watch for the moment: a new budget, a new leader, a problem the proposal solves.
- Bring it back with a short note on what changed since last time.
Keep each return small enough to look like progress, and never argue the last decision again.
What it costs and where it backfires
Every round spends time and goodwill, and people who see the same idea three times may decide you cannot let go. Keep each return clearly different and spaced well apart, and learn to tell when the objections are about the idea itself. Bringing it back while the people who said no are absent, to skip a review they were owed, trades patience for a procedural ambush.
When it is used on you
A rejected proposal that keeps coming back improved deserves a serious hearing: the sponsor has done what you asked. Either say what would still need to change, specifically, or say that the answer is no for reasons no fix can meet, and why. A vague no invites another round.