Move a prototype into dependable production

Review the boundaries, operating controls, and release process a working prototype needs before people depend on it.

2 min read

Define what the release must support

A prototype demonstrates a possible experience. A production release needs a documented scope: who can use it, which workflows are supported, and what happens when an input or dependency fails. Review the shortcuts made during development, including sample data, temporary accounts, and manual steps. Confirm which need to be replaced before launch. Use realistic data shapes and volumes in a separate test environment. Agree acceptance criteria with the person responsible for the service so the release decision reflects business needs, rather than whether the main demonstration still works.

Prepare for mistakes and interruptions

Check authentication, authorisation, input validation, and handling of sensitive information. Keep credentials outside application code and use the minimum access each integration requires. Identify operations that need duplicate protection, safe retries, or a human review step. Decide what users see when a dependency is unavailable and how support staff investigate the incident. If the service stores important data, verify a backup can actually be restored. Define useful logs and alerts without collecting unnecessary personal information. Test the failure paths that could lose work, create duplicate actions, or expose the wrong records.

Make the release reversible

Build and deploy through a repeatable process with clear versioning and documented configuration. Confirm that the hosting environment supports the expected traffic, storage, and background work. Check accessibility and the devices your users rely on. Prepare a rollback plan, including what happens to any data written by the new version. Assign an owner for alerts, support, dependency updates, and operating costs. Start with a controlled release and review evidence from actual usage. Expand access once the application meets its agreed acceptance criteria and the team can operate it without relying on undocumented developer knowledge.