What a business operating system actually is

· Radiant Solutions · Dubbisa daq. 2

Most organisations do not buy a business operating system. They accumulate one, badly, over about a decade — a finance package here, a point-of-sale system there, a spreadsheet holding the two together because nobody could agree on which system owned the customer.

The result runs the business, technically. It just cannot tell you what the business is doing.

A working definition

A business operating system is the environment in which the work of the organisation actually happens: one place where an operational event is recorded once and every consequence of it follows automatically.

That last clause is the whole thing. A transaction in an outlet is not a transaction and then a finance entry and then an inventory movement, reconciled overnight by someone with a spreadsheet. It is one event with several consequences, and the system knows all of them.

The test

Pick any operational event — a booking, an admission, a sale, a hire — and ask three questions:

  1. How many systems have to be told? More than one means someone is doing integration by hand, whether or not they call it that.
  2. How long until management can see it? If the answer is "tomorrow", the organisation is managing yesterday.
  3. What happens when the two systems disagree? If the answer is "we check manually", the disagreement is a permanent tax, not an incident.

An operating system answers: one, immediately, and they cannot.

Why not just a bigger ERP

A traditional ERP programme assumes the business will reshape itself around the package. Sometimes that trade is worth it. Often the parts that do not fit are precisely the parts that make the organisation worth anything — the way a five-star property handles a returning guest, or the way a specialised hospital sequences a patient journey.

Those are not inefficiencies to be standardised away. They are the operating model. Software should be shaped like it.

What this means in practice

Start from the operating model, not the module list. Draw the domain boundaries around how the business actually works. Give every piece of data exactly one owner, and an explicit contract everywhere else reads it. Then the question stops being "which package covers the most boxes" and becomes "what does this organisation do that nothing generic can do for it".

That is the part worth building.

Waa'ee akkaataa daldalli kee itti hojjetuu haa haasofnu.

Adeemsa, sirna, dhiphina yookiin galma nuuf fidi. Nuti arkitekchara siif fidna.

Adeemsa gurgurtaa miti. Marii arkitekcharaati.

Intarneetii irraa citteetta. Fuulonni duraan daawwatte ammallee ni argamu.