The IT/OT Handbook
Chapters 5 & 6 — Quick Reference Guide
Seven Patterns of
IT/OT Cooperation
1 · Work Coupling
Low: Independent Medium: Coordinated High: Continuous
Does the work cross the IT/OT boundary? If you can go a month without talking to the other domain, coupling is low. If you need them in every decision, coupling is high.
2 · System Coupling
Low: Isolated Medium: Shared platforms High: Cascading failures
How tightly are IT and OT architectures connected? When systems go down, does one team handle it alone — or do both have to scramble together?
3 · Change Velocity
Low: Stable & known Medium: Incremental High: Rapid & uncertain
Is the solution stable and predictable? Can you define all requirements upfront — or are you preparing for fast learning and frequent adjustment as you go?
01
Low Complexity
IT and OT in Silos
Recognising This Pattern
  • "Submit a ticket" is the default answer to every cross-domain request
  • No shared roadmaps, no joint projects
  • Networks are black boxes to the other side
Strengths & Constraints
Fast execution, clear boundaries, zero coordination overhead — optimal for routine work. Fails the moment initiatives require sustained cross-boundary cooperation.
→Cybersecurity pressure or data needs will force the move. Consider Pattern 3 or 4 as a first step.
02
Low Complexity
Outsourced Innovation
Recognising This Pattern
  • Suppliers manage IT/OT integration internally
  • Your teams operate tools; vendors own the architecture
  • No internal digital capability is being built
Strengths & Constraints
Fast to value and frees internal focus. But you trade control for ease — suppliers accumulate architectural knowledge while your teams learn only to operate their tools.
→When integration complexity or roadmap conflicts mount, start internalising capability.
03
Medium Complexity
Shadow Teams
Recognising This Pattern
  • Operations builds digital solutions without IT involvement
  • Fast delivery, but absent governance and architecture
  • High key-person dependency
Strengths & Constraints
Speed and autonomy; proves value fast. Shadow teams signal that formal cooperation doesn't match operational urgency — but duplication costs and political friction grow over time.
→Use shadow team members as facilitators to build the foundation for Pattern 4 or 6.
04
Medium Complexity
Facilitation
Recognising This Pattern
  • Named individuals hold a mandate to bridge IT and OT
  • Language shifts from tickets to people
  • Architecture improves incrementally, no restructuring needed
Strengths & Constraints
Builds cooperation muscle cheaply. Facilitators translate requirements and smooth decisions. Cannot scale to high-complexity work — no shared ownership or joint delivery.
→Foundation is in place. When strategic initiatives demand it, move to Pattern 6.
05
Edge Case
IT/OT Convergence
Recognising This Pattern
  • No separate OT function — IT holds lightweight OT competencies
  • One function manages both domains with unified governance
  • Coordination complexity is not the primary challenge
Strengths & Constraints
Simple governance and unified ownership. An edge case that only works when OT complexity genuinely stays low — for example, connecting to vendor-supplied machines without deep operational specialisation.
→Monitor OT complexity. If it grows, structured cooperation models become necessary.
06
High Complexity
Cross-Functional Project Teams
Recognising This Pattern
  • Mixed IT and OT team with shared goals and joint budget
  • Temporary by design — built around a defined deliverable
  • Dual IT/OT leadership; steering committee in place
Strengths & Constraints
Delivers on hard problems; builds shared language and mutual trust. Core risk: knowledge walks out the door when the project closes — or the team becomes a permanent third silo by accident.
→Plan Pattern 7 from day one. Decide permanent ownership before anyone writes a line of code.
07
High Complexity
Product Teams
Recognising This Pattern
  • Permanent team owns a digital capability end-to-end
  • They build it, run it, evolve it — no handover required
  • Backlog balances new rollouts, support, and feature requests
Strengths & Constraints
Sustained evolution, clear ownership, no handover problem. Overhead for stable or simple capabilities. Requires complete capability mapping — partial transitions create the exact problems Pattern 6 was meant to solve.
→Continuously reduce work coupling, system coupling, and change velocity to free capacity for value creation.