diff --git a/content/day0/08_product-thinking.md b/content/day0/08_product-thinking.md
new file mode 100644
index 0000000..9225014
--- /dev/null
+++ b/content/day0/08_product-thinking.md
@@ -0,0 +1,74 @@
+---
+title: Product thinking for cloud native engineers
+weight: 8
+tags:
+ - platform
+ - cloudnativecon
+---
+
+<!-- {{% button href="https://youtu.be/rkteV6Mzjfs" style="warning" icon="video" %}}Watch talk on YouTube{{% /button %}} -->
+
+## How & Why
+
+- IT was a cost center for a long time - not it's critical but still treated as a cost center
+- Why is it important: To much focus in the technical aspects instead of value delivery
+- Importance: Show the value of your work (which means your work has to provide value)
+- Operations and coordination work is not easily visible, but very important
+
+## Principles
+
+- Focus on user value: User problems > Solutions
+- Outcome (Value) > Output (Tickets closed)
+- Products (lifecycle and ownership) before projects (just setting stuff up)
+
+### User value
+
+- "Who is the user": Builders, Enablers, Regulatory, "Viewers"
+- "What is the value": Make the organization more efficient while avoiding risks
+
+## How to start?
+
+TODO: Steal illustration
+
+### Exploring the Problem Space
+
+Goals:
+- Identify top pains
+- Build empathy and understanding
+- Investigate key business aims
+
+Techinques:
+- Customer and stakeholder interviews: Talk to people, they will probably tell you about their pain
+- Data/Process analysis: Where are out bottlenecks
+- Shadowing: Really see how the day to day works
+- Ask "Why"
+- Read business updates (current goals)
+- Build dashboards that show progress and value
+
+### Defining the problem space
+
+Goals:
+- Identify opportunities
+- Prioritise
+- Gather insignts and data
+
+Techniques:
+- Value stream mapping
+- RICE, Value vs Effort or ather cost benefit analysis
+- Analyse your exploration process
+
+## Did we reach our goal?
+
+### Product metrics
+
+- Someone will measure your work, hope they do it right or rather do it yourself to show how you provide value
+- Product metrics should measure outcome not output (or performance metrics)
+- Baseline: You need to know the desired outcome
+
+
+### Frameworks
+
+- DevEx: Triangle of flow state (build&test speed), feedback loops () and cognitive load (code complexity, docs clarity)
+- DORA
+- SPACE
+- DX Core 4
diff --git a/content/day0/_index.md b/content/day0/_index.md
index 619860b..1be04ed 100644
--- a/content/day0/_index.md
+++ b/content/day0/_index.md
@@ -11,6 +11,7 @@ This year I spent most of my time at the platform engineering day.
 
 - [So you want to hire for platform engineering](../06_hire-engineers)
 - [The past, the present and the future of platform engineering](../07_past-present-future)
+- [Product thinking for cloud native engineers](../08_product-thinking)
 
 ## Other stuff I learned or people i talk to