Business Analyst Skills: Score Yourself on the Six That Matter
Lists of business analyst skills are everywhere, and most read the same: communication, problem solving, SQL. They do not tell you which skill is holding you back or what to do about it. This guide uses the competency frameworks published by the International Institute of Business Analysis (IIBA) to give you six areas to score yourself on, one practice exercise for each, and a way to show evidence of each skill on a resume or in an interview. It adds a scorecard example with made-up numbers.
Skills, competencies and tools
A skill is something you can do. A competency is a group of related skills plus the knowledge and behavior that make them work. A tool is software, such as a spreadsheet or a diagramming program. Job ads tend to list tools because they are easy to name. Hiring managers usually care more about whether you can find the real problem, ask good questions and get people to agree.
IIBA, the professional body for the field, publishes two frameworks that help here. The first is the six underlying competencies in its BABOK® Guide. The second is the five foundational competencies in The Business Analysis Standard. Both are summarized below. For what the job involves day to day, read our business analyst job description guide. For where the skills can take you, see the career path guide.
The six underlying competencies
IIBA’s BABOK Guide chapter on underlying competencies names six areas. IIBA describes them as the behaviors, characteristics, knowledge and personal qualities that support the practice of business analysis. The detailed definitions are behind IIBA’s registration wall, so the middle column below is our own description of what each tends to look like at work, not IIBA’s wording.
| Competency (IIBA name) | What it looks like at work (our description) | A quick test |
|---|---|---|
| Analytical thinking and problem solving | Breaking a messy situation into parts, finding causes, comparing options | Can you explain why a problem keeps happening, not just what it is? |
| Behavioural characteristics | Reliability, ethics, adapting when plans change, staying organized | Do people trust your notes and follow-up? |
| Business knowledge | Understanding the industry, the company and how it makes or spends money | Can you draw how your employer earns revenue on one page? |
| Communication skills | Listening, asking questions, clear writing and speaking | Would two readers understand your requirement the same way? |
| Interaction skills | Facilitating meetings, negotiating, resolving disagreements, working in teams | Can you leave a meeting with decisions and owners recorded? |
| Tools and technology | Office tools, modeling and diagramming software, requirements tools, basic data work | Can you pull a simple answer from data without help? |
The five foundational competencies
The newer Business Analysis Standard lists five foundational competencies, which it describes this way:
| Competency | IIBA’s description |
|---|---|
| Adaptability | Adjusting behavioural style to increase effectiveness |
| Facilitation | Facilitating workshops, negotiating, and helping resolve conflicts |
| Leadership and influencing | Building consensus, recommending solutions, and guiding stakeholders to the desired value |
| Problem solving | Ensuring that created value addresses the root cause of problems |
| Systems thinking | Holistically understanding the enterprise and context to maximize the value delivered |
The two lists overlap. Problem solving appears in both, facilitation sits within interaction skills, and systems thinking leans on business knowledge. The newer list adds two things worth noticing: influencing without authority, and seeing the whole system instead of a single request. A business analyst rarely owns the decision, so persuading people matters as much as analyzing.
What the labor statistics say
The US Bureau of Labor Statistics (BLS) does not publish a business analyst occupation, but it covers management analysts, a close neighbor. In its list of important qualities, it names analytical skills (interpreting information and using findings to make proposals), communication skills (conveying information clearly in writing and speaking, and listening), interpersonal skills, problem-solving skills (thinking creatively) and time-management skills. Time management is worth adding to your own checklist, since it does not appear in the IIBA lists.
BLS describes management analysts, not business analysts, so use it as a rough guide. For pay and outlook, see our job description guide.
Worked example: a skills scorecard
Rate yourself from 1 (new to this) to 4 (I do this well and could teach it) on each of the six IIBA areas. Below is our own made-up scorecard for a person moving from customer support into business analysis.
| Competency | Score (1 to 4) | Reason |
|---|---|---|
| Analytical thinking and problem solving | 3 | Tracks ticket trends and finds repeat causes |
| Behavioural characteristics | 2 | Reliable, but has not led anything yet |
| Business knowledge | 2 | Knows the product well, not the finances |
| Communication skills | 3 | Writes clearly, listens well |
| Interaction skills | 2 | Has not run a workshop |
| Tools and technology | 4 | Strong spreadsheet and reporting skills |
The total is 3 + 2 + 2 + 3 + 2 + 4 = 16, so the average is 16 ÷ 6, about 2.7. The average hides the useful part. Three areas score 2: behavioural characteristics, business knowledge and interaction skills. A sensible plan is to work on the two that can be practiced soonest. Here that means business knowledge (read the company’s annual report and map how it earns money) and interaction skills (volunteer to run a short working session). Re-score after 90 days. Be honest with your scores, and ask a colleague to check them, since people tend to rate themselves unevenly.
One drill for each skill
| Competency | Practice exercise | What you end up with |
|---|---|---|
| Analytical thinking | Pick a problem that keeps recurring and ask “why” five times. Check each answer against data. | A one-page cause chain with the evidence |
| Behavioural characteristics | For a month, send a written summary and action list after every meeting you attend. | A record of follow-through |
| Business knowledge | Read one annual report or industry article a week and draw how the company earns and spends money. | A one-page revenue-and-cost map |
| Communication | Take five vague statements from emails or tickets and rewrite each as a testable requirement. | Before-and-after examples |
| Interaction | Run a 30-minute working session with an agenda, a time limit and recorded decisions. | An agenda, notes and an owner list |
| Tools and technology | Learn to answer a business question with a spreadsheet pivot table or a basic database query, and draw one process map. | A small analysis and a diagram |
For the modeling drill, our guide to process modeling techniques shows how to choose a diagram type.
Worked example: fixing a vague requirement
Communication is the skill most often named and least often tested. Here is a made-up example of what a rewrite looks like.
| Version | Statement | Problem |
|---|---|---|
| Before | “The search should be fast.” | “Fast” means different things to different readers; no way to test it |
| After | “For 95% of searches during normal load, results appear within 2 seconds.” | Measurable, with a clear pass or fail |
The numbers (95% and 2 seconds) are ours; in a real project, the stakeholders would agree on them. The skill is not the wording. It is knowing which question to ask: “How fast, for how many users, measured how?” Our guide to requirements management goes further into writing and controlling requirements.
Showing evidence
Saying you have a skill is weak. Showing a result is stronger. Use this table to turn each competency into something you can show on a resume or describe in an interview.
| Competency | Resume line pattern | Interview story to prepare |
|---|---|---|
| Analytical thinking | “Traced [problem] to [cause], which led to [result]” | A time you found a cause others missed |
| Behavioural characteristics | “Owned [process] for [period] with [measure]” | A time you changed course or admitted a mistake |
| Business knowledge | “Mapped [process] across [teams] to show where [cost] arises” | How your last employer made money |
| Communication | “Rewrote [number] requirements into testable form” | A time two people understood the same request differently |
| Interaction | “Facilitated [number] sessions with [groups], resolving [issue]” | A time two stakeholders disagreed and what you did |
| Tools and technology | “Built [analysis or model] in [tool] to answer [question]” | A time data changed someone’s mind |
Fill in only numbers you can back up. A smaller verified result is worth more than a large one you cannot support.
Common mistakes
- Learning tools first. Tools change; analysis and communication last.
- Rating every skill the same. The point of a scorecard is to find the gap.
- Skipping business knowledge. A solution that ignores how the business works gets rejected.
- Treating soft skills as personality. They can be practiced, as the drills above show.
- Listing skills without evidence. Every claim needs an example.
- Collecting certificates instead of results. Training helps, but a finished piece of work helps more.
Learn more
Online platforms such as Coursera and Udemy list business analysis courses that can help with the weakest areas on your scorecard. We may earn a commission if you sign up, at no cost to you. We are not affiliated with any university. Check each syllabus for practice exercises, not only video lessons.
Frequently asked questions
What skills does a business analyst need?
IIBA names six underlying competencies: analytical thinking and problem solving, behavioural characteristics, business knowledge, communication skills, interaction skills, and tools and technology.
What is the most important business analyst skill?
There is no single answer. Many analysts name communication, and IIBA’s newer standard puts problem solving and influencing among its foundational competencies. The most useful one to build is your lowest-scoring area.
Do business analysts need to code?
Not always. Many roles expect spreadsheets and some data querying, while others expect more technical depth. Check the job ad for the role you want.
Are soft skills more important than technical skills?
They matter at least as much. Gathering requirements and getting agreement depend on communication, facilitation and influence, and tools can be learned on the job.
How can I build these skills without a business analyst job?
Practice in your current role. Map a process, rewrite vague requests, run a working session and keep the results. The drills above are designed for that.
Which skill is hardest to learn?
It varies, but many people find business knowledge and influencing slowest, because both take time with real people and real organizations.
How do I prove my skills?
With specific examples and verified numbers: a process map, a rewritten requirement, a meeting record, an analysis. Certifications can help, but evidence of work is stronger.
Where do these skills lead?
To roles such as senior analyst, product owner and consultant. See our career path guide.
Browse certificate, course and degree programs side by side.