A product feature is being retired, but a renewing customer depends on it and cannot migrate in time. What would you recommend?

Instruction: Use the actual retirement policy, supported alternatives and customer dependencies. An exception or contract change requires the relevant owner’s approval.

Context: It assesses a supported transition and the option of not renewing, rather than assuming a commercial promise can solve a product lifecycle conflict.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I'd verify the retirement date, the customer's dependency and which alternatives are supported. I'd ask what makes migration infeasible: missing functionality, limited capacity, another system or an internal approval. That determines whether we need a technical solution, extra migration support or a different commercial decision...

Upgrade to view official answer

Related Questions