Where the Hours Go
The week a team remembers and the week it works can differ. Why the hours get counted before any new tool, hire or process change.
On Monday morning the team sits down to plan the week, and someone asks why the proposal slipped again. The answers come quickly and they all sound right. Client work ran over, and Wednesday went on a system that stopped working. Everyone nods, because everyone was there.
Now picture the same week written down as it happened. The client work is there, and so are the meetings. So is a status update that two people prepared separately for the same meeting. So is a tracker someone updates by hand on Tuesdays, and a long stretch of Thursday afternoon spent chasing an approval that had already been given, in a chat thread nobody could find.
This team is hypothetical. Its two accounts of the week are the subject of this essay, because a team decides what to fix based on one of them.
The week a team remembers
Nobody in that Monday meeting is wrong. They're describing the week the way it felt.
People remember the deadline and the day the system broke. The small jobs that come back each week are easy to leave out, because none of them feels like an event. A few minutes on a tracker is easy to forget, even when it happens several times a week. So people describe the large things accurately and leave out the small, repeated ones, and nobody in the room can say what those add up to over a quarter.
Why the count comes first
When a team feels stretched, the fixes on the table tend to be a new tool, a new hire or a new process. Each of them is a bet on where the time is going. Placed on the remembered week, the bet can miss.
A tool bought on that week can speed up a part of the job that was never slow. A hire can take over the repeated work nobody questioned, so it keeps running, now with a second salary behind it. A process change can add a step to fix a delay that started somewhere else.
Writing the week down first leaves the decision where it was, with the team. The team can then see what it's betting on before it places the bet.
Work nobody asked to stop
One thing a written-down week can show is recurring work that has outlived its reason. Each piece started for a good one. Someone needed that tracker for a project that has since closed. A second sign-off went in after one mistake, years ago, and stayed.
Nobody is to blame for any of it. It keeps going because stopping it would take a decision, and no one has had the numbers to make one. Once the week is written down, the team can put a plain question to each piece: does the reason still hold?
Work that's fine
A written-down week can also show the opposite. Some hours that felt wasted may be the job itself. A long call with a client who needed reassurance, or an afternoon spent getting a new colleague up to speed, can feel like an interruption on the day. Written down next to what it was for, the same hour can look like work worth protecting.
The second step of our method is Diagnose, and the line we hold ourselves to there is "We tell you what we found, including the parts that are fine." If the team only looks for waste, it can cut in the wrong places. If it also writes down what's working, that work has a reason on paper the next time the budget is set.
Where the Hours Audit fits
Our Hours Audit, one of the two audits we run for clients, sits in Business Diagnosis, one of our three buckets. Both of our audits go through your data and processes before handing you the numbers and the options.
If you can't say which of the two weeks your team is working, the Brief Diagnostic is a place to start. It's free, it takes thirty minutes, and it's the first conversation you'd have with us rather than diving straight into a solution. Bring the one recurring job your team has never questioned, and we'll look at it with you.