• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : System thinking guides delivery decisions

Purpose and Strategic Importance

This standard ensures that delivery decisions are made with a holistic understanding of the interconnected systems in which they operate. System thinking enables teams to recognise dependencies, feedback loops, and unintended consequences—reducing waste and aligning efforts across organisational boundaries.

It supports our policy to “Understand the Whole System, Not Just the Parts” by embedding a mindset of optimisation for the whole, not sub-optimisation of parts. Without this, teams may inadvertently duplicate effort, introduce friction, or solve the wrong problems.

Strategic Impact

  • Aligns delivery to broader business outcomes, not isolated outputs
  • Reduces cross-team friction by making dependencies visible
  • Improves decision-making by accounting for upstream and downstream effects
  • Minimises unintended consequences and systemic inefficiencies
  • Enables continuous value flow across silos and domains

Risks of Not Having This Standard

  • Teams optimise for local goals at the expense of global outcomes
  • Dependencies are discovered too late, causing rework and delays
  • Work is duplicated or misaligned across departments
  • Decisions introduce downstream risk or unanticipated side effects
  • Lack of shared understanding hampers cross-functional collaboration

CMMI Maturity Model

Level 1 – Initial

Category Description
People & Culture - Teams operate in isolation with minimal awareness of broader impact.
- Silos inhibit collaboration and systems-level insight.
Process & Governance - Delivery decisions are reactive and locally optimised.
Technology & Tools - Tools and dashboards focus on team metrics, not system flow.
Measurement & Metrics - Performance is measured at the component level, not the system level.

Level 2 – Managed

Category Description
People & Culture - Teams acknowledge some dependencies but rarely coordinate proactively.
- Shared understanding across teams is inconsistent.
Process & Governance - Some coordination mechanisms exist (e.g., Scrum of Scrums).
Technology & Tools - Tools support partial visualisation of cross-team dependencies.
Measurement & Metrics - Work flow and blockages tracked within teams, not end-to-end.

Level 3 – Defined

Category Description
People & Culture - Teams think beyond their own backlog to system-wide outcomes.
- Decisions are informed by conversations across boundaries.
Process & Governance - System-level impact is considered in planning and retrospectives.
Technology & Tools - Tools highlight system dependencies, blockers, and flow constraints.
Measurement & Metrics - End-to-end flow metrics (e.g., lead time across teams) are tracked.

Level 4 – Quantitatively Managed

Category Description
People & Culture - Teams actively collaborate to optimise shared value streams.
- Leaders reinforce systems thinking in planning and review rituals.
Process & Governance - System health is reviewed regularly to guide delivery strategy.
Technology & Tools - Visual tools map value streams, queues, and systemic constraints.
Measurement & Metrics - Flow efficiency and constraint removal tracked across systems.

Level 5 – Optimising

Category Description
People & Culture - Systemic learning drives continuous improvement and organisational design.
- Teams experiment with structural changes to improve value flow.
Process & Governance - Delivery processes are dynamically adapted to optimise system flow.
Technology & Tools - Integrated telemetry and observability systems reveal system dynamics.
Measurement & Metrics - Optimisation based on throughput, value, and system responsiveness.

Key Measures

  • % of delivery decisions made with system-level trade-offs considered
  • Time lost due to unmanaged cross-team dependencies
  • Frequency of system-wide retrospectives or flow reviews
  • Flow efficiency across the full value stream
  • Number of duplicated or conflicting efforts detected and resolved
Associated Policies
Associated Practices
  • Flow-Aligned Backlog Structuring

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering