Case study
What it takes to improve a live service while also moving it to the cloud
RtaNCa, MVP discipline, and the product reality of migration under pressure
Live services do not pause while strategy catches up. This piece reflects on product work in RtaNCa where user-facing improvement, backlog pressure, governance expectations, and AWS migration all had to move together.
There is a clean version of product management where roadmap work, platform work, and service operations can be neatly separated. In live services, that separation rarely holds.
In live services, the separation between roadmap work, platform work, and operations rarely holds — the product question is what moves without lying about risk.
The RtaNCa context required continual improvement while the service was already in active use. User needs did not pause because migration work was underway, and migration risk did not disappear because users needed immediate improvements.
User-management functionality became a practical MVP discipline test. The question was not how much we could ship, but which changes reduced meaningful friction without creating avoidable continuity risk.
The AWS migration mattered, but not as a standalone technical milestone. Its product value depended on decision quality, close collaboration with developers, and transparent trade-off framing.
Moving from Scrum to Kanban was a pragmatic response to work shape, not ideology. With live interruptions, variable task sizing, and dependency-driven flow, Kanban gave clearer visibility and reduced process friction.
Avoiding analysis paralysis mattered. We needed enough certainty to move responsibly, but not so much pre-analysis that value stalled. Stakeholder confidence came from explicit reasoning, not from false certainty.
The migration delivered cost savings and improved resilience, but the deeper lesson was about maturity under constraint: product work includes service posture, infrastructure decisions, and the discipline to keep moving with coherence.