diff --git a/data/workshop/exercise4.mdx b/data/workshop/exercise4.mdx
index 06f9ac5..dcc317b 100644
--- a/data/workshop/exercise4.mdx
+++ b/data/workshop/exercise4.mdx
@@ -92,6 +92,22 @@ From here it is trivial to perform a **Rollback** to remove our misconfigured up
 </Zoom>
 
 
-
+## 4.4 - Rollback to a previous helm release
+
+Our previous helm upgrade for the Gitea application didn't succeed due to the misconfiguration we supplied. **Helm** has features for rolling back to a previous release through the `helm rollback` command line interface. OpenShift has made this even easier by adding native support for interactive rollbacks in the OpenShift web console so let's give that a go now.
+
+Start in the **Helm** view of the **Developer** perspective.
+
+In the **Helm Releases** tab you should see one release called `gitea`.
+
+Click the three dot menu to the right hand side of the that helm release and click **Rollback**.
+
+Select the radio button for revision `1` which should be showing a status of `Deployed`, then click **Rollback**.
+
+<Zoom>
+|![helm-rollback](/ocp-app-delivery-workshop/static/images/helm-rollback.gif) | 
+|:-------------------------------------------------------------------:|
+| *Rolling back to a previous gitea helm release*                     |
+</Zoom>
 
 
diff --git a/public/static/images/helm-rollback.gif b/public/static/images/helm-rollback.gif
new file mode 100644
index 0000000..194fabf
Binary files /dev/null and b/public/static/images/helm-rollback.gif differ