Time management at the level of an organisation

Most time management advice is addressed to individuals: prioritise better, batch your email, protect a morning. Useful enough, and beside the point when the problem is that fourteen people have collectively promised more than the coming month contains. That is an organisational problem and it needs organisational data.

Personal productivity is rarely the bottleneck

When deadlines slip, the diagnosis usually lands on individuals and the remedy is a technique. Sometimes that is right. More often the work was scheduled on an estimate nobody checked afterwards, and the same estimate is about to be used again for the next quote.

The same holds for the standing commitments nobody re-examines: the weekly report that takes half a day, the client who was profitable three years ago. Individually reasonable, collectively the reason the month is full before it starts.

Time management at this level is not about working faster. It is about knowing what things actually cost, so commitments are made against evidence rather than against optimism.

Time management starts with where the hours go

Almost every organisation is confidently wrong about its own time. Internal work, rework, handovers, the meeting that exists because a decision was postponed – none of it appears in a plan, and all of it consumes the week.

Recording hours against projects, activities and customers makes that visible without anyone having to argue about it. Time tracking is the mechanism, but the point is the picture it produces after a couple of months: the distribution of effort, as opposed to the distribution people assumed.

• billable against non-billable, as a proportion rather than a total
• estimated against actual, per project and per kind of work
• internal work, named rather than lumped into overhead
• rework, separated from first-time work where it matters
• committed hours against genuinely available ones

Capacity and the gap between promises

Capacity planning fails on availability more often than on effort. A month is not four clean weeks: there is holiday, training, sickness and the two days somebody is at a conference.

Subtract those honestly from a team of fourteen and a month can lose a fifth of the capacity that the plan assumed it had. With leave management held next to the hours, planning starts from the days that actually exist. That is usually where over-commitment is revealed – not in the estimates, which were defensible, but in the number of working days that actually existed.

Deciding what to stop

The hard part of organisational time management is subtraction. Everything on the list has a reason, and the reasons are all sound in isolation. What settles it is a number: how much a piece of work costs against what it returns.

Once hours are attached to customers and projects, budget monitoring makes that comparison routine instead of political. Work that consistently overruns can be repriced, rescoped or declined, and the conversation is about a figure rather than an impression.

Measuring without micromanaging

There is a failure mode where measurement becomes the work: more categories, finer intervals, more chasing, until recording time costs more than it saves. Time management data is worth exactly what it changes, and nothing beyond.

The test is the same one that applies to any measurement: name the decision it will change. Anything that fails it is ceremony, and ceremony is what gives time management its poor reputation among the people who have to do the recording.

So keep the structure to the decisions you actually make, let people book their own hours, and put the rigour in approval rather than in supervision. The sector pages give a sense of how different trades structure this, which is generally a better starting point than designing one from first principles.