💼 Why Individual Contributors Hit Roadblocks (And How to Keep Moving) 🔗

As an Individual Contributor (IC) in tech, the path to seniority isn’t just about writing better code or mastering a new framework. Often, the biggest hurdles are behavioral. We tend to fall into comfortable patterns that, while feeling productive, actually stall our progress on critical projects.

Drawing inspiration from classic engineering leadership discussions—such as those famously explored by Camille Fournier on her Elided Branches blog—it’s worth examining the common traps that cause ICs to get stuck and how we can learn to navigate them.

📑 Table of Contents 🔗

🪤 The Comfort Zone Traps (Getting Sidetracked) 🔗

It is incredibly easy for talented ICs to distract themselves with “useful” work that isn’t actually the priority work. This usually manifests as avoiding the core task by hiding in comfortable, intellectually stimulating activities:

• The Perfectionism Spiral: Spending endless hours on excessive refactoring, building out unnecessary automation, or over-engineering tests for edge cases that will rarely occur.
• Perpetual Research: Staying in the brainstorming or architecture phase indefinitely. Researching forever is safer than making a concrete decision and risking failure.
• The Savior Complex: Dropping everything to fight fires (even when not on call) or constantly helping other teammates with their tasks as a subconscious excuse for not finishing your own.
• Shiny Object Syndrome: Pouring energy into side projects or adopting exciting new tools instead of focusing on the mundane realities of the main deliverable.

🧱 The Friction Points (Getting Stuck) 🔗

While the first category is about active distraction, this second category is about hitting a wall. These are the uncomfortable phases of a project where ICs often freeze up and momentum dies:

• The Final 20%: Starting a new project is fun; finishing the last 20% (documentation, final bug squashing, deployment prep) is a grind. Many ICs stall out right before the finish line.
• The Blank Canvas: Conversely, some freeze when asked to start completely from scratch or handle high-level project planning without a clear roadmap.
• Communication Hurdles: Engineering isn’t just about code. ICs often get stuck when they have to negotiate with other teams, talk to external vendors, navigate corporate bureaucracy, or simply admit they don’t know something and ask for help.
• Dealing with Ambiguity: When unexpected setbacks occur or when forced to work with unfamiliar legacy code, the lack of immediate clarity can cause a developer’s momentum to grind to a halt.

🚀 Moving Forward 🔗

Recognizing these traps is the first step to overcoming them. If you find yourself endlessly researching a solution, set a strict timebox. If you are terrified of a final launch, break the deployment down into microscopic steps. And most importantly, remember that soft skills—knowing when to say “no,” when to ask for help, and how to communicate across teams—are just as critical to an IC’s success as technical prowess.

Kaue's Way of Life

Get It Free