The four questions that reveal whether your IT is really owned.

There is a version of an IT review that makes everyone feel better and changes nothing. It checks that a provider is in place, that tickets get answered, and that the tools are licensed, and it concludes that things are fine. The trouble is that all of those can be true while no one can say who owns the outcome when something goes wrong.

So instead of a longer checklist, we use four questions. They are short, they are deliberately uncomfortable, and the way your team answers them tells you more than any audit.

First, who is responsible when this fails? Not who logs the ticket, and not who answers the phone, but who owns the outcome through to resolution. If the honest answer changes depending on what broke or who is in the office that day, responsibility has not been defined, it has been improvised. And improvisation works right up until the day it does not.

Second, what exactly is included? Most agreements describe what is covered in broad terms that feel reassuring and resist specifics. The useful test is at the edges. Is this integration included, is that legacy system included, is the handover between your provider and Microsoft included. Coverage that cannot be pinned down at the edges is where incidents tend to end up.

Third, what happens when something falls outside scope? This is the question that decides whether you have a provider or a partner. When an issue lands outside the original lines, does someone step in and own a path forward, or does everything stop while whose job it is gets debated. The businesses that stay running are the ones where that answer was settled in advance.

Fourth, would everyone give the same answer under pressure? Ask the first three questions of three different people in your business, separately, on a normal day. If the answers line up, you have clarity. If they do not, you have found the gap before an incident did, which is the entire point of asking.

None of these four questions is about technology, and that is deliberate. A capable provider can fix almost any single fault you put in front of them. What a fix on the day cannot create is a clear operating model underneath, where ownership is defined, scope is specific, the path for anything outside scope is agreed, and everyone would answer the same under pressure. When those four are in place, problems stop repeating, because each one has an owner who closes it for good rather than passing it along.

If reading these made you slightly unsure of an answer, that is not a failing, it is useful information. It is far cheaper to find an ownership gap during a calm conversation than during an outage.

We help teams in the mid market answer all four cleanly, and then hold the responsibility that keeps those answers true. See how we do it: https://www.crimsonline.co.za/our-services/