What is a deployment? A plain-English guide
Your team says the feature is "done" but not "deployed". Or a deployment is planned for Thursday evening. What does that actually mean?
The simple definition
A deployment is the moment new or changed software is put where people can use it. Until code is deployed, it exists only on developers' computers or test systems.
Words you will hear
| Term | Plain meaning |
|---|---|
| Environment | A copy of the system: development, testing (staging) or live (production) |
| Production | The live system real customers use |
| Staging | A rehearsal copy that looks like production, for final checks |
| Release | Making features available to users; sometimes the same as a deployment, sometimes not |
| Rollback | Undoing a deployment by going back to the previous version |
| Hotfix | A small, urgent fix deployed outside the normal schedule |
How a typical deployment works
- Code is reviewed by another developer.
- Automated tests run to catch obvious problems.
- It goes to staging for a final check.
- It is deployed to production, often automatically.
- The team monitors for errors after it goes live.
Many teams deploy small changes often, sometimes several times a day. Smaller deployments are usually less risky, because there is less to go wrong.
Deployed is not always released
Some teams hide new features behind a switch called a feature flag. The code is deployed but turned off, then released to users when everyone is ready. This lets a team separate the technical step from the business launch.
Questions managers can ask
- What could go wrong, and how would we know?
- How quickly can we roll back if needed?
- Do support or customers need to know before it goes live?
- Is anyone available to watch the system afterwards?
Those four questions show you care about risk without needing to read a line of code.