Design principles for
a modern management system
A management system will either enable or constrain delivery. These principles were developed to ensure the company's system does the former — built for an agile, asset-led operator, not inherited from an IOC.
- ·Newly formed operator
- ·One opportunity to design it right
- ·Culture shift from IOC to agile, asset-led business
- ·The system will enable or constrain delivery
- ·Not a document library
- ·Not a compliance exercise
- ·A framework for decisions, risk control, accountability and delivery
- ·Over-documentation
- ·Slow approvals
- ·Poor ownership clarity
- ·Normalised workarounds
- ·Goal-setting regime — outcomes over process
- ·Effectiveness over volume
- ·Leadership intent, risk control, evidence of use
Purpose and Risk
- ·Business objectives first
- ·Material risks drive controls
- ·Avoid 'just in case' processes
Ownership First
- ·Single accountable owners
- ·Clear decision rights
- ·Defined interfaces
Thin at the Top
- ·Lean system manual
- ·Strong core processes
- ·Asset flexibility
Decisions Not Approvals
- ·Decision frameworks
- ·Escalation by exception
- ·Faster, safer decisions
Digital by Design
- ·Live registers
- ·Integrated tools
- ·Leadership dashboards
Understandable by Everyone
- ·Plain language
- ·Visual aids
- ·Mandatory vs guidance clarity
Workforce Capability Spectrum
The system must work across different professional backgrounds and academic learning styles. If it is not understood, it will not be used — which makes it not a system at all.
Assurance: From Audit to Insight
- ·Risk-based assurance
- ·Continuous visibility
- ·Leading indicators
Leadership Role
- ·Use the system
- ·Reinforce clarity
- ·Model behaviours
What Good Looks Like
- ·Clear accountability
- ·Confident decisions
- ·Minimal surprises
The design approach draws on disciplines that have proved themselves in other domains — not as theory, but as operational doctrine. The order matters: most organisations add requirements and process, automate complexity, then complain about inefficiency.
Question assumptions → strip back to fundamentals → rebuild from constraints. Physics-style reasoning applied to process design.
Eliminate waste → remove unnecessary steps → simplify flow → improve cycle time. Automating waste only makes waste happen faster.
Validate requirements → eliminate unnecessary functionality → simplify architecture → improve throughput → optimise through tooling.
When faced with competing explanations, the simplest one that sufficiently explains the facts should be preferred.
Prioritise deletion over optimisation. Optimisation feels productive; deletion feels risky. This needs to become operational doctrine.
Industry document estates typically span three tiers: project records in a document management system, management system documentation (both corporate and asset), and operational records. The company's system governs the management system documentation tier and establishes the relationship with the other two — the framework provides the structure; the departments own the content.
Explore the framework matrix →