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

What are you looking for?

Policy : Create Space for Reflection

Commitment to Deliberate Reflection In high-velocity environments, urgency crowds out reflection. When every moment is spent in execution mode, teams lose the ability to learn from their work, notice what is not working, and improve. Leaders have a responsibility to protect time for reflection — for themselves and for the people they lead — as an investment in sustainable high performance.

What This Means Reflection is not a luxury. It is the mechanism by which experience becomes learning, and learning becomes improvement. Without it, teams repeat the same mistakes, accumulate invisible frustration, and drift from their best work. Leaders model this by reflecting deliberately themselves and by creating the conditions for teams to do the same.

Our commitment to creating space for reflection is built on:

  • Protecting Retrospective Rhythms – Retrospectives are not cancelled under pressure. They are most valuable precisely when pressure is high, because that is when the most learning is available.
  • Leader-Led Reflection – Leaders openly share what they are learning, what they got wrong, and what they are changing. This models the behaviour they want to see.
  • Unstructured Thinking Time – We protect capacity for thinking, not just doing. Calendars full of meetings leave no space for synthesis or creative problem solving.
  • After-Action Reviews – After significant events — launches, incidents, reorganisations — we set aside time to understand what happened and why, without blame.
  • Questions Over Answers – Reflective leaders ask more than they tell. They surface assumptions, invite other perspectives, and sit with complexity before moving to solutions.

Why This Matters Teams that never reflect are teams that never improve. Individual leaders who never reflect lose perspective, repeat patterns, and accumulate blind spots. Reflection is the engine of the learning culture that DORA research identifies as a key predictor of engineering performance.

Our Expectation Leaders must protect time for reflection in team rhythms and in their own schedules. Cancelling retrospectives or skipping review meetings to "catch up on delivery" is treated as a sign that the system needs attention, not as an acceptable trade-off.

Associated Standards

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

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