Keep the learning goal visible
A prototype helps test a risky assumption. Its value comes from what you learn, not how complete it looks. Write down the question it should answer and what evidence would change your mind. This prevents a convincing demonstration from being mistaken for a finished product.
List the production obligations
Before release, review validation, access controls, error handling, data storage and recovery. Decide what happens when a dependency is unavailable or a user repeats an action. These concerns are often invisible in a successful demo, but they shape the real experience.
Release a complete small journey
A first release does not need every planned feature. It does need a useful path from start to finish. Choose the smallest journey that delivers value, support it properly, and make the limitations understandable. Keep unfinished flows out of the public navigation.
Plan for the day after launch
Identify who watches errors, handles enquiries and decides what to improve. Keep deployment and rollback instructions close to the code. A release becomes a product through operation and learning, not simply by being available at a URL.
