Resources

A desk sharing concept that holds

Desk sharing almost never fails on software. It fails on the ratio, on peak days and on missing storage.

Updated:

In short

A workable desk sharing concept answers five questions: what is real attendance on the peak day? What ratio follows from it? What happens when desks run out? Where do personal belongings go? And which rules apply to teams and areas? This guide works through them in order.

Key figure
peak day attendance, not the average
Typical ratio
0.5 to 0.8 depending on industry
Most common mistake
setting the ratio too ambitiously
Second most common
no storage concept

The order decides

Most failed introductions start with the ratio and end at acceptance. Successful ones start with measurement and end at the ratio. The difference is that in the second case the number can be justified – to the workforce as well as to leadership.

The peak day is the planning figure

An organization with 50 per cent average attendance but 80 per cent on Tuesdays needs desks for 80 per cent. Planning by the average saves space on paper and creates shortage exactly on the days when teamwork is supposed to happen. The space calculator works that relationship through with your numbers.

What software contributes – and what it does not

Software solves allocation, visibility and measurement. It does not answer whether your ratio is realistic, whether there is enough storage and whether the rules are accepted. Those three are organizational – and they decide success.

Short checklist

Peak day attendance measured; ratio set and justified per location; rules for full days defined; storage planned and procured; zones for teams set up; exceptions named and limited; accessibility and special needs considered; clean desk policy written; communication before go-live; review scheduled after six months.

How it works

  1. 1

    Measure attendance instead of estimating

    Surveys consistently overestimate attendance. Use access data, Wi-Fi logins or a pilot with a booking system – and evaluate the peak day, not the average.

  2. 2

    Set the ratio with a buffer

    Start conservatively. A ratio that causes shortages on the first busy Tuesday costs more acceptance than it saves in space.

  3. 3

    Define rules for peak days

    Decide what happens when no desks are free: overflow areas, quotas per team, lead times or a deliberately accepted share of home office days.

  4. 4

    Organize storage

    No clean desk policy works without lockers or mobile pedestals. Plan storage as a fixed component, not an afterthought.

  5. 5

    Assign areas, not individual desks

    Teams need proximity, not fixed seats. Colour-coded zones create orientation without giving up flexibility.

  6. 6

    Adjust after six months

    With real usage data the ratio can be corrected per location – upwards as well as downwards.

Frequently asked questions

What ratio is realistic?

It depends heavily on the industry. In consulting and IT 0.5 to 0.7 is common, in administration and production rather 0.8 and above. What matters is not the benchmark but your measured peak load.

Should we start with a pilot site?

Usually yes. A pilot produces data, exposes gaps in the rules and creates internal advocates – considerably more effective than a plan-driven rollout everywhere at once.

What about managers who expect fixed offices?

An exception is legitimate as long as it is named and limited. It becomes a problem when exceptions form informally – then the concept loses its basis.

How do we handle disability and special needs?

Through permanently assigned or priority-bookable desks with the right equipment. That can be modelled with asset attributes and access rules and is often legally required.

Talk it through with someone who has done it

Rollouts fail on the same handful of decisions. Thirty minutes on yours costs less than finding out in month three.

30 minutes, Microsoft Teams, no preparation needed