The Debt You Can't See

I've been thinking this week about the concept of 'technical debt' and how it applies beyond software development. Organisations accumulate process debt, governance debt, and skills debt in exactly the same way developers accumulate technical debt — by taking shortcuts that solve today's problem at the expense of tomorrow's flexibility. The challenge is that organisational debt is harder to see than code debt. Nobody's running a linter on your governance framework. But the symptoms are the same: things that should be simple become complicated, changes take longer than they should, and the gap between what you want to do and what you can actually do keeps growing.

This week I learnt the value of saying 'I don't know' more often. In a client workshop, I was asked a question about a regulatory requirement I wasn't confident about. Instead of bluffing, I said I'd verify and come back with a definitive answer. The client's response? Relief and respect. They'd rather work with someone honest about their knowledge boundaries than someone who guesses and gets it wrong.

Took some time this week to reorganise my home office. It sounds trivial, but the physical environment affects how you think and work. A clear desk, good lighting, and everything in its place makes a genuine difference to focus and productivity. Sometimes the most impactful improvements are the simplest ones.

Obsidian — a markdown-based note-taking app that stores everything locally. What sets it apart is the ability to link notes together, creating a personal knowledge graph. I've been using it to build a library of consulting frameworks, lessons learned, and client patterns. Over time, the connections between notes surface insights you wouldn't have made otherwise.

This week's challenge: identify one area of 'debt' in your work — a shortcut taken in the past that's now costing you time or quality. Write down what it would take to address it. You don't have to fix it this week, but naming it is the first step toward resolution.