Introduction
YONO 2.0 launched in December 2025, and SBI said all existing users would move to the new version in phases over six to eight months, supported by thousands of digital support staff in branches. Migration has not been painless: users have reported re-registration issues, mobile number linking problems and features that worked differently from the old app. The product team now faces a choice: set a firm date to shut down YONO Classic and force the remaining users to move, or keep both apps running and let users migrate when they are ready. Both options carry real costs. I'll clarify the context, identify the trade-off, understand the product, agree a hypothesis, choose metrics, design an experiment, plan the analysis, set a decision framework and give a recommendation.
Migrations are a classic platform trade-off: the cost of running two systems versus the cost of disrupting users. Quantify both sides instead of arguing from principle.
Step 1
Clarifying Questions (3 minutes)
Why it matters: It sizes the risk of a forced cut-over. Expected answer: Hypothetically 3 crore monthly active users, skewed older and semi-urban. Impact on approach: A forced move affects a large, vulnerable group.
Why it matters: Dual running has engineering, security and support costs. Expected answer: Every new feature or regulatory change must be built twice; security patches double; teams estimate 25–30% of YONO engineering capacity goes to maintaining Classic. Impact on approach: Delay is expensive.
Expected answer: 85% of users who try to migrate succeed on the first attempt; the rest need help, often at a branch.
Expected answer: Some new RBI authentication requirements are being built only in YONO 2.0, which makes Classic harder to keep compliant over time.
Expected answer: Avoiding a public outage or complaint wave matters as much as cost.
Practice similar questions
Subscribe to access the full answer
.png){kind=logo}
