Large companies run a mid-year review because they have a planning function. Small ones skip it because they have June. June is busy, the year is half gone either way, and a review feels like the kind of thing you do when you have spare capacity — which is precisely why it never happens.
The version worth running in a five-person company takes an afternoon and answers three questions. Anything longer will not survive contact with July.
Question one: what did we say we would do?
Find whatever you wrote in January. An email, a note, a whiteboard photograph. Most owners discover two things: there were fewer stated goals than they remember, and at least one has been quietly abandoned without anyone deciding to abandon it.
The abandoned one is the useful finding. Something displaced it, and that something is what your business actually prioritised. That is worth knowing, and it is often more accurate than the plan.
Question two: where did the hours go?
Not tracked hours — nobody has those. Take the last four weeks and ask each person to name the three things that ate the most of their time. Then compare that against what you would have guessed.
The gap between an owner’s model of where time goes and where it actually goes is consistently the largest source of surprise in this exercise. Rework, chasing, and re-entering data almost never appear in the plan and almost always appear in the answers.
Question three: what would we not start again?
Every business is carrying a commitment it would not take on today — a customer that costs more than it pays, a service kept alive for one client, a tool nobody uses that everyone still pays for. Mid-year is the only realistic moment to stop one of them, because stopping in Q4 disrupts the year-end and stopping in January never happens.
Pick one. Not three.
Where it gets specific to you
The three questions are the same for everyone. What to do with the answers is not.
If the time is going into rework, the fix is usually upstream of where the pain shows — a capture problem, a handoff, a missing field. If it is going into chasing, it is usually a sequencing problem rather than a diligence problem. And if the honest answer is that the business is simply at capacity, that is a hiring-versus-systems decision with real numbers attached, and the right answer genuinely differs by margin structure. In a year where local operating costs are climbing — Bay Area employers have been reporting meaningful health-insurance increases — that calculation moves.
How we would walk you through it
We run the afternoon with you, mostly by asking your team the second question and listening to the answers you have not heard. Owners are rarely told about the workaround somebody invented in March.
What comes back is one page: what the year has actually been spent on, the two or three places effort is leaking, and one specific thing to stop. Then we help you sequence the second half rather than plan it — sequencing survives, plans do not.
This is the operations half of CAO Digital & Operations. Where the leak is a systems problem, it hands over to workflow automation.
Tell us the one thing you would not start again if you were beginning today. That answer usually explains more about a business than its accounts do.
A question worth answering
What did you plan in January that has not happened, and what took its place? If you cannot name the replacement, the time went somewhere nobody chose.
