The right technology for a small organisation is the one that fits how it actually works — not the flashiest option, not the cheapest, but the one that makes the team more capable without adding friction.
Technology decisions in small organisations tend to go one of two ways. Either the organisation buys the most visible solution — the one someone heard about at a conference, or the one a large-company contact uses — and discovers that it was built for a different scale and generates more admin than it removes. Or the organisation avoids technology investment altogether, running on combinations of spreadsheets, WhatsApp groups, and paper records that were manageable at launch and have become increasingly precarious as the team grew. The technology that actually powers opportunity for a small organisation is neither the most impressive nor the most minimal. It's the technology that fits the real workflow — the one that makes people more capable at the things they're already trying to do, without requiring them to become system administrators. This post covers: - What it means to build systems around workflows rather than around features - The types of systems small organisations typically need - How to evaluate whether technology is helping or adding friction - The role of good IT support in making technology usable ## Building Around Workflows, Not Features Most technology solutions are sold on features. Features are what the system can do. Workflows are what your organisation actually does. The two aren't the same, and the gap between them is where most small-organisation technology failures happen. A compliance dashboard with many features that nobody uses because the interface doesn't match how the team works is an expensive frustration. A simpler system that the team actually uses daily — because it maps to how they think about the work — is worth considerably more. The practical implication: before evaluating any technology solution, describe the workflow it's meant to support in plain language. What does someone do, step by step? Where does information come from, where does it go, who touches it along the way? Technology that fits that description is worth evaluating. Technology that requires the workflow to change to accommodate it requires a stronger justification. > Good technology disappears into how you work. You stop noticing it because it has become part of how things get done — not a separate step. ## The Systems Small Organisations Typically Need Most small organisations with five to thirty people share a common set of operational requirements, even across different sectors. **Communication and collaboration.** Email, messaging, and document sharing. Cloud-based tools (Microsoft 365, Google Workspace, or equivalents) handle this for most small organisations at a manageable cost and with accessible support. **Data and record management.** Some form of system for managing the information the organisation holds — client or beneficiary records, programme data, operational records. For many small organisations, this starts with well-structured spreadsheets or a simple database. It scales to purpose-built tools as volume and complexity require. **Financial and compliance tracking.** Whether through a cloud accounting platform or through outsourced bookkeeping and payroll, the organisation needs to know its financial position and maintain the records that compliance requires. The two functions are related but distinct. **Programme or operational dashboards.** For organisations managing youth placements, community programmes, or multiple operational streams, a dashboard that provides current visibility across activity — who is enrolled, what the status is, what reporting is due — removes the management overhead of tracking these things manually across multiple sources. **Security and backup.** Not a product to buy but a set of practices to maintain: passwords, access controls, regular backups of data that matters, and basic protection against the most common failure modes. ## How to Evaluate Whether Technology Is Helping The simplest test: is the team using it, and does it make their work faster or more reliable? Technology that requires constant prompting, workarounds, or parallel manual systems is usually a poor fit, regardless of how well it was designed in the abstract. A few more specific signals that technology is generating friction rather than capability: the team maintains a "real" record alongside the official system because they don't trust the system; people avoid using features that were the reason for choosing the solution; setup took so long that the problem it was meant to solve had been worked around by the time it was ready; and the support model requires waiting days for a response when the issue affects the whole team's ability to work. ## The Role of Good IT Support Technology that is correctly set up, maintained, and supported costs less over its life than technology that is misconfigured and left to drift. The upfront investment in proper setup — including training the team on the actual workflow rather than just showing them the features — pays for itself in reduced support cal...