Making Work Work
A practical philosophy for removing friction between people, process, technology, and the work itself.
Friction is instrumentation
People rarely say the operating model is wrong. They say the approval takes forever, the report is never right, or the tool creates more work. Each complaint points to a seam where the design and the work disagree.
Read that way, friction stops being a mood in the building and becomes the operation reporting on itself in the only language it has. The reframe changes who is credible. If friction is temperament, the person raising it is a data point about themselves and the response is to manage the person. If friction is output, the person raising it is a sensor that happens to be standing where the problem is.
Complaints are still a weak instrument, because complaint volume measures salience rather than cost. A slow login generates more grievance per week than a broken handoff costing four days per request. What people build is the better signal. Nobody maintains a workaround for fun, so every workaround is a considered judgment about the system, expressed as behavior over time by the person best positioned to make it.
Remove the seam, not the symptom
The work is to locate the seam where responsibility, information, or timing breaks, and redesign that, rather than reporting more accurately on the loss it produces.
The kind of friction tells you which seam gave out, and they route to different fixes. Waiting points at ownership. Re-entry points at boundaries, where two systems that should be connected are not and a person has become the connection. Private records point at trust. Repeated questions point at visibility. Rework points at sequence, where work started before the information needed to do it correctly had arrived.
Collapsing those five into general frustration is how organizations end up delivering training, which is what gets done when the failure has not been identified. Ownership problems are not solved by better dashboards, and visibility problems are not solved by clearer process documents.
Not all friction is a defect
A verification step that catches errors is producing something. A pause before an irreversible action is producing something. A regulatory check that has to happen is producing something, whatever it costs.
Removing friction as a general goal is how organizations delete their own controls and discover later what those controls were for. The test is whether the effort produces a result the organization would pay for if it were priced separately. Checking produces assurance. Waiting for someone to notice produces nothing at all. Both feel identical to the person experiencing them, which is exactly why that person is not the right judge of which is which.
The harder cases are controls that are necessary and badly placed. A check that genuinely has to happen, happening three steps later than it could, produces assurance and rework at the same time. The available move there is usually to reposition it rather than to argue about whether it is needed.
Important work should not fight its systems
The measure of a good operational system is simple: the people doing the important work spend their attention on the work instead of compensating for the system around it.
The compensation is real labor and it is almost never counted, because a tax paid in money has a line item and a tax paid in effort has a person. It also concentrates on the conscientious, who become the informal owners of every seam they cannot stand watching stall, and it scales with the number of connections rather than with headcount. That is the ordinary mechanism behind an organization that feels slower at four hundred people than it did at eighty while everyone is working harder.
A practical philosophy for removing friction between people, process, technology, and the work itself.
If this describes an operation you are responsible for, the diagnostic is where that conversation starts.
How engagements begin
