Making Work Work
A practical philosophy for removing friction between people, process, technology, and the work itself.
Friction is instrumentation
What people actually say is that the approval takes forever, the report is never right, or the tool creates more work. Hardly anyone blames the operating model, yet each of those complaints points to a seam, a place where the design and the work have quietly stopped agreeing.
Read that way, the mood in the building turns out to be the operation reporting on itself in the only language it has, the way a knock in an engine is the car telling you something. The shift changes who gets believed. If friction is a matter of temperament, the person raising it is a data point about themselves, and the response is to manage them. If friction is output, the same person is a sensor who happens to be standing where the problem is.
Complaints are still a clumsy instrument, because their volume tracks how noticeable a problem is, and noticeable and costly are different things. A slow login draws more grumbling in a week than a broken handoff that costs four days on every request. What people build is the better signal. Nobody keeps a workaround going for fun, so every workaround is a considered judgment about the system, made by the person best placed to make it and expressed in what they do.
Remove the seam, not the symptom
The work is to find the seam where responsibility, information, or timing breaks, and redesign it. Reporting more accurately on the loss it produces leaves the seam exactly where it was.
The kind of friction tells you which seam gave out, and each kind routes to a different fix. Waiting points at ownership. When people re-enter the same information, look at the boundaries, where two systems that should be connected aren’t and a person has quietly become the connection. Private records usually mean trust has worn thin, repeated questions mean visibility has, and rework traces back to sequence, where the work started before the information needed to do it correctly had arrived.
Lump those five together as general frustration and the organization usually ends up delivering training, which is what gets done when nobody has identified the failure. A better dashboard won’t settle an ownership problem, and a clearer process document won’t fix a visibility one.
Not all friction is a defect
Some friction is doing a job. A verification step that catches errors is producing something, and so is a pause before an irreversible action, the same pause a carpenter takes to measure twice. A regulatory check that has to happen produces something too, whatever it costs.
Treat friction removal as a general goal and an organization will delete its own controls, then discover later what they were for. A better test is whether the effort produces a result the organization would pay for if it were priced separately. Checking produces assurance, while waiting for someone to notice produces nothing at all, and the two feel identical to the person living through them, which is exactly why that person isn’t well placed to tell them apart.
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 usual move there is to pick it up and set it down earlier in the flow, which tends to beat arguing about whether it’s needed.
Important work should not fight its systems
The measure of a good operational system is simple: the people doing the important work get to spend their attention on the work, and very little of it making up for the system around it.
Making up for it is real labor, and it’s almost never counted, because a tax paid in money has a line item and a tax paid in effort has a person. The conscientious carry most of it, becoming the informal owners of every seam they can’t stand watching stall, and the load grows with the number of connections between people more than with headcount. Put those together and you have the ordinary mechanism behind an organization that feels slower at four hundred people than it did at eighty, even while everyone’s working harder.
A practical philosophy for removing friction between people, process, technology, and the work itself.
If this describes an operation you’re responsible for, the diagnostic is where that conversation starts.
How engagements begin
