Why your reasonable adjustments process should be more apple
There is a moment most line managers will recognise. An employee tells you they need some support. You want to help, so you open the intranet to find your reasonable adjustments process. And suddenly you are inside a Microsoft product from 2009.
TL;DR: Most reasonable adjustments processes fail not because organisations refuse support, but because the process is too hard to use. They are built like old Microsoft software: comprehensive, configurable, and exhausting to navigate. The best ones work like Apple. The complexity still exists, but the system absorbs the effort so your employee does not have to. This post shows line managers what an Apple-style adjustments process looks like, and why ease of access matters more than how thorough your policy is.
The Microsoft experience
You know what it is like to use a system that was built to be comprehensive rather than usable.
Fourteen different forms. A dropdown menu that has not been updated since the company rebranded three years ago. A guidance document that runs to forty pages and references a policy that no longer exists. Three separate email addresses depending on which type of adjustment you are requesting, and no clear sign of which one applies to you.
You are a reasonably competent adult. You use technology every day. And yet you spend forty minutes going in circles before giving up and emailing HR directly, hoping someone there just knows the answer.
Now imagine you are the employee in that scenario.
Except you are also carrying the cognitive load of having disclosed something personal and vulnerable. You are already worried about how this will affect your relationship with your manager. You are probably exhausted from masking and compensating and making do. And now you are expected to self-navigate a system that was not designed with you in mind.
This is what most organisations call reasonable adjustments self-service. It is a Microsoft product. Powerful, configurable, technically capable of doing what you need. But only if you already know exactly what you are looking for, have the time and executive function to find it, and do not give up somewhere in the middle.
A lot of people give up somewhere in the middle.
The Apple experience
Now think about how you use an Apple product for the first time.
You do not read the manual. There is no manual. You pick it up, you tap around a bit, and it works. Not because the technology is simpler. Apple products are extraordinarily complex under the hood. It works because someone made thousands of decisions about what to hide, what to surface, what to name things, and in what order to present them. The complexity still exists. You just do not have to manage it.
That is the difference. Apple does not make things easier by removing capability. It makes things easier by absorbing the effort on your behalf.
Your reasonable adjustments process could do the same thing.
What an Apple-style adjustments process looks like
It does not mean having fewer options. It means your employees do not have to find the options themselves. Here is what that looks like in practice.
A single front door: One place to go. Not contact HR, or speak to occupational health, or raise a request through the system. One starting point that takes the employee to where they need to be, whatever they need.
Language that matches how people think: Not submit a workplace adjustment request under the Access to Work framework. Just: I need some changes to how or where I work. The system works out the rest. Employees should not need to know the name of the policy to get the support the policy exists to give them.
Guidance that arrives before people ask: An Apple product does not wait until you are confused to help you. It anticipates the likely next step. A good adjustments process does the same. Here is what typically helps people in this situation, here is what you can do today, here is what we would need to do together.
A process that moves: One of the most common reasons adjustments fail is not that organisations refuse them. It is that they stall. Someone submits a request and hears nothing for three weeks. The silence is its own message. An Apple-style system has clear timelines, proactive updates, and a named person who is accountable for moving things forward.
You as the interface, not the obstacle: Here is the part that matters most for you as a line manager. In a Microsoft-style system, you are a user of a complex process, often as lost as the employee you are trying to support. In an Apple-style system, you are the human layer that makes the technology feel personal. The system does the navigation. You provide the relationship.
Why your reasonable adjustments process matters more than you think
The adjustments that do not get made are not usually the ones that were formally refused.
They are the ones where the employee looked at the process and decided it was not worth it. Where they did a quiet calculation about the effort required, the likelihood of it working, and the risk of being seen as difficult, and concluded the answer was to keep coping.
That calculation happens every day in organisations that believe they have a good adjustments process because the policy document is thorough and the HR team is well-intentioned.
Thoroughness is not the same as accessibility. A forty-page guide is not accessible simply because it contains all the right information.
The organisations that support neurodivergent and disabled employees well are not the ones with the most comprehensive frameworks. They are the ones that made the process so straightforward that getting support was easier than going without it.
That is the Apple test. Not: does your system technically allow employees to access adjustments? But: is accessing adjustments easier than not accessing them?
A question worth sitting with
If an employee in your team needed a reasonable adjustment today, what would you tell them to do?
If the answer involves more than one step, more than one person, or more than a few minutes of their time, you are probably running a Microsoft process.
The good news is that the gap between Microsoft and Apple is not about resources or policy or senior buy-in. It is about design. It is about someone deciding that the employee’s experience of the process matters as much as the process itself.
That someone can be you.
Work with us
At The Neurodivergent Coach, we help organisations redesign workplace support so it is genuinely accessible, not just technically available. If you want to talk about what an Apple-style adjustments process could look like in your organisation, and join us.









