Protecting delivery milestones after a mid-build obstacle by splitting scope

Quick Overview

A behavioral product manager question about a build that hit an obstacle midway. Candidates explain how they still protected delivery milestones, whether they split or deferred parts of the feature requests, and how they aligned engineering and stakeholders on that trade-off.

Protecting delivery milestones after a mid-build obstacle by splitting scope

Company: American Express

Role: Product Manager

Category: Behavioral & Leadership

Difficulty: medium

Interview Round: Other

In a product manager interview, you are asked to describe a real situation in which your team ran into an obstacle partway through building something. Explain how you still managed to meet the project's milestones, and say whether doing so required you to split, trim or resequence the feature requests you had been given. ```hint Make the trade visible A milestone survives an obstacle only if something else gives: the date, the scope, the quality bar or the team's capacity. Decide which one moved in your story, and be ready to explain why it was that one and not another. ``` ### Clarifying Questions - Does the obstacle need to be technical, such as a performance limit or a broken dependency that engineering raised, or can it be organizational, such as losing team members or a partner slipping its own date? - Were the milestones commitments made to customers, sales or leadership, or internal sprint goals the team could renegotiate on its own? - If I did not end up breaking down any feature requests, should I still describe what I did instead, for example resequencing the work or running pieces in parallel? ### What a Strong Answer Covers - A specific obstacle whose effect on the plan is quantified: which milestone was at risk, by how much, and who would feel the slip. - How the candidate diagnosed the problem and generated options together with engineering and design, rather than simply asking the team to work harder. - The scope decision in detail: how the original request was split into slices, what shipped on time, what was deferred, and why the shipped slice still delivered the milestone's real value. - How and when stakeholders learned about the change, and how disagreement about the cut was handled. - A measurable result, what happened to the deferred work, and a lesson the candidate has applied since. ### Follow-up Questions - Which part of the request did you cut, who pushed back on that decision, and how did you resolve it? - If the obstacle had surfaced one week before the milestone instead of midway through the build, what would you have done differently? - How did you make sure the deferred slices were actually built later instead of sitting in the backlog?

Overview: A behavioral product manager question about a build that hit an obstacle midway. Candidates explain how they still protected delivery milestones, whether they split or deferred parts of the feature requests, and how they aligned engineering and stakeholders on that trade-off.

American Express logo
American Express
Jan 24, 2025
mediumProduct ManagerOtherBehavioral & Leadership
0
0

In a product manager interview, you are asked to describe a real situation in which your team ran into an obstacle partway through building something. Explain how you still managed to meet the project's milestones, and say whether doing so required you to split, trim or resequence the feature requests you had been given.

Clarifying Questions Guidance

  • Does the obstacle need to be technical, such as a performance limit or a broken dependency that engineering raised, or can it be organizational, such as losing team members or a partner slipping its own date?
  • Were the milestones commitments made to customers, sales or leadership, or internal sprint goals the team could renegotiate on its own?
  • If I did not end up breaking down any feature requests, should I still describe what I did instead, for example resequencing the work or running pieces in parallel?

What a Strong Answer Covers Guidance

  • A specific obstacle whose effect on the plan is quantified: which milestone was at risk, by how much, and who would feel the slip.
  • How the candidate diagnosed the problem and generated options together with engineering and design, rather than simply asking the team to work harder.
  • The scope decision in detail: how the original request was split into slices, what shipped on time, what was deferred, and why the shipped slice still delivered the milestone's real value.
  • How and when stakeholders learned about the change, and how disagreement about the cut was handled.
  • A measurable result, what happened to the deferred work, and a lesson the candidate has applied since.

Follow-up Questions Guidance

  • Which part of the request did you cut, who pushed back on that decision, and how did you resolve it?
  • If the obstacle had surfaced one week before the milestone instead of midway through the build, what would you have done differently?
  • How did you make sure the deferred slices were actually built later instead of sitting in the backlog?