I’m hitting ‘save’ on a line of CSS that was mangling the mobile view of our hero banner for the last 48 hours. It was a simple fix, really. A stray semicolon, a misplaced bracket-the kind of digital grit that makes a million-dollar website look like it was built in a garage in 1998. I didn’t wait for a sprint planning meeting. I didn’t draft a proposal. I just saw the fire and reached for the bucket. By 9:08 AM, the site was beautiful. By 10:18 AM, I was sitting in a glass-walled conference room listening to a Project Manager explain why my proactivity was actually a ‘significant breach of protocol.’
They didn’t care that the conversion rate jumped 18 percent in two hours. They cared that there wasn’t a ticket number associated with the change. This is the death of the do-ocracy, that beautiful, fleeting state where the people who do the work are the ones who make the decisions. Instead, we live in the era of the ‘Process-ocracy,’ where the map is more important than the territory, and if you find a shortcut, you’re punished for leaving the designated path.
I spent last night alphabetizing my spice rack. It sounds like a symptom of a breakdown, but it was actually a desperate attempt to exert control over a world that seems increasingly allergic to individual agency. Turmeric, Thyme, Vanilla (which I know is a bean, but it’s in a jar, so it stays). There’s a comfort in seeing things where they belong, but that comfort is a lie when applied to a corporate structure. In a pantry, order serves the cook. In a corporation, order often serves only the order-keepers.
The Addiction to Inaction
‘The moment you take initiative,’ Ruby says, ‘you become responsible for the outcome. And for most people, the fear of being responsible for a failure is much greater than the desire to be responsible for a success.’
This is the core of the frustration. We are told to ‘act like owners,’ to ‘take the lead,’ and to ‘disrupt.’ But the moment we actually do, we hit the invisible ceiling of the 1008-page employee handbook. The owner doesn’t ask for permission to fix the leak in the roof. The owner just gets a ladder. If you’re an employee, however, you’re expected to watch the water ruin the carpet while you wait for the Facilities Department to approve the requisition for a bucket. It’s a form of learned helplessness. After being told ‘no’ or ‘not like that’ about 28 times, the average person simply stops looking for the leaks. They put on their headphones, ignore the drip-drip-drip, and wait for 5:08 PM.
[The process is a shield for the incompetent and a cage for the capable.]
We see this same friction in the way we manage our homes and our resources. People want to take charge of their energy, their waste, and their impact, but they are often met with a wall of ‘that’s not how we do things.’ Utilities want you to stay on the grid, paying the same escalating rates, because your initiative to become self-sufficient is a threat to their predictable, bureaucratic revenue. When you decide to stop being a passive consumer and start being an active producer, you’re essentially fixing the CSS without a ticket. You’re saying, ‘I see a better way, and I’m going to do it.’ This is why companies like Rick G Energy resonate so deeply right now. They represent the transition from waiting for the ‘grid’ to solve your problems to actually owning the solution yourself. It’s about regaining that lost sense of agency, the feeling that you are the primary actor in your own life, not just a line item in someone else’s spreadsheet.
The Cost of Learning
I’ve made mistakes before, of course. There was the time I tried to ‘optimize’ the database and accidentally deleted 488 user profiles. That was a bad day. I apologized, I stayed up for 38 hours fixing it, and I learned. But that mistake taught me more about our infrastructure than a decade of ‘safe’ work ever could. The problem is that most modern organizations have a zero-tolerance policy for that kind of learning. They would rather have a slow, mediocre system that never breaks than a fast, innovative one that occasionally trips over its own feet. They prioritize the absence of errors over the presence of excellence.
The Culture of Cowardice
If I take the initiative to fix the website and it crashes, it’s my fault. But if I follow the process and the website remains broken for three weeks while the ticket clears the queue, it’s ‘the system’s’ fault. No one gets fired for following a broken process. They only get fired for trying to fix it and failing. So, we create a culture of cowards, where the safest thing to do is nothing at all.
But here’s the thing: the world doesn’t move forward because people followed the rules. It moves forward because someone got frustrated enough to break them. We need the people who stay up until 2:08 AM because they can’t stand the thought of a broken link. We need the homeowners who decide that they don’t want to be beholden to a monopolistic power company and decide to generate their own electricity. We need the addicts who realize that the only person who can save them is the one in the mirror.
The Interchangeable Employee
Interchangeable
Minimize Talent Impact
Homogenized
Standardized Result
Process Driven
Bureaucracy Wins
I’m not saying we should live in total anarchy. I like that my spice rack is organized. I like that there are safety standards for bridges. But we have to distinguish between ‘rules that keep us safe’ and ‘rules that keep us quiet.’ Most corporate processes are the latter. They are designed to homogenize behavior, to make every employee interchangeable, and to minimize the impact of individual talent. If everyone follows the same 58 steps, then it doesn’t matter who is doing the work. You can replace a brilliant engineer with a mediocre one, and the process will still produce a mediocre result. To the bureaucracy, that’s a win. To the human soul, that’s a tragedy.
The Cost of Debate vs. The Cost of Errors
48 Mins
Debating Blue Shade
Safari Broken
Ignored Functionality
I remember a meeting where we spent 48 minutes debating the color of a ‘Submit’ button. There were eight people in the room, making an average of $88 an hour. We spent nearly a thousand dollars of the company’s money to decide on a shade of blue. Meanwhile, the actual submission form was broken for users on Safari. I pointed this out, and the response was, ‘We’ll open a ticket for that after we finalize the brand guidelines.’ That was the moment I realized the ‘process’ wasn’t there to help us build a better product; it was there to give eight people a reason to feel busy without actually having to take the risk of building something.
[We are over-managed and under-led.]
So, what happens to the person who keeps taking initiative? Usually, they leave. They go to startups where the do-ocracy still lives, or they start their own businesses, or they just check out mentally and start a side-hustle that actually rewards their effort. The companies that punish initiative end up with exactly what they asked for: a workforce of people who do exactly what they are told and nothing more. And in a world that is changing as fast as ours, ‘exactly what you’re told’ is a recipe for extinction.
The Choice to Re-Engage
I look at my spice rack, perfectly ordered, and I realize I’m doing the same thing. I’m managing the small things because the big things feel unmanageable. But tomorrow, I’m going to go back into that office, and I’m going to look for another broken link. I might get another lecture. I might get another ‘performance improvement plan’ because I didn’t wait for a ticket. But I’d rather be the person who tried to fix the world and failed than the person who watched it break while waiting for permission to care. Because at the end of the day, the only process that matters is the one that leads to a result you can actually live with.
What happens when the people who care finally stop trying? Is that the stability we’re looking for?