Study guide

Foundational Competencies Overview

IIBA ECBA Entry Certificate in Business Analysis

Track your progress as you read

Finished sections get a check mark.

1 Introduction & ECBA Exam Overview

ECBA Exam Facts: Format, Eligibility, Cost, and Scoring How the ECBA Is Built: Source Documents, Blueprint Domains, and Study Plan

2 Understanding Business Analysis

What Is Business Analysis? The BACCM: Business Analysis Core Concept Model How Business Analysis Creates Value Defining Value and Assessing Value Realization

3 Mindset for Effective Business Analysis

The Business Analysis Mindset and How It Drives Effectiveness Shared Values and Core Business Analysis Principles Foundational Competencies Overview

4 Implementing Business Analysis

Business Analysis Roles and Organizational Context Choosing a BA Approach and the Requirements Classification Schema

5 Change

Contextual Factors Influencing the Work Impact Analysis Tracking Progress and Implementing Improvements

6 Need

Elicitation Methods and Stakeholder Rapport Documenting and Modeling Requirements Verifying and Validating Requirements Prioritizing Needs with MoSCoW

7 Solution

Solution Validation Criteria Evaluating Solution Options Scope Definition and Design Artifacts

8 Stakeholder

Communicating with Stakeholders Stakeholder Roles, Analysis, and RACI Facilitating Collaboration and Feedback

9 Value

Confirming Desired Outcomes and Value Opportunities Measuring Value Delivered

10 Context

Validating Information and Adapting Plans Technology Trends and Industry Standards

11 BABOK Techniques for ECBA

Elicitation and Collaboration Techniques Modeling and Analysis Techniques Strategy, Risk, and Investigation Techniques Requirements and Value Techniques

12 Underlying Competencies

Analytical Thinking, Behavioural Characteristics, and Business Knowledge Communication Skills, Interaction Skills, and Tools and Technology

13 Exam Readiness

Final Review & Exam-Day Strategy

Foundational Competencies Overview

Key Takeaways Explain This Topic AI

Foundational competencies are the basic skills, abilities, and characteristics necessary to perform effective business analysis, per the Business Analysis Standard.

The global business analysis community identified five essential foundational competencies: Adaptability, Facilitation, Leadership and Influencing, Problem Solving, and Systems Thinking.

The BABOK Guide expands these into 29 underlying competencies organized across six categories, covered in full in a later chapter of this guide.

Foundational competencies apply across many initiative types, including process redesign, business architecture, technology implementation, digital transformation, data warehousing, cybersecurity, business data analytics, and product ownership analysis.

Competencies are developed through deliberate effort over time rather than being fixed traits, and teams should collectively ensure competency coverage rather than expecting every individual to master every skill alone.

Last updated: July 2026

What Are Foundational Competencies?

Foundational competencies are the basic skills, abilities, and characteristics necessary to perform effective business analysis. They sit alongside mindset and principles as the third pillar the Business Analysis Standard uses to describe what makes a BA effective, and they are the "how do I actually do the work well" layer underneath every technique a BA applies. This section gives the entry-level overview and explains when to apply which competency; the complete BABOK Guide list of 29 underlying competencies, organized into six categories, is covered in full later in this guide.

Five Key Foundational Competencies

While the BABOK Guide documents 29 underlying competencies in total, the global business analysis community identified five as essential starting points for every practicing BA, regardless of industry or initiative type:

  • Competency Core Idea
  • Adaptability Adjusting behavioral style and approach to increase effectiveness as the situation changes
  • Facilitation Conducting productive workshops, negotiating between parties, and resolving conflict

Leadership and Influencing Building consensus, recommending solutions, and guiding stakeholders toward desired value

Problem Solving Ensuring the value created addresses root causes rather than symptoms

Systems Thinking Understanding the enterprise holistically so decisions maximize value across the whole system, not just one part

These five are foundational in the literal sense: they are the competencies a new BA needs on essentially every engagement, before layering on the more specialized skills covered later in the full 29-competency breakdown.

Knowing When to Apply Foundational Competencies

A recurring exam theme is that competencies are not applied uniformly — an effective BA reads the situation and leans on the competency the moment calls for. Facilitation matters most when a BA is running a requirements workshop with stakeholders who disagree. Leadership and influencing matters most when a BA must build consensus around a recommendation that some stakeholders resist. Problem solving matters most when a stated request looks like it is treating a symptom rather than a cause. Systems thinking matters most when a change in one part of the organization risks unintended consequences elsewhere. Adaptability underlies all of the above, because it is the competency that lets a BA recognize which of the others to use, and adjust behavior when a chosen approach is not landing with a particular stakeholder or group.

Foundational competencies also apply differently depending on the type of initiative a BA is supporting. The Business Analysis Standard notes that these competencies carry across a wide range of contexts, including:

  • Process redesign
  • Business architecture
  • Technology implementations
  • Digital transformation
  • Data warehousing and data analytics initiatives
  • Cybersecurity initiatives
  • Business data analytics
  • Product ownership analysis

A BA supporting a technology implementation will lean heavily on systems thinking to anticipate downstream effects, while a BA supporting a process redesign initiative may lean more on facilitation to get frontline staff aligned on a new way of working. Recognizing which competency the situation calls for, rather than applying the same one reflexively, is itself a mark of an effective BA and a frequent theme in situation-based questions.

From Five Foundational Competencies to Twenty-Nine Underlying Competencies

It is worth being precise about the relationship between this overview and the fuller picture taught later in this guide. The Business Analysis Standard highlights five foundational competencies as the essential starting set. The BABOK Guide, in its underlying competencies chapter, expands this into 29 named competencies grouped across six categories: Analytical Thinking and Problem Solving, Behavioural Characteristics, Business Knowledge, Communication Skills, Interaction Skills, and Tools and Technology. The five foundational competencies introduced here map into that larger structure — for example, Problem Solving and Systems Thinking both belong to the Analytical Thinking and Problem Solving category, while Facilitation and Leadership and Influencing both belong to Interaction Skills.

For the ECBA exam, this chapter's job is to make sure a candidate recognizes the five foundational competencies by name, understands what each one means in practice, and can reason about which competency a given scenario calls for. The complete 29-item breakdown, including definitions for competencies outside the initial five, is deliberately deferred to its own dedicated chapter later in this guide, where all 29 are named and organized by category for focused study.

Competencies Are Developed, Not Fixed

Consistent with the mindset chapter, the Business Analysis Standard treats foundational competencies as skills a BA actively builds, not fixed traits someone either has or lacks. A BA who is weak in facilitation can deliberately practice running smaller workshops before leading a high-stakes one; a BA who defaults to narrow problem solving can deliberately practice asking "why" more times before proposing a fix. On the exam, a correct answer will rarely describe a BA giving up on a task because a competency feels unnatural. It will instead describe the BA recognizing the gap and taking a concrete step to close it, or bringing in a teammate whose strength complements their own, consistent with competency coverage across a team rather than every individual mastering every skill alone.

For the Exam

When a situation-based question describes a BA struggling with a specific challenge — stakeholders talking past each other, a solution that treats a symptom, a decision that ignores its ripple effects elsewhere in the organization — identify which foundational competency the scenario is testing before reading the answer options. That habit turns an unfamiliar scenario into a recognizable pattern: conflict or workshop friction points to facilitation, resistance to a recommendation points to leadership and influencing, a shallow root cause points to problem solving, and unintended organizational consequences point to systems thinking.