Analyse the current situation and process
Participants, current workflows, weak points, rules and business objectives are captured in a structured way.
I connect the business unit, product owner, development and operations – from process analysis through unambiguous requirements to acceptance and rollout.

Many projects start with solutions before the objective, the process and the business rules are properly understood. I make sure requirements become testable, prioritised and equally understandable for development and the business unit.
Participants, current workflows, weak points, rules and business objectives are captured in a structured way.
Business expectations are turned into workable requirements, use cases and traceable acceptance criteria.
Queries, changes, testing, approvals and introduction are consistently aligned with the original objectives.
Business analysis is not a pure documentation role. It creates decisions: which requirement contributes to the objective? Which rule is mandatory? Which dependency has to be resolved before development starts?
I facilitate this clarification and document the results so that product owner, development, test and the business unit work to the same expectation.
Depending on the context I use process models, workshops, interviews, use cases, user stories, acceptance criteria, decision matrices and structured functional specifications. What matters is not the format but shared understanding.
The artefacts stay as lean as possible and as detailed as necessary.
Benefits, affected processes, participants and guard rails.
Prioritised and traceable business requirements.
Testable criteria for testing, business acceptance and approval.
Benefits, effort, risks and a basis for decisions.
If requirements are unclear or get lost between the business unit and development: describe the initiative and its phase. You will get an assessment of how to structure the requirements so they are ready for delivery.
Discuss your project