1. What exactly are we engineering?

Organisations spend a great deal of time improving individual things. They redesign processes, replace applications, reorganise teams, automate activities. Increasingly they introduce AI.

All of these improvements can be useful. The difficulty is that each tends to focus attention on just one part of a much larger operational reality.

Business-Systems Engineering starts by asking a broader question:

What is the complete thing that all these changes are intended to improve?

The answer is the Business-System.

A Business-System is not simply a process, an application or an organisational department. It is the interconnected organisational system through which value is continually created.

It brings together Purpose, Capability, people and other participants, Relationships, Behaviour, business Items along with their State, governance, evidence, organisational learning and continuing improvement.

The boundary of the Business-System is important. Inside it are things that organisations often analyse separately: customers, employees, decisions, information, technology and documents.

In operation, however, those things depend upon one another. A decision relies on information. Information moves through applications. People interpret it. Customers experience the combined result.

Business-Systems Engineering therefore illuminates the object of engineering. Instead of beginning with Which process are we changing? or Which system are we replacing?, it begins with Which Business-System are we trying to understand and strengthen?

That does not make processes, software or organisational structures less important. It gives them context. We can still engineer each of them — but now we can see what each one contributes, what else it depends upon, and whether changing it actually strengthens the whole.