Productionize a Successful Proof of Concept

# Productionize a Successful Proof of Concept Explain how you would take a successful proof of concept into production. The prototype demonstrates feasibility but may lack reliability, security, scalability, operability, and clear ownership. Describe how you decide what must change and how you release it safely. ### Constraints & Assumptions - Preserve the learning from the prototype without assuming its code or architecture is production-ready. - Production acceptance must include failure behavior and operations, not only the happy path. - Migration and rollback need explicit data and compatibility boundaries. ### Clarifying Questions to Ask - What user outcome did the prototype prove, and what evidence defines production success? - What load, availability, security, compliance, and support requirements apply? - Is replacement, incremental hardening, or a parallel rebuild acceptable? ```hint Turn unknowns into release gates Inventory the gaps, rank them by consequence and uncertainty, and attach an observable acceptance check to each critical one. ``` ### What a Strong Answer Covers - Requirements, architecture review, and build-versus-rewrite reasoning. - Data integrity, security, testing, capacity, and dependency readiness. - Observability, runbooks, ownership, support, and cost controls. - Staged rollout, compatibility, rollback, and post-release validation. ### Follow-up Questions - When should the prototype be discarded rather than hardened? - How would you migrate users without running two inconsistent sources of truth?