Apidays Virtual Helsinki 20 - Marjukka Niinioja, Osaango
summary
A lean cycle called APIOps Cycles turns customer journeys into concrete APIs by running strategy -> prototyping -> build -> developer experience iterations, using an API value proposition canvas and a business impact canvas to map who needs what. Applied to Finnish water services it finds an existing public pipeline API and Platform of Trust integrations for smart meters, spots a missing installations-order API to build, assesses per-API risks (safety, regulation, uptime) and claims a small prototype can be coded and validated in a day. The method is open-licensed and meant for mixed business+tech workshops.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:07About Marjukka
- 2:04About API Development
- 2:47API Development Cycle
- 4:36Customer Journey
- 6:23Goals
- 7:45Technical Needs
- 9:20Traditional Customer Journey
- 10:54Changing Perspective
- 11:06API Cycles Method
- 12:57API Value Proposition Canvas
- 13:07API Consumer Needs
- 13:19Gains
- 13:44Realtime schedules
- 13:57Pain points
- 14:23Problems
- 14:59API Provider
- 15:18API Consumer
- 15:42Customer Needs
- 16:16Data Hub
- 16:39Services
- 17:50Order API
- 18:08Water Meter Data
- 18:46Who needs to be discussing
- 20:13Business model
- 22:35Templates
- 23:26Business Impact Canvas
- 24:34Location Data Systems
- 27:20Learn more
related talks
24mPractical API Strategy with APIOps Cycles
23mOpen method for Lean & Business-oriented API design APIOPs Cycles
13mFrom Chaos to Clarity: Designing (AI-Ready) APIs with APIOps Cycles
16mMaster API Product Design with APIOps Cycles Method
54mAPI's a drivers for innovative business models
19mAvoiding the 8 Wastes of Lean API Development with OpenAPI & APIOps.
02mApidays India 2025 Highlights
24mFixing API Chaos: A Practical, Open Method to Structure API Work