This is a collection of observations on systems and human behavior—the patterns, interactions, and frictions that emerge when design meets use.
Software gets built with assumptions about how it will be used. Then people show up. They adapt. They find workarounds. They develop expertise the documentation never mentions. They learn which buttons to click twice and which delays to expect. They route around the system when the system doesn’t route around them.
This adaptation isn’t failure. It’s intelligence.

These essays document what happens in that space. How eight-hour users develop operational knowledge that isn’t written down anywhere. How confirmation dialogs become meaningless through repetition. How systems degrade invisibly because they’re too entrenched to replace. How the same interface succeeds for one user and fails for another depending on context. How workarounds reveal what the design missed.
The focus is on enterprise software, but the patterns appear anywhere systems constrain human work. The goal isn’t to complain about bad design. It’s to observe how people and systems actually interact—and what those interactions reveal about both.
Every system has two versions: the one that was designed and the one that gets used. This blog documents the gap.