• Home
  • BVSSH
  • Engineering Enablement
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : Decision-making authority follows the work, not the hierarchy

Purpose and Strategic Importance

This standard ensures decision-making authority sits with the people closest to the work, not just those highest in the hierarchy. It reduces handoffs, speeds up delivery, and increases team ownership and morale.

Aligned to our "Decentralised Decision-Making" and "Developer Experience Matters" policies, this standard empowers teams to act with autonomy and clarity. Without it, decisions are delayed, accountability is blurred, and innovation is stifled.

Strategic Impact

  • Improved consistency and quality across teams
  • Reduced operational friction and delivery risks
  • Stronger ownership and autonomy in technical decision-making
  • More inclusive and sustainable engineering culture

Risks of Not Having This Standard

  • Slower time-to-value and increased rework
  • Accumulation of inconsistency and process debt
  • Reduced trust in engineering data, systems, or ownership
  • Loss of agility in the face of change or failure

CMMI Maturity Model

  • Level 1 – Initial: Decision-making is centralised or unclear. Authority defaults to hierarchy, resulting in delays, misalignment, and disengaged teams.

  • Level 2 – Managed: Some decisions are made by teams, but authority is inconsistently granted and often challenged. Escalation is common even for local matters.

  • Level 3 – Defined: Teams are explicitly trusted to make decisions relevant to their work. Decision rights are documented and understood across the organisation.

  • Level 4 – Quantitatively Managed: Decision-making patterns are tracked to identify bottlenecks, duplication, or friction. Teams actively reflect on the effectiveness of local authority.

  • Level 5 – Optimising: Decision authority is continuously calibrated to follow the flow of work. Organisational structures evolve to reduce dependency on hierarchy and maximise autonomy, speed, and clarity.


Key Measures

  • Adoption rates and coverage across teams
  • Impact on delivery metrics, quality, or team health
  • Evidence of ownership, governance, or learning loops
Associated Policies
  • Decentralised Decision-Making
  • Developer Experience Matters
Associated Practices
  • Microservices Architecture
  • Dynamic Application Security Testing (DAST)
  • Behaviour-Driven Development (BDD)

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

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