I get asked a lot  what skills do I actually need to become a business analyst? Not the copy-pasted LinkedIn list. The real answer.

After 5 years in this role, here’s what I’d tell anyone starting out or trying to grow.

1. Communication
   You talk to the CEO in the morning and the developer in the afternoon. You write emails, run meetings, present to stakeholders, and write documentation  all in the same week. If you can communicate clearly across all those different audiences, you become the person everyone wants on their project.

2. Requirements Gathering
   Your whole job starts here. You talk to people, understand what they need, and write it down in a way the tech team can actually use. Sounds simple. It’s not. People rarely tell you the real problem upfront  you have to dig for it.

3. Critical Thinking
   This is the big one. Anyone can gather requirements. The good BAs ask  are we solving the right problem? They slow down before jumping to solutions. They question assumptions. In 2026, with AI doing more of the documentation work, this is the skill that actually justifies your seat at the table.

4. Process Mapping
   Draw how things work today. Then draw how they should work. That’s process mapping. It sounds basic but it’s one of the most powerful things a BA does. It makes problems visible that everyone felt but nobody could explain.

5. Stakeholder Management
   You will always be working with people who want different things. Your job is to keep everyone aligned, manage expectations, and make sure the right people are in the right conversations. This skill alone will take you further than any tool or certification.

6. Agile Basics
   Most teams work in agile now. You need to know how a sprint works, what backlog refinement looks like, and how to show up usefully in a scrum team. You don’t need to be a scrum master. You just need to not be the person slowing the team down.

7. Writing User Stories
   In most companies today, requirements are written as user stories. Short, simple statements that say who needs something, what they need, and why. If you can write a clear user story, developers stop coming back to you every five minutes asking what you meant.

8. Wireframing
   A rough sketch of a screen solves more arguments than a ten-page document. Tools like Figma or even Miro let you show stakeholders what you mean instead of describing it. When people can see something, they give better feedback. Simple as that.

9. Basic Data Skills
   You don’t need to be a data analyst. But you should be able to open a database, run a basic SQL query, and read a report without needing someone to explain it to you. Data literacy is quickly becoming a basic expectation, not a bonus skill.

10. BABOK and IIBA Certification
    The BABOK guide is the professional framework for business analysis. Learning it gives you structure and a common language with other BAs worldwide. Getting an IIBA certification  ECBA if you’re starting out, CBAP when you’re experienced  shows employers you’re serious about the profession. It matters, especially when two candidates look similar on paper.

One last thing

The tools will keep changing. The methodologies will keep evolving. But the BAs who last are the ones who are genuinely curious, good with people, and honest about what they don’t know yet. That hasn’t changed in twelve years and I don’t expect it to.