Tim O’Reilly on debugging your organisation

The skill of debugging is to figure out what you really told your program to do instead of what you thought you told your program to do.

Tim O’Reilly quoting Andrew Singer on The Product Science Podcast

Tim O’Reilly takes the idea of debugging simple code and applies it to fixing the successful-but-damaging algorithms of the large tech companies that run the world – and on to the ‘algorithms’ of government policy (e.g. tax policy) and their unintended outcomes.

No organisation is immune from the law of unintended consequences. Which parts of your organisation need debugging?

You know what you thought you built your social program to do – is it doing it? Are you running ‘code’ – policies, procedures, practices – that are inadvertently undermining key values or processes and stopping you from achieving your goals?

Due to a scheduling error this post was published late.

I'd love to hear your thoughts and recommended resources...