Why Governance Matters: The Key to Reducing Risk Without Slowing Down

The presentation covers the significance of effective governance in reducing technical risk and maintaining speed in software development.

Key points discussed in the presentation include:

• Governance Image Problem: Governance is often viewed as bureaucratic, but when done right, it aligns teams and reduces risk without slowing the organization down.
• Principles and Practices: Governance should consist of principles, practices, and tools that enable informed and safe technical decisions.
• Traditional Governance Barriers: Sarah critiques the use of Change Advisory Boards (CABs), which are often seen as obstacles that do not improve system stability or efficiency.
• Foundations, Choices, and Guardrails:
  • Foundations: Knowing your software estate is essential for effective governance.
  • Choices: Making smart technological choices can prevent chaos and promote consistency.
  • Guardrails: Automating policies into checks helps embed governance into everyday processes.
• Automation and Self-correction: Implementing automated governance helps teams correct course easily and ensures policies are followed without reducing speed.
• Clarity and Alignment: Effective governance provides clarity on organizational goals and keeps teams aligned.
• Challenges in Governance: The presentation mentions challenges such as the bottleneck of code reviews and AI's poor security code writing but also highlights that AI can help address some existing challenges by automating mundane tasks.
• Continuous Improvement: Automating guardrails and encouraging visibility of good practices are central to continuous improvement in governance.
• Handling Older Projects: A balance is needed in applying new governance practices to existing projects without overwhelming development teams.

Overall, Sarah Wells emphasizes the value of redefining governance to enhance clarity, consistency, and alignment across teams, advocating for governance systems that accelerate rather than impede development processes .

This is the end of the AI-generated content.

When you hear “governance,” you might think of red tape, bureaucracy, or someone telling you what you can’t do. But real governance is about alignment and reducing technical risk. And that matters more than ever.

In most cases, engineers aren’t deliberately making risky decisions—they just don’t have clear expectations. That’s where good governance comes in. It ensures everyone understands what “good” looks like, gives teams the autonomy to move fast while staying on course, and provides built-in mechanisms to self-correct before small missteps become big problems.

In this talk, I’ll break down how to implement governance that actually helps, not hinders, including:

• Understanding what’s in your software estate
• Making smart technology choices - and why “boring” is often best
• Turning policies into automated steps on the way to production

If you want to reduce risk, improve decision-making, and keep your organization running smoothly—without slowing your teams down—this session is for you.