In this LeanPub podcast episode, host Len Epp and I have a deep conversation about my book “The Cybernetic Enterprise: How to Build a Future-Ready Organization.” We cover everything from my career journey at Zühlke, to why the future is cybernetic rather than just AI, to the practical steps of enterprise transformation. If you have ever wondered what it takes to build an organization that can continuously adapt, this conversation covers the essential ideas.
From Civil Engineering to Software Engineering#
My path into technology started in Basel, Switzerland, where I grew up. I did an apprenticeship in civil engineering, and during that time in 1994, computers and the internet arrived. I was always drawn to them, drawing my plans on the computer even though the final exam required hand drawings. After that apprenticeship, I went to university to study technical information science, visited Zühlke during a company tour, and joined right after graduation as a junior .NET engineer. Over 23 years at Zühlke, I progressed from junior to expert software engineer, lead architect, principal consultant, and now global chief of cybernetic transformation.
One thing that was always close to my heart: how can we continuously deliver value, automate things, and ensure quality? That question led me through DevOps, platform engineering, and ultimately to the concept of the Cybernetic Enterprise.
The Missing Piece: System Thinking#
As a consultant working with different clients, I kept seeing the same pattern. Companies would ask me to improve their development process. The developers got faster, but then testing became a bottleneck. We fixed testing, and operations became the bottleneck. The business side had problems bringing requirements in efficiently.
The fundamental thing that is usually missing is that we focus too much on one part and don’t understand the root cause. We don’t have an overview of the whole system.
This is why I wrote “The Cybernetic Enterprise.” Organizations need to zoom out and look at the entire system: technology, processes, and organization together. You cannot fix technology without adapting processes, and you will not get the real benefits unless you also adapt the organization.
Why the Future Is Cybernetic, Not AI#
When I dove into the AI topic, I soon realized that AI is a powerful tool, one I use every day, but it is still just a tool. Then I discovered the concept of cybernetics, which dates back to the 1940s. Cybernetics means that humans and technology (including AI) work together in closed feedback loops.
This is exactly what I always say: AI will not replace us. We need to build organizations where AI and humans work together. The moon landing was a cybernetic system, a profoundly impressive one, where humans and technology collaborated to achieve something extraordinary. An enterprise is the same: a cybernetic system where technology and humans operate in closed feedback loops.
The problem in most enterprises is that these feedback loops are too slow. Budgeting happens once a year. Companies need to adapt much faster in a world where markets shift, tariffs appear overnight, and technology evolves at breakneck speed. The Cybernetic Enterprise shortens these feedback loops so the organization can continuously adapt and improve.
Adaptive Systems and the Power of Focus#
When I talk about adaptive systems, I mean bringing the agility of a startup into larger organizations. Today, most companies have their organizational structure set in stone. In a Cybernetic Enterprise, you decouple organizational units, give them more trust and responsibility, and make them responsive to market demands. Think of smaller units operating like startups within the larger enterprise.
You need to architect your organization as you architect your technology landscape or your software.
Focus is critical and often underestimated. Focus means saying no. When you design the Cybernetic Enterprise, you need to create units that have a clear focus and clear responsibility. Without that, you end up with the organizational equivalent of a big ball of mud.
Engineering Practices Matter More Than Ever#
With AI, many managers believe they will not need developers anymore. I have seen this before. When Java arrived, managers said the same thing. The opposite happened: because you could build more complex applications, you needed more developers.
The same goes for AI. When I vibe-code for more than two hours, everything falls apart. What you need to get it right is engineering practices: creating tests, engineering the system, defining context, designing architecture. Programming was never the bottleneck in a developer’s day. It is perhaps 30% of the time. The rest is thinking through problems, understanding context, and ensuring quality. AI helps with all of that, but it does not replace the need for engineering.
AI will not completely replace developers. Developers are needed to give context, to engineer, to see the bigger picture.
The Cybernetic Transformation: Start Small#
Where does transformation begin? With real need. Either the management is standing on a burning platform, or you have a group of people who genuinely want change. Without that buy-in, stop. The change will never happen.
Once you have buy-in, start with a pilot team. I am not a fan of massive transformations that try to change everything at once, because the danger of creating a mess and destroying things that work is too high. Instead, probe the system with a smaller team, create a protective bubble around them (this is where management support is essential), give them full responsibility and tools, and move fast with short feedback loops. Learn what works and what does not. Then scale to other teams based on what you learned.
The transformation is complete not when the program ends, but when the organization has built the capabilities to continuously evolve, learn, and thrive, even without external intervention.
Governance: The Fourth Pillar#
Beyond organization, processes, and technology, governance is the fourth essential element of a Cybernetic Enterprise. You cannot fix ethical questions, data handling policies, or AI ethics with processes or technology alone. These require governance, guiding rules set at the highest levels of the organization. Usually, enterprises already have governance in place, but it needs to be adapted for the cybernetic model.
Key Takeaways#
- The future is cybernetic, not just AI: Cybernetics means humans and technology working in closed feedback loops to continuously adapt
- Zoom out: Most transformation failures happen because organizations focus on one part without understanding the whole system
- Focus is saying no: Create organizational units with clear responsibilities, just like components in software architecture
- Engineering practices matter more than ever: AI accelerates development, but does not replace the need for solid architecture, testing, and system design
- Start small, learn fast: Begin transformation with pilot teams, protect them, measure outcomes, and scale based on real learnings
- Governance is essential: Ethical guidelines, data policies, and AI ethics cannot be solved by technology or processes alone