Navigating complexity as an engineering leader  ## Metadata - Author: [[Addy Osmani]] - Full Title: Navigating complexity as an engineering leader - Category: #articles - Document Note: --- tags: - #engineering-leadership - #prioritization - #productivity Author: Addy Osmani Source: LeadDev (Article) Reference: https://leaddev.com/process/navigating-competing-priorities-engineer date created: 2025-08-23 00:00 --- # Title: Navigating Complexity as an Engineering Leader ## Table of Contents: - [🧭 Introduction](#-introduction) - [🧪 What Drives Priorities](#-what-drives-priorities) - [⚖️ Making Trade-offs](#️-making-trade-offs) - [🤝 Collaborate with Stakeholders](#-collaborate-with-stakeholders) - [🧩 Working with Your Product Manager](#-working-with-your-product-manager) - [🧱 Working with Your Engineering Manager](#-working-with-your-engineering-manager) - [🧮 Working with Your Tech Lead](#-working-with-your-tech-lead) - [🪓 Prioritize Ruthlessly and Right-size Workload](#-prioritize-ruthlessly-and-right-size-workload) - [⏱️ Time and Energy Management](#️-time-and-energy-management) - [🙅 Learning to Say No](#-learning-to-say-no) - [🏁 Final Thoughts](#-final-thoughts) - [📖 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical validity](#-logical-validity) - [🔍 DARVO Analysis](#-darvo-analysis) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ### References: - LeadDev article: Navigating competing priorities as an engineer — https://leaddev.com/process/navigating-competing-priorities-engineer ## 📝 Summary: The article outlines practical strategies for engineers to manage competing priorities: understand the drivers (business objectives, user needs, team dynamics, stakeholder KPIs), define trade-off principles (impact, urgency, ROI, risk, dependencies), collaborate closely with PMs, EMs, and tech leads, ruthlessly focus on the “vital few,” manage time/energy with time blocking and buffers, and default to “no” for non-essential work. It concludes with a call to stay anchored in delivering value and adapt as conditions change. ## 📖 Main Content: The piece positions prioritization as navigation through complexity. It advises engineers to uncover why priorities exist before acting, then apply explicit principles to make trade-offs. Collaboration is emphasized—priorities aren’t set in isolation—and guidance is given for working with PMs (roadmaps, feasibility, capacity), EMs (risk escalation, alignment, mentoring), and tech leads (architecture, dependencies, load balancing). It promotes ruthless focus: reduce to the vital few, build buffers (~25%), schedule slack time for tech debt, and avoid best-case estimates. Time blocking and energy hygiene help maintain sustainable pace. Finally, “no” is the default for new requests unless they align with the vital few; offer alternatives and escalate when pressured. ### 🗒️ Notes - 🧭 Introduction - Engineers face constant interrupts and shifting deadlines; prioritization is a persistent challenge. - Goal: strategies to manage, not eliminate, competing priorities. - 🧪 What drives priorities - Business objectives: new initiatives vs. maintenance; align actions with strategy. - Customer/user needs: segment requests; map to company goals. - Team dynamics: differing rhythms/processes can cause misalignment. - Stakeholder incentives/KPIs: understand individual drivers to balance satisfaction. - Insight: Root-cause analysis enables informed trade-offs. - ⚖️ Making trade-offs - Principles: Impact, Urgency, ROI, Risk, Dependencies. - Balance multiple factors; avoid single-principle dominance. - Communicate trade-offs clearly to stakeholders. - 🤝 Collaborate with stakeholders - Priorities are co-created with PM, EM, and Tech Lead. - Overcommunicate updates and reasons for deprioritization; offer alternatives. - Set reminders for status updates. - 🧩 Working with your PM - Co-review roadmaps; evaluate new requests’ value. - Be transparent about capacity; regular check-ins on sequencing. - Provide data-driven feasibility and effort estimates. - 🧱 Working with your EM - Escalate risk of overcommitment/misalignment. - Ask for help resolving conflicts, mentor on “no.” - Align on vital few: roadmap, tech debt, standards; get buy-in on estimates. - Offer feedback on process bottlenecks. - 🧮 Working with your Tech Lead - Align on architecture, tech debt backlog, standards. - Share capacity; rebalance team assignments. - Resolve dependencies; balance delivery vs. quality. - 🪓 Prioritize ruthlessly and right-size workload - Reduce to vital few; question value, timing, and ownership. - Say no to non-essential work; back decisions with data/options. - Protect focus to avoid burnout and debt. - Tactics: - Include ≥25% buffer for interrupts. - Estimate from historical throughput, not best-case. - One slack period/quarter for tech debt/infrastructure. - Build breathing room into dates; avoid earliest imaginable promises. - ⏱️ Time and energy management - Time blocking, especially mornings; 2–4 hour focus blocks. - Use blocks for deliverables and admin tasks. - Schedule L&D to avoid crowd-out. - Energy hygiene: breaks, cap meeting length/count, limit after-hours, evening wind-down routines. - 🙅 Learning to say no - Default “no” except for vital few. - How-to: thank, offer alternatives, cite current commitments, propose postponement, escalate if pressured. - 🏁 Final thoughts - Competing priorities are inevitable; anchor in value and adapt with agility. ## 📖 References: - LeadDev article: Navigating competing priorities as an engineer — https://leaddev.com/process/navigating-competing-priorities-engineer ## 🗣️ Paraphrase: - Original idea: “Before diving into tackling priorities, it’s important to understand what’s driving them…” - Paraphrase: Before acting, diagnose the forces behind requests—strategy, customer segments, team practices, and stakeholder KPIs. That context equips you to make sensible trade-offs aligned to business value and capacity. - Original idea: “The easiest way to navigate competing priorities is to reduce them down to the vital few…” - Paraphrase: Strip your workload to the handful of items that truly matter, decline the rest, and defend your focus with data, buffers, and realistic schedules so your team can deliver sustained, high-quality outcomes. ## 📰 Newsletter: This week in the WordPress developer world: learning smarter beats working harder. If your backlog feels like a bottomless brunch of “urgent” tickets, Addy Osmani’s guidance on ruthless prioritization is your new espresso shot. Highlights: - Anchor in value: weigh impact, urgency, ROI, risk, and dependencies before saying “yes.” - Protect your plate: default to “no,” add 25% buffer, and block 2–4 hour focus windows. - Tech health matters: give yourself a quarterly slack cycle for tech debt and infra. Community shoutouts: kudos to contributors shipping accessibility fixes across themes; keep those PRs coming! New plugin to watch: a lightweight time-blocking calendar for wp-admin that syncs with ICS—perfect for focus time. Learning corner: refresh your Git flow with branching strategies that minimize context switching. Further reading: “Navigating competing priorities as an engineer” on LeadDev. Stay kind to your future self—estimate from history, not hope. ## ✅ Action Items: For a Developer Advocate at GoDaddy (open source/WordPress, educator, aspiring OSPO director): - Alignment with open-source advocacy: - Use the trade-off framework (impact, ROI, risk) to prioritize community initiatives (docs, contributor onboarding, a11y fixes) that deliver the highest ecosystem value. - Codify “vital few” priorities per quarter: contributor experience, funding pilots, maintainers’ burnout prevention. - Contributor engagement: - Implement regular stakeholder syncs with core leads and plugin maintainers; publis - Summary: As an engineering leader, navigating competing priorities is a constant challenge. Understanding what drives priorities, such as business objectives, customer needs, team dynamics, and individual stakeholders, can help inform how you manage them effectively. Making trade-offs based on impact, urgency, ROI, risk, and dependencies is necessary when you cannot tackle every priority simultaneously. Collaborating with key stakeholders like product managers, engineering managers, and tech leads is crucial in establishing priorities and delivering value. Prioritizing ruthlessly, right-sizing workloads, and managing time and energy effectively are strategies that can help engineering leaders navigate complexity and bring their best work to meet every challenge. - URL: https://leaddev.com/process/navigating-competing-priorities-engineer You have **0** further articles remaining this month. [Join LeadDev.com for free](https://leaddev.com/register?s=dw) to read unlimited articles. How can you prioritize when everyone’s ask is an urgency and you don’t have time to fit it all in? graphic element ##### Join us at the next New York Meetup - November 30, 2023 Connect with other engineers, share ideas and gain insights from some of the best in the industry at this free-to-attend meetup in New York hosted by Code Climate. You’re in the trenches, knee-deep in code, and you can almost taste the sweet victory of a problem solved. Just then, an email alert disrupts your focus – another fire to put out, another deadline to meet. And so the never-ending cycle of competing priorities begins. As software engineers, we juggle multiple projects and tasks on a daily basis. Deadlines collide, emergencies pop up, and stakeholders make last-minute requests. Navigating these competing priorities is a constant challenge. While you can’t eliminate competing priorities, you can develop strategies to manage them effectively. #### What drives priorities Before diving into tackling priorities, it’s important to understand what’s driving them. Digging into the root cause can provide crucial context that informs how you navigate task conflicts. Here are some examples of what could be driving competing priorities: * **Business objectives** - A new initiative launched to meet a strategic goal can compete with maintaining existing systems. Understanding the business motivations behind both will help guide your actions. * **Customer and user needs** - Different features may be requested by various customer segments. Mapping out each customer need shows how they align with company goals. * **Team dynamics** - Departments may have different processes and rhythms. Identifying these distinctions prevents misalignment. * **Individual stakeholders** - Each stakeholder has their own incentives and key performance indicators (KPIs) driving requests. Knowing these helps balance stakeholder satisfaction. By uncovering the forces that shape priorities, you can make informed trade-offs and balance business needs with your capacity. #### Making trade-offs Since you cannot tackle every priority simultaneously, you’ll need to make trade-offs. Defining principles provides [a framework for making intentional decisions](https://leaddev.com/process/prioritization-framework-uncertain-times): * **Impact** - Prioritize work that will have the greatest effect on customer experience, revenue, or other business objectives. * **Urgency** - Balance long-term goals with tasks needing immediate attention. * **Return on investment (ROI)** - Consider the return on time invested for each priority. * **Risk** - Evaluate the risks of deprioritizing items, both short and long-term. * **Dependencies** - Sequence priorities based on dependencies between tasks. No single principle should dominate. The goal is balancing multiple factors to optimize outcomes. Having defined principles also allows you to communicate trade-offs more effectively to stakeholders. #### Collaborate with stakeholders While you own your priorities as an engineer, you don’t establish them in a vacuum. Key stakeholders like your product manager, engineering manager, and [tech lead](https://leaddev.com/personal-development/what-tech-lead-first-among-equals-developer-team) play an integral role. Effective collaboration is a two-way street. Bring thought leadership in on priorities while also listening to the expertise stakeholders provide. By partnering with stakeholders, you amplify your contribution and help the team deliver value. Overcommunicate with stakeholders early and often about prioritization trade-offs and changes in timelines. Set calendar reminders to give status updates to stakeholders. If deprioritizing a stakeholder request, explain why and offer alternatives. ##### Working with your product manager: * Review the product roadmap together to understand planned initiatives and how new requests fit in. * When new feature requests come in, evaluate their [business value](https://leaddev.com/team/how-business-alignment-works-high-performing-engineering-teams) jointly before committing to anything. * Be transparent about [capacity constraints that could impact delivery timelines](https://leaddev.com/productivity-eng-velocity/mapping-immovable-objects-engineering-projects). * Establish regular check-ins to align on priority sequencing within iterations. * Provide data-driven input on technical feasibility and level of effort for features. ##### Working with your engineering manager: * Escalate risks around overcommitting or misalignment on priorities. * Ask for help prioritizing when facing conflicting stakeholder demands. * Review your "vital few" priorities like the product roadmap, tech debt backlog, team standards. Get buy-in on planned work and estimates. * [Share feedback](https://leaddev.com/team/art-giving-and-receiving-feedback-leader) on your manager's processes that are working well or creating bottlenecks. * [Request mentoring](https://leaddev.com/mentoring-coaching-feedback/want-become-mentee-follow-these-five-steps) on strategies for managing priorities and saying no. ##### Working with your tech lead: * Align on technical aspects like architecture plans, tech debt backlogs, and team standards. * [Provide visibility into your capacity](https://leaddev.com/team/3-ways-make-your-teams-work-more-visible) when planning out team assignments. * Offer to pick up items from other engineers if you have availability. * Ask for help resolving dependencies between team members blocking progress. * Share ideas for how to balance delivery pace with quality and sustainability. #### Prioritize ruthlessly and right-size your workload The easiest way to navigate competing priorities is to reduce them down to the vital few that matter most. Be relentless in questioning whether tasks need to be done now, if they create value, and if you're the best person to do them. Then focus your efforts only on those vital priorities. Taking on too much is a recipe for failure. While having some stretch goals is good, overcommitting will only lead to stress, technical debt, and team burnout. Say no to non-essential work. This intentional focus prevents distractions and fragmentation. Bring data and options to the table to support your decisions and be willing to stand behind the priorities you champion. Be realistic about your team's bandwidth and don't commit to more work than you can deliver. Actively shape priorities focused on delivering maximum value and push back on misguided priorities that don’t make sense for customers or the business. Protect your team's ability to focus and deliver sustained, quality work. * Include at least 25% buffer time in your estimates for unplanned work and interruptions. Block focus time on your calendar to minimize context switching. * When estimating tasks, use your completed work as a baseline, not best-case scenarios. * Have at least one slack period per quarter to [focus on technical debt and infrastructure](https://leaddev.com/architecture-microservices/how-redesign-your-architecture-reduce-technical-debt). * Build breathing room into delivery dates, don't promise the earliest imaginable date. #### Time and energy management Time blocking creates dedicated spaces for focused work. For added impact, try and schedule your time blocks in the morning, when your energy levels are most high. * Schedule your calendar with set blocks of time for high-priority tasks. This avoids double-booking and creates focus time. * Use your time blocks to complete tasks less urgent tasks as well, such as status updates or reporting on completed work. * Schedule time blocks for planned learning and development like training courses or reading. This prevents learning from always getting pushed off by urgent tasks. * [Limit context switching](https://leaddev.com/process/managing-chaos-context-switching) by dedicating extended blocks of 2-4 hours for intensive work. Short fragmented blocks often result in more distractions. Sustainable pacing matters as much as efficiency. How you manage your energy impacts your ability to focus and avoid burnout. A few strategies for maintaining energy: * Take real breaks during the workday – get up, move around, get some air. * [Set guidelines for meeting length and number per day](https://leaddev.com/process/how-protect-your-calendar-against-unnecessary-meetings). Too many long meetings drain energy. * Limit after-hours work to true emergencies – your brain needs recovery time. * Develop consistent wind-down routines in the evening like going for a walk, reading, or meditating. This helps transition out of work mode. Sometimes slowing down is the best way to speed up. Protecting your energy enables greater engagement when working on priorities. ##### Learning to say no The default answer to any request should be “no” except for the vital few priorities already on your plate. This prevents non-critical work from queue-jumping and derailing progress. Saying no is difficult. It can feel easier just to accept more work. However, taking on too much ultimately helps no one. If you don’t know where to start when saying no, the below pointers might be helpful. * Thank them for thinking of you and provide alternative solutions, where possible. * Remind them of your current priorities and commitments. And given this context, you won’t be able to dedicate your time to additional projects or tasks. * Suggest postponing the request until your next free period. * Escalate to your manager if you feel pressured into overcommitting. ### Final thoughts In an engineering role, competing priorities are pretty much inevitable. There will always be more opportunities than time and resources allow. By taking ownership of your priorities, evaluating trade-offs, right-sizing your workload, time blocking, ruthlessly focusing on the vital few priorities, and collaborating closely with stakeholders, you can steer your way through the twists and turns. Though the seas may be choppy at times, you’re capable of charting the right course if you keep your anchor rooted in delivering value and maintain the agility to shift as conditions change. With these strategies, you can navigate priorities with confidence and bring your best work to meet every challenge., Navigating complexity as an engineering leader, Addy Osmani, 01hfw52j5t7xfpc074pw0rpnyn.