03
Streaming infrastructure · Product Owner · SWR/ARD, Audio/Video Competence Center
Starting point
Millions of requests per day. No clear use case.
Part of the scope had long been covered by other products. The only developer did not know what to work on — and a mistake would have meant black screens in the ARD player.
Critical infrastructure, inconspicuously packaged
Mil./day
requests in the millions, partly because the iOS subtitles ran entirely through the service
1
developer carried all the knowledge — a classic single-person bottleneck
From sprawl to a plan
Result
A directionless project became a service with a clear purpose.
A safeguarded operation, and knowledge that no longer depends on a single person.
What I take away
Not every important project looks important. Sometimes an inconspicuous side service turns out to be infrastructure carrying millions of requests. The first step is not a feature but the question: what is this actually here for?