The Team That Does Not Include Them
Tooling, calendars, all-hands and the small administrative exclusions that accumulate into a person feeling outside.
Whether the person feels part of your company
Career progression
Your own share scheme
Who notices when it is going wrong
YoursThe provider'sCrosses the twoNeither contract
Four matters, and no share: what any one agreement covers differs by agreement. One crosses both, and the handoff is where these arrangements fail. Three sit in neither contract. The section where the most arrangements are lost, and the one no document addresses.
Tooling that will not enrol them, a calendar built around a different country, an all-hands at a time they cannot attend, a social event in a city they have never visited: none of it is deliberate and all of it accumulates.
The management gap in “The Team That Does Not Include Them” becomes harder when distributed work is visible only through anecdotes. A team considering a clearer way to assess gdpr employee monitoring for gdpr employee monitoring can add transparent time and project context, but performance conclusions should still combine agreed outcomes, direct conversation and a documented opportunity to correct the record.
The person experiences a pattern. Everybody else experiences a series of unconnected administrative details.
Teams reviewing “The Team That Does Not Include Them” can cross-check their approach against the CIPD flexible-working factsheet. The comparison should produce written questions for the provider, adviser or internal owner instead of a copied checklist.
The licence that excludes them
Software licensed per employee, a seat count drawn from the HR system, a tool that requires a corporate email the policy did not give them.
Each is a half-hour fix and each takes three weeks because nobody owns it. The cumulative message is clear to the person and invisible to everybody else.
Meetings at impossible times
A team spread across four hours of time zones can share a window. A team where one person sits six hours away cannot, and the default is that the majority's convenience wins every time.
Rotating the inconvenient slot is the obvious answer and is almost never done, because the cost falls on one person who will not raise it.
Where rotation is genuinely impractical, say so and compensate in another way. The thing that corrodes is the pretence that nobody noticed.
The all-hands
Usually scheduled for the headquarters afternoon, which is somebody else's night. A recording is offered, which is not the same thing and everybody knows it.
Where the person's time zone makes live attendance unreasonable, say so openly and arrange something rather than leaving them to decide whether staying up is expected.
The calendar
Their public holidays are not yours. Your company closure days are not theirs. Neither calendar is visible to the other by default.
Publish both at the start of the year in a shared place. It is fifteen minutes and it removes a recurring low-grade friction on both sides.
Social and informal contact
The part that does not survive distance without effort. For a person who is also structurally outside the HR apparatus, informal contact is most of what makes the arrangement feel like a job rather than a contract.
That has to be arranged rather than waited for, and it is the first thing to lapse when everybody is busy.
Travel to meet the team
The single most effective intervention available and the one most often cut on cost grounds. A few days in the same room resets a relationship that email cannot.
Budget it at the start as part of the cost of the arrangement, because added later it reads as a response to a problem.
Who they are introduced to
Beyond their immediate team, usually nobody. An employee accumulates a network through induction, projects and corridors; this person accumulates one only if somebody makes introductions.
Writing down five people they should meet in the first month costs ten minutes and compounds for years:
- Somebody in each team they will depend on.
- Somebody who has been there longest.
- Whoever owns the systems they will use.
- Somebody more senior than their manager.
- Somebody doing roughly their job elsewhere in the company.
Repeat it at six months. The useful introductions at that point are different ones, and by then you know what the person is actually doing.
Documentation as the equaliser
A team that writes things down is one a distant person can join. A team that holds everything in meetings and conversation is one they can only observe.
The discipline helps everybody and is the only structural fix in this note, as opposed to a series of individual kindnesses.
The language of the meeting
Where the working language is not their first, the burden of every meeting falls on them. Written communication is easier; fast informal speech is hardest.
Noticing this and adjusting — more in writing, agendas in advance, checking rather than assuming — is a courtesy that costs the team very little.
The exit interview nobody runs
When this person leaves, your HR process does not cover them, and the provider's offboarding is administrative.
Nobody asks why they went. Doing it yourself, informally and honestly, is the only way the next arrangement is better than this one.
Asking the team as well
The exclusions are visible to colleagues, who notice and usually say nothing because they assume it is deliberate.
Asking the team what this person seems to be missing produces a better list than asking the person, who will be polite about it.
What inclusion cannot reach
The structural facts. They are employed elsewhere, on a different package, outside the review cycle, with a different relationship to the company's future. Attention narrows that gap and does not close it.
What is actually available is a working life that is good on its own terms rather than a convincing imitation of being staff. Said that way it is achievable, and it is also honest enough that the person will not discover a gap between what they were told and what they are living in.