Choosing a Leading Metric to Track a Project Racing a Fixed Deadline
Company: T-Mobile
Role: Product Manager
Category: Analytics & Experimentation
Difficulty: medium
Interview Round: Other
Suppose you are a product manager running a project whose delivery date is fixed and leaves almost no slack. What is the single best metric for tracking whether the project is on course? Name the metric, define precisely how you would calculate it, explain why it beats the obvious alternatives, and describe what you would watch alongside it and how the team would act when it signals trouble.
```hint Look ahead, not back
Many progress numbers only report what has already happened. On a tight schedule the useful measure warns about a missed date while there is still time to react, and it should recognize that some unfinished work affects the end date far more than the rest.
```
### Clarifying Questions
- Is the date truly immovable (a contractual commitment, a regulatory cutoff, a coordinated launch), or could it move if scope must be protected?
- If the project falls behind, which levers are open: trimming scope, adding people, or relaxing the quality bar?
- What kind of work is it: a software release built in sprints, a rollout of many similar units, or a cross-team program with hard dependencies between workstreams?
- Who will read the metric: the delivery team every day, or leadership looking for a weekly on-track or at-risk signal?
### What a Strong Answer Covers
- Explicit criteria for a good tracking metric under deadline pressure, such as being predictive, tied to the end date, hard to game and cheap to update.
- A comparison of common progress measures and the blind spot of each.
- One clearly defined headline metric, with its calculation and the thresholds that trigger action.
- Supporting and guardrail signals for scope growth, quality and team load, so the date is not met by cutting corners.
- How the metric drives decisions: review cadence, escalation, and the levers to pull when it turns red.
### Follow-up Questions
- Your headline metric is green, but engineers privately say the date is at risk. How do you reconcile the two?
- Halfway through, a stakeholder adds a requirement they call mandatory. How does your metric show the impact, and what do you do next?
- How would your choice change for a team that works in short sprints without a detailed upfront plan?
Overview: A product management execution and metrics question about choosing the single best measure for tracking a project with a fixed, tight deadline. It tests whether a candidate can weigh common progress measures, define a predictive schedule metric precisely, and pair it with scope, quality and team-load guardrails that trigger action.