Almost every regional plan I have ever written in January was partially wrong by June. Some assumption about traffic did not hold. A vendor situation changed. A key hire did not land. A brand strategy shifted at corporate. By late June, some of the initiatives I committed to in January no longer served the year, and I was quietly ignoring them while officially still working on them. That gap between what the plan said and what the region was actually doing is the exact space a mid-year reset exists to close.
The reset is not annual planning. Annual planning starts from a blank page. The reset takes the picture that emerged over six months of running the region and adjusts the plan to fit the picture. Get this right and H2 has a real chance. Skip it and the region spends the second half of the year pretending the first six months did not happen.
Why the plan drifts
Fig. 1 · The reset closes the gap between plan and reality without discarding either.
Regional plans drift for predictable reasons. A revenue assumption for a category that did not hold. A key hire that took two months longer than planned. A vendor renegotiation that produced a different structure than expected. A corporate priority shift that changed the resource picture. Some drift is normal. The problem is not the drift. The problem is that most operators keep pretending the original plan is still active while the region quietly stops working on the parts that no longer make sense.
When to run it
Late June to first week of July. Early enough that H2 still has almost six months of runway. Late enough that H1 is complete on the books, including the June close numbers, so the reset is working from a full picture rather than a five-month one.
Block two full working days on the calendar. Off the road. If you have an in-person leadership team, do it in person. If your team is distributed, run a tight virtual format across two days with a real break between them, not a compressed one-day marathon.
Who should be in the room
You, your area directors, and whichever functional leaders regularly touch the region: finance partner, HR partner, catering channel lead if you have one. Not every general manager. Not corporate. The room needs to be small enough that real disagreement can happen without being performative, and honest enough that people will name the things that are not working without political varnish.
The mid-year reset only works if the room can say what everyone already knows out loud without anyone feeling exposed for saying it.
Day 1 morning: sit with what is real
Three hours as a leadership team, no laptops, walking through the H1 picture unit by unit. The one-page document you prepared in advance stays on the table. The purpose of this block is not to make decisions. It is to look at what happened together, without softening it, so that the decisions in the afternoon rest on a shared picture.
Three questions to ask about each unit:
- What actually happened versus what we planned?
- What worked that we did not expect to work?
- What is quietly not working that we have not been naming?
The third question is the important one. Every region has three or four things that are quietly not working that nobody has said out loud because saying them would create work nobody wants to sign up for. Naming them is the whole point of this block.
Day 1 afternoon: kill three things
Every regional plan by June has three initiatives that are no longer serving the year. The reset only works if you actually kill them. Not deprioritize. Not "push to Q3." Kill.
Common candidates:
- A cross-unit initiative that made sense in January but that the team has quietly not been working on because the underlying assumption changed.
- A brand or marketing initiative whose sponsor has moved on or lost interest.
- A tooling rollout that turned out to be more work than value.
- A partnership that is not producing the traffic or margin it promised.
The kills need to be named out loud, agreed by the room, and written into the memo that will go to the field in a week. A kill that is not communicated is not a kill. The field will keep spending time on it, quietly, because that is what the plan said in January.
Day 2 morning: pick three H2 priorities
Three. Not ten. Not "our top ten priorities for H2." Three, each with a named owner, a specific KPI, and a check-in cadence.
Fig. 2 · If a priority does not have all three, it is a wish, not a priority.
The KPI is not the outcome. It is the measurable thing that will tell you monthly whether the priority is on track. "Grow catering revenue" is not a KPI. "Add three new corporate catering clients per unit by October 15 with an average check size of $850" is a KPI. The specificity is not pedantry. It is what makes the priority reviewable.
If the H1 numbers are much worse than planned, pick one H2 priority instead of three. Do not spread attention across five recovery initiatives when the region is behind plan. Sequence beats coverage.
Day 2 afternoon: rebuild the operating rhythm
The reset is not complete until the operating rhythm changes to serve the new priorities. This is the block most teams skip, and it is the block that determines whether the reset actually holds.
Walk through the standing meetings. The weekly one-on-ones with area directors. The monthly regional operating review. The quarterly business review. Every one of them should have a slot on its agenda that serves one of the three H2 priorities. Anything on the current agenda that no longer serves a live priority gets removed.
Do the same for the dashboards. If a KPI for a priority you just killed is still on the general manager dashboard, take it off. If a KPI for a new priority is not on the dashboard yet, add it. The dashboard is a physical artifact of the plan. If it does not match the plan, the plan is a suggestion.
The memo
Within one week of the reset, send a three-paragraph memo to the entire field leadership team.
- What we are stopping. The three kills, by name, with one sentence each on why.
- What we are focusing on for the next six months. The three priorities, with the owner and the KPI for each. One sentence each on why this priority now.
- What changes in how we work. Which meetings gained an agenda item, which meetings dropped one, which dashboards updated. Two or three sentences.
That is the whole memo. Do not oversell. Do not apologize for the kills. State them plainly. Then, in the next monthly regional operating review, walk through the memo live with the room and take questions.
What the reset actually does
The mid-year reset changes three things about the second half of the year.
- It gives the field permission to stop working on things that were quietly dead. This is the largest single benefit and the most underrated one. General managers who have been quietly ignoring an initiative can now redirect that time to something the region has explicitly asked them to do. The energy that gets freed up is real.
- It creates a shared picture halfway through the year. Without a reset, every general manager has their own version of what the region's plan currently is. With one, everyone has the same version, in writing, that they can point at.
- It rebuilds credibility with the field. A regional director who admits the January plan needs adjustment in June signals to the field that the operating system is honest. A regional director who keeps insisting the January plan is fine signals the opposite.
The two failure modes
- Too much change. The reset turns into a rewrite. Everyone comes out of two days with ten new initiatives and the field cannot absorb them. This is what happens when the leadership team has been sitting on too much frustration for too long. The reset becomes a venting exercise. Pick three, not ten. Kill three, not seven.
- Too little change. The reset becomes a status update. Nothing dies. Two or three new initiatives are added on top of the existing ten. The field now has more to do with the same attention, and the reset has made the region worse, not better. If you are not killing anything, the reset was not honest.
The corporate conversation before and after
If the region reports up into a corporate structure, the reset requires a corporate conversation before and after. Before, so that corporate is not surprised by the memo when it lands. After, so that the reset's implications for the annual number are agreed rather than argued.
The before conversation is short. Two or three sentences to your leader ahead of the reset: "We are running our mid-year reset July 8 and 9. I expect to come out with three H2 priorities and three initiatives we are stopping. I will send you the memo before it goes to the field." That is enough. You are asking for informed consent, not permission. Any leader who is worth reporting to will value the heads-up.
The after conversation is where the harder work lives. If your reset implies that the H2 forecast should change because of the H1 read, that has to be surfaced to corporate finance with real numbers, not vague concern. Bring a revised forecast to that conversation, not just a story. Corporate can absorb bad news with a plan attached to it. Corporate cannot absorb bad news without one.
The point
January's plan is not a promise. It is a picture of what the region thought was true at the beginning of the year. Six months in, that picture has been overtaken by reality. The mid-year reset is the working meeting where the plan is adjusted to match reality, in the open, with the leadership team.
Two days. Three kills. Three H2 priorities with owners and KPIs. A rewired operating rhythm. A three-paragraph memo. That is the whole reset. Run it every June and H2 becomes a coherent six months of work. Skip it and H2 becomes a slow drift where everyone quietly stops believing the plan while pretending the plan is still active. That drift costs more than the two days it would have taken to reset it.