Process Standardization Is Stifling My CreativityProcess Standardization Is Stifling My Creativity

[Root] Access is an advice column for questions about IT issues, career moves, and workplace concerns.

Want advice? Submit your questions anonymously using this form.

Dear [Root] Access,

I’m a software developer who takes pride in writing clean, efficient code and creative problem-solving. But ever since my new manager came on board, he has made all our work about his quixotic quest for software development process standardization and repeatable outcomes. 

Don’t get me wrong: I understand the value of standardized processes, especially in a large team. But the way they’re getting implemented is stifling. Every task must follow rigid rules, even when they're unnecessary or slow us down. Projects that used to take days now drag on for weeks, stuck in endless approval loops, constant audits, piles of documentation, mind-numbing instructions for trivial tasks (like “how to name a variable”), and meetings to ensure everything is uniform. What was once an exciting sprint of problem-solving has turned into a bureaucratic slog.

I spoke with my manager about how difficult this approach is for me, but he insists that process standardization is the only way to scale and prevent mistakes. 

I’m worried my skills as a developer will stagnate. I barely have time to code anymore because I constantly battle red tape. So, here’s the question: Should I push myself to adapt to this new system, or is it time to move on and find a place where creativity and efficiency are truly valued?

Related:How Do I Tell My IT Security Manager To Stop Crying Wolf?

—Stuck in Standardization

Dear Stuck in Standardization,

Your organization is maturing. Some folks enjoy a slowdown like this. It helps them feel organized and clear-headed. Every step is isolated, every line is reviewed, and entire code bases are updated half as often as before.

Other employees get bored. What’s the opposite of solving problems in innovative ways? Standardized processes.

To be fair, I agree that standardized processes can benefit us all. For example, reminders to design for accessibility make products more usable for everyone, and writing comments in your code helps earlier-career engineers learn from you. However, standardized processes should also make work more enduring and of higher quality. It seems like your manager idolizes processes for the sake of them. 

To decide what’s next for you, you’ll need more information. Cultural change often takes time, but sometimes it’s tied to a single leader. Do the processes also bog down the rest of the organization? Is your new manager gaining praise and respect from his peers and leaders? If so, these changes may be here to stay. If not, this process-heavy phase could be short-lived. 

Related:Did ADHD Traits Shape My Career as a Sysadmin?

You might also want to consider what’s motivating your new manager to stick so strictly to standardization. If the manager before him cut corners, he might be trying to prove himself as the opposite. Maybe he’s nervous about the new role and eager to demonstrate his expertise. It’s also possible that exerting this level of control is comforting to him. While none of this justifies over-complicating your tasks, it could help explain why he’s making these changes.

You’ve observed that these standardized processes are limiting your growth. If you want to convince your manager to give you more breathing room, you’ll have a better chance if you understand what's behind his approach.

Learn more about challenges for software developers