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

What are you looking for?

Standard : Delivery pace is sustainable and protects team wellbeing

Purpose and Strategic Importance

This standard ensures that teams deliver at a pace that is sustainable, humane, and productive. By maintaining a healthy rhythm of work, teams can stay energised, resilient, and continuously improve over time. This creates the conditions for innovation and long-term delivery effectiveness.

Aligned to our "Balance Sustainability with Speed" policy, this standard protects team wellbeing, preserves morale, and reduces the cost of overwork and burnout. Without it, delivery becomes short-sighted, reactive, and damaging to both people and outcomes.

Strategic Impact

  • Improved delivery velocity without sacrificing quality or morale
  • Increased team retention, engagement, and satisfaction
  • Reduced burnout and absenteeism
  • Greater capacity for continuous learning and improvement
  • Consistent ability to meet delivery commitments over time

Risks of Not Having This Standard

  • Burnout and attrition due to chronic overwork
  • Inconsistent or volatile delivery performance
  • Reduced psychological safety and team cohesion
  • Accumulation of technical and process debt
  • Low trust in team commitments or delivery forecasts

CMMI Maturity Model

Level 1 – Initial

Category Description
People & Culture Delivery is reactive and crisis-driven, with little regard for pace.
Process & Governance No formal consideration of workload balance or wellbeing.
Technology & Tools Tools do not support pacing or work-in-progress visibility.
Measurement & Metrics Burnout, attrition, and overwork indicators are not tracked.

Level 2 – Managed

Category Description
People & Culture Teams acknowledge the need for sustainability but often work unsustainably.
Process & Governance Some cadence and planning practices are in place, but not consistently applied.
Technology & Tools Limited use of tracking tools (e.g. velocity, WIP, calendar insights).
Measurement & Metrics Workload and effort are occasionally reviewed.

Level 3 – Defined

Category Description
People & Culture Teams regularly reflect on workload, capacity, and energy.
Process & Governance Planning includes rest, reflection, and realistic forecasts.
Technology & Tools Workload and wellbeing are visible and considered during planning.
Measurement & Metrics Velocity, WIP, cycle time, and wellbeing indicators are tracked.

Level 4 – Quantitatively Managed

Category Description
People & Culture Teams use data to proactively manage effort and focus.
Process & Governance Sustainable delivery is embedded into governance, rhythms, and planning.
Technology & Tools Dashboards integrate performance and wellbeing data.
Measurement & Metrics Trends in burnout risk and delivery health are used in decision-making.

Level 5 – Optimising

Category Description
People & Culture Teams calibrate their pace continuously to maintain long-term performance.
Process & Governance Organisational learning informs investment in team sustainability.
Technology & Tools Predictive indicators highlight risk to team wellbeing and delivery health.
Measurement & Metrics Pace, satisfaction, and outcomes are harmonised and continually improved.

Key Measures

  • Team engagement and satisfaction scores
  • Cycle time, WIP, and flow efficiency metrics
  • Burnout indicators (e.g. attrition risk, stress signals)
  • Variability in team delivery pace over time
  • Balance of planned vs. unplanned work
Associated Policies
  • Balance Sustainability with Speed
Associated Practices
  • SLOs, SLIs, and SLAs
  • Trunk-Based Development
  • Value Stream Mapping
  • Strategy & Outcome Mapping
  • Error Budget Policies
  • Feature Toggles (Flags)
  • Release Orchestration Tools

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

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