Beyond the Feature Factory
As an Engineering Manager (EM), you wield considerable influence. You can either remain entrenched in a relentless cycle of feature production (“feature factory mode”), or you can exercise your power to champion high-leverage technical work. This blog post is a tactical guide on how to effectively advocate for addressing technical debt and enhancing tech leverage, tailored for EMs who aim to strike a balance between immediate feature delivery and long-term system health.
Without going super deep, here’s why prioritizing tech debt or leverage work is important:
- Vital for System Health: Prevents fragile and unscalable systems.
- Enhances Efficiency: Improves development processes and speed.
- Ensures Project Viability: Addresses long-term competitiveness.
- Reduces Risks: Lowers security vulnerabilities and stability issues.
- Boosts Team Morale: Improves job satisfaction and retention.
… and what happens when it isn’t given attention:
- Decreased Productivity: More time spent on fixing and less on development.
- Increased System Failures: Higher risk of downtime and user impact.
- Escalating Costs: Longer neglect leads to higher resolution expenses.
- Lowered Morale and Turnover: Frustrated teams may lead to higher turnover.
- Reduced Market Adaptability: Inability to quickly adapt to changes.
Recognize the Power of Your Voice
First and foremost, understand that your position affords you a unique vantage point and a voice that can catalyze change. You’re not just a conduit for upper management directives; you’re a bridge between individual contributors (ICs) and higher strategic levels. Your advocacy for tech debt reduction can significantly impact your team’s effectiveness and health.
Engage with Your Team
Your team members are often the first to notice issues and inefficiencies. Pay close attention to what your ICs mention during meetings or in conversation. Engage them on technical topics and encourage an environment where they can not only openly discuss challenges, but own driving improvements. This engagement will not only provide you with valuable insights, but also foster a sense of ownership and collaboration within your team.
Create a Backlog of Technical Work
Documenting is key. Maintain a backlog of technical tasks and improvements. This list should be a living document, regularly updated and reviewed. Prioritize these tasks based on potential impact and effort required. During your roadmap reviews, ensure that these technical tasks are considered alongside new feature development. This will help in balancing immediate business needs with long-term technical health.
Collect and Present Impact Data
Data speaks volumes and is hard to refute. Collect basic impact numbers that illustrate how addressing technical debt will benefit the project. This could be metrics like reduced downtime, faster deployment times, or improved performance. Present this data to your Product Management (PM) partner and your own manager, highlighting the value of this work.
Communicate the Value
When discussing technical debt with non-technical stakeholders, avoid jargon. Instead, focus on the tangible benefits: improved efficiency, reduced risk, and the potential for faster feature development in the future. Emphasize how technical improvements can align with and support business objectives.
Remember, as an EM, your advocacy not only benefits your immediate team but contributes to the broader goals of your organization.
The learning continues in…
- All chapters — The Engineering Manager’s Pocket Guide
- Chapter 8 — From Busy to Productive: Time Management Tips for Engineering Managers
- Chapter 9 — Constructive Feedback Strategies Every Leader Should Know
- Chapter 10 — Leading vs. Managing in the Engineering World
- Chapter 11 — “Time to X” — metrics your team should track
- Chapter 12 — Defining “done” in software projects
- Chapter 13 — Continuous Team Advocacy
- Chapter 14 — Cadences — engineering manager time horizons
- Chapter 15 — Beyond the Feature Factory
If you have any thoughts or experiences to add, let me know! Respond to this post or let me know on LinkedIn. I’m happy to talk about anything software engineering related.
