Build systems people can actually use

Working software is only the beginning

A system can pass tests, store data correctly and still feel heavy to the people using it. Real use exposes things that a developer may not notice while building: confusing labels, too many steps, unclear feedback, fragile network assumptions and screens that make sense to the builder but not to the user.

The goal is not only to make software work. The goal is to make it understandable enough, reliable enough and useful enough that people can include it in their actual work.

Trust is part of the interface

People trust a system when it behaves predictably. They need to know whether an action succeeded, what changed, what failed and what they can do next. Good error states, clear empty states, permission boundaries and visible confirmations are not decoration. They are part of the relationship between the product and the user.

This is especially important for business systems where records, payments, inventory, customers or operations are involved. If users do not trust what the system shows them, they will create parallel manual records, and the product will slowly become background noise.

Maintenance is a product feature

A useful system must survive beyond the first demo. It needs understandable code, clear ownership, reasonable dependencies and a path for improvement. A product that cannot be maintained becomes expensive even when it started cheaply.

That is why I think about systems as living things inside organizations. They must be built with enough care that future changes, support and learning are possible.

Build with the same care

Have a product, workflow or system worth thinking through?

I like starting with the real problem, the people around it and the constraints that shape the work.

Start a conversation More insights