The Human Side of How Work Gets Done: Looking Beyond Processes and Outcomes

Every organization runs on process. There are policies to follow, deadlines to meet, reports to prepare, meetings to attend, approvals to secure. From a leadership standpoint, process gives structure to the work: it creates consistency, accountability, and a shared sense of what's expected. But there's another side to every process, one that's usually invisible from where leaders sit: the experience of the person actually doing it. A request that takes five seconds to send might take someone hours to fulfill. A routine approval might rest on three or four conversations nobody sees. A polished report might hide the work it took to reconcile numbers that didn't agree with each other. Every process has a human experience folded into it. Paying attention to that experience tells leaders something a process map never will.
When Effort Hides the Cracks
The gap between how work looks and how work actually gets experienced can be substantial. Take a routine assignment that finishes exactly on schedule. From the outside, everything worked. The deadline was hit, the deliverable landed. But maybe someone had to track down four different people to fill in a missing piece of information. Maybe two systems didn't talk to each other, so someone retyped the same data by hand. Maybe an employee with enough experience to know better skipped a step in the official process, because following it exactly would have blown the deadline. None of that shows up in the finished product. Capable employees get remarkably good at absorbing this kind of friction. They make one more call, build a spreadsheet nobody asked for, find a workaround, track down the right person, stay late, or just figure it out. Their resourcefulness is exactly why the work gets done. It's also why a broken process can look like it's working just fine.
Efficiency or Just Effort?
There's a real risk hiding inside all of this: what looks like organizational efficiency can actually be human effort compensating for organizational inefficiency, over and over, without anyone noticing. Researchers who study workplace workarounds describe exactly this pattern. Workarounds emerge when employees adapt or improvise around obstacles that get in the way of the job (Alter, 2014). And because those improvised fixes solve the immediate problem, they end up hiding the deeper weakness that created it in the first place (Morrison, 2015). The system keeps running because people keep finding new ways to make it run. Over time, that extra effort becomes so routine that nobody thinks to question it anymore. One extra email, one unnecessary meeting, one duplicate entry, one unclear instruction, one more follow-up call: none of it looks like much on its own. Added together, it eats into time and attention that could go toward work that actually matters. That's why leaders should be careful about treating a finished result as proof that the process behind it is healthy. A successful outcome tells you something got done. It doesn't tell you what it cost to get there.
Getting Curious About the Gap
None of this requires leaders to watch over every task personally or eliminate every inconvenience from the workplace. Some complexity is unavoidable, especially in large organizations juggling accountability requirements, legal constraints, and competing priorities. The real opportunity is simpler: get curious about the distance between the process as designed and the process as it's actually lived. Research on organizational coordination backs this up. Formal routines don't replace human interaction; they depend on it. Their success rests on the communication and relationships among the people running them (Gittell, 2002). A useful starting point is just two questions, asked directly of the people doing the work: where does this usually slow down, and what would you remove if you could remove just one thing? Answers like that surface information no dashboard will ever show, and they help leaders tell the difference between complexity the organization genuinely needs and friction it has simply learned to live with.
What Success Doesn't Tell You
Organizations need process. Without it, consistency and accountability fall apart fast. But process doesn't do the work. People do. And when leaders understand what people actually go through to make a process succeed, they get a clearer picture of the organization itself. The goal was never to remove every inconvenience or redesign every procedure that exists. It's to notice when people are spending more energy keeping the system running than doing the work the system was built to support. Sometimes the clearest sign a process needs fixing isn't that it failed. It's finding out how much effort it took to keep it from failing in the first place.
References
Alter, S. (2014). Theory of workarounds. Communications of the Association for Information Systems, 34, 1041–1066. https://doi.org/10.17705/1CAIS.03455
Morrison, B. (2015). The problem with workarounds is that they work: The persistence of resource shortages. Journal of Operations Management, 39–40, 79–91. https://doi.org/10.1016/j.jom.2015.07.008
Gittell, J. H. (2002). Coordinating mechanisms in care provider groups: Relational coordination as a mediator and input uncertainty as a moderator of performance effects. Management Science, 48(11), 1408–1426. https://doi.org/10.1287/mnsc.48.11.1408.268






Join the discussion
Members can read and add comments on every article.