A new book by Alastair Jupp
Workflows, Decisions, Discipline
Would you deliberately design your business to work the way it works today?
Every business already has an operating system, whether anyone designed one or not. It decides how demand enters, how work moves through the business, how decisions get made, and what finally comes out the other end. This book is about seeing it clearly enough to improve it.
The argument
Three words, in that order
Workflows move value. Decisions direct value. Discipline protects value. The order matters, because each depends on the one before it, and a business that skips ahead ends up automating a workflow nobody has understood or enforcing a standard nobody agreed.
How demand enters the business, how work actually moves through it, and what gets produced at the other end. The real path, including the joins between teams where value most often leaks.
Whether the business knows what matters, can act on it, and can see whether it worked. Clarity, capability and control, plus the design of the repeated decisions that quietly set the pace of everything else.
People, process and technology, and what happens to all three under pressure. Systems decay unless something holds them, so this is the part that decides whether the first two survive a busy quarter.
Why this book
Once you see the system, you can improve it. Until then, you are mostly negotiating with symptoms.
The sales team is busy, but opportunities still drift. Delivery is busy, but handovers still cause confusion. Service is busy, but the same issues keep coming back. Finance is busy, but still has to chase missing information. Each one looks like it belongs to a different department with a different fix.
Work moves between those departments. So do decisions, data and delay. What sits in the middle is the operating system of the business, and it shows itself in the handover that works and the one that always needs chasing, in the dashboard people trust and the spreadsheet they secretly trust more.
Weak operating systems are rarely designed. They get inherited, patched, stretched and worked around until the workarounds become the real system. The book is written to be usable while the business is busy and under pressure, without a glossary or a workshop to get started.
The model
Deliberately simple, because business is complicated enough
Nine words carry the whole framework. Reach for it when a customer problem repeats, when a workflow slows down, when a team is overloaded, or when AI feels promising but vague.
Contents
Twenty chapters, four parts
- Part One: Seeing the System
- 01The Business Is Already a System
- 02The Symptom Trap
- 03The Department Illusion
- 04The App Mistake
- Part Two: Workflows
- 05Demand: What Enters the System
- 06Workflow: Where Value Is Created or Lost
- 07Output: What the System Really Produces
- 08The Joins Matter More Than the Boxes
- Part Three: Decisions
- 09Clarity: The System Needs to Know What Matters
- 10Decision Design
- 11Capability: The Business Must Be Able to Act
- 12Control: How the Business Sees and Steers
- Part Four: Discipline
- 13People: Behaviour Is Part of the System
- 14Process: Repeatability Without Bureaucracy
- 15Technology: The Spine, Not the Strategy
- 16AI: The Accelerator of System Quality or System Chaos
- 17Systems Decay
- 18The Discipline Advantage
- 19Building Your Business Operating System
- 20The Future Belongs to Systems-Led Businesses
- The Operating System You Choose
Five practical appendices
Five working tools. Use the one that matches the problem in front of you.
Readers
Written for practical business leaders
- Leaders who want the business to work better without making it heavier
- Anyone who has sat in a meeting and thought there has to be a better way to run this
- Businesses where the same problems keep coming back in different clothes
- Teams about to buy software to solve a problem they have not yet understood
- Leaders being asked about their AI strategy who want a better answer than a tool name
- Anyone trying to make a handover, a report or a decision work across two teams
This is a lens and a language for seeing how a business really works. It stays deliberately informal about method, and nothing in it has to be followed exactly. Anyone wanting a certified framework with a glossary and an accreditation path should look elsewhere.
The author
Alastair Jupp
The figures
Thirteen diagrams, at readable size
The book carries thirteen figures: the operating system itself, the decision spine, the judgement ladder, the cost of drift and the rest. Ereader screens are small and greyscale, so every one of them is reproduced in full colour and full size on this site.
They are free to use inside your own organisation, with attribution.
Before it is published
The same thinking, free and available now
The book is not published yet, so there is nothing to buy today. In the meantime the argument it makes is set out in full on one page, and three free guides turn it into methods you can run with your own team at organisation, workflow and task level.
Start with one workflow
Clarify one decision. Strengthen one handoff. Protect one standard. That is how the operating system changes.
Be told the day it is out
The manuscript is finished and the book is not yet published. Leave an address and you will get one email when it is available to buy, and one before then only if there is something worth telling you.
Your address is used to tell you about this book and nothing else. It is not sold, shared or added to any other list, and you can unsubscribe from any email. See the privacy notice.