You are still responsible, but not for the technical detail
Many owners feel out of their depth with IT and hand it all over, either to a provider or a staff member, without asking much. That's understandable, but it leaves the owner exposed. If a scam email leads to a payment to the wrong account, or a ransomware attack shuts the business for a week, the consequences land on the business and its owner regardless of who set up the systems. The good news is that oversight doesn't require technical skill. You manage your accountant without knowing tax law in detail, and your lawyer without reading case law. IT works the same way: you set expectations, ask sensible questions, look for clear answers and act when something doesn't add up.
Five questions worth asking every quarter
Who has access to our systems, and who has admin rights? You should hear a short list of named people and providers, with nobody who has left still on it. Are our backups working, and when did we last test restoring something? You want a specific recent date, not 'they're fine'. Are our computers and systems kept up to date and protected? Ask whether any are too old to receive updates.
What did IT cost us this quarter and what's coming up? You should see licences, support, hardware and planned projects, with nothing unexpected. And if something went badly wrong tomorrow, what would we do and who would we call? There should be a clear answer and a written plan. If any of these questions produces jargon, vagueness or a promise to get back to you that never arrives, that's your signal to dig deeper.
Understand just enough
A few concepts are worth grasping in outline. Multi-factor authentication means a password alone isn't enough to sign in; a code or approval on a phone is needed too. It stops most account takeovers. Backups should exist in more than one place, including a copy that ransomware on your network can't reach. Updates fix security holes; old systems that no longer get updates are a real risk.
Beyond that, you need to know where your important data lives: email, files, accounting system, customer records. And you need to know who controls your domain name, because that is what your email and website depend on. With those basics you can follow most conversations with an IT provider and recognise when an answer doesn't make sense.
Choosing and managing help
When you choose an IT provider or contractor, look for someone who explains things in plain language without making you feel foolish for asking. Ask how they would describe your current setup in a page, what they'd fix first and why, and what they'd charge. A good provider will be clear about what's included in any monthly fee and what costs extra, and will put project quotes in writing before starting.
Once they're working for you, ask for a short regular report and a meeting at least quarterly. Office IT, for example, gives managed clients a monthly summary and a quarterly review written for owners rather than technicians. Whoever you use, the report should tell you what was done, what risks remain and what decisions they need from you.
Warning signs to watch for
Some signs suggest your IT needs attention even if you can't see the technical detail. Staff regularly complain about slow computers or lost files. You don't know who has the admin passwords. Your provider can't tell you when backups were last tested. Invoices for IT vary wildly month to month with no clear explanation. Nothing is written down, so everything depends on one person's memory.
Another warning sign is a provider who resists giving you access or documentation. Your systems, data and passwords belong to the business. A good provider is happy for you to hold admin access through a separate emergency account and to have your own copy of the documentation, because it protects you both.
Make IT a regular agenda item
Put IT on the agenda of your regular management or board meeting, even for ten minutes a quarter. Review the five questions, note any changes and record decisions. That small habit keeps IT from becoming invisible until something breaks, and it shows insurers, auditors and buyers that the business takes it seriously. Over time you'll find you understand more than you expected, simply by asking the same practical questions and listening to the answers. You don't need to become technical; you need to stay curious and in charge.
In short
- Oversight of IT doesn't need technical skill, just good questions.
- Ask quarterly about access, backups, updates, costs and incident plans.
- Know where your data lives and who controls your domain.
- Choose a provider who explains things plainly and reports regularly.
- Keep admin access and documentation in the business's hands.
