Development, Staging, and Production
Development supports active building, staging provides a production-like review environment, and production serves real users and data. 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.
- Ask a consultant for evidence rather than reassurance.
A founder has a working application and needs a proportionate way to run, monitor, and recover it.
Development supports active building, staging provides a production-like review environment, and production serves real users and data.
A consultant can recommend and implement the technical approach. The founder still needs to decide which outcome matters, which risk is acceptable, and what evidence is sufficient.
The Practical Question
A founder has a working application and needs a proportionate way to run, monitor, and recover it.
The immediate question is development, staging, and production. The technical label matters only because it changes a product decision, a responsibility, or the evidence required before launch.
Technical term
Development, Staging, and Production
Development supports active building, staging provides a production-like review environment, and production serves real users and data.
Treat it like a clause in a commercial agreement: its value comes from making expectations and consequences clear, not from sounding formal.
What a Sound Approach Establishes
Start with the product consequence, then choose the simplest technical treatment that protects it. A longer tool list is not a stronger plan.
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.
- Make the decision explicit: Separate environments when the consequence of testing against live users or data justifies the added operating cost.
- Ask what evidence would show that the chosen approach works.
- Name the person or provider responsible when the approach fails.
- Record the result in the deployment and operations plan.
A Decision Framework
Separate environments when the consequence of testing against live users or data justifies the added operating cost.
The principal risk is that experiments, test messages, or destructive changes affect real customers. This does not require the most expensive possible solution. It requires the consequence to be understood and the control to match it.
- 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 Confidence Should Be Based On
Warning Signs
- Nobody can explain how development, staging, and production changes a user or business outcome.
- The proposal does not address this risk: experiments, test messages, or destructive changes affect real customers.
- The only evidence is a successful demonstration of the easiest path.
- The decision has no named owner, boundary, or review point.
- A provider-specific feature is being mistaken for a permanent product requirement.
Questions to Ask a Consultant
- What decision are we making about development, staging, and production?
- Which user or business outcome does the recommendation protect?
- How have we reduced or accepted this risk: experiments, test messages, or destructive changes affect real customers.
- What evidence can I review without relying on the original implementer?
- What is deliberately deferred, and when will it be reconsidered?
- Who owns the accounts, data, documentation, and recovery process?
Key takeaway
Key Takeaway
Development supports active building, staging provides a production-like review environment, and production serves real users and data. The founder's job is to make the consequence explicit; the consultant's job is to recommend and demonstrate a proportionate implementation.