At many nonprofits and small firms, IT strategy is owned by whoever happened to be standing nearest when the first computer needed setting up. Over the years, that person became the office’s unofficial technology lead, usually while doing a different job full time. Nobody decided this. It simply happened, and it kept working until the organization grew, a funder asked about data protection, or the person who held everything in their head took a new job.
A growing number of organizations are now asking the question directly: who should own technology decisions, and what should that ownership actually mean? The answers are changing how they assign responsibility and how they use outside help.
How IT Strategy Ends Up Owned by Default
Ownership by default usually takes one of a few forms:
- The accidental expert. A staff member who is good with computers becomes the go-to person for everything from printer problems to software purchases.
- The part-time contractor. An outside technician is called when things break, and strategy is whatever they happen to suggest during a visit.
- The hands-on founder. The executive director or managing partner approves purchases based on personal preference or the last vendor who called.
- The assumed owner. The board or partners assume staff has it covered, while staff assumes leadership is deciding.
Each arrangement works for a while. The cost appears in familiar ways: purchases with no connection to priorities, risk that nobody has ever weighed, and knowledge concentrated in one person.
Strategy and Execution Are Different Jobs
Much of the confusion comes from treating two different jobs as one. Execution is running the systems: answering requests, applying updates, fixing problems. Strategy is deciding what the technology should accomplish, how much risk the organization will accept, and where limited money should go.
When the same person does both, execution wins every time, because urgent problems arrive daily while strategic decisions can always wait another week. The result is an environment that runs, but is steered by nobody. Separating the two roles, even informally, gives strategy a chance to happen at all.
Who Decides What
Clear ownership does not require technical skill. It requires deciding who is accountable for each type of decision and who advises them.
| Decision | Best Owned By | Best Advised By |
| Technology priorities for the year | Executive director, managing partner, or leadership team | IT lead or outside provider |
| Budget and how much risk to accept | Leadership, with board or partner oversight | IT lead or outside provider |
| Choice of major vendors and contracts | Leadership or a designated manager | IT lead or outside provider |
| Security standards and data-handling rules | Leadership, with input from legal or compliance | IT lead or outside provider |
| Daily operations and support | IT lead or outside provider | End users, who report problems |
The pattern is consistent: leadership owns the decisions that involve money, risk, and priorities, and technical people advise and carry them out. An organization that reverses this ends up with technical staff making business decisions without the authority or context to do it well.
Why Nonprofits Feel This Sharply
Nonprofits face several pressures that make unclear ownership costly:
- Sensitive records. Donor, client, and beneficiary information carries real obligations, and some of it, such as case notes or health details, is highly sensitive.
- Funder and board expectations. Grantmakers and boards increasingly ask how data is protected, and a board has fiduciary responsibility for risks the organization faces, including cyber risk.
- Restricted funding. Money is often tied to specific programs, so technology spending has to be planned and justified rather than absorbed.
- Turnover. Staff changes and volunteer rotation mean that knowledge held by one person can disappear overnight.
Mission pressure compounds the problem. When every dollar is meant for programs, technology tends to be postponed until it fails, which is exactly when decisions are hardest to make well.
Why Small Firms Feel It Too
Small professional and service firms face a different mix. Clients send security questionnaires before signing contracts. Cyber insurance applications require specific answers that someone has to be able to stand behind. A few key people hold access and knowledge, so one departure or absence creates real exposure. And growth changes the technology needs faster than informal ownership can keep up with.
The Role of an Outside Partner
Many organizations fill the gap by working with managed IT services in Oakville or a comparable outside provider that can serve as the technical advisor, while leadership retains ownership of priorities and risk decisions. The arrangement works when the provider reports to the person who owns technology decisions, brings a recurring review rather than only responding to problems, and documents the environment so that knowledge belongs to the organization, not to an individual.
There are several ways to structure it. Some organizations use an outside provider purely for advice and planning, some pair one with an internal staff member in a co-managed arrangement, and others hand over day-to-day management while keeping decisions in-house. In each case, handing over the work does not mean handing over accountability.
Signs Strategy Has No Owner
- There is no written list of technology priorities, even a short one.
- Spending decisions happen when a renewal or a failure forces them.
- Nobody can say what the organization’s biggest technology risk is.
- One person holds the passwords and most of the knowledge.
- Leadership or the board has never seen a report about the state of technology.
A Simple Way to Assign Ownership
A change of this kind does not need a large project. A workable sequence looks like this:
- Name an owner for technology decisions. This should be an executive or senior manager, not necessarily the most technical person.
- Write a one-page list. Include the top priorities, the top risks, and who is responsible for each.
- Schedule a recurring review. A quarterly conversation with whoever provides technical advice keeps the list current.
- Document the essentials. Access, vendors, contracts, and key configurations should be recorded where the organization can find them.
- Report upward. Leadership or the board should see a short technology summary at least twice a year.
Ownership Is Accountability, Not Labor
The shift these organizations are making is not about hiring more technical staff. It is about being clear who is answerable for technology decisions, and giving that person the information and advice needed to make them well. Whether the technical work is done by one employee, a team, or an outside provider, the questions that matter stay the same: what are we trying to achieve, what risks are we willing to carry, and who is responsible for deciding? Organizations that can answer those questions tend to find that the rest of technology management becomes easier to organize.
