Business Context
Moveworks supports enterprise customers through products like Moveworks Copilot and the employee support platform. You are managing an engineering team responsible for a core Copilot workflow, and leadership wants a clear metric framework to assess whether the team is performing well beyond just "shipping more code."
Over the last quarter, the team shipped 18 production releases versus 12 in the prior quarter. However, Sev-1 incidents increased from 2 to 6, average cycle time rose from 4.5 days to 6.8 days, on-time roadmap delivery fell from 82% to 71%, and employee-reported CSAT for this workflow dropped from 4.6 to 4.3. Team size stayed roughly flat at 10 engineers. The VP of Engineering asks you to define the right metrics, explain which are leading vs. lagging, and show how you would diagnose whether the team is actually improving.
Requirements
- Define the core metrics you would use to evaluate this engineering team.
- Separate the metrics into delivery, quality, reliability, and business/customer impact.
- Identify which metrics are leading indicators versus lagging indicators.
- Explain how you would interpret the quarter-over-quarter changes above.
- Recommend a concise scorecard for monthly review with guardrails against optimizing one metric at the expense of others.
Data Available
- Jira sprint and issue history with story points, status changes, assignee, planned vs. completed work
- GitHub pull request and deployment logs with commit timestamps, review time, merge time, release tags
- PagerDuty / incident records with severity, duration, root cause, and affected services
- Datadog service dashboards with latency, error rate, uptime, and saturation
- Moveworks Copilot product analytics with workflow usage, task completion, deflection rate, and CSAT
