The 80 Per Cent Problem: Rewriting OKRs for a Four-Day Week in UK SMEs

The four-day week has moved from fringe experiment to serious option for many UK SMEs. Pilots in professional services, software, and manufacturing have given leaders evidence that compressed hours can work. But there is a less discussed consequence: most OKR sets were written for a five-day operating rhythm. They assume a certain volume of meetings, a certain buffer for rework, and a certain number of quiet hours for focused delivery. Remove a day and those assumptions do not disappear. They become hidden risks.

The argument here is straightforward. A shorter working week requires a shorter list of outcomes, not a tighter schedule for the same list. Teams that treat the four-day week as a scheduling change will find that their OKRs quietly become decorative.

The hidden five-day assumption

Consider a typical UK SME objective: improve customer onboarding. Under a five-day week, the key results might include reducing onboarding time, increasing completion rates, and producing a new welcome pack. Each result implies meetings, reviews, and coordination. The objective may be sound, but its delivery plan assumes that someone has five days in which to absorb the interruptions.

Compressed hours do not create focus automatically. They expose the absence of it. If an objective already depended on heroic effort, a four-day week will make the heroism visible and unsustainable. The first diagnostic step is therefore not to rewrite every OKR. It is to identify which objectives were only viable because the team had slack that no longer exists.

Fewer outcomes, sharper definitions

A team moving to a four-day week should expect to carry fewer objectives than before. That is not a failure of ambition. It is an acknowledgement that capacity has changed. The practical rule is to protect two or three outcomes that genuinely affect customers, revenue, or operational resilience, and to defer or drop the rest with an explicit record of the trade-off.

Sharper definitions matter as much as fewer objectives. Under reduced hours, an objective such as 'improve collaboration' is too vague to survive. A sharper version might be: 'Reduce the time from client briefing to first draft by 20 per cent by the end of Q1 2027.' The second version can be tested against capacity. The first cannot.

A viability checklist for compressed weeks

Before retaining an objective under a four-day or compressed-week model, test it against the following questions:

• Does the objective still describe an outcome that matters to customers, staff, or the financial position?
• Is there a baseline and a measurable target, or is the objective relying on activity as a proxy for progress?
• Can the named owner realistically deliver the first milestone within the reduced hours available?
• Are the dependencies inside the team's control, or does the objective rely on colleagues who are also compressed?
• Do the key results fit a shorter review cycle, such as a fortnightly or monthly check-in?
• Is there a stopping list that names what will not be done to protect the retained objectives?
• Have stakeholders outside the team agreed that slower progress on deferred work is acceptable?
• Is there a fallback if the compressed week proves unsustainable in the first two months?

If an objective fails two or more of these tests, it should be deferred rather than squeezed. The checklist is not a bureaucratic hurdle. It is a way of preventing the team from making commitments it cannot keep.

A short case-style example

A Bristol-based SME of around seventy people began a four-day week in the first half of 2026. Before the change, the leadership team carried four objectives: improve client retention, reduce onboarding time, launch a new service line, and complete an office relocation. Under the five-day model, all four had sponsors and quarterly milestones.

The first review after the transition exposed a problem. The relocation objective was consuming senior management time, the new service line depended on the same operations lead as onboarding, and client retention was being monitored but not actively managed. The team kept two objectives: client retention and onboarding time. The service line was deferred by two quarters, and the relocation was handed to a smaller project group with a fixed deadline.

The result was not a smaller ambition. It was a clearer one. The operations lead could focus on onboarding without splitting attention between three priorities. The leadership team could review two outcomes in a shorter weekly meeting. The deferred service line returned to the agenda when capacity allowed, with a documented reason for the delay rather than a vague promise to revisit it.

Rewriting the operating rhythm

A four-day week also changes the cadence of OKR management. Weekly reviews may need to become shorter and more disciplined. Monthly business reviews may need to focus on evidence rather than activity. The team should agree in advance which meetings are protected, which are shortened, and which are cancelled.

It is also useful to write non-goals explicitly. A non-goal is not a rejected idea; it is a deliberate boundary that protects the retained objectives. For example: 'We will not start new client pilots in Q1 2027 while onboarding is being redesigned.' That sentence does more for focus than a page of aspirational language.

The leadership test

The four-day week is ultimately a test of leadership discipline. It asks whether a team can choose a small number of outcomes and defend that choice when new requests arrive. OKRs are useful only if they reflect that discipline. If the old five-day list is carried into a four-day week unchanged, the team has not adopted a new model. It has simply given itself less time to fall short.

The 80 per cent problem is not solved by working faster. It is solved by deciding what the team will do with the 80 per cent it has, and by being honest about what will not happen.