Skip to content

Three weeks

People who use Inora in three of their first eight weeks stay. People who start on a group day come back less often. Adoption is decided in the first weeks, in the work, not in a room. What we do differently because of it, and what we are held to from now on.

Written by

Essay4 min read

In March, after seven weeks of training at Vitala+, I wrote that use held where a team wrote Inora into its own work agreements, not where an email announced it (Seven weeks, nine staff groups). Then I knew where use held. Now I also know when it is decided: in the first weeks, and in the work.

What the count says

We counted a year of use, across all organisations together. For each person we counted in how many of their first eight weeks they used Inora, and whether they were still using it in weeks 13 to 26.

Of those who used Inora in one of their first eight weeks, 34% were still using it half a year later. At two weeks it was 52%, at three weeks 71%, at five weeks or more 94%. That counts active weeks of those eight, not necessarily in a row; three in a row is 92%.

FIG 1

Who stays: use in weeks 13 to 26

Used in 1 of the first 8 weeks34%

In 2 of the 852%

In 3 of the 871%

In 5 or more94%

Of every 100 users, by the number of weeks in which they used Inora in their first eight: how many still used it in weeks 13 to 26.

The line falls at around three weeks. Someone who comes back in three different weeks has a habit. Someone who came once has an impression.

What does not decide it

Two things I thought mattered count for less than I thought.

The first answer. Those who saw a visible failure in their first conversation, a refusal or an answer that was no use, came back almost as often as those who got a good answer: 51%, compared with 54%. A good first answer is still needed, for trust and for safety. It does not make a habit.

The training day. Those who started on one day with five or more colleagues of their own organisation came back less often: 38% within thirty days, compared with 59% of those who started alone or with a few colleagues. The gap holds when you take into account the month someone started and how long the organisation had had Inora. Most of those days looked like a session in a room: almost everyone started within the same hour.

In March use at Vitala+ in a month was threefold that of December, after the team training sessions began. That still holds. But it measures who started, not who stayed. In a room everyone asks one real question, and often it ends there.

What does decide it

What the people who stayed have in common is work that comes back. The report of every shift. The handover. The question that comes up again every night. Anyone who ends the first week with such a task done in Inora comes back in the second week, because the work comes back.

That is why it has to happen on shift. In a room, someone practises with an invented question, or plays an informal carer they are not. On shift they do their own work of today, and that work is there again tomorrow.

What we do because of it

We rebuilt implementation around the first three weeks. This is how it is now set out on the Implementation page.

Week one, on their own shift. Everyone starts on their own shift, with one of the people who build Inora beside them. Before the shift ends, they have done their own recurring work in Inora: the report, the handover, that night’s question. By then Inora is already in the start menu and on the phone, because access comes first.

Week two, back on shift. We come back. We fix whatever got in the way in Inora itself, often the same day. That is only possible because we build Inora. A trainer from outside can explain what gets in the way, and an explanation is forgotten.

Week three, the work agreement. The team writes into its own work agreement where Inora comes in and who shows it to a new colleague. That is the moment I described in March. Now I know it has to fall in week three, not in week ten. What a team writes down in those weeks is also the start of the way up: from the work to what the organisation knows.

No more group day as the start. Half an hour in the team meeting to choose what the team will use Inora for, yes. A day in a room, no.

What we are held to

In March I already wrote: count agreements, not attendance. Now we count something more precise. By team, never by employee: how many people used Inora in three of their first eight weeks? That number is in the report to the board every month, and it is what we are held to. Not attendance, not accounts.

For a board that is good news: the adoption problem does not lie with the people who ask the questions. It lies in how the first weeks are set up, and that can be different tomorrow.

Postscript, 2 November 2026

A pilot runs eight weeks, with one team or one location, and the first team is live from day 15. Your manager signs (Implementation).

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.