Setting Goals and Using Metrics That Motivate  ## Metadata - Author: [[Rob Zuber]] - Full Title: Setting Goals and Using Metrics That Motivate - Category: #articles - Document Note: --- tags: - #Engineering - #Leadership - #Metrics Author: Rob Zuber Source: LeadDev Reference: https://leaddev.com/process/setting-goals-and-using-metrics-motivate date created: 2025-08-23 00:00 --- # Title: Setting goals and using metrics that motivate ## Table of Contents: - 📝 Summary (#-summary) - 📖 Main Content (#-main-content) - 🗒️ Notes (#-notes) - 📖 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. Setting goals and using metrics that motivate, by Rob Zuber. https://leaddev.com/process/setting-goals-and-using-metrics-motivate ## 📝 Summary: Rob Zuber argues that metrics should motivate engineering teams by connecting their daily work to clear business outcomes. He distinguishes three complementary categories—business metrics (impact), execution metrics (leading indicators/proxies like throughput and lead time), and team health metrics (satisfaction, growth, sentiment). Leaders should help teams align on company goals, pick a business metric they can own, and then use execution metrics as a debugging tool when progress stalls. Treat metrics at the team level to foster unity and reduce fear of surveillance. Ultimately, metrics enable continuous improvement when they illuminate meaning, not when they become the goal. ## 📖 Main Content: Zuber reframes metrics from being a performance cudgel to an instrument for clarity, motivation, and improvement. He critiques over-reliance on execution metrics (e.g., deployment frequency) as trailing indicators that rarely inspire people. Instead, he recommends: - Start with business objectives the team can influence and own. - Use execution metrics to diagnose bottlenecks once goals are clear. - Track team health to prevent burnout and sustain high performance. - Keep metrics at the team level to create shared accountability and psychological safety. - Embrace continuous improvement, reflecting regularly and celebrating progress. This approach prevents metric fixation and aligns craft excellence with organizational impact. ### 🗒️ Notes - Why metrics feel contentious - Overemphasis on throughput, delivery, and deployment frequency can feel like micromanagement. - These are often trailing indicators and weak motivators. - Reframing the purpose - Metrics are tools to understand what’s working and to start informed conversations. - Execution metrics are not the goal; business impact is. - Two leader moves to set the stage - Collaborate on business metrics aligned with team goals. - Leverage execution metrics to surface challenges once goals are set. - Three metric categories - Business metrics - About impact/outcomes: customer growth, usage, operating margins. - Clarifies “why” and “what” the team is building. - Example metrics: CAC, LTV, gross margin, operating costs. - Execution metrics - Measure speed/efficiency; act as proxies/leading indicators. - Use for baseline and incremental improvement, not “ideal” targets. - Example metrics: throughput, change lead time, MTTR, change success rate. - Team health metrics - Counterbalance output and speed; sustain performance. - Collected via surveys and 1:1s. - Example metrics: job satisfaction, growth opportunities, sentiment toward teammates/company. - Team-level perspective - Software delivery is a team sport; team metrics reduce surveillance anxiety. - Fosters unity, peer support, and shared responsibility. - Continuous improvement - Reflect on progress and misses; set stretch goals; acknowledge achievements. ## 📖 References: - LeadDev article by Rob Zuber: https://leaddev.com/process/setting-goals-and-using-metrics-motivate ## 🗣️ Paraphrase: 1) Original idea: “Execution metrics are not the goal… treat them as a leading indicator, or a debugging tool when goals aren’t being met.” - Paraphrase: Don’t aim at throughput or lead time for their own sake; use them like instrument readings that help diagnose why you’re not hitting the outcomes that matter. 2) Original idea: “Make metrics a team effort… metrics at a team level foster unity and reduce fears of surveillance.” - Paraphrase: Track results across the whole team so people feel collectively responsible and supported, rather than individually monitored. ## 📰 Newsletter: Learning web development is more than memorizing frameworks—it’s about building products that matter. This week, we’re spotlighting a practical leadership lens for dev teams: use metrics to motivate, not micromanage. Start with a business metric your team can own (think: activation rate, trial-to-paid, or checkout success), then use delivery signals like change lead time and MTTR to troubleshoot when progress slows. Don’t forget team health—satisfaction and growth are the fuel for sustainable velocity. Recent updates: - WordPress 6.x performance improvements continue; keep an eye on Core updates and block editor enhancements. - New plugin picks: a11y audit helpers, build-time image optimization for block themes, and quality-of-life tools for pattern libraries. Community highlights: - Contributor onboarding sessions are thriving—join a Make/Core, Docs, or Performance team meeting. - Funding conversations are heating up across the ecosystem; sustainable open source needs your voice. New plugins worth testing: - Performance-focused image CDNs with AVIF support. - Content modelers for headless WordPress. - Editorial analytics dashboards aligning content outcomes with business goals. Resources: - Engineering outcomes over output: see “Setting goals and using metrics that motivate” by Rob Zuber (LeadDev). - For delivery metrics, explore the Four Key Metrics and DORA research for context. If you’re teaching yourself or others, tie lessons to outcomes: set a goal (e.g., reduce TTFB, increase form conversion), measure, iterate. Ship small, learn fast, and celebrate progress. ## ✅ Action Items: Prompt for aligning articles with your role as a GoDaddy Developer Advocate and aspiring OSPO director: “Analyze the provided article through the lens of open-source advocacy, contributor engagement, and education within the WordPress ecosystem: - Open-source alignment: Identify how the article’s principles support governance, transparency, and sustainability in community-led projects (e.g., mapping business metrics to ecosystem health metrics such as contributor retention, security response time, and adoption of open standards). - Contributor engagement: Translate team-level metrics into community-level metrics (onboarding completion rates, first-PR time-to-merge, mentorship touchpoints, and contributor satisfaction). Propose interventions to improve these. - Educational impact: Extract teachable frameworks (business → execution → team health) and turn them into workshops, docs, and asynchronous learning paths for new and returning contributors. - OSPO perspective: Define policies and reporting that connect corporate participation in WordPress to measurable ecosystem outcomes (e.g., funding-to-impact ratios, maintenance SLAs on strategic plugins, DEIB metrics in contributor programs). - Transparency and inclusivity: Recommend dashboards and public scorecards (privacy-preserving) for community health, and outline inclusive practices for meetings, RFCs, and decision records. - Career objectives: Explain how applying these metrics strengthens your path to OSPO leadership by demonstrating accountable stewardship, alignment to business value, and improved community sustainability. Deliverables: a 1-page alignment brief, a metrics rubric (business, execution, health), a contributor journey map with checkpoints and su - Summary: Engineering leaders should use a combination of goals and metrics to motivate their teams. Instead of focusing solely on execution metrics, such as throughput and delivery frequency, leaders should help teams understand the business metrics they are driving towards. By connecting the team's work to business objectives, teams can grasp how their contributions directly influence customer and organizational success. Metrics should be treated as tools to understand and start conversations, with business metrics, execution metrics, and team health metrics being the most relevant for developers. By making metrics a team effort and focusing on continuous improvement, teams can be motivated to deliver and achieve their goals. - URL: https://leaddev.com/process/setting-goals-and-using-metrics-motivate [Rob Zuber](https://leaddev.com/community/rob-zuber) Engineering leaders should use a combination of goals and metrics to motivate their teams to make the biggest possible impact. [Metrics](https://leaddev.com/reporting-metrics/using-success-metrics-foster-autonomy-engineering-teams) have long held a tenuous position in software development circles. Leaders want to know how teams are doing and where they can help unlock greater efficiency. Teams want to do great work and progress in their careers, and not feel like they are being micromanaged. A disconnect often emerges here from [too much emphasis being placed on execution metrics, particularly throughput, delivery, and deployment frequency](https://leaddev.com/reporting-metrics/flawed-five-engineering-productivity-metrics), which are trailing indicators that rarely motivate people. Metrics are a powerful tool to help teams do great work. They can tell you a ton about what is and isn’t working. But execution metrics are not the goal. The best teams I’ve worked with had a [clear understanding of the business metrics](https://leaddev.com/team/how-business-alignment-works-high-performing-engineering-teams) they were driving towards and treated their execution metrics as a leading indicator, or a debugging tool for when they felt like they weren’t hitting these goals. Leaders should spend their time either helping teams connect with those big-picture goals or helping them solve the problems that their operational metrics are identifying. #### Set goals that meet business objectives There are a few things you need to do first to get your developers to track the right metrics and be excited about using them: 1. Collaborate on business metrics that are aligned with team goals 2. Leverage execution metrics to surface challenges The teams in your engineering organization exist to deliver against the goals of the company. How each team contributes should be obvious to you and to the team. That means they need to understand where you’re going and the role they play. [They also need to know what success looks like](https://leaddev.com/productivity-eng-velocity/how-measure-and-improve-success-your-engineering-team). It’s unlikely that the overall success of your business is measured in deployment frequency. Help those teams understand what business success looks like and then help them find a business measure that they can own and which relates to that success. When developers have clarity on the company’s mission and vision, they can grasp how their contributions directly influence customer and organizational success. This insight is a strong motivator. As a result, if the team feels like they are not fully hitting those business goals, they will seek out more information for troubleshooting and improving their own work. At that point, they will be much more interested in what good execution looks like than if a CTO is telling them to deploy more often. #### Apply the right metrics in the right situation We’re all drowning in data, yet we often lack a clear understanding. When we make metrics the goal, we focus on the metrics instead of what the metrics are telling us. Instead, [treat metrics as an important tool to help you understand and start conversations](https://leaddev.com/reporting-metrics/using-metrics-communicate-state-your-engineering-org). The most insightful and relevant metrics for developers typically fall into three categories: business, velocity, and team health. ##### Business metrics The key to unlocking value from engineering efforts is connecting those efforts with easily understood business objectives and associated metrics. Business metrics are all about [impact and outcomes](https://leaddev.com/process/focus-outcomes-over-outputs). From growing customer count and usage, to increasing operating margins, engineering teams can have a tangible impact on the trajectory of a company. With a clear connection between the work they are doing and this type of impact, engineering teams will start to think about how they can create more impact with less effort. Common business metrics range from cost of acquisition and lifetime value, to operating costs and gross margin. ##### Execution metrics Execution metrics measure the speed and efficiency of software delivery. This category of metrics is primarily proxy metrics or leading indicators for delivering business metrics. Once teams are bought in on moving the needle on business metrics, they will start to ask how they [could do more faster, or with less effort](https://leaddev.com/productivity-eng-velocity/learnings-deconstructing-engineering-velocity). That’s when they should start to look at their own execution metrics for clues. Ultimately your goal is to measure your baseline metrics and make incremental improvements, rather than chasing “ideal” numbers. Common execution metrics include throughput, change lead time, mean time to recovery, and change success rate. ##### Team health metrics Team health metrics are easily overlooked, but are an important counterbalance to the other two categories. It’s entirely possible to achieve great business outcomes and execution at the expense of team health. At least for a short period. [Luckily, it’s also possible to achieve those outcomes as a result of great team health.](https://leaddev.com/productivity-eng-velocity/balancing-delivery-speed-engineering-health) Measuring how team members are feeling gives a clear sense of which of those camps you’ve fallen into. And in the case of healthy, high-performing teams, [you will get great feedback](https://leaddev.com/productivity-eng-velocity/optimizing-micro-feedback-loops-engineering) on how things can be going even faster. Organizations can collect and track team health metrics in different ways, either through surveys or by having managers [lead 1:1 conversations to understand how engineers are feeling](https://leaddev.com/team/how-hold-more-effective-11-meetings). Common team health metrics include job satisfaction, growth, opportunity, and sentiment toward teammates and the company. #### Make metrics a team effort Software delivery is a team activity with team outcomes. That means that execution metrics can feel intrusive for individual contributors. They can introduce thoughts about how they may be assessed in their next performance review, that they are being monitored, or a sense that executives or the organization at large may not fully grasp the intricacies of the complex inputs and outputs of software development. Instead, thinking about metrics from a team perspective can foster a sense of unity. The emphasis shifts from scrutinizing individual performance to assessing collective progress. Since the entire team shares a common goal, they will willingly offer assistance to help individuals learn and, in turn, improve the team’s overall performance. Team-level metrics also create a sense of responsibility for individuals. When others are depending on you, you want to do your part. #### Wrapping up Ultimately, the success of an engineering team hinges on more than execution metrics alone. You need clarity on team goals. People need to understand the business metrics and be motivated to deliver because they’re excited about what they’re doing. Focusing on business metrics allows teams to understand the why and the what that they are building and how their contributions align with the company’s goals and visions. Execution metrics become a tool for diagnosing issues or improving delivery against goals that are much more motivating. Finally, great work is about continuous improvement. Metrics are a tool to expose opportunities to be better. No matter where you are on the path toward your goals, take the time to reflect on progress and learn from where you missed. Push yourself towards stretch goals and take the time to acknowledge all that you’ve achieved along the way., Setting Goals and Using Metrics That Motivate, Rob Zuber, 01hbreqcatftyw78hq1ep272hs.