The digital tools that last are the ones shaped by the people who use them. Why building with communities, not just for them, changes what gets delivered.

When we wrote the proposal for Ulkatcho First Nation's website, the line we cared most about was not in the design section. It was a sentence about what would happen after we left: Nation staff would publish their own news, programs, and job postings without calling us. That sentence shaped every decision that followed, from which content system we chose to how many training sessions we budgeted.
It is easy to say a project was built with a community. Here is what it looked like in practice, and what it tends to look like when it is only built for one.
The site nobody can log into
Most of us have seen some version of this. An organization inherits a website from a previous vendor. The site looks good. Nobody on staff has the login, or the login works but the editing screen might as well be in another language. Every text change means an email, a wait, and sometimes an invoice. So when office hours change, somebody prints a sign and tapes it to the door.
That is not a technology failure. The site works fine. It is a distance failure. The people who built it were never close enough to the people who would keep it alive to notice that the person updating it would be an administrator with forty other jobs, not a developer.
Proximity changes the specification
Get close enough and the brief changes under you. A few things we have learned by sitting in the room, or at least on the call, often enough:
The person who will maintain the site has about twenty minutes a week for it. If an event cannot be posted in twenty minutes, it will not be posted. For Ulkatcho that meant a content studio at ulkatcho.ca/studio with a short list of page types and nothing extra to click past, and it meant training sessions where we worked through real updates together instead of demonstrating features.
The map should show what a community has, not only what it lacks. The survey you planned may need to become a conversation, because that is how people in that place share what they know. For the Knowledge Weavers Hub, built with the National Centre for Collaboration in Indigenous Education at First Nations University of Canada, that meant structuring a national resource library around how educators actually search for a lesson plan, in English and French, and making sure NCCIE staff could add to it themselves.
None of that is visible from a distance, and none of it is in an RFP.
Listening is a design decision
Most discovery processes are theatre. A kickoff workshop, some sticky notes, a slide of "key themes," and then the vendor disappears to build what it was always going to build. The consultation happened. It did not change anything.
What people tell you they need, in their own words, is the specification. Not raw material for one. In our work with First Nations, nonprofits, and public institutions the knowledge already lives in the people we are working with; the job is to build something that carries it faithfully, not to swap in our own ideas and call it strategy. Skipping that step produces a familiar thing: the tool that passes every test except the one where someone tries to use it on a Tuesday.
Made to be handed over
A simple way to tell the two approaches apart is to watch what happens after launch.
A tool built for an organization leaves it dependent. A tool built with one leaves it capable. The organization holds its own accounts and passwords. The content system is plain enough that a new hire can learn it in an afternoon. The guide is written for the actual staff, not a hypothetical technical person who does not work there. When Health Quality Alberta asked for Portraits of Care on WordPress so their own team could maintain it, that was the right call even though it was not the platform we would have picked for ourselves.
The unglamorous training call where someone publishes their first page is worth more than a lot of polished design hours. It is the moment the thing becomes theirs.
Building this way means designing yourself out of a permanent role. We still think it is the only version of this work worth doing. A project that leaves a community more capable than it found them earns the next honest conversation.
The year-later test
Launch day tells you almost nothing. The real measure comes a year later. Is the site still being updated? Do staff reach for it without thinking, or route around it with a taped-up sign? Ulkatcho's team publishes on their own now, and that is the result we point to, not the launch.
If that is how you would want your next platform approached, see our digital platforms work or get in touch.



