diff --git a/docs/pages/docs/core-concepts/why-turborepo.mdx b/docs/pages/docs/core-concepts/why-turborepo.mdx
index 5d015076aa161..312a05a8279c8 100644
--- a/docs/pages/docs/core-concepts/why-turborepo.mdx
+++ b/docs/pages/docs/core-concepts/why-turborepo.mdx
@@ -2,10 +2,14 @@
 
 ## The problem
 
+![](../../../public/images/docs/why-turborepo-problem.png)
+
 Monorepos have many advantages - but **they struggle to scale**. Each workspace has its own test suite, its own linting and its own build process. A single monorepo might have **hundreds of tasks to execute**.
 
 ## The solution
 
+![](../../../public/images/docs/why-turborepo-solution.png)
+
 **Turborepo solves your monorepo's scaling problem**. Our remote cache stores the result of all your tasks, meaning that **your CI never needs to do the same work twice**.
 
 Task scheduling can be difficult in a monorepo. Imagine `yarn build` needs to run before `yarn test`, across all your workspaces. Turborepo **can schedule your tasks for maximum speed**, across all available cores.
diff --git a/docs/public/images/docs/why-turborepo-problem.png b/docs/public/images/docs/why-turborepo-problem.png
new file mode 100644
index 0000000000000..4e0549648d796
Binary files /dev/null and b/docs/public/images/docs/why-turborepo-problem.png differ
diff --git a/docs/public/images/docs/why-turborepo-solution.png b/docs/public/images/docs/why-turborepo-solution.png
new file mode 100644
index 0000000000000..7e763defb2b05
Binary files /dev/null and b/docs/public/images/docs/why-turborepo-solution.png differ