Role of a Business Analyst: BABOK Definition vs Real Job Ads

The role of a business analyst, in BABOK v3 terms, is to enable change: define what an organization needs and recommend solutions that bring value to stakeholders. Anyone doing this work is a business analyst, whatever the job title. Job ads are narrower and wider at once: almost all ask for requirements work, only about 30% mention strategy [2], and many add testing, SQL and project management, which BABOK does not treat as core [2, 3].

Last verified: October 2026 (BABOK Guide v3, published 2015, is still the current version).

How BABOK defines the role of a business analyst

BABOK v3 defines the role by the work, not by the title. Business analysis is "the practice of enabling change in an enterprise", done by defining needs and recommending solutions that deliver value. A business analyst is any person who performs the tasks described in the guide, no matter their job title or place in the organization.

IIBA lists many titles that do this work: Business Analyst, Business Systems Analyst, Requirements Engineer, Business Architect, Data Analyst, Process Analyst, UX Designer, Product Owner, Product Manager and Change Manager, among others [1]. IIBA chapter pages also note that BAs can work at every level, from strategy and enterprise architecture to project requirements and continuous improvement [1].

The guide frames the work through six core concepts (the Business Analysis Core Concept Model, BACCM): Change, Need, Solution, Stakeholder, Value and Context. It then organizes tasks into six knowledge areas:

For a deeper look at the structure of the guide, see our overview of the BABOK Guide and the map of all 50 BABOK techniques.

Why the definition matters for CBAP, CCBA and AAC

The Certified Business Analysis Professional (CBAP) and Certification of Capability in Business Analysis (CCBA) exams test the BABOK view of the role, not the view of any one employer. The Agile Analysis Certification (AAC) applies the same view to agile teams, where analysis is a shared activity rather than one person's job. Exam questions often describe a person with a title such as Product Owner or Project Manager who elicits needs or evaluates a solution. In BABOK terms, that person is doing business analysis. If you answer from the habits of your current company, you can pick an answer that is normal at work but wrong for the exam.

Two points help most:

• The title does not decide the role. The tasks do.
• The BA recommends solutions and enables change. The BA does not own the decision. Sponsors and other stakeholders approve.

What real job ads ask for

Job ads describe a narrower core and a wider list of extra skills than BABOK. Three recent sources show the pattern.

58 LinkedIn ads in Denmark (December 2025). An IIBA Denmark review compared Danish BA ads with BABOK [2]. Almost all ads expect work in Elicitation and Collaboration and in Requirements Analysis and Design Definition. Just over 30% expect Strategy Analysis. Only about a third mention any of the supporting areas (planning, life cycle management). About 60% mention agile methods, and user stories with acceptance criteria are the most common techniques. Many ads also ask for testing, implementation and project management, which sit outside BABOK. The author ends with a useful reminder: a job ad is a wish list, not an answer key [2].

1,480 ads in Poland (July 2024, published 2026). A study from the Silesian University of Technology analyzed BA ads from Pracuj.pl, LinkedIn and JustJoin.it [3]. The most requested tools were Microsoft SQL Server, Excel, Python, Power BI, Jira and Confluence, plus BPMN and UML. English was the top requirement at every level. Junior ads stress communication; senior ads add project management, leadership and data management. The authors also cite a 2019 study of 240 Australian and New Zealand ads that found project management, implementation and technical skills in demand but not explicit in BABOK [3].

Two live ads from one global employer. British American Tobacco (BAT) shows how far one title can stretch inside one company [4, 5]:

The first ad is a classic IT business analyst. The second is close to a data analyst or a business data analytics role, the area covered by the CBDA exam.

Experts disagree on the role of a business analyst

Practitioners agree on the core of the role, but not on its borders. Their views fall into five positions.

1. The role has no single definition. One view is that the profession is still loosely defined: ask ten hiring managers what an analyst does and you get ten different answers [8]. The set of tasks changes from project to project and between organizations, so the title alone tells little [8, 9].

2. The work defines the role, not the title. Supporters of this view, including IIBA itself, say anyone who elicits needs, analyzes them and recommends solutions is a business analyst, whether the title is Data Analyst, Operations Analyst or Product Owner [1, 6]. In this view business analysis has strategic, tactical and operational levels, and the classic IT business analyst is only one part of it [6].

3. The core is requirements; technical work belongs to others. A more narrow view treats requirements analysis as the main BA activity and sees systems analysis and detailed data analysis as technical design work that most BAs do not do [9]. Practitioners in banking and finance disagree: there, BAs often spend most of their time on systems analysis [9].

4. The BA is a hybrid who fills gaps in the team. Another group says the modern BA wears many hats: in some companies the BA takes on part of the project manager's work, in others Scrum Master duties [7, 10]. Some authors accept this; others warn that a job is still a BA role only if most of the time goes to analysis tasks [6].

5. The line with product roles is blurred. In agile companies the BA and the Product Owner often share work. In some teams the Product Owner is in practice a lead BA; in others several BAs act as proxies for one Product Owner [11]. Some authors even place product ownership inside strategic business analysis [6].

There is also a debate about seniority. One author argues that "Lead BA" should be a temporary role on a project, not a permanent grade, so a person can lead on one project and work as a regular BA on the next [9].

From my practice: one title, different jobs

I worked as a business analyst for more than six years, and my work was different from project to project. Looking back, it fell into two modes.

Technical mode. On some projects the job was to design how systems talk to each other and to build the business process at the technical level. I spent my days on integrations between systems, process flows, and digging into data to understand what was really happening.

Product mode. On other projects the job looked like product work. I studied the market, ran interviews with customers, and worked out how the product should be sold.

The second point is just as important: the tasks changed with the needs of each project and each team. When the team lacked someone who understood the data, I went deep into data. When the team did not know who the customer was, I went to the market. The title "Business Analyst" stayed the same; the job did not.

Both modes fit inside BABOK. They simply use different parts of it:

This is why I read BABOK as a toolbox, not a job description. The guide itself says the BA should choose the approach that fits the context; see Plan Business Analysis Approach and predictive vs adaptive approaches.

Common misconceptions about the BA role

• "A business analyst only writes requirements." Requirements are the most common task in job ads, but BABOK also covers strategy, planning and solution evaluation.
• "If my title is not Business Analyst, I am not a BA." BABOK and many practitioners say the work, not the title, defines the role [1, 6]. Product owners, data analysts and process analysts often qualify.
• "The BA decides on the solution." The BA recommends; stakeholders with authority decide.
• "Job ads show what the role is." They show what one team needs right now; a job ad is a wish list [2].
• "Technical BA and product BA are different professions." They are the same profession using different knowledge areas and techniques.

Early-career analysts often hit these misconceptions in practice; see 6 junior business analyst mistakes.

Practice Questions

Question 1. A Product Manager runs customer interviews to understand why orders are dropping and recommends changes to the checkout process. According to the BABOK Guide, how should this work be classified?

• A. Product management, because the person's title is Product Manager
• B. Business analysis, because the person defines needs and recommends a solution
• C. Project management, because a change to a process is planned
• D. Not business analysis, because no requirements document was produced

Question 2. Which set lists the six concepts of the Business Analysis Core Concept Model?

• A. Plan, Elicit, Analyze, Design, Validate, Evaluate
• B. Change, Need, Solution, Stakeholder, Value, Context
• C. Strategy, Requirements, Design, Solution, Risk, Value
• D. Business, Stakeholder, Solution, Transition, Change, Benefit

Question 3. A business analyst joins a new team. The team has a strong product owner but no one who understands how data moves between the order system and the warehouse system. What should the BA do first?

• A. Follow the same approach used on the previous project
• B. Write a full requirements specification for all systems
• C. Tailor the business analysis approach to the context and focus on the interface and data gaps
• D. Ask the product owner to take over the analysis work

Answers

1. B. BABOK defines a business analyst by the tasks performed, not by the title. Interviews are elicitation, and recommending a change is part of Strategy Analysis and solution definition.
2. B. The BACCM consists of Change, Need, Solution, Stakeholder, Value and Context. Option A mixes task verbs, the others mix unrelated terms.
3. C. BABOK asks the BA to plan an approach that fits the context (BABOK v3, 3.1). Here the gap is in interfaces and data, so techniques such as Interface Analysis and Data Flow Diagrams fit best.

Conclusion: the gap between BABOK and real BA tasks

The role of a business analyst in BABOK is wider than in most job ads, and job ads add tasks that BABOK does not treat as BA work. The shared core is small but stable: eliciting needs and turning them into requirements with stakeholders.

In short: most job ads focus on two of the six BABOK knowledge areas and add a technical and project-management layer on top. BABOK gives the full toolbox; each team takes the tools it needs now. That is also why the job changes from project to project, as described in the practice section above.

Related topics

• BABOK Guide: the backbone of business analysis
• Strategy Analysis
• Elicitation and Collaboration
• Benchmarking and Market Analysis (BABOK 10.4)
• Stakeholders and Personas

To test how well you know the BABOK view of the role, try the CBAP exam simulator.

FAQ

What is the role of a business analyst according to BABOK?

BABOK v3 says the business analyst enables change in an organization by defining needs and recommending solutions that deliver value to stakeholders. Anyone who performs these tasks is a business analyst, whatever their job title. The work is organized into six knowledge areas, from planning to solution evaluation.

Why do business analyst jobs look so different between companies?

Each company hires for the part of business analysis it needs now. A 2025 IIBA Denmark review found almost all ads ask for elicitation and requirements work, but only about 30% ask for strategy. Many ads also add testing, SQL or project management, which BABOK does not treat as core BA work.

Do I need SQL to be a business analyst?

BABOK does not require any specific tool. Job ads often do: a study of 1,480 Polish BA ads found Microsoft SQL Server was the most requested tool, followed by Excel and Python. For technical and data-focused BA roles, basic SQL is a common expectation.

Is a product owner a business analyst?

In BABOK terms, a product owner who elicits needs and defines solutions is doing business analysis. IIBA lists Product Owner among the titles that perform business analysis. In Scrum, the product owner also owns product value and backlog decisions, which is a wider accountability than the BA role.

Does the CBAP exam test the role as it is in my company?

No. The CBAP exam tests the BABOK view of the role. Answer questions by asking which task is being performed and what BABOK recommends, not by what your current employer would expect.

Sources

1. IIBA Ireland Chapter – What is Business Analysis?
2. IIBA Denmark – Business Analysis in Numbers: What Do Danish Companies Expect? (December 2025)
3. Kowalska-Styczeń & Juszczyk – Employer expectations of business analysts, Journal of Innovation & Knowledge (2026)
4. BAT careers – Business Analyst, Corporate (Kuala Lumpur)
5. BAT careers – Business Analyst, Data & Analytics (Warsaw)
6. BA Times – My Job Title is Not Business Analyst, But Am I One? (2014)
7. BA Times – 10 Characteristics of an Awesome Business Analyst
8. Modern Analyst – Definition of the Business Analyst Profession
9. Modern Analyst – How do BAs operate in your organisation? A pragmatic guide to the different roles of the Business Analyst
10. IIBA – Wearing Many Hats: The Modern BA
11. Scrum.org forum – Product owner vs business analyst