Start with a map. Build only what it calls for.

We work where technology, people, processes and ownership stop fitting together. The visible problem may be AI adoption, workflow, governance, communication or a system people have learned to work around.

3 stages, taken 1 at a time.
Every stage ends with something your team owns and runs without us.

Which of these is you?

Read the 5 below. Whichever one you recognise, the first move is the same: a map of where your operation loses clarity and momentum, before anyone builds anything.

  • Usually both. From one side, a straightforward request disappears into a queue, so people find a faster route through a favour, a message, or the person they know will get it done. From the other, one team is absorbing work from across the organisation, with urgent and complex requests entering through the same door. The pressure lands on the team handling the work, even when the friction began upstream in how work was requested, prioritised, or owned.

  • The technology can be ready before the organisation is. Infrastructure gets built, adoption accelerates, and suddenly AI is touching work across functions before anyone has agreed where it should be used, who owns the risks, or what happens when something goes wrong. What follows is often firefighting: new checks, unclear exceptions, duplicated oversight and ownership decided after deployment rather than before it.

  • Sometimes the team at the end of the chain becomes accountable for problems it did not create. A business decision arrives late, a product assumption goes unchallenged, or an upstream team leaves something unresolved, and the support function is expected to absorb the consequence. When some functions carry more organisational power than others, this can become normal. Over time, the issue stops being efficiency alone and becomes one of ownership, trust and whether teams believe the process is fair.

  • A process can fail in two directions. Sometimes it was never documented clearly enough to become the way work is actually done. Sometimes people follow it and the outcome still does not improve. Either way, adding another rule rarely settles the question. The useful decision is whether the process needs to be clarified, redesigned, replaced, or retired altogether.

  • Each team may be doing reasonable work against the references it has. The problem appears when those references differ, ownership is unclear, and nobody can say which standards take precedence when the situation changes. Consistency then becomes less a writing problem than a governance problem: what should repeat, who decides, and where judgement is still allowed.

  • Bring the version you would say out loud. The first conversation is for locating the problem, not fitting it into a category. We will tell you what we think would help, and where S31 fits.

3 stages

The work starts with a diagnosis, then takes only the shape the problem calls for. Each stage stands on its own and is approved separately.

Diagnose

For organisations that can feel the friction but cannot yet locate its cause.

We map how work enters the organisation, moves between people and systems, gets decided, handed over and completed. Then we identify where clarity, ownership and momentum leak, and what that is already costing.

You get the map, a sequenced fix plan with owners, and a readout with your decision-makers. Findings are graded by how firmly we can stand behind them.

You keep the map whether or not the work continues.

Install

For organisations that know what needs to change and want to put the new system into practice.

An install addresses what the diagnosis found. That may involve workflow, ownership, governance, communication, user-facing systems, or the way AI is introduced into existing work.

Which areas, and how far into each, follows the map rather than a predetermined menu. Changes are introduced in stages, tested against real work, and built for the client team to own.

We design and specify. Where substantial engineering or specialist build is required, your existing team can take it on, or we can help define what the builder needs to deliver.

Accompany

For teams that want a senior hand while a new way of working beds in, or while a function needs direction without a permanent senior hire.

We work in agreed blocks of time around the moments that need senior judgement, such as a launch, migration, organisational change or system going live.

Work with a clear end is scoped separately as a fixed deliverable.

How the engagement works

Stage by stage.
Each stage is scoped, quoted and approved before it starts. You take only the stages you need. If the scope changes materially, we stop and agree what changes before more work continues.

A clear definition of done.
Before a stage starts, we agree what it will produce, what finished looks like and who signs it off. You should never have to guess whether the work is complete.

You own the work.
Maps, standards, requirements, templates and other working material are handed over in usable, editable form at the end of the relevant stage.

Built for independence.
Someone on your side owns the new way of working from the beginning. We make clear who owns what, how it should change over time and what needs watching after we leave. S31 is not designed to become your permanent production line.

3 steps, starting with a conversation

Step 1

The first conversation.
30 minutes, no charge.

You describe the situation. We ask how the work moves, who is involved, where it stalls and what the problem is already costing. You leave with a view on what would help. If S31 is not the right call, we will tell you.

Step 2

The diagnosis.
Scoped with you, then quoted.

We map what is happening, locate the underlying friction and set out what should change first, in what order and with whose ownership. The diagnosis stands on its own. You keep the map and can act on it with or without us.

Step 3

The work,
in the shape the map calls for.

That may mean an install, a period of accompaniment, or both. The work is taken in stages, approved separately and built so that ownership ultimately sits with your team. You fix what the map found and nothing more.

Before you book

  • Where the work has a defined deliverable, we quote a fixed fee rather than an hourly rate. The cost depends on the shape of the problem, including how many teams, markets, systems and decision layers are involved. You get the scope and the fee in writing before the stage starts.

  • Because the diagnosis is the work, not a sales exercise. It produces a map of what is happening, where the underlying friction sits and what should change first. You keep that map whether or not S31 does the work that follows.

    The first conversation is free.

  • Usually not. We work on the system around the work: how it enters, moves, gets decided, crosses between teams and holds its standard. Your internal teams, engineers, agencies and specialist suppliers continue to do the parts they are best placed to do.

    If the diagnosis shows that a capability or supplier is part of the problem, we will say so.

  • We design the operating structures the diagnosis calls for and take them far enough to work in practice. That can include workflows, decision rights, governance, standards, requirements, playbooks and working examples.

    Where implementation needs substantial engineering or another specialist build, your existing team can take it on, or we can help define what the builder needs to deliver.

  • Both, according to what the work needs. Much of an engagement can run remotely. We come into the room for the parts that benefit from it, such as interviews, working sessions, observing how work actually moves and reading findings back with decision-makers.

    The balance follows the work rather than a fixed delivery model.

Get your map

Bring the question you are already asking. Leave with a view on what would help.

Talk to Us
Talk to Us