From "Computer Person" to Technology Strategy
Your organization has an IT person. What it doesn't have is a technology strategy. Here's what that distinction costs you — and a practical path to fix it.
Your organization has an IT person. What it doesn't have is a technology strategy. Here's what that distinction costs you — and a practical path to fix it.
In most schools and nonprofits, "IT" is handled by whoever is least afraid of computers. Maybe it's the office manager who helped with a Wi-Fi password three years ago and never stopped getting called. Maybe it's a teacher who's comfortable with Google Workspace. Maybe it's the executive director themselves, resetting passwords between board meetings.
This is not a technology strategy. It's a workaround — and it works until it doesn't.
When that person leaves, burns out, or simply can't keep up with the complexity of modern technology and cybersecurity demands, the whole organization is exposed. This brief explains the difference between having a "computer person" and having a real operating model — and gives you a practical path from one to the other.
The reliance on a single individual creates a single point of failure — for IT operations and for institutional knowledge. The informal nature of the role means nothing is documented, no standards exist, and no one knows what they don't know.
The person filling this role is often doing it on top of another full-time job — teaching, coordinating programs, or managing operations — and is silently burning out. When something breaks (and something always breaks), the response is reactive rather than strategic. Leadership has no visibility into what's actually happening until a crisis forces the conversation.
⚠ Common symptoms to recognize in your organization:
If any of these sound familiar, you're not alone — and you're not behind. But you do need a different approach.
A technology strategy is simply a documented, accountable operating model for how your organization manages its technology. It answers four questions: Who is responsible? What do we have? What are our standards? What happens when something breaks?
It doesn't require a big budget or an in-house IT team. It requires clarity and consistency. It should fit on a single slide for your board and in a single page for your staff.
A basic operating model includes five things: an asset inventory, a support model, a security baseline, written documentation, and a leadership-level governance touchpoint. That's it.
What it is not: a 40-page policy binder that lives in a shared drive no one opens. Not a vendor's sales pitch dressed up as a "roadmap." Not something that requires a full-time CTO to maintain.
Before you can fix anything, you need to know what you have. Run a simple audit: What devices exist? What accounts? What software are you paying for? Who has admin access to what? A spreadsheet is fine. But you have to actually do it.
With visibility comes the ability to prioritize. Most organizations need to do three things immediately: set up multi-factor authentication on critical accounts, verify backups are running and restorable, and document who to call when something breaks.
Technology strategy isn't a project — it's a practice. Once the basics are in place, the goal is a sustainable cadence: regular reviews, clear ownership, and a leadership-level conversation about technology at least once per quarter.
Some organizations can build this model internally if they have the capacity and the mandate. Many can't — and that's not a failure, it's a resource reality.
A managed IT partner can accelerate stages 1 and 2 significantly and provide the ongoing support for stage 3. The right partner respects your context, speaks plainly, and doesn't create dependency on unnecessary complexity. The wrong time to hire a partner is after the crisis. The right time is before.
Signs you need outside support: You don't know what you have. You've had a security incident in the past 12 months. Your "IT person" has asked for help and not received it. Leadership cannot answer basic questions about technology risk.
You don't need a perfect plan before you start. You need to stop treating technology as something that runs itself — or as the problem of whoever happens to be nearby when it breaks.
The organizations that handle technology well aren't necessarily the ones with the biggest budgets. They're the ones that have made a deliberate decision to treat it seriously: document what they have, set clear expectations, and review it regularly.
If you're not sure where your organization stands, a 30-minute conversation is usually enough to find out — and to map a path forward.
AshTechWisdom works with schools, nonprofits, and small businesses in Chicagoland to build exactly this kind of operating model — without the jargon or the vendor pitch.
Book a Strategy Call →RELATED ARTICLES