
IT governance for SMEs: who decides on IT, and where that is written down
IT governance sounds like something for large organisations with a CIO and a steering committee. In a smaller business the question is narrower and more urgent: who actually decides on IT, who carries the risk when it goes wrong, and is any of that written down anywhere other than in someone’s head? You can settle it with one table, three lists and one fixed meeting.
IT governance is not about what you do with IT, but about who decides it, who checks it and where it is recorded.
In many smaller businesses the IT manager or the supplier ends up deciding things that belong to the board, such as which risk to accept and which contract to renew.
A decision table, a delegation of authority, a risk register with owners and a decision log, plus one meeting a quarter, is enough to get it in place.
What IT governance is, and what it is not
IT governance is how an organisation settles who decides on IT, on what basis, and how it checks that it works. The international standard ISO/IEC 38500 sums it up in three verbs for the board: evaluate, direct and monitor. The doing itself, day-to-day management, is not part of it, and that is the part you can outsource.
The difference from an IT strategy is that a strategy says which choices you make, while governance says who may make them and who keeps watch. A strategy without governance goes stale quietly: nobody feels they own it, and the first exception becomes the new rule.
In a smaller business governance nearly always exists already, just unwritten. The managing director decides on anything that costs money, the IT person on anything that sounds technical, and the supplier on whatever is left over. That works as long as the three agree and nobody leaves.
The decisions somebody has to own
Start with the decisions, not the people. Almost every IT question falls into one of these six kinds, and each needs one fixed name against it:
- Principles and standards: which devices, which platform, how accounts and passwords work. Little meeting time, but the foundation for everything else.
- Investment and priority: which project goes first, what gets deferred, and who weighs it up when two departments want the same thing.
- Accepting risk: keeping a system running that no longer gets updates, an exemption from multi-factor authentication, a backup that is not held off site. This is the decision most often sitting with the wrong person.
- Suppliers and contracts: who chooses, who renews, who gives notice. A contract that rolls over automatically is also a decision, just not one anybody made.
- Data: who owns the customer records, the finance system and the HR files, and so decides who has access.
- Access exceptions: admin rights for a user, an external account, a shared password for a machine.
Who decides: a decision table on one screen
List those six kinds and fill in four columns for each: who decides, who advises, who carries it out and who is informed. That is a RACI table, and for a smaller business it fits on one screen. One name per box in the “decides” column, never two: two owners means no owner.
Three rules make the difference:
- Accepting risk belongs to the board, or to whoever it formally delegates to. Not to the IT manager and not to the supplier, even if they understand the risk best. Knowing a risk and carrying it are two different roles.
- A supplier advises and delivers, but does not decide on its own contract, its own scope or the risks it manages itself.
- The data owner sits in the business, with the head of the team that uses the data, not in IT. IT makes the permissions work; the owner says who gets them.
Which roles exist inside an IT team and who does what is covered in our piece on IT roles. The decision table sits one level above: who in the organisation says yes or no.
Where it lives: delegation, risk register and decision log
Governance that only exists when it is spoken in a meeting stops existing when the meeting ends. Three documents are enough, and they belong in one fixed place that does not depend on one person:
- The delegation of authority. Who may approve what without asking anyone else: a new licence, an extra device, additional work from the supplier, an exception to a standard. Set the limits by type and scale, so nobody has to ask the managing director about every purchase and nobody signs a contract that belongs to the board.
- The risk register. For each risk a short description, the control, and a named owner. A risk you consciously accept goes in too, with the date and the reason. That is how you can later show it was a decision rather than an oversight.
- The decision log. Date, decision, reason, who decided. One line per decision. It answers the question every new IT manager, new supplier and auditor asks: why is it set up like this?
An email thread is not a record. It cannot be found by anyone who was not copied in, and it disappears with the mailbox of whoever leaves.
One meeting a quarter, with a fixed agenda
Governance needs a moment when decisions actually get made. In a smaller business that is one meeting a quarter with the board or managing director, whoever is responsible for IT internally and, if you outsource support, your supplier. An hour is enough if the agenda is fixed:
- What went wrong, and whether it is a pattern: not every ticket, but the outages that stopped work.
- The risks from the register: what has changed, what needs a decision.
- Contracts and licences that expire or renew in the next six months.
- Exceptions granted in the past quarter, and whether they are still needed.
- Decisions needed now, each with a proposal attached. A meeting with no decision on the agenda turns into a report.
Your supplier’s reporting should land in this meeting, not alongside it. How to reduce it to one overview your board can read is covered under service governance.
Why the board can no longer stay out of it
For a long time IT governance in smaller businesses was a matter of tidiness. That is shifting, for three reasons that all end up on the board’s desk.
- Regulation. In the EU, the NIS2 directive explicitly makes management bodies approve cyber security measures, oversee their implementation and take training. In the UK, NIS2 does not apply as such; the NIS Regulations cover operators of essential services, and the government’s Cyber Governance Code of Practice, developed with the NCSC, is written directly for directors. If you have customers or sites in the EU, the NIS2 question may reach you through them.
- Customers and insurers. Questionnaires from larger customers and from cyber insurers increasingly ask who is responsible for information security and whether that can be shown. A decision table and a risk register are exactly that evidence.
- Certification. Anyone working towards ISO/IEC 27001 finds that the standard explicitly tests leadership and board commitment. That is governance under another name.
A framework such as COBIT, from the professional body ISACA, is useful as a reference, but for an organisation with a few hundred seats or fewer it is too large to implement. Take what you need from it; the table and the three lists above are the core.
Where our work stops
What we do. We help fill in the decision table for the technical side, carry out what is decided, maintain the risk register for the systems we manage, and supply the figures and proposals for the quarterly meeting. For any risk we say what it is and what it takes to remove it, so the board has a real choice. We are ISO 9001 and ISO/IEC 27001 certified ourselves, and that is how we work; it is not a judgement on your organisation.
What we do not do. We do not take the decisions: accepting risk, investing and entering into contracts stay with your board, even when we run your IT. We are not auditors and do not issue any opinion or certificate on your governance. And we are not lawyers: whether NIS2 or the NIS Regulations apply to you, and what that means for directors’ liability, is a question for a lawyer or the regulator.
Questions we get about this
The five that come up most often.
What is IT governance?
IT governance is how an organisation settles who decides on IT, on what basis, and how it checks that it works. It is about decision rights, accountability and oversight, not about running IT day to day. In a smaller business it comes down to a decision table, a delegation of authority, a risk register with owners and a fixed meeting.
What is the difference between IT governance and IT management?
Governance sets who decides and how oversight works; management delivers within those limits. The board belongs to governance, the IT team and the supplier to management. You can outsource management, but not governance: the decision to accept a risk stays with the organisation itself.
Does a small business need IT governance?
Yes, in a light form. Every business already has governance, usually unwritten, and that breaks down when someone leaves, after an incident or when you change supplier. A table of who decides what, three short lists and one meeting a quarter is enough for most SMEs.
Should we use COBIT or ISO/IEC 38500?
For an SME both are mainly reference material. ISO/IEC 38500 gives principles for the board, COBIT a detailed framework of processes and objectives, and implementing it in full is too heavy for a small organisation. Take what you need: clear decision rights, named risk owners and oversight that is recorded somewhere.
Can you set up or assess our IT governance?
We help with the technical side: filling in the decision table, maintaining the risk register for the systems we manage and bringing proposals to the meeting. The decisions themselves stay with your board. We do not give an independent assessment or opinion, as we are not auditors, and legal questions about NIS2 or directors’ duties are for a lawyer.
Further reading
Where this connects.
Shall we fill in the table together?
An hour is usually enough to walk through the six kinds of decision and see where a name is missing. The decisions themselves stay with you.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.