Skip to content

Foundation first: the eight-week plan

The eight-week plan for Inora, summarised. The foundation first, the features after: an environment we control, the source with every answer and no single language model to depend on. Every decision that follows can be laid beside it.

Written by

Field note4 min read

Tonight I am sharing the eight-week plan for Inora: ten pages on what we build first, and in what order. Below I summarise it, quoting only its heading word for word.

What matters most in it is not a feature but the order.

The choice

The plan’s first priority is a foundation that does not give way. Further on, it appears as the heading of the plan itself:

Our Next 8-Weeks: Build the Bedrock, Not Just a Facade.

The obvious route is a demo: features that impress in a presentation, as fast as possible. This plan does the reverse. First come three things nobody looks at in a demo, and only then the features that rest on them. Do it the other way round and you build a facade, then have to take the house apart later to lay the foundation you skipped.

An environment we control

Everything runs in an AWS environment we control ourselves. That lets us act fast, with no black boxes.

When care organisations trust us with their protocols, and their staff ask us the questions they would otherwise ask a colleague, we have to be able to say where everything is, who can reach it and what happens to it. That is only possible in an environment we run ourselves. No black box also means that when something breaks, we look for the cause ourselves instead of waiting for someone else.

So the environment itself is set down in code, from the first day. The plan calls that a requirement, expressly not a luxury.

What is set down in code can be rebuilt, read and rolled back. A change to the environment gets a date and an author, like a change to the product.

The source with every answer

The plan calls the source beside the answer essential for verification and trust: for every significant piece of information, the user sees which document it comes from, which section and, where possible, which page.

In care, a fluent answer without a source is worth nothing. The reader, a senior care assistant or a nurse, must be able to check which document it came from, which section, which page. The professional decides, not the system; the source makes sure that decision rests on something you can look up. And the organisation sees what an answer rests on too, so it knows which document to update when an answer is wrong.

Tied to no single language model

The language model sits behind a layer of its own in our backend. That lets us move to a new, stronger or cheaper model with few changes to the code.

The plan calls this a key strategic decision, and it is. Language models get better, cheaper or simply different every few months. Tie a product to one model and another company decides how that product behaves, what it costs and when it changes. To us the model is a part we can replace. What has to make Inora worth using is the knowledge underneath and the way it reaches the question.

Eight weeks in four cycles

The plan lays the foundation first and builds on it step by step, with feedback all the way. It divides the eight weeks into four cycles:

  • weeks 1 and 2: the environment and the base of the backend, in code;
  • weeks 3 and 4: the pipeline that reads documents in, cuts them into coherent pieces and makes them searchable;
  • weeks 5 and 6: the question, the search through those documents and the language model, with the source beside the answer;
  • weeks 7 and 8: the whole chain from end to end, then testing, finishing and documentation.

There is a demonstration at least every two weeks. Once the core works, acceptance tests follow, with a nurse wherever possible.

The measure for the first two weeks: an environment built entirely from code, and a user who can log in.

After two weeks, then, a user sees nothing more than a login screen. That is not a delay. It is the plan.

Why it is here

We write down what we decide, with the date and the name of the person who wrote it, before we build it. This plan is where that starts.

The last page ends sternly: only ruthless focus and hard choices get us there. It is meant that way. Every feature that comes along in the next weeks waits until the foundation is under it. Every decision that follows can be laid beside this plan. That is why it is here.

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.