10 Questions Every Leader Should Be Able to Answer
Most leaders have a good instinctive sense of how their business is doing commercially — revenue, growth, customer numbers, cash in the bank. Far fewer have an equally clear picture of the technical foundation underneath it. That’s not a criticism; it’s simply not what leaders are trained or expected to track day to day.
But a handful of straightforward questions can tell you, fairly quickly, whether your systems are in good shape or quietly accumulating risk. None of these require a technical background to answer — if anything, the questions you can’t answer confidently are the most useful signal of all. Here are the ten worth asking yourself.
1. If your most technical person left tomorrow, would the business keep running?
Every business has some concentration of knowledge in one or two people. The question isn’t whether that risk exists — it almost always does — but whether anyone’s aware of it and has a plan, or whether it would simply cause chaos.
2. Could a new hire understand how your systems fit together without asking three different people?
If the answer requires tribal knowledge scattered across your team rather than something written down, that’s not a hiring problem — it’s a sign your systems’ design lives in people’s heads rather than in the systems themselves.
3. Do you know where your single points of failure are?
One server, one integration, one manual process that everything else depends on — most businesses have at least one. The businesses at risk aren’t the ones with a single point of failure; they’re the ones who don’t know they have one.
4. Could you answer “how many active customers do we have?” in under a minute?
Simple operational questions should have simple, fast answers. If getting a clear number requires cross-referencing multiple systems or chasing down several people, that’s a data silo costing you more than you’d guess.
5. If you doubled in size next year, what would break first?
Not “would something break” — something always does — but do you have any idea what, specifically? Leaders who can name their likely breaking point are already ahead of the ones who’d only find out when it happens.
6. When did you last review what your tools and infrastructure actually cost you?
Costs creep quietly, especially with cloud infrastructure and AI tools priced on usage. If it’s been a while since anyone looked properly, there’s a reasonable chance you’re paying for waste you’re not aware of.
7. Is your customer and business data something you could hand over cleanly if you needed to?
Whether that’s for a new hire, a new tool, an investor, or a buyer, this is a good proxy for how healthy your data actually is. If the honest answer is “it would take weeks to untangle,” that’s worth knowing now rather than discovering under pressure.
8. How many of your current tools were adopted under time pressure, without much evaluation?
Not a criticism — every growing business does this. But knowing roughly how many of your systems were quick fixes rather than deliberate choices gives you a sense of how much hidden technical debt you’re likely carrying.
9. Do you know what it would cost, in time and money, to switch away from your most important vendor or platform?
You don’t need to actually switch. But not knowing the answer means you don’t know your own negotiating position, and you won’t know if that cost has quietly grown to an uncomfortable size.
10. Is there a plan for your technology, or is it being decided reactively, tool by tool?
This is the question that ties the others together. Businesses with a plan make each new tool or system decision in the context of where they’re heading. Businesses without one make each decision in isolation — and end up with the accumulated result of nine separate “good enough for now” calls.
What your answers tell you
If you answered most of these confidently, that’s a genuinely good sign — you likely have a clearer picture of your technical foundation than most businesses your size. If several answers were a shrug, or “I’m honestly not sure,” that’s not a crisis. It’s simply information nobody had gathered and organised yet, which is exactly what a proper architectural review does.
The value of this exercise isn’t the score. It’s that leaders who can answer these questions make faster, better decisions — about hiring, about growth, about fundraising, about which fires are actually worth fighting first. The ones who can’t tend to find out the hard way, usually at the worst possible time.
Ashdown Systems helps UK startups and SMBs get clear, honest answers to exactly these questions — and a plan for what to do about the ones that came up short. If any of this sounds familiar, get in touch.