The digital tools that actually last aren't the flashiest ones — they're the ones shaped by the people who use them. A note on the difference that makes.
Every organization we've worked with has, at some point, been handed a tool that was built for them without ever being built with them. A website nobody on staff can update. A dashboard that measures the wrong things. An app that looked impressive in the pitch and went unused within a month.
None of those failed because the technology was bad. They failed because they were designed at a distance from the people who were supposed to use them.
Proximity is the whole thing
The difference between a tool that works and a tool that gets abandoned usually isn't budget or technology. It's proximity — how close the people building it stayed to the people who'd live with it.
When you build with a community, you find out early that the survey needs to be a conversation, that the map should show assets and not just gaps, that the people who'll keep the website alive need to actually be able to edit it. You catch the small things that decide whether something gets used or quietly dropped. You can't catch those from a distance, and no amount of polish makes up for missing them.
Listening is a design decision, not a courtesy
It's easy to treat consultation as a box to tick — a workshop at the start, then heads-down until launch. But the listening is the design work. What people tell you they need, in their own words, is the specification. When that gets skipped, you end up building something technically correct and practically useless.
This is especially true in work rooted in community — with First Nations and Indigenous partners, with nonprofits, with any group whose knowledge lives in the people, not in a brief. The vision is already there. The job is to build something that reflects it, not to replace it with our own.
Made to be handed over
There's a quiet test for whether something was built with people or just for them: what happens after it ships. A tool built for someone leaves them dependent — every change means coming back, cheque in hand. A tool built with them leaves them capable. They can update it, extend it, and make it theirs, because they were part of making it in the first place.
We'd rather build the second kind, even though it means designing ourselves out of a permanent role. Work that leaves a community more capable than it found them is the only kind worth doing.
The short version
Good digital work isn't measured on launch day. It's measured a year later — whether the thing is still used, still true to the people it was made for, and still theirs. That's the standard we hold our own work to, and it starts the same way every time: by getting close, and listening first.
If that's how you'd want your next project approached, we should talk.
