Building Internal Tools That People Actually Use

Dev portals and admin interfaces don’t have to be awful.

Internal tools rarely win design awards, largely because nobody remembers to enter them. They still deserve thoughtful interfaces, because saving a colleague five frustrating minutes every day is a far better outcome than adding another impressive dashboard nobody opens.

Internal users deserve the same curiosity as paying customers. They may tolerate a rough edge because they have to, but that tolerance should not be mistaken for evidence that the tool works well.

What makes this interesting is not the fashionable part. It is the effect on the person doing the work after the initial excitement has worn off.

Engineering choices are rarely permanent, but they can make the next choice dramatically easier or harder. The useful question is not whether an approach is perfect. It is whether it leaves the team in a good position when reality changes.

That is not a dramatic conclusion, but useful work is often built from undramatic conclusions applied consistently.