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

What are you looking for?

Standard : Technical reflection is a regular team ritual

Purpose and Strategic Importance

This standard ensures teams regularly reflect on their technical decisions, patterns, and practices – creating space for deliberate improvement and shared learning. It deepens expertise and strengthens engineering culture.

Aligned to our "Foster Craftsmanship & Mastery" policy, this standard promotes continuous growth and thoughtful delivery. Without it, teams risk stagnation, repeated mistakes, and missed opportunities to raise the bar.

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

Category Description
People & Culture Technical reflection is informal or absent.
Improvements rely on individual initiative.
Process & Governance No process exists for scheduled or structured reflection.
Technology & Tools No tooling or templates support reflective practices.
Measurement & Metrics Learnings are rarely captured, shared, or acted upon.

Level 2 – Managed

Category Description
People & Culture Some engineers initiate reflection sporadically.
Engagement varies by team or context.
Process & Governance Sessions are occasionally scheduled but lack consistency.
Technology & Tools Teams may capture notes informally but without standardisation.
Measurement & Metrics Reflections exist but outcomes are not measured or reused.

Level 3 – Defined

Category Description
People & Culture Teams value technical reflection as part of their practice.
Sessions are supported and expected.
Process & Governance Reflection is built into ceremonies or engineering cycles with defined outcomes.
Technology & Tools Templates or collaboration tools standardise reflective practice.
Measurement & Metrics Reflections generate documented actions that are reviewed periodically.

Level 4 – Quantitatively Managed

Category Description
People & Culture Teams use reflections to identify patterns and continuous improvement areas.
Process & Governance Themes across teams are analysed and used to inform engineering priorities.
Technology & Tools Tooling supports trend analysis and historical insight tracking.
Measurement & Metrics Outcomes are measured against technical quality, speed, or decision effectiveness.

Level 5 – Optimising

Category Description
People & Culture Reflection is part of the team's identity and drives proactive learning.
Process & Governance Learnings from reflection inform policy, architecture, and investment.
Technology & Tools Integrated platforms support shared learning and improvement metrics.
Measurement & Metrics Reflection effectiveness is reviewed, improved, and used in strategic planning.

Key Measures

  • % of teams with regular technical reflection sessions
  • Number of systemic improvements traced to reflection outcomes
  • Reduction in repeated incidents or architectural regressions
  • Improvement in engineering KPIs linked to shared learning
Associated Policies
  • Foster Craftsmanship & Mastery
Associated Practices
  • Non-functional Requirement Testing
  • Software Composition Analysis (SCA)
  • Auto-scaling Infrastructure

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

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