Entry level business analysts are entering the profession at a uniquely complicated moment. The tools are more powerful than ever. The learning curve has never been steeper. And the pressure to move fast exists in tension with the need to build real, durable judgment.
Organizations are hiring junior BAs and handing them AI tools, expecting productivity quickly. And they can get it. But there is a difference between a junior BA who can produce outputs fast and a junior BA who is genuinely developing the craft. If we are not deliberate about how we develop entry level BAs in an AI environment, we risk creating a generation of practitioners who can generate requirements but cannot think through a complex business problem without a prompt to lean on.
This piece is for two audiences: junior BAs who want to develop well, and BA managers and organizational leaders who want to build a team that actually knows what it is doing.
Here are five approaches to consider for developing Business Analyst skills for entry-level BAs:
1. Learn the Technique First. Then Bring in AI. Then Compare.
The most important thing a junior BA can do early in their career is learn to perform core BA techniques without AI assistance first. Not because AI is bad. Because you cannot evaluate something you have never done yourself.
When a junior BA writes their own process flow, facilitates their own elicitation session outline, or drafts their own requirements without AI, they are building a mental model for what good looks like. They are developing instincts. They are learning where the hard parts are and why.
Once that foundation exists, even modestly, bring AI into the work. Run the same exercise with AI assistance. Then compare. Where did the AI output match what you produced? Where did it go deeper? Where did it miss something that you caught? Where did your organizational context and stakeholder knowledge change everything?
This teaches junior BAs to evaluate AI output rather than simply accept it, and it gives them a real sense of where their human judgment adds value.
For managers: build this into onboarding deliberately. Do not skip the manual step because AI can do it faster. The slower path builds better analysts.
2. Use AI as a Coach, But Teach the Prompts That Matter.
AI can be a remarkably effective learning coach for junior BAs. It is patient, available, and capable of explaining complex concepts in multiple ways until something clicks.
But the way most people use AI as a coach produces shallow learning. Asking AI to explain a concept or give you an example is useful. Asking AI to challenge your thinking, expose the gaps in your analysis, or stress-test your assumptions is far more valuable.
Teach junior BAs to prompt AI this way. Phrases like “What am I missing in this requirements analysis?”, “What assumptions am I making that I should test?”, and “Where is my logic weakest here?” produce a fundamentally different quality of learning interaction than “How do I write a user story?” or “Write me a user story for this.”
3. AI Role Play Designed Specifically for the BA Role.
Business analysis is a conversational craft. So much of what makes a great BA great is how they facilitate a stakeholder conversation, how they navigate a difficult session with a development team, how they handle a room where three people have conflicting priorities and a decision needs to get made.
Those skills are built through repetition. The challenge for junior BAs is that the real meetings are high-stakes environments for learning. You cannot practice on stakeholders the way you can practice a technical skill in a sandbox.
AI role play changes that. A junior BA can simulate a requirements session with a skeptical product owner, a conversation with a development team pushing back on scope, or a discussion with a business leader who is not sure what they want yet. Specific, realistic, BA-focused scenarios run as role plays with AI give junior BAs repetitions they simply cannot get any other way.
The key is specificity. Generic role plays produce generic learning. Role plays designed around real BA conversation types, including the nuances of facilitating AI fluency conversations with stakeholders who are new to the topic, build the skills that actually matter.
4. Shadow, Observe, and Reflect Together.
There is knowledge inside an experienced BA that does not live in any document or training module. It lives in how they prepare for a meeting. In what they notice in the first five minutes of a conversation. In the question they ask that shifts the whole discussion. In the thing they choose not to say yet.
Junior BAs need access to that knowledge, and the only way to get it is proximity.
Structured shadowing means more than attending the same meetings. It means a junior BA watching a senior BA prep, understanding what they are anticipating, what concerns they are carrying in, what outcome they are hoping to create. It means sitting in the meeting specifically to observe, not to contribute, and paying attention to the how, not just the what.
And critically, it means sitting down together after the meeting for a genuine reflection. What did you notice? What would you have done differently at that moment? Why did I ask that question when I did? What was I reading in the room?
That joint reflection is where shadowing becomes learning. Without it, junior BAs attend meetings and absorb atmosphere. With it, they start to develop judgment.
5. Small Scope Work, With Incrementing Complexity.
Confidence and competence in business analysis are built through completing real work, reflecting on it, and taking on work that is slightly harder next time. Neither too easy nor too overwhelming.
Start junior BAs on work that is well-scoped and bounded. A process flow for a single workflow. Requirements for one feature. Stakeholder mapping for a limited set of users. Give them enough room to own the work and enough support to not get lost in it.
When they complete it, build in a deliberate reflection. What was hard? What would you do differently? What did you learn about the stakeholders or the process that you did not expect? Then increase the scope and complexity of the next piece of work.
This iterative approach to skill building is not glamorous. It is also how genuine expertise gets built. Skipping ahead to complex, high-stakes work too early produces either dependence on more senior team members or, worse, junior BAs who do not know what they do not know.
A Note for Organizations and BA Managers
All five of these approaches require something from the organization: intentionality, time, and the willingness to invest in development even when the pressure to deliver is high.
The temptation right now is to hand junior BAs AI tools, give them tickets, and measure their output. That can produce activity. It does not reliably produce analysts.
The organizations that will have strong BA teams in three years are the ones building them deliberately today. The investment is not large. The return, in terms of team quality and retention, is significant. Entry level BAs entering the profession now have access to tools and resources that did not exist five years ago. They also face a steeper and more ambiguous learning curve than any previous generation of analysts.
The goal is not to develop junior BAs who are fast. It is to develop junior BAs who are genuinely good and getting better. Those two things can coexist, with the right approach.