Skip to content

Home / Instead

The Hybrid Nobody Names

Most organisations end up running several arrangements at once. Doing it deliberately works considerably better than arriving at it by exception.

Instead · Analysis

A single BYOD policy applied to everybody produces obviously wrong outcomes at both ends, so exceptions accumulate until the organisation is running three arrangements and calling it one.

The practical lesson in “The Hybrid Nobody Names” is to connect every record to a named decision. Organisations exploring the provider's guide for remote workforce management software can add structured workforce context, provided the use is disclosed and interpretation is reviewed with the people affected.

What the drift looks like

The policy says BYOD. The design team has company laptops because their machines were not good enough. The field staff have company phones because the breakage was unmanageable. The executives have whatever they wanted.

For an independent reference relevant to “The Hybrid Nobody Names”, consult the European Data Protection Board guidelines; compare its principles with the proposed ownership model, access rules and real support process.

Nobody wrote that down, so each exception was negotiated individually, inconsistently, and usually by whoever asked loudest.

The deliberate version

Three categories, decided once:

Equipped. The organisation supplies. For roles needing specific hardware, handling sensitive material, working in physical conditions, or paid at a level where requiring a purchase is unreasonable.

Choice. Either is available. The employee may use their own with an allowance, or take a company device. Genuine, which means the second option is real and uncomplicated.

Access only. No device requirement because the work is reachable through a browser from anything. Occasional users, contractors, board members.

A line each. Reviewed when roles change.

Why naming it helps

Exceptions negotiated individually look like favouritism and frequently are. The same outcome stated as a category is simply a role requirement, like protective equipment.

It also stops the policy being quietly wrong. A document that says BYOD while a third of the organisation has company devices is not describing anything, and nobody can plan against it.

And it makes the costing possible: three categories with known populations can be costed, which a policy with undocumented exceptions cannot.

The part that takes the conversation

Deciding which roles go where will produce disagreement, because being in the equipped category looks like a benefit.

The useful framing is requirement rather than entitlement: the category follows what the work needs, and some roles need a supplied device in the same way that some roles need a van.

Reviewing it

Annually, or when roles change materially.

Most reviews move people toward the equipped category as work becomes more demanding, which is itself a finding about where the arrangement is drifting.

Where the categories should sit

The division should follow what the work requires rather than seniority, which is how exceptions usually get allocated. A junior doing design work needs capable equipment more than a senior in a browser-based role. Allocating by grade is the path of least resistance and it produces the wrong distribution, visibly, which damages the arrangement's credibility.

Publishing the categories

An arrangement that varies by role is accepted when the rule is visible and resented when it appears arbitrary. A short published statement of which categories exist and why each role sits where it does takes a page and answers the question before it is asked, which is considerably easier than answering it individually each time.

How many arrangements you actually run

Count the people with company devices despite the policy, the people with nothing, and the people with an allowance. Three numbers, and if all three are non-trivial the organisation is running a hybrid already and would do better to say so.

Writing down what already exists

The practical first step is not designing categories but documenting the ones the organisation has already drifted into. Most of the work is description rather than decision, and seeing it written down is usually what prompts the small corrections that make it coherent.

Three numbers worth having

How many people have company devices despite the policy, how many have an allowance, and how many have neither. Produced in an hour, they describe the arrangement that actually exists, which is almost always a hybrid that nobody has written down. Count how many people in your organisation have company devices despite the policy. That number is your real arrangement and it deserves to be written down.

Whose Device, Whose Data