Technical Business Analysis
Business–IT bridge with delivery ownership
- ✓Eliciting, structuring and prioritising requirements with business and engineering
- ✓Translating process and product needs into technically feasible solution options
- ✓Making dependencies, risks and trade-offs visible for decision-ready foundations
- ✓Facilitating alignment between stakeholders, product and delivery teams
- ✓Validating scope early — including controlled no-go when the business case does not hold
Quick Facts
- Focus
- Technical business analysis & requirements
- Location
- Lucerne (CH), available nationally
- Work model
- Remote / Hybrid / On-site
- Availability
- immediately (flexible)
- Capacity
- 80–100%
- Languages
- German (native), English & Spanish (business fluent)
Work permit: Switzerland (unrestricted)
My understanding of technical business analysis
Clarity, feasibility & decision-making
What I take on as a technical BA
From requirements to decision-ready solutions
Discovery & problem framing
Clarify context, users/stakeholders and business goals before solutions are built.
Requirements structure & prioritisation
Sharpen epics/user stories, acceptance criteria and priorities so delivery becomes plannable.
Solution options & trade-offs
Compare technical and business options including effort, risk and value.
Business–IT alignment
Workshops and decision briefs that bring business and engineering onto the same scope.
Scope validation & go/no-go
Test assumptions early; stop in a controlled way when the business case does not hold.
Handover into delivery
Clear work packages, dependencies and acceptance logic for implementation and UAT.
Methods & tools
For structured analysis, alignment and handover into delivery
Proof from real projects
Selected cases that show how this focus looks in practice.
References from the collaboration
From collaboration in delivery and platform ownership
Martin played an important role at the interface between management, engineering, operations, and external stakeholders. He helped us bring structure to complex platform and operations topics, supported the development of our engineering team, and created clear decision-making materials around priorities, risks, resources, and implementation options. What stood out was his ability to translate technical platform challenges into management-relevant decisions while keeping business goals and operational stability in focus. Martin was a reliable, structured, and trusted partner throughout our collaboration.
Ich habe mit Martin 1,5 Jahre in einem agilen cross-funktionalen Team bei OTTO zusammengearbeitet. Wir verantworten einen sehr wichtigen Teil des live-Shops und arbeiten mit einer Vielzahl live-kritischer Teams direkt zusammen. Martin war bei uns in einer Rolle mit technischer Verantwortung und Delivery-Fokus eingesetzt. Die Zusammenarbeit mit ihm empfand ich als sehr wertvoll. Er lieferte inhaltlich ab, war ein toller Sparringspartner, half an jeder Stelle, konzipierte Lösungen, setzte sie um, fixte Bugs und war immer einer der ersten, der sich meldete, wenn ein Freiwilliger gesucht wurde. Martin war ein großer Fan unseres Teams, wobei sich sein Enthusiasmus von Beginn bis zum Ende des Einsatzes durchzog. Er war immer gut erreichbar und ansprechbar. Kulturell schaffte er in schwierigen Zeiten durch seine angenehm ruhige Art eine wichtige Balance im Team. Mit großer Motivation stürzte er sich in längere Umbauten und zog diese bis zum Ende durch. Dabei konnte er z.B. sein SEO-Know-How einbringen und sprach sich ohne Betreuung mit Kollegen aus anderen Teams ab. Es war eine super Zeit, gerne wieder!
Core competencies
Technically grounded analysis at the business–IT interface
Need a technically grounded business analysis?
Happy to discuss how I can structure requirements and drive decisions between business and IT.