BABOK Techniques: A Map of All 50 by Knowledge Area

The BABOK techniques are the 50 methods described in chapter 10 of the BABOK Guide v3 (sections 10.1 to 10.50). They have no exam weight of their own: the Certified Business Analysis Professional (CBAP) exam tests them inside the six knowledge areas, which carry 12–30% each. The fastest way to learn them is to map each technique to the knowledge areas and tasks where it does its work.

Last verified: October 2026 (exam facts from iiba.org).

What the BABOK techniques are and how much they weigh

A BABOK technique is a named way of doing part of a business analysis task, such as Interviews (10.25) for eliciting information or Decision Modelling (10.17) for specifying rules. Tasks in chapters 3–8 list the techniques that support them; chapter 10 describes each technique once, in the same four parts: Purpose, Description, Elements, and Usage Considerations (strengths and limitations).

The International Institute of Business Analysis (IIBA) publishes these CBAP facts on its CBAP page:

The blueprint weights belong to the knowledge areas, not to the techniques:

According to a summary of recent CBAP holders on BA Times, the blueprint shows techniques as not applicable, yet many questions ask which technique fits a situation. So the techniques are tested everywhere, but through the tasks. If you need the bigger picture of the guide first, start with our overview of the BABOK Guide as the backbone of business analysis.

The map: BABOK techniques by knowledge area

The map below groups each technique by the knowledge area where it does most of its work, and shows where else it appears. It is a study aid built from the task technique lists in chapters 3–8; when you need the exact list for one task, check the Techniques section of that task in the guide.

Techniques that appear in almost every knowledge area

Seven techniques show up across nearly all six chapters. They are the safest to know in depth, because a question about any task can name them:

Survey or Questionnaire (10.45), Reviews (10.37), Process Modelling (10.35) and Decision Analysis (10.16) come close behind.

Planning and Monitoring (ch. 3)

Planning techniques help you design the work rather than the solution. Estimation (10.19), Functional Decomposition (10.22) and Scope Modelling (10.41) size and split the BA work. Stakeholder List, Map, or Personas (10.43) and Organizational Modelling (10.32) plan engagement and governance. Metrics and KPIs (10.28), Process Analysis (10.34) and Root Cause Analysis (10.40) appear in Identify Business Analysis Performance Improvements (3.5), where you measure your own work.

Elicitation and Collaboration (ch. 4)

Elicitation has the widest menu. Conduct Elicitation (4.2) lists the classic elicitation set: Benchmarking and Market Analysis (10.4), Collaborative Games (10.10), Concept Modelling (10.11), Data Mining (10.14), Focus Groups (10.21), Interface Analysis (10.24), Mind Mapping (10.29), Observation (10.31), Prototyping (10.36) and Survey or Questionnaire (10.45), plus the travelling techniques. Collaborative Games is the one technique that rarely leaves this chapter. For the tasks themselves, see our guide to Elicitation and Collaboration.

Requirements Life Cycle Management (ch. 5)

Life cycle tasks keep requirements traced, current, prioritised and approved. Backlog Management (10.2) and Prioritization (10.33) live here, together with Business Cases (10.7) and Financial Analysis (10.20) for value-based ranking. Acceptance and Evaluation Criteria (10.1) supports approval. Use Cases (10.47), User Stories (10.48), Data Flow Diagrams (10.13) and Business Rules Analysis (10.9) show up in Maintain Requirements (5.2) as forms of reusable requirements. Our article on Requirements Life Cycle Management covers the five tasks.

Strategy Analysis (ch. 6)

Strategy techniques describe the enterprise and the change. The strategy-only set is Balanced Scorecard (10.3), Business Capability Analysis (10.6), Business Model Canvas (10.8), SWOT Analysis (10.46) and Vendor Assessment (10.49), with Benchmarking, Business Cases, Financial Analysis, Root Cause Analysis and Metrics and KPIs used heavily too. Several of them also appear in chapter 7 when you choose a solution. Read Strategy Analysis and Gap Analysis for the current state to future state logic.

Requirements Analysis and Design Definition (ch. 7)

This is the 30% knowledge area, and Specify and Model Requirements (7.1) holds most of the modelling techniques: Data Dictionary (10.12), Data Modelling (10.15), Decision Modelling (10.17), Glossary (10.23), Non-Functional Requirements Analysis (10.30), Roles and Permissions Matrix (10.39), Sequence Diagrams (10.42), State Modelling (10.44), Use Cases (10.47) and User Stories (10.48), along with Process Modelling, Concept Modelling and Prototyping. Verify (7.2) and Validate (7.3) rely on Reviews (10.37), Acceptance and Evaluation Criteria and Metrics and KPIs. Our guide to specifying and modelling requirements walks through the model categories.

Solution Evaluation (ch. 8)

Solution evaluation measures a solution that exists, in part or in full. Metrics and KPIs, Acceptance and Evaluation Criteria, Data Mining, Observation, Root Cause Analysis and Benchmarking carry most of the load, with Decision Analysis and Prioritization used when you recommend actions (8.5).

How the map works in practice: one scenario, six chapters

A single initiative uses techniques from every chapter, which is why the exam can ask about the same technique in different knowledge areas. Take a regional insurer that wants to cut claim handling time.

1. Planning (ch. 3). The BA uses Stakeholder List, Map, or Personas to see that adjusters, the fraud team and a regulator have a stake, and Estimation to size the BA work.
2. Elicitation (ch. 4). Observation of three adjusters shows that half their time goes to retyping data. Interviews with the fraud team uncover a manual check that nobody had documented.
3. Strategy (ch. 6). Root Cause Analysis traces the delay to two disconnected systems. SWOT Analysis and Benchmarking against published industry data shape the future state; a Business Case argues for integration.
4. Requirements analysis (ch. 7). Process Modelling shows the target flow, Decision Modelling captures the fraud rules in a decision table, and a Data Dictionary fixes the meaning of claim status values.
5. Life cycle management (ch. 5). Prioritization with the product owner ranks the backlog; Item Tracking records a change request from compliance.
6. Solution evaluation (ch. 8). After release, Metrics and KPIs show handling time fell, but not for complex claims; Data Mining finds the pattern.

Note the double roles: Root Cause Analysis appears in strategy and in solution evaluation; Metrics and KPIs appears in planning, strategy, analysis and evaluation. The technique stays the same; the task decides why you use it.

What practitioners say about studying the techniques

Candidates and trainers agree on one point: learn the techniques through the tasks, not as a list of 50 definitions.

• A BA Times summary of recent credential holders reports that successful candidates spent about 150–200 hours and read the guide two or three times. Its advice on techniques is short: "Do not rely on memorization."
• Watermark Learning advises learning each technique in the context of the tasks it is most closely tied to, and using BABOK terms even when your workplace uses different ones.
• A CBAP holder writing for Techcanvass in 2024 says he gave about 20 hours to techniques against roughly 5 hours per knowledge area, and studied each one by mapping it to a system from his own projects.
• Techcanvass also suggests grouping the techniques and using the guide's technique-to-task mapping, and spending the most time on techniques that support many tasks.
• An August 2026 article by trainer LN Mishra on Adaptive US says past participants found Financial Analysis, Decision Analysis and UML-style models hardest, and were less comfortable with techniques from strategy, planning and solution evaluation.
• A candidate on Modern Analyst describes logging why each simulation answer was right or wrong, which built a list of 200–300 explanations, and mind-mapping each knowledge area.

The common lesson: the map is the study tool. Once you know which tasks use a technique, a scenario question becomes a question about the task.

What the CBAP exam looks for in technique questions

Technique questions on the CBAP exam usually test fit, not definitions. Typical patterns, based on the candidate reports above and on the structure of the guide:

Pay extra attention to close pairs. Process Analysis (10.34) assesses a process for improvement; Process Modelling (10.35) represents it. Decision Analysis (10.16) compares options; Decision Modelling (10.17) specifies how a repeatable decision is made, a distinction our decision modelling and decision analysis article covers in detail.

Practice Questions

These are original questions written for this article.

Question 1

A business analyst must understand how claims staff actually work, because the written procedures are out of date and staff find it hard to describe their routine. Which technique is most appropriate?

A. Document Analysis B. Observation C. Survey or Questionnaire D. Focus Groups

Answer: B. Observation (10.31) captures how work is really done, including tacit steps people do not mention. Document Analysis relies on the outdated procedures; surveys and focus groups depend on what people can describe.

Question 2

During Analyze Current State, the analyst needs to show the organisation's capabilities and which ones underperform, to find where change will add the most value. Which technique fits best?

A. Business Capability Analysis B. Functional Decomposition C. Roles and Permissions Matrix D. State Modelling

Answer: A. Business Capability Analysis (10.6) maps what the enterprise can do and assesses performance and value per capability. Functional Decomposition breaks down a scope but does not assess capability performance.

Question 3

A team must specify how a premium discount is calculated from five conditions, so that developers and business staff can check every combination. Which technique should the analyst use?

A. Decision Analysis B. Business Rules Analysis C. Decision Modelling D. Process Modelling

Answer: C. Decision Modelling (10.17) shows a repeatable decision and its rules, often as a decision table, so every combination can be checked. Decision Analysis compares alternatives for a one-off choice.

Question 4

Which technique is listed for tasks in almost every knowledge area and is a safe choice when a scenario needs information from one stakeholder in depth?

A. Interviews B. Collaborative Games C. Sequence Diagrams D. Balanced Scorecard

Answer: A. Interviews (10.25) appear in almost every knowledge area. The other three are specialised: Collaborative Games mainly in elicitation, Sequence Diagrams in requirements modelling, Balanced Scorecard in strategy.

Key takeaways

• The 50 BABOK techniques live in chapter 10 but are tested through the six knowledge areas and their tasks.
• Seven techniques travel almost everywhere: Brainstorming, Document Analysis, Interviews, Item Tracking, Lessons Learned, Risk Analysis and Management, and Workshops.
• Most modelling techniques sit in Requirements Analysis and Design Definition, the 30% area.
• Strategy-only techniques (Balanced Scorecard, Business Capability Analysis, Business Model Canvas, SWOT, Vendor Assessment) are where many candidates feel weakest.
• Study each technique by Purpose, Elements and Usage Considerations, then link it to the tasks that list it.

IIBA also offers the Certification in Business Data Analytics; if you want to practise scenario questions in that format, try our CBDA practice exam.

FAQ

How many techniques are in the BABOK Guide v3?

The BABOK Guide v3 describes 50 techniques in chapter 10, numbered 10.1 (Acceptance and Evaluation Criteria) to 10.50 (Workshops). Each has the same structure: Purpose, Description, Elements and Usage Considerations.

Do I need to memorise all 50 BABOK techniques for the CBAP?

You need to recognise all 50 and know when each one fits, but memorising definitions is not enough. CBAP questions are scenario based, so candidates report better results from linking each technique to the tasks that use it.

Which BABOK techniques are most important for the CBAP exam?

Techniques that support many tasks give the best return: Interviews, Workshops, Document Analysis, Brainstorming, Risk Analysis and Management, Item Tracking and Lessons Learned. After those, focus on the modelling techniques of chapter 7, because that knowledge area carries 30% of the exam.

Are techniques a separate section of the CBAP exam?

No. IIBA weights the exam only by the six knowledge areas. Technique questions are built into those areas, so a question in Strategy Analysis may ask about SWOT or Benchmarking.

Where does the BABOK Guide show which technique belongs to which task?

Every task in chapters 3–8 ends with a Techniques list, and the guide also includes a mapping of techniques to tasks. Use that mapping to check any study map, including this one.

Sources

• IIBA: Certified Business Analysis Professional (CBAP)
• IIBA: BABOK Guide
• BA Times: How to Pass the CBAP Exam: Study Tips from Recent Credential Holders
• Watermark Learning: How to Pass the CBAP Exam, study tips
• Techcanvass: How I aced the CBAP exam
• Techcanvass: 5 Essential Tips to Memorize the 50 BABOK Techniques
• Adaptive US: Important Techniques for CBAP Certification Examination
• Modern Analyst: Strategy for Passing the CBAP Version 3 Exam