From BA-ish to BA-shaped: A Simple BA Skills Plan for 2026

If your BA development plan is basically “learn more” and “get better”, you’re not alone. A lot of capable people are doing BA work without the title — and without a clear map of what good looks like. 

The result is predictable: more rework, more circular conversations, and more second-guessing than necessary. 

This article gives you a simple planning method you can do in under an hour. By the end, you’ll have: 

  • a clear list of the BA work you already do (and the parts you dodge) 

  • two capability gaps to focus on this quarter 

  • a realistic next step you can actually fit into your calendar 

It will help you stop overpromising your deliverables — and start building capability in a way you can sustain. 

If you’re doing BA work without the title, you’re not alone

In many teams, BA work lands on whoever is dependable and organised. 

You might be in support, ops, product, project work, UX, data, or change. And you end up being the person who: 

  • captures what the business needs 
  • documents processes and rules 
  • keeps stakeholders aligned on what “we’re changing” and “why” 
  • translates business needs into something a delivery team can work with 

So what’s the issue if you’re already doing these things? 

Usually, it’s because there’s: 

  • no shared language (everyone means something different by “requirement” or “scope”) 
  • no sequence (you’ve picked up techniques, but not in a useful order — and you’re not sure how to apply them) 
    You’ve learned bits and pieces — but not the order that makes them work. 
  • no toolkit you trust (you don’t know which approach fits which situation, or which BA tools you actually need) 

When these combine, it’s easy to be doing valuable work and still feel unsure about your approach. 

Step 1: Map the BA work you already do 

Don’t start with a future job title. Start with your actual work. 

Spend 10 minutes listing the BA-ish tasks that show up in your role. Typical examples include: 

  • Clarify the need: what’s required, what “good” looks like, and what’s out of scope 
  • Map the process: the current flow, pain points, and a better future flow 
  • Define business rules: exceptions, approvals, handoffs, constraints 
  • Write requirements: a clear list, brief, or structured set of needs 
  • Align stakeholders: priorities, roles, and decision rights 
  • Think through impacts: users, teams, policies, training, reporting — after the change goes live 
  • Agree “done”: acceptance criteria and sign-off before work starts 

Don’t only list what you do confidently. List everything you end up doing — including the parts where you feel uncertain. 

Then tag each item using these four self-evaluation labels: 

  • I do this well (confident and consistent) 
  • I do this, but it’s shaky (I do it, but I’m not always sure it’s good-quality) 
  • I avoid this (it comes up, but I delay it, delegate it, or hope someone else handles it) 
  • I don’t know how (I’m not sure what good looks like, so I wing it or leave it hanging) 

This works because it stops vague thinking. Instead of “I should improve”, you get a real picture of where you’re solid — and where things are shaky. 

A quick scenario you’ll recognise 

A manager says, “We need to improve the handover process. Customers are getting frustrated.” 

Everyone agrees it’s a problem. No one agrees on the cause. Ops thinks it’s training. Another team thinks it’s the form. Someone suggests a new tool. 

You get pulled in to: 

  • write down what the business needs 
  • map the process as it really works (not as it should work) 
  • capture rules and exceptions 
  • help the group agree what changes first 

That is BA work. The challenge is doing it consistently — not just “sorting it out” each time. 

Step 2: Choose 2 gaps that matter (for this quarter) 

This is where most people go wrong: they try to fix everything at once, and end up doing nothing well. 

Pick two gaps. Two that keep showing up — and keep slowing you down right now. 

Common gaps for people doing BA work without the title: 

  • Stakeholder alignment: meetings go in circles and decisions keep reopening 
  • Requirements quality: what you write gets misunderstood, challenged, or ignored 
  • Technique choice: you’re not sure whether to map a process, write rules, run a workshop, or produce a simple brief 

How to choose your two: 

  1. Look at your Step 1 list. 
  1. Circle the items that create the most stress, rework, or delay. 
  1. Ask: “If I got better at this, what would become easier at work this quarter?” 

Two is enough to make real progress — because you can actually practise and embed what you learn, instead of spreading yourself thin. At the end of the quarter, reassess and choose your next two. 

Step 3: Build a realistic pathway 

Once you know your two gaps, you need a pathway that actually supports them. 

Here’s a simple, reliable sequence: 

1) Foundations 

Foundations give you shared language and core BA concepts that make everything else easier. They help you stop guessing — and start choosing techniques on purpose. 

Without foundations: 

  • you learn techniques in isolation 

  • you apply them inconsistently 

  • you keep doubting whether you’re doing it “properly” 

2) One structured course that matches your gaps 

Here’s the key: don’t scatter yourself across random learning. 
Skip the scattergun approach. Choose one course that matches your gaps, complete it, then practise it. 

A good course does two things at once: 

  • it gives you the structure and sequence you’ve been missing 

  • it gives you a toolkit you can apply immediately to real work 

3) Deliberate practice in your day job 

The real shift happens when your learning starts showing up in your day-to-day work. 

Use this simple approach: 

  • pick one real piece of work 

  • apply one technique properly 

  • note what changed (clarity, fewer follow-ups, less rework, better decisions) 

  • repeat the next week 

For example: when a change request arrives, start by writing a clear problem statement and drawing a simple process map before anyone proposes solutions. Done regularly, this turns learning into a habit you rely on — not something you collect. 

Three mistakes to avoid this quarter 

1. Overcommitting
A plan that ignores your workload and what you can realistically take on is a plan you won’t follow. 

2. Skipping foundations
If you don’t have a solid base, you’ll keep feeling unsure about what to do — and when to do it. 

3. Chasing titles over capability
Titles are nice, but capability is what earns trust and creates real career progression. 

To summarise: Your minimum viable BA plan template (for this quarter) 

Use this checklist to build your BA progression plan — and refer back to it over the next 12 weeks to stay on track. 

Checklist: Minimum Viable BA Plan 

  • Action 1 (15 min): List the BA work that shows up in your role, then tag each item: do well / shaky / avoid / don’t know how 

  • Action 2 (15 min): Pick two gaps that are costing you the most time, confidence, or rework this quarter 

  • Action 3 (10 min): Choose your next step: foundations first, then one structured course that matches your gaps 

  • Timebox (5 min): Block one weekly slot in your calendar for practice (even 30 minutes) 

  • Say no to (5 min): Write down one thing you are not doing this quarter (e.g., “no extra courses until I finish foundations and apply them twice”) 

If you only do one thing after reading this, do the checklist. The best way to build momentum is simply to start. 

A calm, practical next step 

If foundations are the missing piece, Foundation in Business Analysis is a strong starting point for formalising the core tools and concepts you need to operate confidently. 

You don’t need more random training. You need a simple pathway — starting from the BA work you already do — and a foundation you can build on. 


{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}
>
Success message!
Warning message!
Error message!