What Does a Business Analyst Actually Do? The DACH Mittelstand Reality

What is a business analyst? — Role, tasks, demarcation

The formal definition for Germany comes from the BERUFENET profile of the Federal Employment Agency: business analysts examine processes, identify weaknesses, and define new structures, processes, and IT systems. In 2023 IIBA decided against a monolithic v4 and announced a modular ecosystem — v3 remains the valid reference as of 2026.

Five task areas shape the role: requirements elicitation (workshops, interviews, observation), process analysis (capture of as-is processes, BPMN modelling), documentation (use cases, user stories, acceptance criteria, written and reviewable), stakeholder management (alignment between business, IT, leadership, and external vendors), and solution evaluation (assessment of software options, KPIs for solution evaluation after roll-out).

The demarcation: the project manager owns time, budget, and resources — the BA owns the functional requirements. The product owner carries product accountability in an agile team — the BA translates between business and engineering. The requirements engineer (IREB scheme) covers a sub-domain of the BA profile: elicitation, documentation, validation of requirements. Cleanly separated in the corporation; combined in one person in the DACH Mittelstand.

Why the business analyst role matters in the DACH Mittelstand in 2026

First, ERP modernisation. Mid-sized firms face legacy-system replacement. Bitkom studies on Mittelstand digitalisation document that specialists in requirements analysis and business-process / IT interfaces are among the most frequently unfilled IT roles in German mid-sized companies. Firms below 500 employees rarely staff the BA function as a dedicated position; they distribute it across IT leadership, process owners, or external consultants.

Second, methods capability. An internal IT department of three to eight people has neither methodological authority nor sprint capacity for professional elicitation. The typical BA need: temporary, project-based, with a clear handover after the specification.

Third, AI and data architecture. AI and cloud selection pushes requirements elicitation into depths a project manager without a BA profile cannot cover. Per the StepStone Business Analyst salary report 2026, the German range sits between EUR 46,000 and EUR 64,400 gross per year (lower / upper quartile), with 662 open positions concentrated in Frankfurt, Berlin, and Munich. The market is tight — the Mittelstand competes with banks, insurers, and corporations for the same scarce profile.

Project example: mid-sized manufacturer in southern Germany, c. 240 employees

A manufacturer with 240 employees, five sites, and an ERP landscape from the early 2000s had advertised the "Business Analyst (ERP modernisation)" role for twelve months. Three candidates reached the final round, two withdrew, one stayed three months. Not a pay problem — a job-profile problem: a pure BABOK role with no project responsibility, no test coordination, no change accompaniment. In a 240-person company with a five-person IT department that division of labour was not constructible.

We were called in for the restart and took the BA mandate ad interim. The pragmatic correction: one person, three hats — elicitation (BA), documentation per IREB scheme (RE), and light coordination of the ERP selection. We deliberately did not separate BA and RE because the project ran twelve months over three ERP modules — below our pragmatic threshold.

The result after eight months: a coherent specification with 312 use cases and 47 acceptance criteria per core process, a vendor-neutral shortlist of four providers, and a selection decision in eleven weeks instead of the market-typical twenty-four.

What BABOK conceals about the Mittelstand reality

1. BABOK separates cleanly — the Mittelstand cannot

BABOK v3 cleanly separates the BA role from project, test, and change management. That works in corporations with dedicated PMO and test teams. A 50-to-500-person Mittelstand has neither. From experience the BA also handles test coordination, stakeholder reporting, and light project steering in 80 percent of engagements. A pure-form advert leads to twelve-month vacancies. The realistic answer: a role cluster BA + RE + light project coordination.

2. CPRE instead of CBAP — IREB is often the more relevant certification in the DACH Mittelstand

The BABOK path runs through the IIBA cascade (ECBA, CCBA, CBAP). In DACH the IREB scheme has prevailed. The IREB CPRE Foundation Level Syllabus v3.3.0 dated 1 April 2026 covers both plan-driven and agile approaches and is the most frequently held BA-relevant certification in the German-speaking Mittelstand. We separate RE and BA only when the project runs longer than twelve months or covers more than four ERP modules — otherwise: one person, two roles, documented in a coherent specification.

3. Without KPI definition before project start the BA fails — even the best one

In a corporation the BA inherits OKRs from strategy teams. In the Mittelstand they do not exist — management expects the external BA to define them. Not "more efficiency" but measurable metrics: selection duration, budget deviation, user acceptance after three months, manual corrections per week. The competence model of business informatics (Gesellschaft für Informatik) orders BA competences along process analysis, elicitation, and IT system design — KPI anchoring belongs in that matrix. Skip it and you get a clean requirements analysis without measurable benefit.

How we deploy the BA role in the Mittelstand

Within our vendor-neutral ERP consulting we treat business analysis as the methodological core of every selection. The four stages:

Phase 1 — Goal clarity and KPI set before any elicitation. Phase 2 — As-is process analysis, structured capture of existing processes, BPMN- or value-stream-mapping-based. Phase 3 — Specification with use cases and acceptance criteria — functionally reviewable, vendor-neutral. Phase 4 — Solution evaluation, KPI-based assessment after three and six months of roll-out.

The material difference: we recommend vendor-independently. We take the BA role ad interim to build methods capability in-house and keep the specification vendor-neutral. The result is a traceable selection decision rather than a gut call. See our consulting approach for the methodological stance.

Common mistakes with the BA role in the Mittelstand

Mistake 1 — Pure BABOK job profile in a 200-person company. The advert describes the corporate role, untenable in the Mittelstand. Result: twelve-month vacancy, then a three-month hire. Fix: advertise the role cluster (BA + RE + light project coordination) explicitly.

Mistake 2 — KPIs only after the first workshop. Elicitation runs without success metrics defined. The most common reason for cancellations in month nine. Fix: KPI set during goal clarity, before any workshop invitation.

Mistake 3 — Tool selection before elicitation. Management has a target system in mind. The BA is asked to "write the requirements for it" — not business analysis but vendor confirmation. Fix: the BA receives the mandate before the vendor conversation.

Mistake 4 — No internal handover point. The external BA produces the specification and leaves. Nobody in-house can defend the requirements against the vendor. Fix: an internal requirements owner is named on day one and supported in parallel.

Frequently asked questions

Next steps

Before posting a vacancy or engaging an external BA, a short clarification pays back: which business goals should the engagement support, how is success measured, which roles combined and which separated? Skipping this yields a textbook job profile that attracts no candidates or the wrong ones. Background in our Insights and under independent ERP consulting.

Matthias Müller Senior Consultant for Process Optimisation, ERP and Digitalisation at Dreher Consulting. Guides Mittelstand companies across DACH through complex ERP implementations and requirements analyses — pragmatic, without corporate overhead. Book an appointment directly →