Mid-Year Strategy Review Template for Small Teams
A ready-to-run 90-minute agenda and scoring rubric for your mid-year strategy review, so annual goals stop drifting and you can fix them by July.
A mid-year strategy review is a single 90-minute meeting where you score each annual goal against actual H1 results, test whether the original assumptions still hold, and decide what to keep, adjust, or cut. The template below gives you the agenda, a three-part scoring rubric, and a decision rule for each score band. Run it in the first weeks of July and you have two full quarters to act on what you find.
Why annual goals drift quietly
Annual goals rarely fail in a visible way. They drift. In January the plan is clear. By April, a big customer request has taken two weeks of your best developer. By June, nobody can say whether the new-market launch is late or just "in progress."
Monthly and quarterly check-ins catch execution problems, such as a missed deadline or a campaign that underperformed. They are poor at catching strategic problems, such as a goal that no longer matters or an assumption that turned out wrong. A monthly business review asks "are we on pace?" A mid-year review asks "was this the right pace to be chasing, and is this still the right goal?"
That second question needs its own meeting. If you fold it into a regular review, the regular review's agenda wins and the hard conversation gets squeezed to five minutes.
Before the meeting: the prep that makes 90 minutes enough
The meeting only works if the facts are on the table before anyone sits down. Assign one person, usually whoever runs operations or finance, to spend about two hours on this the week before.
Collect these five things on one page:
- The original annual goals, copied word for word from January. Do not paraphrase them.
- H1 actuals for each goal, next to the H1 target (not just the full-year target).
- The assumptions behind each goal. Example: "Close rate stays at 22%," "We hire two engineers by April," "Ad costs stay flat."
- Resource spend so far: hours, budget, and headcount by goal.
- Three external changes since January: a competitor move, a customer shift, a cost change, anything that touches the plan.
Send it out 48 hours ahead. Ask each goal owner to pre-score their own goal using the rubric below. Self-scores are often optimistic, and that gap between self-score and group score is useful information by itself.
The 90-minute agenda
Keep the clock visible. Assign a timekeeper who is not the senior person in the room.
| Time | Block | Purpose | Output |
|---|---|---|---|
| 0:00 to 0:10 | Reality check | Walk through H1 actuals vs. plan with no discussion of causes | Shared view of the numbers |
| 0:10 to 0:20 | External changes | Review the three changes since January | Updated list of what is different |
| 0:20 to 0:50 | Goal scoring | Score each goal on the three-part rubric (about 6 minutes per goal for five goals) | Scored table |
| 0:50 to 1:10 | Decisions | Apply keep, adjust, or cut to each goal | Decision per goal |
| 1:10 to 1:25 | Resource shifts | Move people, budget, and time to match the decisions | Revised allocation |
| 1:25 to 1:30 | Commitments | Name owners and dates for every change | Action list with dates |
Notice what is missing: a long "what went well" segment. You can celebrate in Slack. This meeting exists to change the plan.
The scoring rubric
Score each annual goal on three dimensions, from 0 to 3 each. The total runs from 0 to 9.
Progress vs. plan (0 to 3)
Compare H1 actuals to the H1 target, not the full-year target. Some goals are back-loaded, and a flat 50% rule punishes them unfairly.
- 3: At or above 95% of H1 target
- 2: 80% to 94%
- 1: 60% to 79%
- 0: Below 60%
Confidence in year-end delivery (0 to 3)
Ask the owner: "Given what we know today, what are the odds we hit the full-year number if nothing changes?" Then ask the room to vote with fingers, all at once, to prevent anchoring on the first speaker.
- 3: Better than 80%
- 2: 50% to 80%
- 1: 20% to 49%
- 0: Under 20%
Assumption validity (0 to 3)
List the assumptions behind the goal and mark each as holding, shaky, or broken.
- 3: All assumptions holding
- 2: One shaky, none broken
- 1: Two or more shaky, none broken
- 0: At least one broken assumption
This third score is the one most teams skip, and it is the most valuable. A goal can be on pace and still be wrong, for instance when you are hitting a lead target for a channel that no longer converts.
Decision bands
| Total | Decision | What it means |
|---|---|---|
| 7 to 9 | Keep | Protect it. Do not add scope. |
| 4 to 6 | Adjust | Change the target, timeline, or resources. Write down which one. |
| 0 to 3 | Cut or reset | Stop it, or rewrite it from scratch with a new owner and new numbers. |
One rule: a broken assumption (a 0 on validity) forces at least "Adjust," even if the total is 7 or higher.
A worked example
Take a 14-person B2B software company with a $3.1M annual revenue goal. In January they set five annual goals. Here is how their July review scored out.
| Goal | H1 target | H1 actual | Progress | Confidence | Assumptions | Total | Decision |
|---|---|---|---|---|---|---|---|
| Revenue of $3.1M | $1.40M | $1.31M (94%) | 2 | 2 | 2 | 6 | Adjust |
| Launch self-serve tier by June | Launched | Slipped to September | 1 | 2 | 2 | 5 | Adjust |
| Cut monthly churn from 2.4% to 1.8% | 2.1% | 2.2% | 2 | 2 | 3 | 7 | Keep |
| Hire 3 people by June | 3 hires | 1 hire | 0 | 1 | 1 | 2 | Reset |
| Partner channel at 15 leads/month | 12/month | 4/month | 0 | 0 | 0 | 0 | Cut |
The revenue number looked fine at 94% of the H1 target, and a quick review would have stopped there. The rubric surfaced the problems underneath. The revenue plan assumed the self-serve tier would add about $180K in H2. With that launch three months late, only about one quarter of that revenue is realistic, roughly $45K. That is a shaky assumption, so revenue dropped to a 2 on validity.
The partner channel scored a clean zero. Four leads a month against a target of twelve, and the original assumption (that two agencies would resell actively) was wrong. One agency had gone quiet and the other had built a competing product.
The decisions that came out of the room:
- Cut the partner channel. This freed roughly 12 hours a week of the head of sales' time and a $2,000 monthly budget.
- Reset hiring. The team had missed the hires because the role descriptions were vague. They cut the target from three hires to two, rewrote both roles, and set a deadline of September 15.
- Move the freed capacity to the self-serve launch. The sales lead's 12 hours went to onboarding content and pricing-page tests, helping pull the launch back to September 1.
- Lower the full-year revenue goal from $3.1M to $2.95M. This was a 5% cut, written down and agreed by everyone. The alternative was keeping a number nobody believed.
The whole review took 85 minutes. The change that mattered most was cutting one goal, which gave the others room to succeed. For help redistributing time after a decision like this, the resource allocation template is a useful companion.
Template: copy and paste
Use this outline as your meeting document. One page per goal is plenty.
MID-YEAR STRATEGY REVIEW: [Company/Team] [Year]
Date: ____ Facilitator: ____ Timekeeper: ____ Scribe: ____
1. REALITY CHECK (10 min)
Goal | H1 target | H1 actual | % of target
2. EXTERNAL CHANGES SINCE JANUARY (10 min)
- Change 1:
- Change 2:
- Change 3:
3. GOAL SCORING (30 min)
Goal: ______________________
Owner: _____________________
Assumptions (mark Holding / Shaky / Broken):
a) ____
b) ____
c) ____
Progress (0-3): __ Confidence (0-3): __ Assumptions (0-3): __
Total: __ / 9 Owner self-score: __
4. DECISIONS (20 min)
Goal | Keep / Adjust / Cut | What changes | Why
5. RESOURCE SHIFTS (15 min)
From | To | Amount (hours, $, people) | Start date
6. COMMITMENTS (5 min)
Action | Owner | Due date
NEXT STEP: Feed decisions into Q3 planning within 7 days.
In your own copy, use a plain hyphen or "to" for the score ranges. It reads fine and avoids formatting issues in shared docs.
Common mistake: reviewing progress instead of relevance
The most common failure is a meeting that reports status. Everyone presents a slide, everyone nods, and the agenda ends with "we're mostly on track." Nothing changes, so the meeting was a calendar entry rather than a review.
The cause is usually that the group only asks "how far along are we?" That question has a comfortable answer for almost any goal that has had some effort put into it. The fix is to force the assumption check and the cut decision into the structure.
Three habits that help:
- Require at least one "Adjust" or "Cut" outcome. If five goals all land at "Keep," your scoring is too soft or your goals were too easy. Rescore with the confidence vote done blind.
- Ask "what would we have to believe?" For each goal, state what must be true for the year-end number to land. If the answer sounds like hope, score confidence at 1.
- Separate facts from discussion. The first ten minutes cover numbers only. Debating causes before everyone agrees on the data wastes the meeting.
A second mistake is adding new goals in July. If the review frees up capacity, the default response is to fill it. Resist that. A review that ends with six goals instead of five has made the drift worse. Move the capacity to the goals you kept, and let any new idea wait for quarterly planning.
After the meeting: make the changes stick
Within 48 hours, send a one-page summary: the scored table, the decisions, and the action list with dates. Update the master goal document so that anyone looking at it in September sees the revised targets, not the January version. Leave the old targets in a "v1" column so you can learn from the gap later.
Then connect it to your regular rhythm. Your Q3 plan should be built on the review's output, using the process in how to run a quarterly planning process for small teams. If an adjusted goal needs smaller steps, the three-step cascade for monthly milestones turns the new target into dated checkpoints.
For the following months, check on the changed goals only. A light weekly or monthly touchpoint is enough, and tracking strategic goals without micromanaging covers how to do it without turning every goal into a status report. Then hold a short follow-up at the 60-day mark in September to confirm that the resource shifts happened.
Key takeaways
- Hold the review within three weeks of the end of Q2, so you still have two full quarters to act on what you find.
- Prep matters more than the meeting: send H1 actuals, the original goals, and the underlying assumptions at least 48 hours ahead.
- Score every goal on progress, confidence, and assumption validity from 0 to 3, and let the total decide whether you keep, adjust, or cut.
- A goal can be on pace and still be wrong, so always test whether the assumptions behind it still hold.
- Require at least one real change, such as a cut, a reset, or a resource shift. A review that confirms the January plan unchanged usually missed something.
- Do not add new goals in July. Move freed capacity to the goals you kept and send new ideas to quarterly planning.
Frequently asked questions
- When should you hold a mid-year strategy review?
- Hold it within three weeks after the end of Q2, ideally in the first half of July for calendar-year companies. That gives you actual H1 numbers and still leaves two full quarters to act on what you decide. Wait until August and the changes you make will only affect a few months.
- How long should a mid-year strategy review take?
- Ninety minutes for the meeting itself, plus about two hours of preparation by whoever owns the numbers. If you need more than 90 minutes, you are probably reviewing too many goals or debating data that should have been settled beforehand.
- Who should attend a mid-year review in a small team?
- Include the decision maker and every person who owns an annual goal, usually 4 to 8 people. Add anyone who controls budget or headcount. Leave out observers, because they slow down the decisions.
- What is the difference between a mid-year review and a quarterly planning session?
- A quarterly session sets the next 90 days of work. A mid-year review tests whether the annual goals and the assumptions behind them are still valid, then feeds the results into Q3 planning. Run the review first and the quarterly plan second.
Related playbooks
Resource Allocation Template for a Small Team (With Example)
A practical resource allocation template for small teams: map people and budget to competing priorities, with a worked example and a copyable worksheet.
How to Run a Project Kickoff Meeting: Step-by-Step Guide
Run a project kickoff meeting that locks in scope, owners, risks, and success criteria. Includes a pre-work checklist, 60-minute agenda, and example.
How to Write OKRs for Small Teams That Get Followed
A step-by-step guide to writing OKRs for small teams, with a worked example, a copyable template, and a weekly check-in routine that keeps goals real.
How to Build a Project Roadmap Template for Small Teams
A lightweight project roadmap template for small teams under 20: how to set milestones, sequence work, assign ownership, and communicate progress clearly.