The Control Standard Review: What Drift, Control & Predictable Surprises Teach Us About Work

Redworm-S

Aug 1

5 min read

https://youtube.com/shorts/E2RhsERVWGA?feature=share

A practical business book about moving from task thinking to systems thinking

Some business books motivate you to work harder. The Control Standard: How to Own Outcomes, Reduce Surprises, and Become the Person Leaders Trust by Andrew Ward takes a different route: it asks us to examine how work is controlled, where it drifts, and why seemingly unexpected problems are sometimes visible long before they happen.

That distinction made this book particularly interesting to me. Although Ward identifies ambitious contributors and emerging managers as his primary audience, I found the framework relevant to anyone trying to build a more organized, reliable approach to work.

Ward's experience running Scorchsoft, a software development company, is visible in the book's structure. The writing is precise, the progression is controlled, and the flowchart-like diagrams repeatedly reminded me of my computer science teacher. The book feels less like a motivational manual and more like an attempt to make workplace behaviour observable and manageable.

From Doing Tasks to Thinking in Systems

One of my biggest takeaways was the gap between task thinking and systems thinking.

It is easy to think:

I completed the task, so my responsibility is finished.

But a task rarely exists in isolation. It affects another person, another process, another deadline, or another decision. Systems thinking asks us to step back and examine those relationships rather than concentrating only on our individual piece of work.

This broader approach is consistent with research on systems thinking in organizations. A systematic review by Bui and Galanou found that systems-thinking approaches have been applied to organizational learning and management precisely because organizational problems often require more than isolated solutions.

That is where The Control Standard became particularly relevant to me. I found myself recognizing how often I still approach work as a collection of tasks rather than as an interconnected system.

Drift: When Work Slowly Moves Away From the Plan

The idea of drift was one of the concepts that stayed with me.

A process does not necessarily fail dramatically at the beginning. It can start correctly and gradually become less clear. A responsibility becomes assumed rather than explicit. A decision is postponed. A small communication gap remains unresolved. Eventually, the original plan and the actual situation are no longer the same.

Ward's framework puts attention on this gradual movement.

That idea also connects naturally with systems thinking, where feedback loops and interactions between different parts of a system can produce outcomes that are difficult to see when each component is considered separately. MIT Sloan's recent discussion of systems thinking in business similarly emphasizes looking beyond isolated mistakes toward the interaction of processes, behaviours, incentives and strategies.

For me, this was one of the book's strongest lessons:

The absence of an obvious crisis does not necessarily mean that a system is under control.

The Drift Tax: The Hidden Cost of Letting Problems Continue

The concept of drift tax particularly caught my attention.

The term made me think about the invisible cost created when small process problems are allowed to continue. A little extra clarification here, another follow-up there, repeated corrections, duplicated work, delayed decisions and unnecessary escalation may each appear insignificant. Together, however, they consume time and attention.

This is where I would have liked to see even more examples in the book. I found myself wanting to see drift tax separated more explicitly across process, activity and authority, because the source of the cost can differ considerably.

The idea is especially relevant to modern workplaces where repeated operational pain can eventually become a candidate for process redesign, automation or AI. Interestingly, Ward's own material on systemising operational pain makes a similar distinction: repeated problems should be understood and structured before organizations rush to automate them.

That principle seems increasingly important in an automation-driven workplace.

Predictable Surprises: When the Surprise Was Already There

The chapter on predictable surprises immediately reminded me of an event I once experienced.

The chief guest had an allergy to a particular flower. The event managers knew about the allergy, but the information was not communicated effectively. At the last moment, the bouquet had to be changed, thanks to a skilled assistant who noticed the problem and acted quickly.

What struck me was that the incident was not truly unpredictable.

The risk was already known.

The problem was that the information did not successfully travel through the process.

This interpretation is supported by established management research. Watkins and Bazerman describe predictable surprises as problems that organizations could anticipate but fail to address adequately. Their work identifies psychological, organizational and political vulnerabilities behind this failure.

A later analysis in California Management Review similarly emphasizes the importance of identifying problems, acknowledging them, and ensuring that information moves through an organization to people who can act on it.

That made Ward's discussion especially relatable to me. A predictable surprise does not necessarily require a dramatic catastrophe. Sometimes it is simply the bouquet that almost became an embarrassing moment because one known piece of information did not reach the right person.

Control Points, Control Levers and Ownership

Another set of concepts I found interesting was the relationship between control points, control levers, standards and authority.

At first, these can seem like separate ideas. As the book progresses, however, their relationship becomes clearer: controlling an outcome is not simply about putting in more effort. It involves knowing where intervention matters, who has the authority to act, what standard should guide the action, and how the system should respond when conditions change.

This also explains why the book's emphasis on ownership is more useful than a simple productivity message.

Ownership is not merely completing an assigned activity. It is recognizing what the outcome requires and responding when something begins to move away from that outcome.

That distinction made me reflect on my own work habits. I am still far from completely transforming task-based thinking into systems thinking, but the book made that gap much easier to recognize.

Why the Book's Structure Matters?

One of my favourite aspects of The Control Standard was its pacing.

I never felt lost while moving through the chapters. The controlled progression and precise visual explanations made even unfamiliar concepts approachable. There is something fitting about experiencing such careful control of learning in a book called The Control Standard.

I also enjoyed the clever use of SME, where the familiar business abbreviation can refer to small and medium enterprises while also meaning subject matter expert.

And, unexpectedly, the ideas followed me outside the workplace. While rewatching Game of Thrones, I started identifying examples of drift and failures of ownership in both the Stark and Lannister houses. That was perhaps a sign that the book had done what a good practical framework should do: it had given me a new way of observing situations.

Final Verdict: A Book About More Than Productivity

I would recommend The Control Standard not primarily as a motivational book, but as a book for identifying and correcting the crucial gaps we often overlook during systems thinking.

Its strongest contribution, at least for me, is the shift from asking:

“Did I complete the task?”

to asking:

“Is the outcome actually under control?”

That is a small change in wording, but potentially a significant change in how we understand work.

For managers, contributors and anyone interested in operational thinking, the book offers useful concepts for examining drift, ownership, control points and predictable surprises. And in workplaces increasingly shaped by automation and predictive technologies, learning to recognize where a system is drifting may become just as important as learning how to make the system faster.