Leadership playbook

Managing the brilliant
rogue IT operator

Turn individual brilliance into reliable, scalable capability.

High-performing technical teams include people with deep system knowledge, fast problem-solving instincts, and strong ownership. Unfortunately some of these people often skip processes, dodge documentation, and change things without telling anyone. The risk is not their talent; the risk is organisational dependency on that hidden way of working. This playbook helps shift from heroics to trustable systems without dampening performance.

The pattern to
recognise early

Strength

  • Deep system knowledge
  • Fast problem solving
  • High ownership
  • Delivers under pressure

Risk

  • Single point of failure
  • Uncontrolled change
  • Low visibility
  • Bypasses safeguards

Leadership implication

  • They are rarely the issue.
  • Dependency on them is.
  • Build structures that spread capability.
  • Keep performance while reducing fragility.

Seven moves for
sustainable delivery

1. Establish credibility

Understand how they work before introducing structure. Acknowledge capability first.

2. Replace rules with ownership

People who resist control often respond to responsibility.

  • Involve them in defining standards
  • Give ownership of critical systems
  • Hold them accountable for outcomes

3. Redefine what good looks like

Speed and cleverness are not enough. Quality also means supportable, observable, recoverable.

4. Remove real friction

If the process is slow or unclear, people work around it.

  • Eliminate unnecessary approvals
  • Automate repetitive controls
  • Simplify decision paths

5. Use guardrails, not gates

Heavy process creates resistance. Define boundaries and make compliant paths easiest.

6. Make work visible

Hidden decisions create hidden risk.

  • Shared visibility of changes
  • Lightweight design discussion
  • Accessible operational insight

7. Be clear on non-negotiables

Security controls, production access, and traceability require explicit boundaries and calm direct response when breached.

Keep the system in
the balanced zone

Too loose

Hero dependency, hidden knowledge, and fragility drive unpredictable outcomes.

Balanced

Trusted systems, shared capability, and resilience support consistent delivery.

Too tight

Bureaucracy and disengagement create slow delivery and workarounds.

Leadership principle for
high-capability teams

Give capable people ownership, remove unnecessary friction, and build systems where their work can be trusted by others.

The goal is not tighter control. The goal is confidence: strong individuals keep contributing while risk becomes visible, knowledge becomes shared, and delivery becomes reliable.