Can a 90% deployment claim retire the old service?
Distinguish delivery, adoption and a cash saving.
“Provides a centralized roadmap to track timelines, launches, and impact” (opens the source)
The question
A programme serves 120 internal client teams. It has deployed the new API to 108. Ninety teams send their production traffic through it; 18 have configuration but no production traffic. Twelve still use only the old API. The programme claims 90% adoption and a $24,000 monthly saving.
| Teams | |
|---|---|
| New API production traffic | 90 |
| Configured, no production traffic | 18 |
| Old API only | 12 |
The three groups are disjoint and total 120 teams.
Retirement requires all 120 teams on the new API, zero old-API traffic for 14 consecutive days and service-owner sign-off. The $24,000 monthly licence ends only after formal notice; the notice period is one full month.
“Correct the report and choose evidence for the retirement decision.”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Separate the measures
What would you do here? Open the move you’d make.
Report 90% deployed and 75% active separately.
The strong move. Configuration is delivery evidence, not proof of use.
Call the configured group active.
Tempting, but it misses something. The 18 configured teams send no production traffic and are not active users.
See how a strong candidate says it
“Deployment is 108/120 = 90%. Active adoption is 90/120 = 75%. Thirty teams are not yet sending production traffic through the new API.”
Why it works: Configuration is delivery evidence, not proof of use.
Step 2: Work across the missing teams
What would you do here? Open the move you’d make.
Track migration blockers and accepted usage evidence.
The strong move. The two groups need different work before the shared service can close.
Close the programme when all deployments are complete.
Tempting, but it misses something. Deployment does not establish 14 days without old-API traffic or service-owner acceptance.
See how a strong candidate says it
“I would separate the 18 configured teams from the 12 still on the old API, then name their blockers and migration owners. Old-API traffic and service-owner acceptance must remain visible at programme level.”
Why it works: The two groups need different work before the shared service can close.
Step 3: Hold the retirement claim
All 120 teams now send production traffic through the new API. The old API has recorded zero traffic for ten consecutive days. No retirement notice has been sent.
What would you do here? Open the move you’d make.
Complete the zero-traffic window and sign-off first.
The strong move. Active use does not establish that the old dependency is gone.
Claim the saving as soon as the last team activates.
Tempting, but it misses something. Ten quiet days do not meet the 14-day gate, and no cancellation notice has been sent.
See how a strong candidate says it
“All 120 teams are active, but the zero-traffic run is only ten days. The 14-day gate is not yet met. I would wait at least four more consecutive days and obtain sign-off before sending notice.”
Why it works: Active use does not establish that the old dependency is gone.
Step 4: Track cash after the gate
What would you do here? Open the move you’d make.
Separate forecast savings from the bill that actually stops.
The strong move. A delivered benefit and a realised cash saving have different dates.
Book the saving on the deployment completion date.
Tempting, but it misses something. The full notice month is still billed; deployment does not stop the licence charge.
See how a strong candidate says it
“After the gate and sign-off, notice starts a full month of licence cost. I would forecast the $24,000 monthly saving after that notice period, then verify that billing ends.”
Why it works: A delivered benefit and a realised cash saving have different dates.
The answer, in short
- Decision
- Keep retirement open until its evidence and notice gates finish.
- Because
- Deployment, active use, old-service silence and cancelled billing are separate facts.
- What would change it
- Four more clean days, sign-off and the notice process can change the retirement and savings dates.
Common traps
- Calling configuration adoption.
- Claiming savings before billing stops.
Check your answer
- I separated deployment and use.
- I found all 30 inactive teams.
- I applied the 14-day gate.
- I kept the notice cost visible.
Last reviewed Nov 10, 2026