TL;DR
Workplace experience used to mean the building: the desks, the coffee, the front desk. Distribute the team and most of that disappears while the job does not. What is left is harder to see, sits in three different budgets, and usually ends up owned by whoever complains loudest.
- The building was the delivery mechanism, not the job.
- Three things survived: equipment, moments, and the place things are found.
- The home office is not your office, and pretending otherwise causes trouble.
- Budget per head beats a stipend menu. People know what they need.
- Offsites carry more weight now, so plan them as infrastructure.
- If nobody owns it, it defaults to HR without the budget attached.
What workplace experience means without a building
Three things survive the building, and they are the whole job now.
The equipment somebody works on. Previously provided by walking in and sitting down. Now a supply chain with a lead time, which is a different discipline entirely.
Best tools for HR Operations
The moments that used to happen by proximity. A first day, a goodbye, a team forming. These had no owner before because the building produced them.
The place things are found. The noticeboard, the person at the next desk who knew. Now a documentation problem.
| Used to be | Now is | Usually owned by |
|---|---|---|
| Desk and chair provided | Budget and a supply chain | Unclear |
| Walk over and ask | Written documentation | Nobody |
| Birthday cake in the kitchen | A deliberate ritual or nothing | HR, by default |
| Facilities fixes it | A ticket and a courier | IT |
Nothing in that right-hand column is hard. The difficulty is that each item moved to a different function when the building went, and the move was never announced.
Two rows say nobody. That is the honest state in most distributed companies, and it is why the work gets done late and by whoever notices.
The home office is not your office
The most common mistake in this area is treating somebody’s home as a branch to be standardised, and it causes more problems than it solves.
You do not control the space, the lighting or the broadband. You cannot inspect it without being invasive, and the person lives there after work ends. Policies written as though it were a company site run into all three.
What works better is funding an outcome and letting the person choose.
A budget per head rather than a catalogue. A menu of three approved chairs serves the company rather than the person, and the person knows whether they need the chair or the second screen.
Say what the company owns. The most-skipped line and the one that matters at the exit. Our strong preference is that the person keeps furniture and accessories, because recovering a desk across a border costs more than the desk.
Keep computing devices out of the stipend. Those need tracking, enrolling and recovering, and once they are bought on a personal card the ownership question has already gone wrong. For the detail, see our guide to equipment stipends.
The thing that must not sit in this budget
Anything connected to health, pain or accessibility. That needs its own route with a different owner and no fixed cap, because a stipend turns a need into a shopping decision and queues it behind somebody wanting a bigger monitor.
It is also where a little structure goes a long way. The W3C Web Accessibility Initiative introduction to accessibility is written for digital work rather than for buildings, which makes it a better starting point for a distributed team than a facilities checklist built around a floor plan nobody shares any more.
Offsites became infrastructure, not a perk
Disclosure: RemoAsset, named below, is owned by the same people who publish HROpsLab. It is described with its limitations stated, on the same terms as every other supplier. This site takes no vendor money.
When the team shared a building, the offsite was a treat on top of daily contact. Without the building it carries the entire load of people knowing each other, which makes it infrastructure and changes how it should be planned and funded.
Three consequences.
Frequency matters more than production value. Two modest gatherings a year beat one expensive one, because the point is the number of times people are in a room, not the quality of the venue.
Attendance is close to mandatory in effect. Whoever does not come loses something real, so the planning has to take seriously who cannot travel: caring responsibilities, visas, health. Treating it as optional while it functions as essential quietly disadvantages the same people every time.
It needs a budget line that survives a bad quarter. The first thing cut is the thing that was holding the team together, and the effect shows up two quarters later where nobody connects it.
The logistics nobody plans
Equipment for the event itself: adapters, a spare machine, the power strips for a room never designed for forty laptops. It gets handled the week before by somebody with another job, every time.
Where devices travel or are issued for an event, they still need to come back, and an event loan is the commonest entry that never reaches the register. Collection with packaging and a courier arranged handles the return; it cannot tell you a loan happened, which remains yours to record.
The decision table
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| Closed the office | Any | Newly distributed | Nobody owns what is left | Name an owner before a budget |
| Stipend menu in place | 100 plus | Approved catalogue | Serves the company | Switch to a budget per head |
| Offsite cut this year | Any | Fully remote | Cut the load-bearing thing | Protect frequency over venue |
| Devices in the stipend | Any | Grown informally | Ownership unclear | Move computing out, procure it |
| Hybrid, office half empty | 200 plus | Lease still running | Paying for both | Measure days used before deciding |
Naming an owner is most of the fix
Everything above is tractable. What makes it hard is that the role sits across HR, IT and finance, and a job shared between three functions is a job nobody has.
The default outcome is that it lands on HR without the budget, so HR becomes accountable for equipment it cannot order and spending it cannot approve. That is the arrangement to avoid.
Three workable options, in order of how often they succeed. None of them is a committee, because a committee is what you get when nobody will name a person, and it produces meetings rather than decisions.
One named person with a budget line. Does not need to be full time below a few hundred people. Does need the budget, or it is a coordination role with no authority.
Split by object with a written boundary. IT owns anything with a serial number, HR owns the moments and the policy, finance owns the limits. Workable, and only if the boundary is written down.
Rotate it. Rarely works. The role is mostly accumulated knowledge about who to call, and rotation discards exactly that. It also guarantees that every improvement stalls at the handover, because the incoming person inherits a list of open items with no context about why any of them matter.
What the owner should hold
Four numbers, reviewed quarterly: days from offer to equipment delivered, days from leaving date to device recovered, spend per head against budget, and the count of open requests older than a week.
The quarterly question worth asking out loud
Ask the owner one thing each quarter: what did somebody have to chase this quarter that they should not have had to chase?
It surfaces the gaps a dashboard will not, because chasing leaves no record anywhere. The new joiner who messaged three people to find out about a monitor. The leaver who emailed twice about returning a laptop and gave up. Neither appears in any system, and both are the experience the company actually delivered.
Collect the answers for a year and the pattern is usually a single missing handover rather than a general shortage of care, which is both cheaper and more encouraging than it feels.
Where personal data sits on any of those devices, obligations follow the data rather than the hardware, which is the practical reading of the consolidated text of the General Data Protection Regulation and a reason the recovery number deserves an owner rather than drifting. For the wider category this sits inside, see our piece on the digital workplace.
See how equipment comes back after an offsite or a departure at device retrieval with packaging arranged, or read our guide to equipment stipends.
Frequently asked questions
What does workplace experience mean without an office?
Three things survive the building and they are the whole job: the equipment somebody works on, which is now a supply chain with a lead time; the moments that used to happen by proximity, like a first day or a team forming; and the place things are found, which has become a documentation problem rather than the person at the next desk.
Should we standardise home office setups?
No, because it is not your office. You do not control the space, the lighting or the broadband, you cannot inspect it without being invasive, and the person lives there after work. Fund an outcome and let them choose: a budget per head beats a catalogue of three approved chairs, because they know whether they need the chair or the screen.
What must be said in writing?
Who owns what, before anything is bought. Most teams land on the person keeping furniture and accessories, because recovering a desk across a border costs more than the desk. Computing devices should be kept out of the stipend entirely, since they need tracking, enrolling and recovering.
Where do accessibility needs go?
Down a separate route with a different owner and no fixed cap. A stipend turns a need into a shopping decision and queues it behind somebody who wants a larger monitor. This is the single most important line in any equipment policy and it is missing from most of them.
Why treat offsites as infrastructure?
Because without a shared building they carry the entire load of people knowing each other. That makes frequency matter more than production value, two modest gatherings beating one expensive one. It also means attendance is effectively mandatory, so planning has to take seriously who cannot travel.
Who should own this?
One named person with a budget line, which does not need to be full time below a few hundred people but does need the budget. The alternative that works is splitting by object with a written boundary: IT owns anything with a serial number, HR owns the moments and the policy, finance owns the limits. Rotating the role rarely works.
What should the owner measure?
Four numbers quarterly. Days from offer to equipment delivered, days from leaving date to device recovered, spend per head against budget, and open requests older than a week. The recovery number is the one that drifts when nobody owns it, and it is the one that matters where personal data sits on the devices.