Skip to content

Per team, never per employee

From 21 January 2026 every organisation that works with Inora receives its own usage report. It is drawn from the system’s own log, counted per team and never per employee. The reason: in South-East Brabant the impression of use and the log were far apart.

Written by

Field note5 min read

I write the reports myself, every month. They hold four things: how many people use Inora and come back, what for, which answers were rated good, and which topics have no good answer yet.

Why a report, and why this one? It goes back to something I saw in December.

Impression and log

In early December I wrote here about the first three months in South-East Brabant. In the same weeks, the project had a different picture: a small group of active users. The log said otherwise: 70% of the staff in the pilot had asked Inora five questions or more.

That is no criticism of the people who held that picture. An impression forms from the people you speak to: the project lead, the keen colleague, anyone with something to report. In Brabant, Inora began on the evening, night and weekend shifts. The nurse who asks a question at night is not in the meeting where the picture forms.

An impression is not a measurement. Inora counts every question, per team and without a name. Anyone who wants to know how it is going should look at that count: every month, not once at the end of a project.

Nor is the question how many people attended a training session or got an account. The question is whether the work went better, and that shows in what people did, not in what they completed.

What we count

People who come back, not accounts. An account says someone was given access. It does not say whether they ever opened Inora. I count who comes back: for each month’s newcomers, who still asks questions in the months after, and who came five times or more. One question can be curiosity. Five times is no longer chance.

What for. By subject, and by kind of question: looking something up, or having Inora do something. A team sees where its questions are, and an organisation sees which of its sources carry the most weight.

Which answers were good. Under every answer a member of staff can give a thumbs-up or a thumbs-down. I read it by subject and look hardest at the thumbs-downs. Each theme comes with a count, never a question as someone asked it.

Which topics have no good answer yet. We find them in the messages with a thumbs-down and in a selection of conversations that our own team reads without a name, identified only by a technical number. To me this is the most important part of the report. A question without an answer is not the fault of the person who asked it. It is a gap in the sources, and that gap has an owner.

What we never count

Who asked what. No report names an employee. A team is counted only from five people up; a smaller team stays out of the report, because there you could guess who it was. Inora assesses no one, and there is no figure for any individual anywhere. No one in the organisation reads the conversations, managers and board included. Only our own team reads a selection, to see where the sources fall short.

This is not politeness. Senior care assistants who think their manager reads along will not ask the question they need most: the one they feel they should already know the answer to. That is exactly the question Inora needs to receive. Count per employee and you get only the questions people dare to ask, and you no longer measure what a team needs.

Who reads the report

The team leader sees which topics the team asked about, which went unanswered, and whether a new work agreement is taking hold, from how often the team asks about that topic. Every month the board sees, summed across all teams, what people ask about, which topics found no answer yet and which gaps were closed. Every quarter those figures go into the board’s account of quality to the supervisory board’s quality and safety committee, beside the audits and the incident analyses.

And we read it. We measure our own work by use, month after month, against what we set down with the board beforehand. Not by installation, not by launch and not by the end of a pilot. We do not call software implemented when nobody uses it.

Anyone who works on project money also writes a report for the funder. That report is needed. But a report written for the funder measures what the funder asks, once a year, and by then it is too late for a team. So we turn it round. The usage figures in a report to a funder come from the same monthly reports, not from a separate count or a survey. That report is a by-product. The monthly report is for the teams.

The agenda

What went unanswered is in the report as a topic, for the person who keeps that knowledge in the organisation, with the number of times it was asked and never with the question itself or the name of the person who asked. The next report shows which of those gaps have been closed. That is how the list of topics without a good answer becomes the agenda for the organisation’s knowledge, and that agenda starts today.

Postscript, 26 September 2026

Since August 2026 we no longer read a selection of conversations: for every message a language model determines whether it was answered, whether knowledge was missing and what kind of knowledge that was, and we read a conversation only when the organisation asks in writing, with every access logged. Since September 2026 the topic of a question without an answer reaches the person who keeps that knowledge as a task, without the question itself, in the organisation’s own document system. The date of each change is in our answers on privacy.

Postscript, 2 November 2026

What a care worker asks Inora never reaches the organisation. Only what the care worker sends reaches it, such as a report or an incident report, and the competence record the inspectorate expects (Wkkgz, Wet BIG). That record (demonstrably competent, reserved procedures included) holds only that a protocol was followed, with its version and date, without a usage figure, a score or the content of a conversation.

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.

Talk through what your team needs next.