Governance is a critical aspect of any organisation, ensuring that we operate safely and effectively. However, I’ve observed that excessive governance can often hinder our ability to seize opportunities and respond to unexpected challenges. When surprises arise, be it a market shift, a product issue, or an internal complication, the time and cost to rectify these problems can escalate dramatically.
The Pitfalls of Over-Governance
From my experience, I’ve seen that much of the governance we encounter is self-imposed. This is particularly true in organisations that operate in silos or have a dedicated governance department. Here’s the crux of the issue: when governance becomes a separate entity, it often leads to local optimisation rather than system optimisation.
- Local Optimisation: This occurs when we focus on improving one aspect of the organisation without considering the broader implications. For instance, imagine a cog in a machine that’s struggling to turn because it’s jammed against other cogs. If we decide to remove the teeth from this cog to make it spin freely, we’ve achieved a local optimisation. However, this cog is now ineffective in driving the entire system.
This scenario is all too common when governance is treated as an isolated function. Decisions made in an ivory tower can lead to regulations that, while well-intentioned, fail to add value to the organisation as a whole.
Compliance vs. Overzealous Governance
Take the example of compliance regulations, such as the Sarbanes-Oxley Act (SOX). The intent behind SOX is to ensure transparency and accountability, but many organisations misinterpret this as a need to exceed the minimum requirements.
- Minimum Compliance: The SOX audit requires organisations to trace actions within their systems, but it doesn’t mandate that this process be user-friendly. A simple log file suffices. Yet, I’ve seen organisations burdened with excessive documentation and processes, all in the name of compliance.
In one instance, I worked with a US-based organisation that had a stringent compliance framework. Every meeting required notes to be sent to compliance for review. During a discussion about transitioning to Team Foundation Server, compliance personnel insisted on maintaining change request logs.
I invited them to observe how Azure DevOps functions, which maintains a complete history of every work item. When I asked if this was sufficient for compliance, they confirmed it was. We eliminated the need for change request work items entirely, streamlining the process and reducing unnecessary overhead.
Lean Governance: A Path Forward
This experience highlights the importance of lean governance. We must regularly assess our processes to identify and eliminate waste. Here are some strategies I recommend:
-
Organisational Hygiene: Regularly review policies and procedures to ensure they still serve a purpose. Often, we create policies out of fear, only to find they’re no longer relevant.
-
Compliance as Code: Where possible, integrate compliance requirements directly into your product. This approach minimises the effort needed to meet regulations while ensuring that compliance is maintained.
-
Focus on Value: Always ask whether a process adds value to the overall system. If it doesn’t, it’s time to reconsider its necessity.
Conclusion
In conclusion, while governance is essential for organisational safety, it’s crucial to strike a balance. We must avoid the trap of overzealous compliance that stifles innovation and agility. By embracing lean governance principles, we can create a more efficient, responsive organisation that is well-equipped to navigate the complexities of today’s business landscape. Remember, the goal is to meet compliance with the minimum amount of work required, no more, no less.
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Avoiding the Local Optimisation Trap: How to Ensure Your Governance Drives Organisational Success
Explains how focusing on isolated improvements in governance can harm overall organisational success, and offers strategies for integrated, …
Scrum is like communism, it doesn't work. Myth 5
Explains why Scrum does not mean a lack of governance, highlighting the need for regulatory compliance and internal standards while …
Mastering Agility: Balancing Engineering Excellence and Effective Processes in a Rapidly Changing Business Landscape
Explores how to balance engineering excellence and effective Agile processes, highlighting the need for technical skills, continuous …
Empowering Teams to Tailor Their Processes: A Path to True Agility
Explains why empowering teams to adapt their processes boosts agility, reduces waste, and fosters innovation, using real-world examples and …
Mastering the Agile Balance: Navigating Flexibility and Inflexibility for Project Success
Explores how agile teams can balance flexibility and structure, manage data integrity, and adapt processes to achieve project goals and …
Sculpting the Product Backlog: A Delicate Balance Between Lean Inventory and Future Readiness
Explores how to maintain a lean, transparent product backlog that balances current needs with future readiness, enabling teams to adapt and …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
Why Measuring Individual Cycle Time Fails to Help Teams
Measuring individual cycle time overlooks team performance and system bottlenecks. Focus on lead time, throughput, and process efficiency to …
Measuring Worker Speed in Manufacturing Plant Operations
Measuring individual worker speed in manufacturing or knowledge work can create bottlenecks; true efficiency comes from improving the whole …
At the end of the day, Kanban is about improving flow
Kanban focuses on improving workflow by removing bottlenecks and constraints, reducing work in progress, and increasing process efficiency, …
Why Handoffs Are Killing Your Agility
Excessive handoffs in software development create delays, reduce quality, and harm team morale. Learn how eliminating handoffs boosts …