Perspectives / Business Systems
01 · Business Systems
BEFORE THE INTEGRATION.
Why integration performed before architecture reproduces disconnection at a higher level — and what a proper assessment examines first.
The quiet condition
Most organisations do not lack systems. They hold several — a platform adopted at one stage of the business, a tool chosen at another, a spreadsheet that quietly became infrastructure. Each made sense when it arrived. Together, they form an environment that nobody designed.
The symptoms are familiar. The same record is kept in more than one place. Work pauses because information sits in the wrong system. Reporting is assembled by hand because no single view exists. These are not technology failures; they are architecture failures, felt long before anyone names them an integration problem.
Why integration-first fails
The instinct, when systems disagree, is to connect them. But integration performed before architecture tends to reproduce the disconnection at a higher level: data begins to move, yet decisions do not improve, and the organisation inherits the seams of every system it ever adopted.
This is why transformation programmes so often fail at the architecture stage rather than the technology stage. The tools were never the design. Connecting systems that were never meant to be one environment does not create coherence — it distributes the absence of it.
What an assessment examines
A proper assessment is not an inventory of software. It examines the four things a business system is actually responsible for.
Records — where information lives, which source holds the truth, and where the same fact is silently duplicated.
Workflows — how work actually moves through the organisation, including the steps that exist only because systems do not speak.
Permissions — who can see and act on what, and whether access reflects accountability.
Continuity — what survives a person leaving, a team growing, the organisation changing shape.
None of these questions is technical on its own. Each is a question about the business, asked precisely.
The outcome
A proper assessment does not end in a recommendation to buy. It ends in an order of operations: what must be structured first, what can be connected afterwards, and — frequently — what should be retired altogether.
Sometimes the most valuable integration is the removal of a system that should never have been maintained. The goal is not more connection; it is fewer places where the organisation's truth can disagree with itself.
Perspective before action
Assessment is the first movement of the method: discover the organisation, architect the environment, then engineer and evolve it.
This is why a private consultation at Altura begins with the business rather than the technology. The systems follow.