Organisational Systems • Governance • Operational Redesign
Redesign the system behind operational friction.
The Systems Practice helps leaders identify hidden work, weak handoffs, unclear ownership and ineffective controls — then redesign one critical workflow for clearer decisions, controlled execution and measurable performance.
When hard work is not producing reliable performance
Work passes through too many hands. Information is entered more than once. Ownership becomes unclear between departments. Controls sit outside the workflow. Reports show activity without providing a reliable view of performance.
The result can be delay, rework, inconsistent outputs, recurring audit issues and limited management visibility.
These are not always isolated process problems. They can be signs that the wider operating system needs attention.
Start with one bounded workflow.
The Systems Practice examines how work, information, decisions, measures, controls and technology interact.
What The Systems Practice does
The aim is to identify what is producing operational friction and redesign the system around:
- Clearer work, ownership and decisions.
- Better information flow.
- Fewer unnecessary steps and handoffs.
- Controls embedded within daily operations.
- More reliable measures and evidence.
- Technology that supports the workflow.
Methods support the engagement. The business problem comes first.
Why organisations become complicated
Organisations rarely become complicated by design.
Complexity accumulates.
A control is added after an incident. A spreadsheet fills a reporting gap. One department adopts a different system. An exception becomes standard practice. Growth introduces more roles, approvals and communication paths.
Each decision may be reasonable in isolation. Together, they can create a system nobody deliberately designed.
The answer is not simply to remove controls, automate existing steps or ask people to work harder. It is to understand how the parts interact and redesign the relationships producing the problem.
Start with one bounded workflow
The preferred starting point is one important workflow where friction is visible and the boundary can be clearly defined.
Identify → Map → Remove → Redesign → Deploy → Sustain
The engagement examines the work, information, handoffs, controls, measures and failure points within that workflow. Unnecessary activity is removed, ownership and decisions are clarified, and a controlled future state is developed.
Performance is compared with an agreed baseline. Wider expansion is considered only where the evidence supports it.
What gets redesigned
Depending on the problem, the work may address:
- Workflow steps and ownership.
- Handoffs between teams.
- Information capture and transfer.
- Decision rights and escalation.
- Operational controls and approvals.
- Measures, reporting and audit evidence.
- Supporting technology and security requirements.
Technology may form part of the solution, but it should support a well-designed workflow rather than automate unnecessary work.
Who this is for
The Systems Practice is intended for leaders in mid-sized organisations where growth, regulation, technical delivery or fragmented systems have made work difficult to control.
It may be relevant when:
- Manual reporting or duplicated entry consumes capacity.
- Work crosses departments without clear ownership.
- Delay and rework persist despite sustained effort.
- Teams use inconsistent systems, standards or measures.
- Audit findings recur because controls are not embedded in daily work.
- Leaders receive data but lack a reliable operating picture.
The initial focus is particularly relevant to engineering, the built environment, technology-enabled professional services and other regulated or audit-sensitive operations.
Darren McGinley
Founder and Principal Consultant
Darren has more than 25 years of experience across architecture, engineering, information systems, technical standards, quality governance, secure workflows and operational redesign.
His work has included standardising technical platforms, developing governance and control frameworks, redesigning workflows, improving audit evidence and training multidisciplinary teams. His work also draws on Lean Six Sigma methods, systems thinking, governance, risk management and cybersecurity.
He also holds a BSc (Hons) in Cyber Security, certified by the UK National Cyber Security Centre (NCSC), adding formal cybersecurity depth to his practical experience in systems thinking, process engineering, governance, risk management and technology.
Watch: Organisational Thinking
- Episode 1 — How Organisations Fail
- Episode 2 — Every Process Is a Symptom
- Episode 3 — When Every Department Wins, the Organisation Can Lose
- Episode 4 — Why More Controls Create More Problems
Short explorations of organisational systems, complexity, controls, workflows and unintended consequences.
In development
Paolo Maldini — The Tackle That Never Happened
What can we learn from interventions that were never required because the situation was understood earlier?
Arrigo Sacchi — Remove the Ball
Before solving the visible problem, remove it and examine the structure that produced it.
Jackie Stewart — The Slow Way Is the Quick Way
Why smooth systems often outperform organisations that confuse activity, urgency and intervention with speed.
Richard Wyckoff — Read the Structure Before You Act
Events matter less than the structure producing them. Intervention should follow understanding, not precede it.
Begin with a workflow.
If one critical workflow is creating delay, rework, weak control or unreliable information, email a short description of what is happening.
You might briefly explain:
- What workflow is causing friction?
- Where does delay, duplication or rework appear?
- Who is affected?
- What would improve if the workflow worked properly?
This will help establish whether a bounded engagement would be useful.