If you are actively working on your business analyst career right now, whether you are trying to land your first role, earn a promotion, or move into more complex engagements, the advice you usually find is too abstract to act on. Qualities like “communication skills” and “stakeholder management” are real, but they do not tell you what to do tomorrow morning. This article is built around the specific habits, skills, and decisions that have made a concrete difference in my own career across 25 years of BA work in government, utilities, health, education, and enterprise settings. Start here, and take something away you can use today.
What Separates Good BAs from Great Ones
The technical skills matter. Knowing how to write a use case, structure a requirements workshop, or assess your core BA competencies against a recognised framework is all legitimate and worth doing. But in my experience, those skills are rarely what separates a BA who gets noticed from one who gets overlooked. The difference tends to come down to a smaller set of habits that compound over time.
- Understand the business before reaching for a solution. Technology is a means to an end. The first question I ask on any engagement is not “what do you want the system to do?” but “what problem are we actually trying to solve?”
- Select the right approach for the context. Applying Agile methods to a heavily regulated procurement project, or Waterfall thinking to a fast-moving product team, creates friction that slows everything down. Knowing which tools and methodologies fit the situation is a genuine skill.
- Communicate differently to different audiences. An executive summary and a technical specification serve different people. Writing both well, and knowing which one you are writing, is not optional at mid-career level.
- Ask the questions others avoid. “What does this mean?”, “Why do you need this?”, “What happens when it goes wrong?” Good requirements come from genuine curiosity, not from nodding along and filling in a template later.
- Build trust across both sides of the fence. Business stakeholders and technical teams have different priorities, different vocabulary, and different definitions of “done.” Your value as a BA depends heavily on being credible to both.
- Focus on value, not documentation volume. Producing a 90-page BRD nobody reads is not a career achievement. Producing a 20-page document that actually drives good decisions is.
A Real Example: When the Stakeholder Pushed Back Hard
On a data migration project for Organisation A, a large public-sector body, I was brought in to capture requirements for moving a legacy case management system onto a new platform. The project sponsor had already briefed the development team informally before I arrived, and the developers had started scoping work based on those conversations. When I began structured elicitation sessions with the operational team, it became clear very quickly that the sponsor’s understanding of “current state” was about three years out of date. Staff had built a series of manual workarounds around the legacy system that nobody had documented, and those workarounds were handling roughly 40% of active cases.
When I raised this in a project meeting, the sponsor pushed back. He was confident the original scope was correct and suggested I was overcomplicating things. I had two choices: accept the framing to keep the peace, or document what I had found and present it clearly. I put together a simple process map showing the workaround flows alongside the documented system behaviour, with an estimate of the case volume affected. That map changed the conversation. The development team, who had been quietly uneasy about scope, were visibly relieved someone had put it in writing. The sponsor took a day to sit with it and then agreed to a scope revision.
The friction was real and uncomfortable. But the willingness to ask the question others were avoiding, and to document the answer in a way that made it impossible to ignore, is exactly what BA practice looks like in a real project environment. If you want to see how that kind of finding gets structured into a formal document, this guide on documenting your findings at the start of a project is worth reading alongside this one.
Six Habits Worth Building Deliberately
These are not aspirational traits. They are specific behaviours I have seen accelerate careers at every stage of the profession.
- Find a mentor with genuine BA experience. A mentor is a sounding board, a second opinion, and access to a network you have not built yet. If someone with significant experience is willing to invest time in you, take that seriously and show up prepared.
- Research the competency frameworks properly. The IIBA’s BABOK Guide is the recognised standard. Understanding what effective BA practice looks like in a structured way helps you identify exactly where your gaps are, rather than guessing.
- Get certified at the right level for where you are now. The ECBA is a natural starting point for early-career BAs. CCBA and CBAP become relevant as your experience builds. Certification signals credibility and gives you a framework that organises your own thinking.
- Engage with the people around you on every project. Subject matter experts, project managers, developers, and other BAs all carry knowledge worth understanding. Ask questions, listen carefully, and be respectful of people’s time. You can learn something from almost anyone at any level.
- Practise reflective listening as a deliberate skill. Listening is the most consistently underestimated skill in BA work. Offering back what you have heard, to confirm your understanding before moving on, keeps you active in complex conversations and builds genuine trust with stakeholders faster than almost anything else.
- Do not underestimate the value of a sense of humour. BA work involves asking uncomfortable questions and surfacing gaps that people would rather not acknowledge. A genuine, well-placed sense of humour makes those conversations easier, reduces your own stress, and builds rapport across very different personality types.
Certification vs Experience: How They Compare
One of the most common questions I hear from early and mid-career BAs is whether to prioritise certification or practical experience. The honest answer is that they do different things, and the strongest candidates have both. Here is how they compare in practice.
| Factor | Certification | Practical Experience |
|---|---|---|
| Signals credibility to employers | Yes, particularly when entering a new industry | Yes, particularly when supported by concrete examples |
| Builds structured knowledge of the discipline | Strong: frameworks, terminology, and methodology | Variable: depends on quality and range of projects |
| Demonstrates real-world judgement | Limited on its own | High, especially with complex or difficult projects |
| Supports a career pivot into BA from another field | Very useful as a credibility bridge | Harder to demonstrate without the title |
| Keeps you current with the profession | Requires renewal and continuing education | Depends entirely on the types of projects you take on |
| Cost | $100 to $600 depending on level and provider | Time investment rather than direct cost |
If you are weighing your options on certification specifically, this overview of BA certifications covers the main options across different career stages.
Where AI Fits Into Your BA Career Development
The tools available to BAs have changed significantly, and AI is increasingly part of how good BA work gets done. I want to be direct about what this means in practice, because a lot of the commentary around AI and the BA role misses the point. The core discipline has not changed. Requirements still need to be complete, traceable, and appropriate to the stakeholder audience. The thinking is still yours. What AI changes is how efficiently you can do the structured, repeatable parts of the work: drafting, structuring, formatting, and gap-checking documentation that previously took hours.
For BAs working on requirements documentation in particular, this shift is meaningful. The time recovered from those tasks is time you can redirect toward the analysis, facilitation, and stakeholder work that requires human judgement and cannot be automated. BAs who treat AI tools as a capability amplifier rather than a threat tend to be more productive and more visible in the organisations they work in. If you want a clear-eyed look at what AI actually changes about the role, this piece on AI for business analysis is worth your time.
The habits that build a strong BA career have not changed in the twenty-five years I have been doing this work: ask better questions than everyone else in the room, document what you find in a way that makes it easy to act on, build trust across the business and technical divide, and keep your focus on the value the organisation is actually trying to create. Those habits compound. The BAs I have watched advance fastest are not the ones who knew the most tools or carried the most credentials. They are the ones who made the people around them feel genuinely heard, and who produced work that made it easier to make good decisions. That is still the job, and it is still worth doing well.
Frequently asked questions
How do I advance my business analyst career?
Focus on building the habits that compound over time: asking better questions, practising reflective listening, and producing work that drives decisions rather than just documentation. Pair that with deliberate skill development through certification and structured self-assessment against frameworks like the IIBA BABOK. Visibility matters too, so look for opportunities to lead elicitation sessions, mentor junior colleagues, and contribute to more complex or cross-functional projects.
What skills do I need to develop as a business analyst?
The skills that matter most are stakeholder communication, requirements elicitation, structured analysis, and the ability to adapt your approach to the context of a project. Technical skills like process modelling, data analysis, and documentation are important and worth developing steadily. The habit of reflective listening, genuinely confirming your understanding before moving on, is one of the most underestimated skills in the profession.
Is certification important for a business analyst career?
Certification demonstrates credibility and gives you a structured framework for your practice, which is particularly useful when you are entering the field or moving into a new industry. Practical experience matters equally to most employers, and the two together are more powerful than either alone. The ECBA is the natural starting point for early-career BAs, with CCBA and CBAP as your experience grows.
Will AI replace business analysts?
AI is changing how BAs do parts of their work, particularly the documentation-heavy and structurally repetitive tasks, but it is amplifying the role rather than replacing it. The core BA skill set, stakeholder communication, requirements analysis, facilitation, and problem structuring, is fundamentally human and not easily automated. BAs who embrace AI tools as a capability amplifier tend to be more productive and more valuable, not less relevant.
How do I get business analyst experience if I am just starting out?
Look for opportunities within your current role to do BA-adjacent work: documenting processes, facilitating requirements conversations, or mapping stakeholder needs. Volunteer for project work where you can observe or contribute to requirements activities, and consider entry-level certification to build a credible foundation. Engaging with BA communities online where experienced practitioners share real-world knowledge is also a practical way to accelerate your learning.
Try Ash, Your Virtual BA
If you are working on building your BA knowledge alongside your career, Ash Virtual BA gives you two practical resources in one place. The Ash Glossary covers business analysis concepts, terms, and methods in plain language, with working examples drawn from real BA practice, exactly the kind of grounding that supports the habits this article describes. For BAs actively working on requirements documentation, the Ash BRD Writer guides you through a structured elicitation process that models rigorous BA practice from first question to confirmed requirements summary. Whether you are learning the discipline or applying it on a live project right now, Try Ash Virtual BA and see where it takes your next piece of work.
Further reading
Written by Sam Cordes, founder of the Business Analyst’s Toolkit.