Skip to content
Go Flow
← All concepts

Organizing fitness

Technical, functional and organizational debt

Also known as: Debt, Legislative debt, (Technical) debt

Three stacking forms of debt that leave legacy organizations paralysed.

From Onder druk wordt alles vloeibaar: the book deliberately uses the Dutch word schuld (debt) rather than "technical debt", for three forms that hold each other in a "deadly embrace":

  • Technical debt, the information systems are outdated and no longer meet modern architecture and technology standards.
  • Functional debt, demand for new functionality grows faster than the supply side, limited by technical debt, can deliver; a special form is legislative debt, when new laws cannot be implemented in time.
  • Organizational debt, a rigid way of working built on outdated processes, for example when a framework like SAFe is implemented "in name only" and old roles and entitlements stay intact.

Together they form a catch-22: old entitlements keep existing, so escaping requires a disruptive cut. The book recommends decoupling new solutions from the existing debt as much as possible, with Team Topologies as a guiding framework, exactly the logic behind de-cauliflowering.

Discussions about this

Have a question about this topic, or an experience to share? Start a discussion; it stays linked to this page.

Start a discussion

Comments on this concept

No comments yet

Be the first to comment.

Want to comment? Log in or join for free.