The Mid-Year Reset
What will you do differently in the second half?
It’s the end of July.
The year has been busy! A process change in Q1. A promotion on the team in the spring. New equipment that took three weeks longer to install than planned. A quality initiative that’s wrapping up. And somewhere in all of that, seven months have passed.
Most managers I know treat this moment as one to survive — the mid-year review that HR requires, the check-the-box conversation that proves the meeting happened, the paperwork that goes into a file and gets referenced in December when the real review comes around. You do it because you’re supposed to, and then you get back to the floor.
That’s not what this article is about.
I want to talk about something different: the deliberate choice to pause. Before the pace picks back up in Q3, before peak season prep starts consuming everything, before the second half of the year is already happening around you, take a few minutes to reflect and ask a few honest questions about where your team actually is. Not for HR. Not for a file. For yourself, and for the people you’re managing.
Not a formal review. A reset.
The Review vs. The Reset
The formal mid-year review looks backward. It assesses the first six months against goals that were set in January, when you didn’t yet have a full picture of the year ahead, and generates a rating that most people find either demoralizing or meaningless, if not both.
The reset I’m describing looks forward. It uses the first six months as context (what actually happened, what changed, what you learned) to make better decisions about the next six. The first half already occurred. You can’t manage it anymore. The second half is still entirely in front of you.
In sports, halftime isn’t primarily a review of the first half. The coaches aren’t in the locker room dwelling on the score or distributing grades for individual performance. They’re asking two questions: what do we know now that we didn’t know before the game started, and how do we adjust? A mid-year reset asks those same two questions.
The mid-year reset takes an honest look at what the first half taught you—about your team, about your gaps, about what you got right and what you misread—and uses that information to make better decisions about the upcoming months you still have time to shape.
You can’t manage the first half anymore. The only thing the mid-year reset can change is the second half.
Why This Particular Pause Matters
In most warehouse and manufacturing environments, late July sits in a unique spot in the calendar. Q2 is closed. Peak season prep hasn’t fully consumed the schedule yet. The floor is a little quieter than usual, with a relative softness in the pace that won’t appear again until January.
That window is worth using deliberately, because it closes. By September, you’re managing Q3 pressure. By October, you’re in peak preparation. By November, you’re in peak itself. The decisions you make in July—which of your people to develop more aggressively, which gaps to address before they become Q4 problems, which processes to fix while there’s still time to fix them—determine what December looks like.
There’s also a development argument for this specific timing. As I’ve written about before, development takes time, consistency, and progressive challenge. If someone needs to be ready to run their zone independently by November, you need to have started that work in July. Waiting until Q3 review season means you’ve waited too long.
The mid-year reset is when you identify who needs what, while you still have time to provide it.
Start With Yourself
Before any conversation with the people you manage, the reset starts with a self-assessment.
This is the manager’s version of what I described in Start the Year By Understanding Yourself. That post was about using January to set your leadership intentions for the year ahead. The mid-year version of that question is sharper: how has the reality of the first half matched the intentions you set?
There are three questions worth asking yourself before you talk to anyone else:
What did I get wrong about my team in January that I understand better now? Six months of daily context creates knowledge that no amount of pre-year planning can replicate. The person whose capability you underestimated. The process problem you didn’t yet know existed. The associate who was struggling with something that only became visible gradually. What did the first half reveal that you didn’t expect?
Where did I invest my development attention, and does that distribution match what I actually needed? This is the question most likely to produce an uncomfortable answer. Who actually got your time, your stretch assignments, your coaching conversations? Does that match the floor you need to build for the second half? Where are the gaps and what will you do differently?
What conversations have I been postponing? The Conversation You Keep Postponing was about performance specifically. But the question applies more broadly. Are there development conversations that haven’t happened yet? Feedback that someone needs but hasn’t received? Someone who’s been operating in a role they’ve outgrown, waiting for a conversation that would open the next chapter?
The self-assessment doesn’t have to be a long process. An hour of honest reflection, with your notes from one-on-ones and shift reviews, is usually enough to surface the things worth addressing. The hard part is being willing to answer the questions accurately rather than justifying yourself.
The Individual Reset Conversation
Once you’ve done your own assessment, the most valuable thing you can do is have a reset conversation with each person who reports directly to you.
This applies whether you’re managing associates, team leads, or a mix of both. The level doesn’t change the principle—it only changes the vocabulary. A reset conversation with an associate looks different than one with a department manager, but both conversations are asking the same basic questions: where are you, what has the first half been like, and what does the second half need to look like for you?
This is not a formal performance review. No ratings, no documentation for HR, no evaluation that carries weight in December. The reset conversation is designed to create space for honesty that the regular operational rhythm doesn’t always allow.
I stumbled onto this practice during my transition from Area Manager to Operations Manager. In July of that year, I scheduled reset conversations with each of the team leads I’d inherited. I didn’t know what I’d find, but what I learned changed the entire second half of the year. One had been managing around a process gap since February and hadn’t raised it because their previous manager had dismissed an earlier concern. Another was ready for a significant stretch assignment but had assumed it wasn’t coming. A third was dealing with some things in her personal life that had been affecting her energy since May. None of it would have come up in a regular check-in.
The same kinds of discoveries can happen at every level. The associate who’s been improvising around a training gap for months. The reliable performer who’s ready for more responsibility but hasn’t said so. The person whose home life has been affecting their focus. What you learn depends on what you create space for, and the reset conversation is designed to create that space.
The conversation covers four areas. I’ve found that running through them in roughly this order tends to work well:
Where do they think they are? Open with something like: “If you think back to where you were in January (the things you were working on, what you were trying to get better at, etc.) where do you feel like you are now compared to where you thought you’d be?” Let them answer before you offer your own read. Their self-assessment often reveals things you haven’t noticed.
What’s been harder than expected, and what’s clicked? “What’s taken more out of you than you expected this year? And what’s felt easier or more natural than you thought it would?” The first question surfaces hidden struggles. The second surfaces capability you might not have fully recognized. Both are useful.
What do they want the second half to look like? “When we talk again in December, what would need to have happened for you to feel like this was a good year for you?” This is the most forward-looking question in the conversation, and it often produces the clearest picture of what someone actually wants.
What do they need from you? “What would help from my end? Where could I be more useful to you in the second half of the year?” This question signals that the conversation is genuinely bidirectional. You’re not only assessing them, you’re asking them to assess you. The answers are often small and immediately actionable. They’re also the ones most likely to change the quality of your relationship through the rest of the year.
The whole conversation takes 10-15 minutes at most, but I’ve found it pays outsized dividends.
The Team-Level Reset
Beyond the individual conversations, You should also do a team-level assessment to get a realistic feel for where your team’s collective capability sits relative to what the second half will require.
This isn’t about reviewing individual performance. It’s about three questions:
What is the operation going to need from this team in the next six months? Peak volume. New equipment. A process change. A staffing transition. Whatever Q3 and Q4 hold, what does your team need to be able to do well by the time those demands arrive?
What’s the gap between where the team is now and where it needs to be? The Team Capability Mapping post might be helpful here. Go through it with the second half’s demands in mind rather than the first half’s context. You’re not evaluating past performance; you’re identifying future gaps while there’s still time to close them.
Which gaps can be closed before August and which need the full six months? Some are addressable quickly: a training conversation, a process clarification, a responsibility shift. Others require months of consistent development to close. Knowing which is which tells you where to start this week and what to begin planning for.
The team-level reset often reveals things the individual conversations don’t. The coverage gap that you identify when you think about who can run which area independently. The bench that’s thinner than you realized in a specific function. The process that two people understand fully and nobody else has ever been properly trained on. Recognizing these gaps in July will make November less stressful.
What to Do With What You Find
The reset is only useful if what you find in it changes what you do.
This sounds obvious, but it’s where most mid-year reflections fail. The assessment happens. The conversations happen. The gaps become visible. But then the pace of operations absorbs everything and the insights disappear into the same forward motion that made them invisible in the first place.
The first step is triage. Not every gap the reset surfaces is equally urgent or equally addressable. A quick way to sort them: anything that’s been affecting performance or morale since before June is probably overdue and should be addressed this week. Anything that relates to a Q4 operational demand get planned immediately. Anything developmental that doesn’t have an operational deadline gets scheduled but doesn’t need to happen before September.
From there, two practices keep the reset from evaporating. The first is immediate action on anything quickly addressable. If someone has been managing around a process gap since February, fix it before the week is out. If someone is ready for a stretch assignment and hasn’t been offered one, identify the assignment before the next check-in. These small items have an outsized effect on trust; they demonstrate that the reset conversation led somewhere, which makes the next one more honest.
The second is a written plan for the things that can’t be addressed quickly. It doesn’t need to be an elaborate document. A one-page summary of the three or four most important development investments is all you need. Make a note of who they’re for, what they involve, and what success looks like by December. Actually writing it down is what makes it plannable rather than aspirational.
As I explored in Balancing Short-Term and Long-Term Goals, the investments that produce the most durable results are rarely the ones that feel urgent in the moment. They’re the ones that get planned and protected during the windows when the pace allows for it. This is that window. The plan you make in the next two weeks will either be followed or forgotten, and it depends almost entirely on whether you write it down.
Summary
The mid-year reset isn’t a formal review. It doesn’t produce ratings or go into files. Nobody requires you to do it, and the floor will keep running whether you do or not.
What it produces is a clearer picture of where your team actually is. Not where you assume they are, not where the metrics suggest they are, but where they truly are. From that picture, you get a specific set of decisions about what the next few months need to look like.
The year is half over. The decisions you make in July still have six months to compound. That’s enough time to develop someone from capable to excellent, to close the process gap that’s been generating friction since winter, to build the depth that makes peak season manageable rather than surviving.
From Theory to Action
Block an hour this week for your own assessment. Before any conversation with your team, sit down with your notes from the first half—one-on-ones, shift reviews, incident reports, recognition records—and work through the three self-assessment questions in this article. Where did you misread something? Where did your development attention actually go? What conversations are still pending that shouldn’t be? Write the answers down. The act of writing makes the gaps harder to rationalize away.
Schedule reset conversations with each of your direct reports before the end of July. Not a regular check-in. A specifically designated reset conversation: ten minutes, clearly framed as a step-back conversation about the second half. When you schedule it, tell them what it’s for: “I want to spend some time talking about where you are and what you want the next six months to look like.” That framing changes the quality of what they bring to the conversation.
Run the Team Capability Mapping exercise with Q3 and Q4 demands in mind. Use the Team Capability Mapping guide — but run it forward, not backward. The question isn’t “how did my team perform in Q1?” It’s “what will my team need to do well in Q4, and what’s the gap between that requirement and current capability?” Write down the top three gaps. Those are your development priorities for the second half.
Triage what you find before you plan. When the reset surfaces more gaps than you can address at once, sort them into three groups: overdue and urgent, tied to a Q4 operational demand, and developmental with no hard deadline. Address the first group this week. Plan the second group now. Schedule the third group for the second half without letting it crowd out the first two.
Address the one thing that should have been fixed already. In almost every reset, something emerges that should have been addressed earlier and wasn’t. Pick the most important one and fix it before the end of this week. The speed of the response signals that the reset produced something real.
Write a one-page second-half plan. Three or four development investments, each with a name, a specific goal, and a rough timeline. Not an elaborate document, a page that answers the question: if someone reads this in December, would they know what I was trying to build and whether I built it? Put it in your Growth Documentation System where you’ll see it regularly.
Have the conversation with the person who’s ready for more. Every team has someone who’s been performing at or above the ceiling of their current role for months and is waiting for the next step. The reset conversation will surface them if you haven’t already identified them. Don’t wait for an opening to appear. Create one—a stretch assignment, a genuine development conversation, a responsibility shift that signals you’ve noticed where they are and where they could go.