If someone asked you right now where your BA career is heading, how long would you pause before answering? In my experience, that pause is one of the most reliable indicators of mid-career drift. You have the experience, you are delivering, you are in demand. But you do not have a deliberate business analyst career strategy, and without one, you are letting the market decide your trajectory for you.
This article is not about reframing how you think about career planning. It is about giving you a working method you can apply this week, starting with an honest inventory of where you actually are.
Why BAs Are Particularly Prone to Drifting
The generalist nature of the BA role is both its strength and its career planning liability. The skills that make you effective in the role, the ability to move between domains, translate across technical and business audiences, and adapt to different methodologies, are the same skills that make it easy to slot into almost any project. Organisations will always find work for a competent BA. Being consistently busy feels like momentum, but it is not the same as direction.
There is also an identity problem specific to the role. Because the BA sits at the intersection of business, technology, and process, it is poorly defined in many organisations. Without a clear picture of what the role is supposed to grow into, it is easy to drift toward project management on one assignment, product ownership on the next, and business architecture on a third, without ever deciding which direction actually fits you. If you have hit a ceiling and are not sure why, the structural reasons for that are worth understanding alongside this article. I have written about this in more detail in Experienced Business Analyst Stuck? Here’s Why.
A Three-Step Framework for Deliberate Career Strategy
A career strategy does not need to be a five-year roadmap. It needs to answer three questions with enough specificity to actually change your behaviour: where are you now, where do you want to be, and what is the gap?
Step One: Take an Honest Inventory
Before you plan forward, you need to be clear about what you have actually built. This means going beyond job titles and mapping the following with genuine honesty:
- Capabilities you have genuinely developed: Not the skills listed on your CV, but the ones you could demonstrate under pressure on a new project tomorrow.
- Sectors you understand deeply versus those you have only touched: There is a significant difference between having worked in a sector for six months and understanding its regulatory environment, its stakeholder culture, and its political dynamics.
- Work you find energising versus work you merely tolerate: The distinction matters because the former is where your strongest future positioning lies.
- The level at which you actually operate: Whether that is tactical delivery, programme-level analysis, or strategic problem framing will shape which path forward makes sense.
- Genuine gaps: If most of your career has been in waterfall environments, your agile practice may be shallower than your CV implies. If you have moved frequently across sectors, you may lack the domain credibility that commands senior stakeholder respect in any one of them.
A structured way to do this is to work through the Business Analyst Core Skills assessment, which maps your current capabilities against what the market actually values at each level.
Step Two: Choose a Direction, Even If It Is Not Perfect
One of the most paralysing things about career planning at mid-career is the feeling that you need to make the right choice. You do not. You need to make a choice that is directionally coherent with your strengths and interests, and that is better than no choice at all. Having a primary orientation changes how you evaluate opportunities, how you position yourself in conversations, and where you invest your development effort.
The common branches for a BA at mid-career are set out in the table below. These are not mutually exclusive, and your direction may shift over time. But picking one as your primary orientation is what separates deliberate career movement from drift.
| Direction | Best suited to | Key capability to build |
|---|---|---|
| Deep sector specialisation | BAs who find one domain consistently more interesting than others | Regulatory knowledge, stakeholder network, domain credibility |
| Business or enterprise architecture | BAs energised by strategic problem framing and operating model design | Architecture frameworks, strategic analysis, executive engagement |
| Product management or product ownership | BAs drawn to roadmap decisions, prioritisation, and customer outcomes | Product thinking, commercial awareness, agile delivery |
| Agile or regulatory change specialisation | BAs who want methodology depth rather than domain depth | Agile frameworks, change management, compliance analysis |
| Lead or principal BA with coaching focus | BAs who find more satisfaction in developing others than in solo delivery | Practice leadership, mentoring, BA capability frameworks |
For a broader view of what these paths look like in practice, the article on Career Progression After Business Analyst is worth reading alongside this one.
Step Three: Map the Gap and Work It Deliberately
Once you have a direction, the gap between where you are and where you want to be becomes a working list rather than a source of anxiety. Each item on that list translates into a concrete action: a project type to seek out, a relationship to build, a piece of work to volunteer for, or a skill to develop. Apply the same analytical rigour to your own career that you would to a problem statement from a stakeholder. Vague is not acceptable.
A Worked Example: From Generalist Delivery BA to Strategic Analyst
I worked alongside a BA I will call Sam, who had seven years of delivery experience across utilities, local government, and education. Sam was competent, well-liked, and permanently in demand. Every performance review noted strong stakeholder management and solid documentation. The problem was that Sam had been at the same seniority level for four years, doing essentially the same type of work on progressively larger projects. Busy, but not moving.
When we mapped Sam’s inventory together, a clear pattern emerged. The projects Sam talked about with genuine energy were all at the front end of change: the problem framing phases, the executive workshops where nobody yet agreed on what the problem actually was, the work that happened before anyone started designing solutions. One assignment in a utilities environment, involving enterprise analysis and customer co-design for a major self-service transformation, had been the standout. The delivery phase that followed had felt like routine execution by comparison.
The direction became obvious: enterprise and strategic analysis. The friction came immediately. When I suggested Sam reframe the CV to reflect this, the response was direct pushback: “I don’t have the title or the credentials for that. I’ll look like I’m overclaiming.” That resistance is one I have heard many times, and it is almost always wrong. The CV read as a delivery BA not because the work history was thin, but because every project description led with artefacts produced rather than strategic problems solved. The positioning was the problem, not the experience.
We built a specific twelve-month plan. Sam requested involvement in the initiation phase of an upcoming transformation at the current organisation, making the case directly to the programme director rather than waiting to be assigned. Sam also drafted a short internal paper reframing the customer co-design work from the utilities project as enterprise analysis practice, circulating it to the senior leadership team. And the CV was rewritten so that every project description opened with the strategic problem being addressed, not the documents produced.
Within fourteen months, Sam had moved into a senior BA role with an explicit enterprise analysis remit. The move was not luck. It was the result of a strategy that was specific, sequenced, and grounded in an honest reading of both strengths and gaps.
The Role of Sector Depth in Career Strategy
One of the most undervalued levers in a business analyst career strategy is deliberate sector depth. Many mid-career BAs have accumulated breadth without depth, which makes them versatile but undifferentiated in hiring conversations. A BA who genuinely understands the regulatory environment, the customer base, and the organisational dynamics of a specific sector will consistently be preferred over an equally skilled generalist who does not. This does not mean limiting yourself to one sector for the rest of your career. It means being intentional about which sector you want to be known for, and building depth there rather than treating every new domain as equally useful experience.
Three Disciplines That Make Strategy Stick
Career strategy fails when it lives in a document you open once a year. These three disciplines keep it operational:
- Review your direction quarterly, not annually: Quarterly reviews are short enough that you can still remember what you decided to do and whether you actually did it. Annual reviews are long enough for a full year of drift to occur between them.
- Use your project work as evidence of strategy: Every project you take on is either building toward your intended direction or it is not. You do not have to refuse work that is not perfectly aligned, but you should be conscious of the trade-off and find ways to extract learning that serves your direction even from tangential assignments.
- Tell people where you are going: This is the discipline most BAs resist. Stating your direction feels presumptuous, as though you are claiming something you have not yet earned. In practice, the people who move deliberately in their careers are nearly always the ones who articulate their intentions clearly to managers, mentors, and sponsors. Others cannot help you get somewhere if they do not know where you are trying to go.
If part of your direction involves how you are perceived in the market, the work of building a professional identity sits alongside internal positioning. The article on Business Analyst Personal Brand covers how to do that without it feeling performative.
The most important thing I have learned across twenty-five years of BA practice in government, utilities, health, and enterprise environments is that career direction does not have to be perfect to be useful. A specific, imperfect direction will always outperform a vague aspiration, because it gives you a basis for making decisions rather than just reacting to whatever comes next. Pick your direction, work the gap deliberately, and tell the people around you where you are heading. That combination, more than any credential or lucky opportunity, is what actually moves a BA career forward.
Frequently asked questions
How do I build a business analyst career strategy at mid-career?
Start by taking an honest inventory of your skills, sector experience, and the types of work you find genuinely energising. Then choose a primary direction, even if it is not perfect, and identify the specific gap between where you are and where you want to be. Translate that gap into concrete actions you can take over the next three to twelve months.
Why do business analysts struggle to progress after several years of experience?
Mid-career BAs often drift because the generalist nature of the role makes it easy to stay busy without building a coherent direction. Breadth accumulates across sectors and methodologies, but depth and clear positioning in a specific area do not, which makes it hard for others to see where you should progress to next. The result is that you stay in demand but stuck at the same level.
Should a business analyst specialise or stay a generalist?
Most mid-career BAs benefit from choosing a primary orientation rather than remaining a pure generalist. This might be sector depth, a strategic analysis focus, or a move toward product management or business architecture. You can retain broad skills while building a clearer professional identity that makes your next career move legible to hiring managers and sponsors.
What career paths are available for a senior business analyst?
Common paths include enterprise or business architecture, programme-level analysis, product management, lead or principal BA roles with a coaching focus, and deep sector specialisation. The right path depends on your strengths, the type of problems you find most meaningful, and where your energy is highest in the work you already do.
How do I stop drifting between BA roles and take control of my career?
Commit to a direction, even an imperfect one, and evaluate every new opportunity against it. Tell your manager, mentor, and trusted colleagues where you are trying to head, because others cannot help you get somewhere if they do not know where that is. Review your progress quarterly and use your current project work deliberately to build evidence of the capability you want to be known for.
Try Ash, Your Virtual BA
If part of your career strategy involves deepening your BA knowledge base and sharpening the analytical language you use with senior stakeholders, Ash is a practical place to start. Ash gives you instant access to a BA-specific glossary and knowledge base built around real practice, so you can move into strategic analysis conversations with the vocabulary and framing that commands credibility. It is the kind of tool that supports the direction you have just been planning, not generic AI output, but analysis grounded in BA methodology. Try Ash Virtual BA.
Further reading
Written by Sam Cordes, founder of the Business Analyst’s Toolkit.