docs(day0): Lego talk

content/day0/13:paap.md

@@ -0,0 +1,55 @@
+---
+title: Platform as a Product
+weight: 13
+tags:
+ - platform
+ - cloudnativecon
+---
+
+<!-- {{% button href="https://youtu.be/rkteV6Mzjfs" style="warning" icon="video" %}}Watch talk on YouTube{{% /button %}} -->
+
+The CNCF's research into product thinking for platforms.
+
+## But why
+
+- Get insights into the current product thinking practives of platform builders
+- Topics: Needs/Paintpoints/Behaviour
+- Target: Create personas based on insights
+- Find out what people are doing, not hew they are doing
+
+## How?
+
+- Survey for quantity
+- Interviews for quality
+
+## Challenges
+
+- Asking questions without sugessting answers
+- Consensus on research goals
+- Motivation and time investment (on interviewer and interviewee side) + Non-Responses
+- Toolsing: There is no standard tooling at the CNCF for this kind of research
+- Small sample size -> No real research insights, just signals/hints
+
+## Analysis
+
+- Working with assumptions was hard in combination with the small sample size
+- Survey: Survey Tool (Google Forms) combined with a whiteboard tool for clustering and analysis
+- Interviews: They used ai for time efficiency but the prompt escalated a bit leading to no real time gain -> But you can scale the same prompt to infinite sample sized
+- Challemnge: AI confidently churns out wrong answers -> Use source links to verify and scoping 
+
+TODO: Steal worklow from slides
+
+## Outcome/Signals
+
+- Platform Orgs use Prioritization Frameworks onconsciously: "We don't use product management and tools like that" -> Well you do, you just don't call it PM and are a bit unstructured
+    - Structured Activities: Interviews (talking to each other), Focus groups, quantitative data, ...
+    - Roadmap influence: Insight, prioritization, painpoints, backlogs
+    - Regular planning meetings
+- Platform orgs struggle to define and actually implement measures of success: Measure activity over impact, success is often felt instead of proved
+- Platform teams have varied control over their work: Depndening on company size and business relationships
+
+## Future
+
+- Baseline: They have some signals
+- Question: Are these pattern successfull
+- Needed: More data and better organization

content/day0/14_lego.md

@@ -0,0 +1,57 @@
+---
+title: Building Platforms with empathy and yaml at the lego group
+weight: 14
+tags:
+ - platform
+ - cloudnativecon
+---
+
+<!-- {{% button href="https://youtu.be/rkteV6Mzjfs" style="warning" icon="video" %}}Watch talk on YouTube{{% /button %}} -->
+
+Very nice kids playing with lego intro analogy about creativity, sharing and colaboration.
+
+## The golden brick
+
+- The brick could get picked up and sometimes picking it up is mandatory
+- Devemopment in close colab and trust with users
+- Focus on good enough instead of perfect but everyone is unhapy
+
+### Guidelines
+
+- API first: Define a speration beween users and services with abstractions
+- Self services: Freedom of choice and combination
+- Constraints that are soft and can be modified on feedback
+
+### Offers
+
+- Kubernetes as a service
+- Runtime as a Service: NAmespace as a service with argo and without cluster access
+    - Problem: Users want kubeapi access
+    - Method: Talk with the users
+    - Solution: Zero Trust proxy that provides operational access to kubeapi via OIDC
+- There are multiple APIs that can be combined -> You need constraints
+
+### What's needed
+
+- Conversation
+- Trust
+- Striking a balance
+
+## The human aspect
+
+- Treat people as colleagues instead of customers
+- Build empathy to reach a ballanced "good enough"
+- Lead with transparency: Publish your metrics
+- Visit their context
+- Explore unknowns together
+- Create a shared understanding of challenges
+
+### Team culture
+
+- Know who you are helping an who helps you
+- Empower them to shine by getting to know their context
+- Hear them out in small meetings ore in person
+
+## Platform maturity
+
+TODO: Steal maturity chart

content/day0/_index.md

@@ -8,6 +8,12 @@ Day 0 of KubeCon aka CloudNativeCon aka the day on which the co-located events h
 This year I spent most of my time at the platform engineering day (with a short visit to argocon).
 The emerging motto of platform engineering day was "platform as a product".
 
+This was the third conference day (fourth travel day) and in the afternoon i started to feel the brain-overflow.
+But powewring through I ended up attending two keynotes (no notes, they were pretty much a welcome and goodbye) and 14 talks.
+
+And most importantly: This is the day my friends an coworkers joined (they are only in town for kubecon, not for rejekts).
+Sometimes we ended up in the same talks, sometimes in different talks which lead to a rich set of talk notes.
+
 ## Talk recommendations
 
 - How to design a good hireing process: [So you want to hire for platform engineering](../06_hire-engineers)
@@ -15,6 +21,7 @@ The emerging motto of platform engineering day was "platform as a product".
 - How to design a good product: [Product thinking for cloud native engineers](../08_product-thinking)
 - Staging with gitops: [A million ways to promote changes between environments](../09_promotions)
 - How to handle abstractions and new requriements: [Platform abstractions: Asset or liability](../10_abstractions)
+- Very nice slides: [Building Platforms with empathy and yaml at the lego group](../14_lego)
 
 ## Other stuff I learned or people i talk to