
When the Founder Changes Their Mind, the Team Needs a New Contract
A founder can change direction in a brief conversation while the rest of the organisation continues working to the previous instruction. The new idea travels informally, deadlines remain unchanged and managers begin reconciling contradictory expectations without a clear decision to refer to.
Changing one's mind can be good leadership when evidence changes. The problem is failing to reset the commitments that depended on the earlier choice. The team needs a new working agreement about scope, resources and timing, rather than an assumption that the consequences will take care of themselves.
The contract in the title is an operating agreement, not a legal instrument. Its purpose is to make the revised decision usable by the people who must implement it.
Explain what changed and why
State the new decision, the evidence or judgement behind it and the part of the previous plan that no longer applies. This helps colleagues distinguish a genuine revision from an exploratory comment or a personal preference expressed in passing.
Founders should be especially careful where employees treat every observation as an instruction. Saying that an alternative is interesting can trigger work if the organisation has learned to anticipate the founder's wishes. Label exploration as exploration and identify when a decision has actually been made.
In an illustrative visitor attraction, a founder may decide to alter a planned guest route after an operational test. The change could be sensible, but it may affect signage, staffing, access arrangements and communication. Those dependencies need explicit review before the original launch date is reaffirmed.
Reopen the affected commitments
Ask each accountable owner what the change means for their work. Which completed activity is now redundant? What additional work is required? Which other commitments compete for the same resources?
The discussion should include costs already incurred and the consequences of delay, while avoiding the assumption that past spending automatically justifies continuing a weak plan. The team needs a forward decision informed by the full situation.
Agree revised scope, timing and authority. If the founder expects the original deadline to remain, establish how that is feasible and what trade-offs it requires. An instruction to make it happen does not resolve an impossible dependency.
Communicate one authoritative version
Record the revised decision in the place the team normally uses for active commitments. Tell affected colleagues what has changed and remove or clearly supersede outdated instructions. People should not need to reconstruct the current plan from several conversations.
Name the owner of further questions and agree what would justify another review. This creates a stable basis for action without pretending the business will never learn anything new.
After implementation, examine the effect of the change. Did it improve the intended outcome? Was the disruption proportionate? Could earlier testing have revealed the issue before more work was committed? The purpose is to improve decision quality, rather than discourage leaders from correcting a mistake.
Decision debt can arise when unresolved choices accumulate. A similar burden develops when changed choices leave old commitments behind. Founders can preserve their ability to adapt while giving the organisation a clear account of what it is now expected to deliver.






Comments