A decision reached with your principal did not actually close the question. It closed the question in the room where it was made. When a new manager met the senior leader for the first time, the shared understanding that took weeks to build stayed behind, and the original ambiguity rushed back in to fill the gap. The cycle you are trapped in is not a scope problem. It is a context-transfer problem wearing a scope problem’s clothes.
The Decision Didn’t Reopen. The Context Didn’t Transfer. #
When leadership says “build this feature” without saying what “this” means, they have not given you a requirement. They have handed you a fog bank, and asked you to find a form inside it. You did the right thing. You built a demo to turn the fog into something people could react to, you sat with the principal, and you negotiated a concrete, buildable target. That work was real, and it was correct.
Then a person who was not in the room walked into a different room with the senior leader, and the target moved.
This feels like betrayal, or like a failure of the new manager, or like leadership changing its mind. It is usually none of those. It is the predictable consequence of a decision that was never written down in a form that could travel. A decision that lives only in the heads of the people who were present is a decision that cannot survive contact with anyone who was absent. Your organization keeps generating absent people: new hires, new managers, new conversations, new quarters. Every unwritten decision has a half-life, and the half-life is exactly as long as it takes for one new person to enter the chain.
The senior leader was never actually aligned with you on a specific scope. They were aligned with a feeling, which is that the feature should be impressive and should exist. The specific, feasible compromise you reached with the principal was never transferred back to the person whose vague wish started the whole thing. So when the topic came up again, the leader reached for the only thing they still held, which was the original wish, unmodified by everything you had since learned was impossible.
You Have Two Problems, Not One #
The conversation keeps oscillating because two genuinely different questions have been tangled into a single thread, and the two questions keep pulling against each other.
The first question is the north star: what would the ideal version of this feature look like, if the tools caught up and the constraints disappeared? That vision is valuable. It tells you which direction to walk, and it is the thing that excites leadership in the first place.
The second question is the milestone: what will we actually ship this quarter, with the tools we have today? That answer is necessarily smaller, uglier, and more compromised than the north star, and it is the only thing you can actually build.
The cycle happens when leadership talks about the north star and hears your milestone answer as a refusal, and when you talk about the milestone and hear their north star answer as scope creep. You are both correct, about different questions, and the fight is sustained entirely by the fact that nobody has written the two answers on the same page and drawn a line between them.
The fix is to separate the questions, explicitly and in writing. Keep the north star. Document it, reference it, and let it do the work of inspiring people. Then draw a hard line underneath it and write, separately, what you are committing to build now, why that subset and not another, and what specifically would have to change for the next slice to become feasible. The north star is a direction. The milestone is a contract. Conflating them is what makes every meeting feel like the last meeting, again.
“That’s Impossible” Is Not an Answer a Leader Can Process #
Here is the cruelest part of the situation, and the one most likely to keep you stuck.
When you tell leadership “we can’t build the full vision, the tools aren’t there yet,” you are reporting a technical fact, and you expect it to land as a boundary. It does not. It lands as an opinion, and a suspicious one, because every leader has heard engineers declare things impossible that later turned out to be merely hard. The word “impossible” carries no information a decision-maker can act on. It sounds like reluctance, and so it invites the very relitigation you are trying to end.
The move that actually closes the loop is to convert impossibility into a set of specific, dated, falsifiable claims. Not “we can’t do X,” but “X requires capability Y, which does not exist in our stack; the closest vendor offering is at stage Z; building it ourselves is an estimated N months of work from the platform team, which is not currently funded.” Now the leader is not arguing with your willingness. They are looking at a menu, and the menu has prices on it. They can choose to accept the limit, fund the enabler, or descope, but whatever they choose, they are choosing with information instead of against a vibe.
“Impossible” is a wall. The list of what it would take is a door. Leaders cannot walk through walls, but they will walk through doors all day, and often they will fund the hallway that leads to the next one. This reframing also protects you. The day the tools do catch up, your document already names the capability you were waiting for, and the path to the north star becomes a matter of executing a plan you wrote months ago instead of restarting the conversation from scratch.
A Verbal Decision Is Just an Opinion That Hasn’t Been Overwritten Yet #
The single highest-leverage thing you can do to stop the back-and-forth is to insist that decisions get written down the moment they are made, in a place that outlives the meeting.
This is what Architecture Decision Records were invented for, as Michael Nygard argued when he proposed the format.
The record is a short document that captures the context, the decision, the alternatives considered, and the status, so that a person who arrives later can understand not just what was decided but why.
The same discipline applies to scope decisions, which are every bit as consequential as architectural ones.
A one-page record that says “we will build this subset, not the full vision, because of these specific constraints, and we agreed this on this date with these people” is worth more than any number of follow-up meetings.
The reason writing matters more than talking is that writing has different physics than speech.
A conversation degrades the instant it ends.
The memory of it degrades faster, and as it passes through more mouths it distorts, the way the children’s game of telephone turns a clean phrase into nonsense in a few retellings.
A document does not degrade.
It says the same thing to the new manager on their first day as it said to the principal on the day it was written.
It says the same thing to the senior leader in their next one-on-one as it said in the room where the compromise was struck.
If a decision is worth making, it is worth making durable, and a decision is only as durable as the artifact it is recorded in. The cost of writing it down is ten minutes. The cost of not writing it down is the cycle you are currently living in, paid in weekly installments, forever.
The New Manager Is Not the Enemy. They Are a Missing Node. #
It is easy, and emotionally satisfying, to blame the new manager for reopening the wound. Resist that story. Almost certainly, they walked into their first meeting with the senior leader underprepared, because nobody had handed them the history. They improvised from the leader’s enthusiasm, which pointed at the north star, not at your milestone compromise. That is not sabotage. That is a new person doing their best with the information they were given, which was not enough.
The deeper structural issue is that information in an organization flows along its communication paths, and an org that just gained a new link between the team and the senior leader has, in effect, rewired those paths.
A decision that was stable under the old wiring may be unstable under the new wiring, because the new path bypasses the node where the context lived.
This is why onboarding a new manager is not a courtesy, it is a defensive necessity.
Within their first week, they need to receive, in writing, the current decisions, the reasons behind them, and the constraints that produced them.
A new manager who has read the decision records cannot accidentally contradict them, because they know they exist.
There is also a principal-agent dynamic here that is worth naming.
The senior leader, the new manager, the principal, and you all have different information, different incentives, and different audiences they are trying to satisfy, the classic pattern of the principal-agent problem.
The new manager may be, reasonably, trying to demonstrate value to their new boss, and an enthusiastic “we can do more” lands better in that first meeting than a cautious “actually, we already agreed to less.”
They are not wrong to want to look good.
The system is wrong to have left them no shared record to align to.
Fix the system and the manager will fall into line with it, because the record gives them something safer to bring to the leader than improvisation: a documented plan they can defend.
A Playbook for Breaking the Cycle #
When you find yourself back at the start of a scope conversation you thought was over, do the following, in order.
First, stop re-arguing the scope in the meeting where it resurfaced.
Relitigating under pressure produces worse decisions than the original ones, and it taxes the same finite decision-making energy that you need for the work itself.
Buy time.
Say that you want to make sure the conversation reflects everything the team has already learned, and that you will come back with a written summary.
That sentence is free, and it breaks the spiral.
Second, write the decision record, if it does not already exist. Context, the north star, the agreed milestone, the specific technical constraints that forced the compromise, the people who agreed, and the date. This is the artifact that should have existed all along, and creating it now is not bureaucratic theater, it is the wall that holds up everything that follows.
Third, convert every “we can’t” into a priced option. For each piece of the vision that is out of reach, write what it would take to reach it: which capability, which team, which rough timeline, which dependency. Hand leadership a menu, not a wall.
Fourth, brief the new manager before the next senior-leader conversation. Walk them through the record in person, make sure they understand the constraints, and explicitly invite them to bring their own objections now rather than in the room with the leader. Make them a co-author of the record, and they will defend it instead of overturning it.
Fifth, re-present to the senior leader, on your terms, with the record in hand. Acknowledge the north star openly, because dismissing the vision is what makes leaders dig in. Then show the milestone, show the priced options, and ask for a single explicit decision: accept the current scope, fund an enabler, or descope. Whatever they choose, write the new decision down before anyone leaves the conversation. A meeting that ends without a written decision is a meeting that will have to be held again.
Finally, schedule the next scope review in advance, on a date you control, instead of waiting for the topic to erupt on its own. Scope conversations are not avoidable, and they are not the enemy. The enemy is surprise relitigation, the version that ambushes you in someone else’s calendar. A standing quarterly review where the north star, the milestone, and the priced options are revisited together turns the cycle into a rhythm, and a rhythm is something a team can plan around.
The Real Lesson #
You cannot build something that is impossible today, and you should not promise that you can. But you also cannot expect a vague wish, transmitted through a changing cast of people, to ever stop generating the scope conversation you dread. The way out is not to win the argument one more time, harder. It is to change the medium in which the argument happens. Write the vision. Write the milestone. Write the prices of the gaps between them. Put all of it where the next person can find it. The conversation that reopens next month will reopen against a record instead of against your memory, and records win those fights.
Decisions that are written, priced, and shared do not need to be relitigated, because they travel to the rooms you are not in and make your case for you.
See also #
- When Engineers Disagree on Best Practices - the same decision-making discipline (reversible vs. irreversible, disagree and commit) applied to team-internal conflicts
- Bringing Everyone to the Same Level - the same context-transfer problem (knowledge trapped in one head) at the level of engineering execution
References #
Michael Nygard, “Documenting Architecture Decisions” - the origin of the Architecture Decision Record format, the lightweight written record this article recommends for scope decisions
Wikipedia, “Telephone (game)” - the canonical model for how information distorts as it passes through a chain of people, which is what happened when the decision crossed the new manager