Development, Staging, and Production
Can the team operate this service after launch with the people, access, budget, and recovery time it actually has? Separate environments when the consequence of testing against live users or data justifies the added operating cost.
What You Will Be Able to Decide
- Explain development, staging, and production in product and business terms.
- Apply this decision: Separate environments when the consequence of testing against live users or data justifies the added operating cost.
- Recognise this material risk: experiments, test messages, or destructive changes affect real customers.
- Use this review: Ask a second operator to deploy the dashboard, find a failed request in logs, and roll back a deliberately broken release.
A founder has a working application and needs a proportionate way to run, monitor, and recover it. This lesson gives you a concrete question to take into a build brief, proposal review, or product decision.
Can the team operate this service after launch with the people, access, budget, and recovery time it actually has? The course example is A small SaaS dashboard with a public marketing site; use it to decide what evidence would justify the choice before a builder implements it.
What Does Development, Staging, and Production Mean for Your Product?
A founder has a working application and needs a proportionate way to run, monitor, and recover it.
Use the illustrative service for this course (A small SaaS dashboard with a public marketing site) to make the choice concrete. Can the team operate this service after launch with the people, access, budget, and recovery time it actually has?
Technical term
Development, Staging, and Production
Development supports active building, staging provides a production-like review environment, and production serves real users and data.
How Should a Founder Use Development, Staging, and Production?
For a small saas dashboard with a public marketing site, ask what would happen if experiments, test messages, or destructive changes affect real customers.
For this decision, the useful standard is that the team knows where the product runs, who operates it, and how service is restored after failure.
- Decision: Separate environments when the consequence of testing against live users or data justifies the added operating cost.
- Evidence to request: show that the team knows where the product runs, who operates it, and how service is restored after failure.
- Owner: name who will respond if experiments, test messages, or destructive changes affect real customers.
- Record the result in the deployment and operations plan.
- Practical review: Ask a second operator to deploy the dashboard, find a failed request in logs, and roll back a deliberately broken release.
How Do You Choose an Approach to Development, Staging, and Production?
Can the team operate this service after launch with the people, access, budget, and recovery time it actually has? Separate environments when the consequence of testing against live users or data justifies the added operating cost.
The risk is that experiments, test messages, or destructive changes affect real customers. Compare a simpler option with the proposed one, including who will operate either choice.
- Describe the user or business outcome that must be protected.
- Identify the most credible failure and its consequence.
- Compare the simplest adequate approach with one realistic alternative.
- Set a review point for when the decision may need to change.
What Evidence Should You Accept for Development, Staging, and Production?
What Warning Signs Should You Look For?
- The proposal does not address this risk: experiments, test messages, or destructive changes affect real customers.
- Nobody can show whether the team knows where the product runs, who operates it, and how service is restored after failure.
- The decision has no named owner or review point.
What Should You Ask a Consultant?
- What changes for the user if we choose this approach to development, staging, and production?
- How have we reduced or accepted this risk: experiments, test messages, or destructive changes affect real customers.
- Can you demonstrate that the team knows where the product runs, who operates it, and how service is restored after failure?
- Who owns the result, and when will we reconsider it?
Key takeaway
Key Takeaway
Separate environments when the consequence of testing against live users or data justifies the added operating cost. Ask for evidence against the specific risk: experiments, test messages, or destructive changes affect real customers.