I Didn't Set Out to Build Software. I Set Out to Remove Friction.

I didn't set out to build software. I set out to remove friction.

The first systems I saw break down weren't digital. They were operational. Care organisations running on memory and spreadsheets. Schools coordinating people across paper. The problem was never that people didn't care · it was that the system around them demanded effort the work itself didn't need.

Friction is the distance between what should happen and what actually happens. It hides in the gap between a decision and the action that follows it. Multiply that gap across an organisation and you get exhaustion: people working hard just to move information from one place to another.

Software, at its best, is not a product. It is a mechanism for collapsing that distance. It takes a load off people so they can spend their energy where it matters · on care, on teaching, on the actual work.

The instinct predates the medium. Engineering taught me to look for the load path · to find where force is concentrated and where it dissipates. Software is the same exercise, translated. The forces are decisions. The structure is the system. The failure is friction.

When I build now, I ask one question before anything else: what is this system forcing people to do that the work itself does not require? That question is where the design begins.

The medium changes. The instinct remains.