Without systems, capability leaves with people
Knowledge held only in someone’s head walks out with them. A described process is the cheapest form of insurance an organisation has.
Business Core · Object
Operational Systems
How the work actually gets done — the processes, tools and standards that turn intention into output without requiring a decision every time.
The term
What it is
A system is what lets an organisation do something twice without deciding how, both times. That is the whole value: it converts judgement into routine and frees the judgement for things that need it.
It also converts individual competence into organisational competence. Work that only one person can do is a dependency; work described well enough that someone else can do it is a system.
The risk runs the other way too. Systems designed for one scale become obstacles at another, and the organisation that cannot revisit them ends up defending processes whose reason has been forgotten.
Why it earns a place
What goes wrong without it
Bad systems are more expensive than none
A process that exists but is routinely worked around costs the time of following it, the time of the workaround, and the credibility of every other process.
They are the main lever on cost
Most cost reduction that lasts comes from doing the work differently rather than from buying inputs cheaper. That work happens here.
One level in
The modules within operational systems
Four working areas: how the work flows, what supports it, what good looks like, and how it gets better.
Process design
Mapping how work actually moves through the organisation, as opposed to how it is supposed to. The gap between the two is where most operational problems live.
LearnStandards and quality
What good output looks like, defined precisely enough that two people would agree. Without it, quality is a matter of who checked.
LearnContinuous improvement
A rhythm for changing the process based on what it produces, rather than only when something breaks. The rhythm matters more than the method.
Learn
Across the framework
What it touches
- Goal CoreMost tactical goals land on an operational system, whether or not they say so.
- Omni CoreWhat the customer experiences is produced by these systems, not by intentions about service.
- Data CoreProcess measures are what tell you whether a system is working before customers do.
- Business CoreSystems, people and assets are the three things every operation runs on.
Beyond the framework
Models worth knowing here
The Omnigoal says where this belongs and what it touches. It does not tell you how to think about it — other people have done that, and done it well. These are theirs.
The theory of constraints
Eliyahu M. Goldratt · 1984Every system has one bottleneck at a time, and improving anything else changes nothing.
Find the constraint, get everything possible out of it, subordinate the rest of the system to it, then lift it — and when it moves, start again. The counter-intuitive part is subordination: deliberately running other parts below capacity, which looks like waste on every local measure and is the only thing that raises throughput.
- Reach for it when
- When a process has been optimised in many places and the output has not moved.
- Where it stops
- It assumes a system with a stable, findable bottleneck. In knowledge work the constraint moves, is often a person’s attention, and does not sit still to be measured.
Eliyahu M. Goldratt & Jeff Cox, The Goal, North River Press, 1984.
Lean thinking
Womack & Jones, from Taiichi Ohno’s work at Toyota · 1996Define value from the customer’s side, then remove everything in the flow that does not create it.
Five principles: specify value, map the stream that delivers it, make it flow, let the customer pull, and pursue perfection. Underneath is a definition worth stealing on its own — waste is anything the customer would not knowingly pay for, which includes most waiting, most rework and most of what is done just in case.
- Reach for it when
- When work moves slowly through a process and nobody can say where the time goes.
- Where it stops
- Removing slack removes resilience with it. A system tuned for flow is fragile to variation, as several lean supply chains discovered at the same moment.
James P. Womack & Daniel T. Jones, Lean Thinking, Simon & Schuster, 1996; Taiichi Ohno, Toyota Production System, 1978.
Porter’s value chain
Michael E. Porter · 1985Break the business into the activities it actually performs, and ask which of them the customer is paying for.
Primary activities — bringing things in, making them, getting them out, selling them, supporting them — run across the middle, with procurement, technology, people and infrastructure supporting all of them. The point is not the diagram but the question it forces at every box: does this activity add value the customer would pay for, does it cost less than a competitor’s, and if neither, why is it here?
- Reach for it when
- When looking for where margin actually comes from, and when deciding what to keep, improve or hand to someone else.
- Where it stops
- It was drawn for manufacturing and fits a linear flow best. Service and software businesses often have to redraw it before it says anything useful.
Michael E. Porter, Competitive Advantage, Free Press, 1985.
The McKinsey 7S framework
Waterman, Peters & Phillips · 1980Also known as The seven S’s
Seven things that have to agree with one another for an organisation to work: strategy, structure, systems, shared values, style, staff and skills.
Three of them are hard and can be changed by decision; four are soft and change slowly whatever anyone decides. The argument is that a change to one obliges a change to the others, which is why a new strategy imposed on an unchanged structure, unchanged incentives and unchanged habits reliably comes to nothing.
- Reach for it when
- Before a reorganisation, and when a strategy has been announced twice and nothing downstream has moved.
- Where it stops
- It says what has to agree, not what any of them should be. As a diagnosis it is strong; as a design it is empty.
Robert H. Waterman Jr., Thomas J. Peters & Julien R. Phillips, “Structure Is Not Organization”, Business Horizons, 1980.
These are other people’s models, named here so you can go to the source and use them properly. The Omnigoal is not affiliated with their authors and is not endorsed by them; nothing of theirs is reproduced here — no canvas, no diagram, no wording. Each is described in our own words, with the originator credited, because the framework is a place to put thinking, not a replacement for the people who did it. Model names and trademarks belong to their respective owners and are used here only to refer to the work itself.
Every model in the framework, and where each one belongsA process that is routinely worked around is worse than no process. Find the workarounds before redesigning anything — they are the honest description of how the work is done.
The other objects in the Business Core
HR
Responsible for managing the organisation’s workforce. HR’s purpose is to recruit, hire, train, and support employees, ensuring they are high-performing, satisfied, and aligned with the company’s goals.
LearnValue Proposition
Centres on articulating the unique benefits and value that your business’s products and services provide to customers, ensuring these offerings are directly aligned with customer needs and contribute effectively to the organisation’s overall strategy.
LearnMonetisation
Focuses on defining and implementing revenue generation strategies that are integral to the business’s financial sustainability and overall strategic success, ensuring every monetisation effort aligns with and supports the company’s broader objectives.
LearnCore Competencies
These are the unique strengths and abilities that give the company a competitive advantage in the market. The purpose is to focus on these key areas to drive innovation, efficiency, and value creation.
LearnBusiness Assets
Represents the valuable resources owned by the company, such as physical property, intellectual property, technology, or capital. The purpose of assets is to support the company’s operations and strategic objectives, providing the foundation for growth and stability.
LearnPartners
Involves collaboration with external organisations or individuals that complement or enhance your business capabilities. The purpose is to leverage these partnerships for mutual benefits, such as expanding market reach, sharing resources, or enhancing product offerings.
LearnStakeholders
These are the individuals or groups that have an interest in or are affected by the company’s activities, including employees, customers, investors, and the community. The purpose is to manage and balance their expectations and needs, fostering positive relationships and ensuring the long-term success of the business.
LearnFinance
Ensures the strategic management and oversight of company funds, focusing on budgeting, forecasting, and resource allocation to support sustainable growth and financial health.
LearnSupply Chain
Supply Chain encompasses the strategic and operational management of goods and services from procurement to delivery, optimising logistics to ensure timely distribution and customer satisfaction.
LearnManufacturing Operations
Manufacturing Operations focuses on optimising factory performance and production processes. This object ensures that machinery and manufacturing systems are managed strategically to maximise efficiency, reduce costs, and enhance product quality.
LearnCompliance
Focuses on maintaining legal and ethical integrity across all business operations. This includes ensuring regulatory, financial, data, environmental, health & safety, and corporate social responsibility standards are met to foster a sustainable and trustworthy business environment.
Learn