What we've learned from making software for organizations that already have a job.
Every client we take on has a job that exists whether or not we show up. The transit workers run buses. The lodge meets. The photographer books shoots. Software is infrastructure — it either gets out of the way or it doesn't.
What this means in practice: the best interfaces we've shipped are ones the users don't think about. Not "beautiful" in any portfolio sense. Functional in the sense that the job gets done faster, with less friction, with less explanation.
We've learned to start with the existing workflow, not the desired one. Too many studios arrive with an opinion about how the work should be organized. We prefer to watch first. The software that comes out of watching is different from the software that comes out of assumption.
This is what we mean when we say we build from inside the industries we know. Not that we know better. That we've watched long enough to know what to leave alone.