From signal to steering: the growth path of your company brain

Most data programmes start at the end goal. A platform for everything, an AI strategy and an architecture diagram with twenty blocks. Six months later that diagram hangs on the wall, and not a single team has been helped.

The problem is not the ambition. The problem is the order. Organisations do not become data-driven in one step; they grow into it, and every step has to earn the trust the next one needs. A team that does not yet trust a notification will not allow automation. An organisation that disagrees on what "revenue" means cannot steer on it.

That growth follows the same five stages in virtually every organisation: see, act, connect, steer and look ahead. Whoever knows the route knows where they stand and which step is next.

The five stages of the route

The five stages of the growth path

See. The brain notices and reports. One file or source becomes a governed business asset, and rules watch over it. Deviations arrive in Teams, Outlook or the channel where the team already works. The question answered here: what is happening now?

Act. The brain does the work. Signals become actions with an owner, and actions that keep repeating become automations, with approval where it matters. The question: why does this keep costing us time?

Connect. The brain means the same everywhere. Teams keep their own domain, and agreements on shared concepts connect those domains into one truth. The question: do we all mean the same thing?

Steer. The brain manages the work. Key figures get an owner and a target, and processes across teams are managed as a whole. The question: are we performing, and where do we intervene?

Look ahead. The brain looks forward. Scenarios and forecasts rest on the same recorded history, and proposals arrive before the problem does. The question: what if?

Nobody skips a stage. The trust from one stage is the admission to the next.

The first step is smaller than it looks

Growth starts where the work already is, not where it should one day be. The first step is therefore not a project, but one file. An Excel a team runs on daily, or a source a department already knows, becomes a governed business asset: the columns become concepts with a definition and an owner, and from that moment there is one current version. How that works in minutes is described in the article on version control and collaboration in Excel.

On that asset comes the first notification, in the channel where the team already works. Stock below the threshold, a payment that does not match, a deadline that expires. The team does not have to learn anything new or visit a dashboard; the signal comes to the work. How such alerts work, and why they are as reliable as the data underneath, is described in the article on alerts in Teams and Outlook.

Between reporting and automating lies a bridge

A notification to everyone is an action by no one. That is the place where most programmes lose the team: the jump is made straight from signal to automation, and the team gets a flow it does not recognise and therefore does not trust.

The bridge is the action list. A signal becomes an action with an owner, a status and a trail, and that action lives next to the data it comes from. After a few weeks the list itself is a body of evidence: the same action returning every week, the same handling being identical every time. Those are the candidates for automation. Not devised on a drawing, but proven in the work.

Only then does that one action become a workflow. The team trusts it, because it has already done the action itself dozens of times. The articles about the action list and about the step towards automation work out that bridge.

After that: connect, steer, look ahead

When several teams each have their own business assets and automations, the next question presents itself: do we mean the same thing? Finance counts a customer differently than operations, and every meeting starts with the question of which figure is correct. Data contracts answer that question once: they record what a shared concept means, who owns it and what may be expected of it. Each team keeps its domain; together they form one truth.

On that one truth, steering becomes possible. Key figures become governed objects with one owner and one target, and chains of work across teams are managed as a whole: an exception in one department opens an action in the other. And whoever can steer on the present can look ahead on the same recorded history, with scenarios and forecasts that use the same concepts as the management report.

That is not a promise for tomorrow. It is the direction in which every small step adds up.

Every transition is a decision

A route without decision points becomes a slide: more and more is added, and nobody knows whether it works. That is why every stage has a beginning and an end. At the start, measurable goals are agreed, in the organisation's own terms: hours, errors, days. The transition to the next stage is a joint decision, based on those goals.

A no is a normal outcome. Not ready for the next stage means closing the gap first, and different teams may sit in different stages. Stopping is possible too, in every stage, keeping everything the brain has learned about the organisation. That remains the organisation's, always exportable.

Recognise your stage by the question you ask

The fastest way to find your place on the route is to listen to the question heard most often.

Recognise your stage by the question you ask

Wherever you stand, the next step is small. The full route, with goals and transitions per stage, is on the growth path page.

Frequently asked questions

How long does a stage take? The team decides that, not a project plan. The first alert is live in days; the transition to the next stage follows once the goals of the current stage are met.

Do we need all our data in order first? No. The route starts with one asset and one team. Order grows with use.

Can we skip stages? No, and that is deliberate. Every stage builds the trust the next one needs. The pace may differ per team.

What does the route cost? The price grows with the stages. Alerts and reading stay free forever; you pay per team that joins and per work the brain successfully performs.

Think big. Start small. Grow on trust.

Fourteen statements, one minute: discover where your organisation stands on the route

Take the self-scan · Plan an introduction

Read more

• Version control and collaboration in Excel: the first governed business asset.