An Executive Wants the Feature Now. Bring a Better Decision, Not a Veto.

The sales director wants a custom board-report export built immediately. A large prospect says it needs the feature before signing a three-year contract. The opportunity is substantial, and the request sounds specific enough to send straight to engineering.

Engineering sees more than an export button. The work needs new rules controlling who can use it and an audit trail recording relevant actions. The estimate is four weeks, using capacity already committed to a retention problem affecting existing customers.

Product has one prospect interview, no proof that the exact format is essential, and no authority to abandon the retention work. Procurement will confirm the requirements in ten days.

In this constructed case, protecting the backlog is not a sufficient response. Neither is accepting the feature before understanding what the company would give up. The useful contribution from Product is to make the commercial opportunity easier to pursue without hiding its cost to existing customers.

The request deserves a commercial answer

It is understandable that the sales director wants movement. A potential three-year contract is not merely an interruption to the team's plan. Responding as though the executive has broken a process rule would miss why the request matters.

At the same time, the prospect's preferred implementation and the outcome it needs are not necessarily identical. The board may need reliable figures in a particular presentation, while several ways of producing those figures remain possible. That is a question to investigate, not an assumption that a workaround will be accepted.

One interview provides a starting point. Procurement's confirmation can establish whether the exact export is a purchase condition, whether a smaller response would be acceptable, and which commitments the customer actually expects. Product Management's role in connecting customer needs, product direction, and feasible delivery makes this an investment conversation, not a contest over who controls the backlog. [2]

I would focus the next investigation on that purchasing condition. An open-ended discovery program would be hard to justify while a deal is moving, but four weeks of engineering would also be hard to justify if the company has not confirmed what the buyer will accept.

Existing customers are part of this deal's cost

The development estimate contains two useful pieces of information. The permission rules and audit trail explain why this is more than a button. The existing retention commitment explains where the four weeks would come from.

Neither automatically defeats the new feature. Leadership may decide the prospect deserves priority. But that choice should include the current customers whose problem would wait, rather than leave the team to absorb the displacement inside a sprint plan.

This is where a comparison becomes more useful than a veto. The full build offers one route to pursuing the contract, with known delivery displacement and continuing support implications. A smaller response might preserve more of the current plan, but only if the prospect accepts it. Maintaining the existing commitment protects the retention work while potentially affecting the commercial opportunity.

There is no free option hidden among those descriptions. The person who can accept the trade-off needs to see the same consequences that engineering and sales are discussing separately.

Use the ten days to answer the question that matters

Under these facts, I would recommend using the stated procurement window to verify the requirement and compare the smallest acceptable response before committing the full build. That recommendation could sound like this:

This contract is worth pursuing. Give us the ten days already set aside for procurement to confirm what the buyer will accept. We will compare a smaller response with the full export and show what each does to the retention work. Before we commit the four weeks, we need a clear decision on which customer commitment takes priority.

This is proposed wording for the case, not a conversation that has occurred. It gives the investigation a question and a return point without pretending that Product can approve the entire trade-off on its own.

Useful clarification can begin within the team's existing authority. A new external promise or a decision to abandon the retention work may need a different approval. Keeping those decisions separate lets people make progress instead of waiting for permission to investigate anything at all.

Learning first has a cost

The prospect may want a promise before the ten days are over. The staged recommendation does not guarantee that preferred timing, and preserving retention work during the window means the full export has not started merely because the opportunity is attractive.

That consequence belongs in the recommendation. If the requirement is confirmed and the commercial case justifies displacement, the full build may become the right choice. If a smaller response is accepted, the company may obtain a better route to the same opportunity. If the requirement remains uncertain, leadership should know that before making an irreversible promise.

Once a choice is made, the roadmap and customer expectations need to reflect it, including the work that now waits. [1] Product has then done more than agree or resist: it has turned an urgent request into alternatives the business can actually choose between.