The Control Library (Guides)
Make work easier to trust.
Clear, practical guides on keeping work under control — and a glossary of the terms every operator should know. Drawn from The Control Standard.
Start with a topic
Project Control: How to Keep Work Genuinely Under Control
Project control is the practice of keeping work predictable and steerable — converting uncertainty into clear owners, dated next steps, decision points and fallbacks — so problems surface early instead of as surprises. It is not about controlling people; it is about controlling drift, signals and outcomes.
4 guides
TopicDelegation: How to Hand Over Work So It Actually Holds
Effective delegation means handing over an outcome — not just a task — with a clear standard, sensible constraints and the right check-ins, so the work comes back finished rather than bouncing back to you. Done well, it raises a team's capacity and lowers the manager's role as bottleneck.
2 guides
TopicManaging Up: How to Communicate So the People Above You Can Act
Managing up is the practice of communicating so the people above you can steer the work without chasing you. Done well, it reduces their uncertainty — stating the situation, the consequence, what is in hand, what is not, and what you recommend — instead of merely reporting activity. The book calls this skill executive usefulness.
1 guide
TopicSystemising Pain: When to Fix a Process with Software, Automation or AI
Systemising operational pain means turning a repeated, painful task into a clear, owned process before you reach for software. A process is worth fixing with software, automation or AI when the pain is frequent, structured and costly, and the data already exists. Most teams either automate too early or never systemise at all.
10 guides
TopicOwnership: How to Own the Outcome, Not Just the Task
Ownership is holding yourself responsible for whether the work succeeds — not just for finishing your part of it. An owner believes in the mission, steers toward the outcome, and asks questions at the altitude of someone driving the work rather than being driven by it. The book treats it as a visible behaviour, not a job title.
1 guide
Latest guides
How to Run a Lessons-Learned Session That Actually Changes Things
To run a lessons-learned session, gather the people who did the work, ask four questions — what was meant to happen, what happened, why the difference, and what we'll change — keep it blameless but accountable, then turn each lesson into one specific change with a named owner and a date. Without that last step, it's a document nobody reads.
GuideWhy Does My Team Keep Making the Same Mistakes?
Your team keeps making the same mistakes because the problem lives in the system, not the people. A mistake that recurs across different people and projects is a signal about how the work is shaped: unclear handoffs, fuzzy decision rights, missing standards and slow feedback. The fix is to redesign one of those, not to ask people to be more careful.
GuideWhy Is My Team Busy But Still Missing Deadlines?
Your team misses deadlines while staying busy because activity is not control. The work slips in the gaps between decisions, dependencies and handoffs — places effort never reaches. Everyone is occupied, but uncertainty is not shrinking, so the date moves a day at a time until the slip surfaces as a surprise.
GuideHow to Take Ownership at Work: Raise the Altitude of Your Questions
To take ownership at work, own the outcome rather than the task and raise the altitude of the questions you ask. Low-altitude questions handle the detail; high-altitude questions reach for the mission and the pain driving the work. Start at the highest altitude you can, confirm you are enabled, then descend to the specifics.
GuideBuild vs Buy: When Custom Software Beats Off-the-Shelf
Buy when the process is generic and a credible tool fits it with little bending; most needs are like this. Build bespoke software when the process is core to how you compete, no off-the-shelf tool fits without heavy workarounds, or per-seat licensing scales badly. The honest default is buy. Custom earns its cost only on the few processes that genuinely set you apart.
GuideBusiness Process Automation: A Practical Starting Guide
Business process automation (BPA) is using software to run a repeatable business process — approvals, reminders, data entry, status reporting — with little or no manual effort. Start where the work is frequent, rule-based and structured, the data already exists, and an error is costly. Systemise the process first, then automate it.