diff --git a/content/blog/ci-shootout-conclusion.md b/content/blog/ci-shootout-conclusion.md
index 96f123b8..064af102 100644
--- a/content/blog/ci-shootout-conclusion.md
+++ b/content/blog/ci-shootout-conclusion.md
@@ -1,7 +1,7 @@
 ---
 author: Daniel Jones
 date: "2022-01-14"
-heroImage: /img/blog/shootout-third-person.jpg
+heroImage: /img/blog/ci-shootout/goodbadugly.jpg
 title: "CI Shootout: Conclusion"
 draft: true
 heading: Our
@@ -9,6 +9,12 @@ headingBold: blog
 Description: Get the very latest updates about recent projects, team updates, thoughts and industry news from our team of EngineerBetter experts.
 ---
 
+<figure>
+    <figcaption style="font-size: .75em; font-style: italic;">
+    The Good, The Bad, The Ugly by <a href="https://www.flickr.com/photos/kaptainkobold/1021866852">Alan</a>
+    </figcaption>
+</figure>
+
 When should you use Jenkins, Concourse, Tekton or Argo Workflows? What work is each suited to, and what limitations do they each have? How will your choice of CI server affect the way that you work?
 
 After comparing them on a variety of fronts, in this article we comment on how these systems differ and which you should use.
diff --git a/static/img/blog/ci-shootout/goodbadugly.jpg b/static/img/blog/ci-shootout/goodbadugly.jpg
new file mode 100644
index 00000000..7c3700f8
Binary files /dev/null and b/static/img/blog/ci-shootout/goodbadugly.jpg differ