When a grants office tells us they forgot they were using the system we built for them, that is the highest compliment our software practice receives. The tool is not a product they open; it is the shape of their workflow.
That is a specific design principle, not an accident. For most of the internal tools KP builds, the job is not to teach users a new way of working. It is to remove the friction from the way they already work — and then quietly absorb the parts that used to happen in email, spreadsheets, and sticky notes.
Software that gets out of the way is harder to build than software that demands attention. It means listening carefully to the existing work before you design, making fewer features, and resisting the temptation to show off the technology. It is also what actually gets used.
