A Product Extension Validated Before a Single Line of Code by Alexander KarlA Product Extension Validated Before a Single Line of Code by Alexander Karl
A Product Extension Validated Before a Single Line of Code
Bikeleasing.de's digital claims-management backoffice needed to handle additional damage types — a change touching processes, data and the daily work of claims processors. Building the wrong thing would be expensive; the client needed certainty before committing development budget.
What I did
Strategic product leadership — owned the content and strategic preparation of the product extension through a 10-week conception phase
Requirements analysis — analyzed technical requirements and evaluated existing processes for the new damage types
Roadmap development — turned the analysis into a robust product concept with detailed roadmap planning
Backlog construction — elaborated structured user stories and built a prioritized product backlog for efficient development cycles
User acceptance testing — planned and ran UAT with a team of claims processors; evaluated feedback, prioritized via MoSCoW, and handed findings over as clearly defined tickets
Process optimization — leveraged existing backend automation and documented workflows to reduce build effort
The result
A validated product concept, prioritized backlog and roadmap — development-ready after 10 weeks, with the people who process claims daily having already tested and shaped it.
Stack & methods: Jira, User Story Mapping, MoSCoW Prioritization, UAT
Like this project
Posted Jul 18, 2026
Business lead for a claims-management product extension: 10 weeks to a validated concept, prioritized backlog and a UAT-tested roadmap.