The Journal

Why communities shouldn’t have to adapt to their technology.

Tech · Sep 15, 2026 · 6 min

Technology is supposed to make life easier. It should help people access information, connect with one another, and accomplish things more efficiently. Yet, for many organizations and communities, the experience can be the opposite. People are expected to navigate complicated platforms, learn unfamiliar systems, create accounts, remember passwords, and adapt to processes that were designed around the technology rather than their needs.

Over time, these challenges become part of everyday life. Staff develop workarounds. Information becomes harder to access. People who could benefit most from digital services may find themselves excluded by the very systems intended to help them. The problem isn’t always the technology itself. It’s how that technology was designed, implemented, and introduced. Technology should adapt to the people who use it, not the other way around.

Technology should start with people.

When organizations consider a new website, digital platform, or software solution, the conversation often begins with features. What can the platform do? What tools does it include? How much does it cost? How quickly can it be implemented? These are important questions, but they shouldn’t be the starting point.

A more useful starting point is understanding the people who will use the technology.

What information do they need? How do they currently access services? What challenges do they encounter? What would make their experience easier? These questions help organizations identify the actual problem before committing to a solution. A platform may offer dozens of features, but if the people it’s intended to serve struggle to use it, its value is limited. Effective digital strategy begins with understanding people, their needs, and the environments in which they interact with technology.

One solution doesn’t fit every organization.

Off-the-shelf software and standardized platforms can offer significant advantages. They can reduce development costs, accelerate implementation, and provide access to established tools.

However, standardization has its limits. Organizations have different structures, priorities, processes, and communities. A solution that works well for one organization may create unnecessary challenges for another.

This is particularly relevant for First Nations and community-based organizations, where local priorities, governance structures, cultural considerations, and communication needs can vary considerably. A digital platform should reflect those differences. That doesn’t mean every organization needs an entirely custom-built solution. In many cases, existing technology can be configured or integrated to meet specific requirements.

The important distinction is that the technology should serve the organization’s needs, rather than forcing the organization to change how it works simply to accommodate the software.

Accessibility is more than design.

When people talk about accessible technology, the conversation often focuses on visual design, readable text, and compatibility with assistive technologies. These are essential considerations, but accessibility extends beyond the interface. It also includes how easily people can find information, understand instructions, complete tasks, and receive support when something goes wrong. A website may look modern but still be difficult to navigate. A member portal may contain valuable information but be of little use if members don’t understand how to access it.

Digital inclusion requires organizations to consider the entire experience. That means accounting for different levels of digital literacy, device preferences, connectivity, language, and individual needs. The goal isn’t simply to make technology available. It’s to make it genuinely useful.

Community input should shape the solution.

One of the most effective ways to create better digital experiences is to involve the people who will use them. Consultation shouldn’t happen only after a platform has been selected or a website has been designed. Community members, employees, leadership, and other stakeholders can offer valuable perspectives before development begins. They understand the questions people ask, the information they need, and the barriers that may not be obvious to an outside developer.

Involving these voices early can help organizations avoid costly assumptions and build solutions that reflect real-world requirements. It also creates a stronger foundation for adoption. People are more likely to understand and use technology when they can see how it responds to their needs.

Better technology starts with better questions.

As digital platforms, artificial intelligence, and online services continue to evolve, organizations will have more options than ever. But more choice doesn’t automatically lead to better outcomes. Before investing in a new digital solution, organizations should ask a few fundamental questions: Does this solve a real problem? Who will use it, and what do they need? Does it work with our existing systems and processes? Will it make information and services easier to access? Have the people affected by this technology had a meaningful voice in its design?

These questions can help distinguish technology that creates genuine value from technology that simply adds another layer of complexity. Ultimately, successful digital transformation isn’t measured by the number of platforms an organization adopts or the features it implements.

It’s measured by whether those investments make a meaningful difference.

The best technology doesn’t ask people to change who they are or how their community works. It meets them where they are, responds to their needs, and makes the things that matter easier to accomplish. That is what technology should be designed to do.