Why Do You Dread a Process When It Was Built to Support Your Work?

Introduction

We have all been overwhelmed by a painful process one time or another. Although processes are meant to provide necessary scaffolds to build a solution, if not set up right, these very scaffolds can make it difficult and sometimes impossible to make any progress. So much so that the actual work it was meant to support, feels trivial compared to the process that surrounds it.

This gap between what you came to achieve vs the path that you are forced to take is what I wanted to explore in this essay.

Why does the process feel heavier than the actual work it was built to support?

The Work Is Never The Problem

Think about filing an expense report. The actual task is trivial: you spent money, you want it back. Two minutes of real work. But to get there you log into a portal you forgot the password to, scan and attach receipts in an exact format, hunt for the right category code, route it for a manager approval, then wait on a finance review and then wait for it to be reimbursed in the payroll. The task is two minutes. The process around it takes 2 weeks.

That gap is the whole problem. A light task can sit inside a heavy process, and what you feel when you face it is the drag of the weight. Like carrying the tree home when all you wanted were the fruits.

A Heavy Process Is A Threat

Processes can feel threatening, especially when they aren't created by you.

If you are following a process just for the sake of it, without understanding the reasoning or the why behind each step, you will get infuriated, because by nature we tend to seek meaning of the tasks.

On the other hand, even if you do understand the why, a process can still come off as heavy-handed. This is because generalizing an approach without considering when it actually makes sense to apply, is similar to treating every problem like a nail because all you have is a hammer.

In fact, the heavier the hammer, the more it costs the person swinging it. This is how these costs show up:

1. You see the whole climb at once. You do not experience a process one step at a time. You see the entire thing as a single hurdle before taking a single step, and the imagined version is almost always heavier than the real one.
2. Your working memory has a ceiling. A heavy process asks you to hold more than fits. When it spills past the edge, you feel the overflow as dread, not as "this happens to have eleven steps."
3. Every step is a decision, and decisions drain you. A process thick with small choices empties your tank before you ever reach the work you showed up to do.
4. It threatens your sense of competence. You expect to be good at your job. Fumbling through something you feel you should already know lands as a small failure, and the mind works hard to avoid even small failures.
5. Starting costs the most. The first step is the steepest. A heavy process raises the wall you have to clear just to begin, which is exactly why you stall at the edge before doing anything at all.

What Makes The Threat A Trap

Two conditions decide how much the weight of the process hits you at once:

1. Frequency of Execution - The less often you touch a process, the harder it is to learn it.
2. Frequency of Change - The more often a process changes, the less confident you become with every change.

The clearest place to see this is something you only do once a year. Filing your taxes is the perfect example. You gather the numbers, you put them in the right boxes, you submit. But you are simply never given enough chances to get good at it because the cadence is once a year. You do not remember which documents you uploaded the last time or what details you filled in 2 years ago, because the fields have since changed.

Worse, every year there are new regulations, new sections to consider, new documents to upload. So every year you arrive back at the foot of the same hill you climbed twelve months ago, and every year you feel the same dull dread. Whatever familiarity you earned resets to zero, and you fight your own memory before you can learn the new version, just to repeat the cycle next year.

The Trap Then Becomes Checkmate

You don't learn it unless you do it. And you are typically executing a process because something is due, and usually because other people are waiting on it. When this happens, three pressures arrive at the same moment:

• Time - The deadline is real and close.
• Effort - You don't remember the process or it has changed. So you have to relearn it.
• Capacity - You were already underwater before any of this landed on your desk.

In this situation, there are only two ways out, and both of them cost you:

• Do it properly and bury yourself.
• Work around it and trim until it fits the time you have.

Think about assembling IKEA furniture the night before guests arrive. The instructions run to forty steps, and you have one hour. You are not going to read forty steps. You are going to eyeball it, perhaps skim the basic instructions. Who needs those anyways. Tiny plastic stabilizers..... hmmmm these can surely be fitted later you think, except that they can't and you only realize this when the thing is standing on its feet. You feel relieved and take a step back to admire the result, only to notice the front panels look slightly off and the whole thing wobbles every time someone puts a finger on it.

The Lesser Of Two Evils

In the moment, shrinking the work really is the correct call. Given the time and energy in front of you, the lighter version is what keeps you on your feet. It is the best move available with the small sliver of time you have.

But distance yourself from the deadline and you realize that the lighter version may cost you more than it promises to save. The wobbly furniture has to come apart and go back together. The step you skipped resurfaces three weeks later as a problem, at a worse time, in front of more people, wearing a bigger price tag. The thing you avoided would genuinely have helped, and some quiet part of you knew it the entire time.

Laziness would have felt like relief. This feels like guilt.

You Are Not The Only One

Everyone around you is facing the same problem.

You trimmed the work. Your colleague skipped the entire process. And another grits their teeth, does the whole thing properly, and burns a weekend doing it.

The person who owns the process looks at all of this and reaches for the most natural and most wrong conclusion available: people are not disciplined enough. So the fix becomes more reminders, firmer enforcement, a mandatory training nobody has the hours to attend.

What the owner may not see from where they sit is the hidden math every one of those people ran in private. Each of them stood at the bottom of the same hill, looked up, and decided, correctly for their own situation, that climbing it cost more than walking around it. From the summit you only ever see the skipped step. You never see the silent reasoning that led there, because no one writes that part down. Nobody sends the honest email that says, "I did a worse job today because relearning the new system would have eaten four hours I did not have." They do the worse job, feel bad about it, and move on.

The degradation is invisible from the top. All the owner sees is the skipped step, never the math behind it.

The Next Question

If any of this feels familiar, remember that this is evidence that something needs to be improved. Either the hammer needs changing, or the nails aren't quite right. Which leaves one obvious question: If the process is the real problem, then how does anyone design better processes?