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

What are you looking for?

Policy : Visualise the Work

Commitment to Transparency and Shared Understanding
We believe that making work visible is a core enabler of collaboration, accountability, and improvement. When teams can see what is happening—across backlogs, pipelines, and production—they can make better decisions, manage flow more effectively, and respond to change with clarity and confidence.

What This Means
We ensure that work, risks, and system health are visible to all those involved in delivery. This is not just about tools or dashboards—it’s about creating shared context so that teams can work with purpose and alignment. Visualisation helps us detect issues early, reduce ambiguity, and promote healthy flow across the value stream.

Our commitment to work visualisation is built on:

  • Delivery Boards and Story Maps – Teams use boards, backlogs, or story maps to make work-in-progress (WIP) visible and limit overload. This includes clear status signals, ownership, and flow stages.
  • Groomed Backlogs with Definitions – Backlogs are regularly refined, prioritised, and aligned with definitions of ready and done—ensuring work is understood before it starts and finished when it meets shared criteria.
  • Transparency of Blockers and Risks – Technical debt, delivery risks, and impediments are surfaced early and tracked openly. We do not hide problems—we make them visible so they can be addressed collaboratively.
  • Production Observability – Live dashboards show real-time states of services, infrastructure, and customer journeys. Monitoring and alerting are visible, actionable, and accessible to all relevant teams.
  • Self-Service Insight for Engineers – Engineers can independently explore the state of pipelines, services, and systems without relying on gatekeepers or ad hoc requests. Visibility is a default, not a privilege.

Why This Matters
Invisible work creates misalignment, delays, and missed opportunities for collaboration. Without visibility, teams lose situational awareness, leaders make assumptions, and issues are often discovered too late. Visualising the work brings clarity, builds trust, and supports continuous delivery by ensuring everyone knows what’s happening, why it matters, and where help is needed.

Our Expectation
All teams must adopt visual management practices that expose the state of work, risks, and system health. This includes maintaining visual boards, monitoring dashboards, and promoting open communication about progress and problems.

To support this policy, teams will be guided by visualisation standards, observability tooling, and coaching on delivery flow and transparency. By visualising the work, we enable smarter decisions, faster feedback, and healthier delivery ecosystems.

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