# Access is not a matter of rank

24 December 2025 · Essay · 7 min read

By [Ahsan Fazal](https://axiomatic.digital/en/about#ahsan), Founder and CEO

Rationing knowledge by rank is a human artefact, and in care it leaves the nurse alone on the night shift with less than the manager by day. In Inora everyone gets the same sources, and the same answer from the same source. What differs by role is the work, not what you may know.

Around noon today I was sent a slide on how you influence a system, as opposed to how traditional management steers it. It had a word on it I did not know: heterarchy. An order with no single fixed top, in which the connections between people carry the work, not the line from top to bottom.

It stayed with me for the rest of the afternoon. At last I could say why I instinctively distrust hierarchies: nature does not work that way.

An instinct is not an argument. So I am writing it out here, because it is about what we are building with Inora.

## Access, alone

Twelve days ago I saw a table from a review of what changes behaviour. Of all the factors it weighed, one alone came out in the top category: access.

That made me happy, because it matches what I have seen since 4 September, when the first care organisation started with Inora. People use the knowledge they can reach. What they cannot reach does not exist for them, however well it is written.

And access is exactly what a hierarchy hands out.

## Knowledge by rank

It is an old order. For centuries books were rare and expensive, and in some libraries they were chained to the shelf. Anyone who could read them had status or money. Every time access to knowledge widened, more changed than who was reading.

In many organisations, what you can read follows your place on the organisation chart. It is rarely decided as such. It creeps in. A folder only managers can open. A policy paper that stays with the management team. The work instruction the senior care assistant gets, without the reasoning behind it.

On top of that, the knowledge that does exist is seldom where the work is. No one opens the quality handbook in the middle of a shift. What a team really knows sits in the heads of a few colleagues and leaves with them. And the people who keep the protocols cannot see whether the floor works from the right version.

Then look at who works when. By day there is someone to ask: the team leader, a colleague, the quality adviser down the corridor. In the evening, at night and at the weekend, a care location often has one nurse in the building. Anyone in doubt then calls the person on call or decides alone.

The result is an inverted distribution. The people with the least rank, who are most often alone, have the least knowledge at hand. The people with the most rank, who are least often alone, have the most. Nobody designed it that way. It is what happens when you hand out knowledge the way you hand out authority.

## Where the variety is

Then something came back from when I was learning control theory: Ashby’s law of requisite variety.

To steer something, you need at least as many different responses as there are different situations coming at you. Apply that to a care organisation. The variety is not in the meeting room. It is on a ward at three in the morning: a client who is different from yesterday, a colleague who calls in sick, a question no training ever covered. No manager keeps up with that variety from above. The person who is there is the senior care assistant or the nurse on shift.

So the knowledge has to be there. Not a summary of it, not the half someone thought suited the role: the knowledge itself. I added this afternoon that an organisation needs people who can organise themselves for that. Only people who can see what the organisation knows can do so.

## What rank is for

This evening I argued against myself. An aircraft has a captain and a co-pilot. A space shuttle has a commander. I did not know which order is objectively the right one.

The objection is fair, and it points straight at the distinction this piece is about. A cockpit has a rank order in who decides. It has no rank order in who may see the instruments. The co-pilot reads the same altimeter as the captain.

Care is no different. There is an order of responsibility, and there should be. A nurse carries out acts a senior care assistant does not. A physician decides what a nurse does not. A board answers for the whole organisation. Who decides follows who answers for it.

But who may know how things are done here need not follow it. Knowing is not doing. Senior care assistants who read how their organisation carries out an act that belongs to the nurse do not carry out that act by reading it. They understand better what they see, and they know sooner whom to bring in, and when.

Rank settles who decides. Rank need not settle who knows.

## What that means for Inora

This is how we build Inora.

Everyone gets the same sources of the organisation: the quality handbook, the protocols, the work agreements. There is no folder only managers can open.

Anyone who asks the same question gets the answer from the same passage, whether they are a senior care assistant on the night shift or a manager on a Monday morning. The source comes with the answer, and anyone can read it. If the answer is not there, Inora says so. Ask again tomorrow, and the answer is the same.

What differs by role is the work Inora helps with, not what anyone may know. Every question arrives with the role of the person asking it. Senior care assistants get their step in the protocol and whom they tell. The nurse unsure whether to call the physician gets the escalation agreement word for word and sees which observations it asks for and which are still missing; they decide whether to call. Which topics a team asked about and where the sources had no answer should reach the team leader team by team and the board summed across all teams, never employee by employee and never as the question itself. From the care assistant at vocational level 2 to the supervisory board, everyone should get the ground for their own work, from the same knowledge.

Inora does not decide. It decides nothing about a client and nothing about which source comes first. That stays with those who answer for it.

## Where the line runs

Not everything is for everyone. But the line follows the content, not the rank. Knowledge about the work, about how things are done here, is for everyone who does the work. Information about one person is not.

Inora does not look into the client record and does not ask for a name or a date of birth. And conversations with Inora are private: no one in the organisation reads them, managers and the board included.

So it runs both ways. Knowledge goes to the floor regardless of rank. Nothing about the people on the floor goes up, person by person. A system that shares knowledge and watches at the same time does not share knowledge. It controls, with a friendlier face.

## An artefact

In [South-East Brabant](https://axiomatic.digital/en/customers/south-east-brabant), Inora has worked on the evening, night and weekend shifts since 15 September. There is no one to ask on those shifts, so that is where the knowledge belongs first. Not because the night shift deserves a privilege, but because that is where the variety is greatest and the help is least.

“It’s a human artefact,” I wrote this afternoon: people made the hierarchy. It sounds like a reproach. It is actually good news. What people have made, people can make differently.

An organisation chart says who decides. It need not say who may know.

## Postscript, 26 September 2026

What was still an intention above is in place now.

Since 21 January 2026 every organisation has received a monthly report for each team: the board sees, summed across all teams, how Inora is used and which topics found no answer yet, the team leader what their team asked about, never employee by employee and never a question as it was asked.

Since February 2026 staff have signed in through their own organisation’s single sign-on, and Inora reads from that sign-in which function someone holds today, not which diploma; the organisation decides what belongs to which function.

Since September 2026 every source in Inora has an owner, a version, a review date and a status, every member of staff can see which of the organisation’s sources are in it, and Inora no longer uses a document that has expired or been withdrawn.

And the source is now marked in the answer: anyone can open it with one tap.

## Do you work in care and use Inora?

Sign-in and help go through your own organisation: your team’s project lead and ambassadors can help you.

## Read on

- [The gap is not the model. It is the knowledge.](https://axiomatic.digital/en/updates/the-gap-is-not-the-model.md): The knowledge care runs on lives in the protocols and in the heads of the few people in every team who quietly do the work better. A general model does not bring the two together, not even with your documents added. A knowledge system does.
- [Variation between professionals is information](https://axiomatic.digital/en/updates/variation-between-professionals-is-information.md): The case for replacing professional judgement with algorithms stands or falls with one assumption: that a brain is a computer. Where a judgement has no right answer apart from the judgement itself, difference between professionals is information. Give them the same sources, not the same conclusion.
- [Our answers on privacy](https://axiomatic.digital/en/updates/our-answers-on-privacy.md): A care organisation asked how Inora handles its data. This is my answer of 1 October 2025: no training on conversations, no name attached to a message, storage in Europe, and a library that grows only after experts check it. What has changed since is dated beneath it.
