A north star
was missing

So we defined one. And built a system around it.

Where this came from

The project closes. Everyone calls it a success. Three months later, the problem it was supposed to solve is still there.

Any experienced analyst has lived this. The scope was delivered. The milestones were hit. The steering committee got its green report. But the problem that motivated the whole initiative was still quietly, stubbornly intact. Lars spent nearly ten years watching this paradox repeat before he could articulate what was wrong.

He went back to first principles. What is a change? What determines whether it succeeds? What can you actually pay attention to, during a change, that tells you whether it's going to work?

The answer reframed the whole discipline. Business analysis is not a set of activities that supports projects. It is, fundamentally, the practice of organisational change. And every change has one thing it has to protect: the integrity of its original intent across the full lifecycle, from the reasoning that motivated it to the outcomes that prove it worked. That is the north star. Intent integrity.

What the discipline is missing

Once the north star was clear, the gap became obvious.

The discipline has no shared framework for keeping a change faithful to its purpose. Two analysts on the same problem produce two different artefacts, in two different tools, with two different definitions of done. The work depends almost entirely on the individual skill of the analyst doing it. The tooling is fragmented across requirements platforms, process modellers, decision logs, wiki pages, and slide decks that never connect to each other. The thinking lives in someone's head. The artefacts live in seven systems. Nothing holds the full picture.

That is why analysis is so hard to learn, so hard to scale, and so easy to dismiss.

Where AI came in

Programming has always been the other half of how Lars thinks. When ChatGPT was released in 2022, the fascination turned into a single question that wouldn't leave him alone: how does a business analyst actually use this? The obvious use is faster drafting. The interesting use is the analytical work itself. AI that holds the reasoning behind every decision and validates whether intent stayed intact from kickoff to outcome.

That question is what Enterwise is built to answer.

Enterwise

Enterwise brings it together. The discipline reframed around intent integrity. The TRACER framework as the shared method. AI doing the overhead so the analyst can do the thinking.
The full picture of a change initiative held in one place: context, reasoning, evidence.

Built for the business analysts of tomorrow