# Release Engineering The release process is the final step before getting your product into the hands of the customers. CI/CD, Phased rollouts, monitoring, alerting, and greater visibility into the system all make the release and post-release process smoother. Keeping this phase manual leaves a lot of chance and human error. Automating this process ensures there is no duplicate work or mistake. Release automation enables you to control the user experience. It gives you insights into how the system performs, how it is being used, and what your user's experience is. Your release engineering determines the impact of all the hard work put into creating the features that go into a release. Instead of your releases being 0 or 1, good release management ***allows*** them always to become 1***.*** In this section, we'll take you through a few practices followed at Wednesday to make releases smooth. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://playbook.wednesday.is/engineering-playbook/release-and-delivery.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.