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

What are you looking for?

Standard : Feedback flows upward as well as across

Purpose and Strategic Importance

This standard ensures feedback flows not just across teams but upward into leadership, creating a culture of trust, responsiveness, and shared growth. It helps leaders stay connected to reality and act on what matters most to their teams.

Aligned to our "Psychological Safety First" policy, this standard encourages open dialogue and empowers teams to shape the environment they work in. Without it, issues stay hidden, morale declines, and improvement stalls.

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: Upward feedback is rare or discouraged. Concerns are filtered or silenced, and leadership remains disconnected from day-to-day team realities.

  • Level 2 – Managed: Some teams surface upward feedback through retrospectives or engagement surveys, but it’s inconsistently reviewed or acted upon.

  • Level 3 – Defined: Clear channels exist for feedback to flow upward. Teams are encouraged to share observations and concerns with leadership. Responses are timely and visible.

  • Level 4 – Quantitatively Managed: Upward feedback is systematically gathered, synthesised, and linked to action. Trends are tracked over time and used to inform leadership behaviours and organisational priorities.

  • Level 5 – Optimising: Feedback loops between teams and leadership are embedded in decision-making. Trust and responsiveness are actively cultivated, and leadership adapts based on regular, high-signal input from across the organisation.


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
  • Fast Feedback Loops
  • Minimise Handoffs
Associated Practices
  • GitOps
  • Integration Testing
  • Retrospective Action Loops

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

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