From 45a26383e0ac8e2407d7b042a4dfc655cde4020f Mon Sep 17 00:00:00 2001 From: Nicolai Ort Date: Tue, 1 Apr 2025 16:52:43 +0200 Subject: [PATCH] docs(day0): Research talk --- content/day0/13:paap.md | 55 +++++++++++++++++++++++++++++++++++++++++ content/day0/_index.md | 6 +++++ 2 files changed, 61 insertions(+) create mode 100644 content/day0/13:paap.md diff --git a/content/day0/13:paap.md b/content/day0/13:paap.md new file mode 100644 index 0000000..fdc2acf --- /dev/null +++ b/content/day0/13:paap.md @@ -0,0 +1,55 @@ +--- +title: Platform as a Product +weight: 13 +tags: + - platform + - cloudnativecon +--- + + + +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 \ No newline at end of file diff --git a/content/day0/_index.md b/content/day0/_index.md index d31ee36..287c845 100644 --- a/content/day0/_index.md +++ b/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)