The system nobody dares touch
Could anyone in your organisation explain how your website is set up? Not what it does, but how it is put together, what it depends on, and what would break if one part were updated?
In many organisations the people who could have answered left when the project finished.
Signed off because it worked
AI is making old software weaknesses easier to find. Many were built in when systems were signed off because they worked. What a board should ask.
Built for one person, relied on by everyone
Spreadsheets, databases and automations that staff build for themselves can quietly become critical. Four questions a board can ask about them.
The equipment nobody tested
Boards check people and machinery before trusting them. Software that staff bring in deserves the same diligence, and the questions are familiar.
Why good boards love bad news early
Every board says it wants to hear bad news. Fewer behave in a way that makes it likely.
Bad news that arrives early is an asset. It keeps options open: there is still time to change supplier, add resource, re-plan, or tell customers before they hear it elsewhere. The same news six weeks later is a crisis, with fewer choices and a larger bill.