Deciding to Do Less Today

Below a certain point the honest answer is not to find cover but to do less. Close an area, suspend an activity, turn away work, run a reduced service, consolidate two sites into one for the day.

The decision boundary in “Deciding to Do Less Today” needs a named human owner even when software supplies the evidence. Teams researching ethical employee monitoring in relation to ethical employee monitoring should document access, escalation and review, while keeping health details and consequential judgments outside routine activity reporting.

Organisations resist this to a degree that produces real harm, because reducing feels like failing while running short feels like coping. The arithmetic is the other way round: a reduced operation is a controlled state and a short one is not.

For an independent benchmark relevant to “Deciding to Do Less Today”, consult the official Scrum Guide. Use it to test scheduling, working-time limits, attendance records, employee rights and exception handling against the real operation rather than treating a software report as self-explanatory evidence.

Working it out in advance

The reason it does not happen at six forty is that nobody knows what it would look like. Deciding which of three areas closes, who tells the clients, where the people consolidate, and what happens to the work, is twenty minutes of thinking that cannot be done in a crisis.

Do it once, per site, per shift pattern. The output is a short plan: at this level of shortfall, this is what we stop doing, this is who is told, and this is who decides.

Half a page. It converts the hardest decision of the morning into the execution of something already agreed.

The levels

It helps to have two or three defined steps rather than one.

A minor reduction: non-urgent work deferred, a service running slower, appointments spread. Usually within the shift leader's authority.

A material reduction: an area closed, an activity suspended, work turned away. Needs the authority above, and the clients or families told.

A suspension: the operation does not run today. Rare, serious, and it needs the plan more than any other level because it is the one nobody has thought about.

Telling people

The complaint that follows a reduction is almost never about the reduction itself; it is about finding out late or not at all.

Work out in advance who has to be told at each level, and have the message drafted. "We are short-staffed today and your visit will be in the afternoon rather than the morning" sent at eight is a minor inconvenience. The same information discovered at eleven when nobody arrives is a complaint.

Say what is happening rather than why in detail. The client does not need the absence; they need the change to their day.

The contractual question

Some reductions breach something: a service agreement, a contract, a regulatory expectation, a funding condition.

That is a reason to know in advance which ones, not a reason to run unsafely instead. Where a reduction would breach a contract, the plan should say so and should say who must be notified — because a breach notified is a commercial conversation and a breach discovered is a dispute.

Recording it

The same four facts as any other outcome: what the shortfall was, what was reduced, who decided, and what the consequence was.

Reductions are the most under-recorded outcome in this whole subject, because they feel like something to be quiet about. The result is that an operation reducing service twice a month has no record of it, and the establishment conversation has no evidence.

The honest framing

A reduction is the operation telling the truth about what it can do with the people present. Running short and hoping is the operation concealing it, and the concealment is paid for by whoever is on shift and by whoever is receiving the service.

Senior people presented with that framing usually support the reduction, which is a surprise to the shift leaders who have spent years assuming they would not. Finding that out — by asking once, in advance, rather than at six forty — is often the whole of what this change requires.

Who it affects most

Reductions are rarely neutral. The work deferred first tends to be the work with the least vocal recipient, which in many settings means the people least able to complain.

Build that into the plan rather than leaving it to the morning. Stating which activities are protected regardless of staffing, and which may be reduced, is a decision about priorities that belongs with whoever is accountable for the service — not with a shift leader choosing under pressure at seven, who will reasonably protect whatever generates the loudest consequence.