The Two Weeks After You Change Something
Most operational changes are announced, adopted for a week, and quietly abandoned. What happens in the fortnight after a change, and the small number of things that decide whether it survives.
You changed how something works. Everyone was told, everyone agreed, and it went well for about a week.
Three weeks later it is gone, and nobody decided to stop.
The shape of the fortnight
Predictable enough to plan around:
Days one to three. Everyone does it, because it is new and someone is watching.
Days four to seven. The first busy night. ⚠️ The change gets skipped once, nothing bad happens, and the skip becomes available as an option.
Week two. Split adoption — some people doing it, some not — which is worse than either extreme, because now there are two systems and nobody can rely on either.
Week three. Whichever way the split resolves becomes permanent, and it usually resolves toward the old way, because the old way requires no effort to remember.
Why the busy night kills it
Not resistance. The new thing has a cost in attention, and attention is what a busy night has least of.
⚠️ A change that costs even slightly more effort than the thing it replaced will be abandoned under pressure, regardless of how much better it is when there is time.
This is the design constraint, not a discipline problem. If the change is not cheaper in the moment, it needs to be so much better that people carry the cost deliberately — and that requires them knowing why.
What decides whether it survives
Whether the reason was given. ⚠️ "What it prevents", not "what to do." People carry a cost for a reason they understand and drop it for an instruction they do not.
Whether the first skip was noticed. Not punished — noticed, and mentioned. The unremarked skip is the moment the change starts dying.
Whether the old way was removed. If both are available, the old one wins. Removing the alternative is more effective than any amount of reminding.
Whether someone owns it. By role. A change belonging to everyone belongs to nobody by week two.
The check at day ten
One question, asked of two or three people:
"Are we still doing the thing we changed?"
⚠️ Ask it of people who do the work, not of the person who introduced it — the introducer will say yes, sincerely, because they are still doing it themselves.
Day ten, because week two is when the split appears and it is much cheaper to correct then than after it has resolved.
When the answer is no
Do not simply re-announce it. Ask why it was dropped, and take the answer seriously:
It cost more than it saved. ⚠️ Frequently true, and the honest response is to redesign or abandon it, not to insist.
It was unclear at the edges. It worked for the standard case and nobody knew what to do with the variations.
It conflicted with something else. Two rules, and the other one is older and better understood.
Only after ruling those out is it a discipline question — and it usually is not.
Changing fewer things
The most reliable improvement to adoption is doing less of it at once.
⚠️ Two changes in the same fortnight halve the attention available for each. Three means none of them survive, and the team learns that changes do not stick — which makes the next one harder still.
One change, given a fortnight, is faster in aggregate than three changes given none.
The fortnight has a predictable shape
Days 1-3 everyone remembers, because it is new
Days 4-9 it depends on whether anyone is checking
Days 10-14 it is either the way things are done, or it is gone
⚠️ Nothing decides itself in the first three days, which is exactly when attention is highest and when people conclude it worked.
The busy night is what kills it
A busy night everyone reverts to what is fastest
And the old way is faster, because it is practised
⚠️ A change survives its first busy night or it does not survive. ⇒ So the question is not whether people agree with it. It is whether it is fast enough to hold under pressure.
One person doing it under pressure
Someone visibly doing it on the busy night, without being asked
⚠️ One person doing it under pressure teaches more than any amount of explanation, and it is usually the person who was least enthusiastic about it.
Ask about the busiest night, not about everyone
Not "is everyone doing it?"
But "what happened on the busiest night since we started?"
⚠️ That single night contains the whole answer. ⇒ If it held there, it will hold. If it did not, no amount of reminding will change that.
Withdraw it openly rather than letting it fade
Reminding again the second attempt decays faster than the first
Changing the change or withdrawing it
⚠️ A change that failed once has already taught people that this kind of change does not stick, which makes the second attempt harder than the first was. ⇒ Withdraw it openly rather than letting it fade. What is withdrawn costs nothing; what fades costs the next change.
Change fewer things
Two at once neither gets the attention it needs on the busy night
One at a time and the fortnight actually finishes
⚠️ The limit is not appetite. It is that only one new thing can be held in mind at 22:00, and everything beyond that reverts.
Three to hold
Changes introduced in the last quarter, and how many are still running. ⚠️ The number is usually sobering and it is never counted.
Days since the last change was introduced. If it is under fourteen, the previous one has not landed yet.
Whether the day-ten check happened. The single behaviour with the largest effect on whether any of this works.
Where the record has to sit
A change that lives in an announcement leaves no trace to check against. What changed, when, who owns it, and what it prevents — written down, or in two months nobody will be able to say whether it is still in force.
tasteck keeps recurring tasks and operational notes on the screens staff already use, so a new step appears in the work rather than in a message that scrolled away.
Nobody rejected your change. It was skipped once on a busy Friday, and nothing in the operation noticed.
Read next
Related articles
Who Types The Request In
A guest asks for somebody by name. Between that sentence and the figure on your monthly sheet, three or four people handle it. Every one of them is a place where it can quietly vanish.
What One More Regular Is Worth
Venues in this trade know what a quiet Tuesday costs them. Far fewer can say what one additional regular is worth over a year — which is the only number that tells you what you can sensibly pay to find one.
What a Listing Is Worth To One Room
A single-room salon and a twelve-room clinic get the same price from the same portal. Only one of them can work out whether that price is defensible, and it is the small one — because the arithmetic is smaller.
Map out your operations in 5 minutes
Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.
Your answers are not stored. The assessment runs entirely in your browser.
Try tasteck free for 30 days
No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.
- No card required
- Free data migration support
- All features unlocked for 30 days