Business Analysis

Analysis that enables decisions

Good analysis is not a documentation exercise. It's about understanding the right thing – before building begins. I gather requirements in a structured way, identify contradictions early and translate business needs into technically feasible solutions. This saves time, money and frustration.

From requirement to solution

I work as a bridge between business and technology – in roles as business analyst, proxy product owner or solution architect. This includes requirements engineering, process modelling, utility analyses and the preparation of decision documents for C-level. Whether SharePoint, Power Platform, ERP or custom developments – I speak both languages.

When business analysis creates clarity

Many IT and change initiatives start with a solution before the actual problem is sufficiently understood. Requirements are not yet clear, business and IT view the situation from different perspectives, or several solution paths are under discussion. Business analysis creates the foundation for well-informed decisions. I structure requirements, processes and relationships, make dependencies visible and help evaluate business and technical options transparently. The goal is not as much documentation as possible. It is about creating enough clarity for the next good decision before time, budget and resources are invested in a solution.

From analysis to implementation

A good analysis does not end with a document. Its results must be clear and robust enough to lead to decisions and concrete next steps. Depending on the situation, this ranges from requirements engineering and process modelling to solution design and decision support to acting as a proxy product owner. When analysis leads to a complex initiative, responsibility can seamlessly transition into project management or digital transformation.

Analysis in practice

The following examples show how structured analysis has led to concrete decisions and actionable results.

Selected references