The role of technology in crafting customer experience

19 Feb 2026

How to Transition into BA Work from a Non-BA Role

How to Transition into BA Work from a Non-BA Role

"I'm in admin/project management/support/operations. How do I become a BA?"

I get this question every week.

And here's the good news: Most successful BAs didn't start as BAs.

I didn't. I started in operations. Then moved into BA work.

And the BAs I mentor come from:

  • Admin

  • Project management

  • Customer support

  • IT support

  • Operations

  • Finance

  • HR

You don't need a BA background to become a BA.

You need to position what you're already doing as BA work.

Here's how.

Step 1: Understand What BAs Actually Do

Most people think BAs write requirements documents.

That's part of it. But BA work is broader than that.

BAs:

  • Identify problems

  • Gather information from multiple sources

  • Analyse current processes

  • Propose improvements

  • Facilitate decision-making

  • Bridge the gap between business and tech

If you've done any of these, you've done BA work.

Step 2: Find the BA Work You're Already Doing

Let's look at common roles and the hidden BA work in each.

From Admin → BA

Admin work that's actually BA work:

  • Process documentation: You've documented how things work (that's process mapping)

  • Coordination: You've gathered input from multiple people to make decisions (that's requirements gathering)

  • Problem-solving: You've identified inefficiencies and proposed improvements (that's business analysis)

How to position it:

  • "Documented invoice approval process across Finance, Procurement, and Operations (15 steps, 4 stakeholders, identified 3 bottlenecks)"

  • "Proposed process improvements that reduced approval time from 2 weeks to 3 days, saving 40 hours/month"

From Project Management → BA

PM work that's actually BA work:

  • Requirements gathering: You've collected requirements from stakeholders (that's core BA work)

  • Scope management: You've defined what's in/out of scope (that's requirements analysis)

  • Stakeholder management: You've facilitated workshops and managed conflicting priorities (that's BA work)

How to position it:

  • "Gathered and documented requirements from 8 stakeholders across Finance, Operations, and IT for CRM implementation"

  • "Facilitated 12 requirements workshops, identified 15 must-have vs. nice-to-have requirements, reducing scope by 30%"

From Customer Support → BA

Support work that's actually BA work:

  • Root cause analysis: You've identified patterns in customer issues (that's analysis)

  • Process improvement: You've proposed changes to reduce repeat issues (that's business analysis)

  • Requirements gathering: You've collected customer feedback and translated it into product improvements (that's BA work)

How to position it:

  • "Analysed 500+ customer complaints, identified 3 recurring issues accounting for 60% of all tickets"

  • "Proposed system improvements that reduced ticket volume by 40%, saving 20 hours/week of support time"

From IT Support → BA

IT Support work that's actually BA work:

  • Requirements gathering: You've gathered user requirements for system changes (that's BA work)

  • Process documentation: You've documented how systems work (that's technical BA work)

  • Gap analysis: You've identified gaps between user needs and system capabilities (that's BA work)

How to position it:

  • "Documented user requirements for new HR system, working with HR, IT, and Payroll stakeholders"

  • "Identified gaps between current system and user needs, proposed 5 system improvements adopted by IT"

From Operations → BA

Operations work that's actually BA work:

  • Process improvement: You've optimized workflows (that's business analysis)

  • Data analysis: You've analysed operational data to inform decisions (that's BA work)

  • Stakeholder coordination: You've worked across teams to solve problems (that's BA work)

How to position it:

  • "Mapped order fulfillment process, identified bottleneck causing 3-day delays, proposed improvement reducing lead time by 40%"

  • "Analysed 6 months of operational data, identified root cause of delays, presented findings to senior leadership"

Step 3: Build a Portfolio (Even If You're Not a BA Yet)

You don't need permission to build a portfolio.

Pick 2-3 projects from your current role and document them as BA work:

Portfolio Piece #1: Process Improvement

  • Map a current process (As-Is)

  • Identify problems

  • Propose improvements (To-Be)

  • Quantify impact (time saved, cost saved)

Portfolio Piece #2: Requirements Document

  • Pick a project where you gathered input from multiple people

  • Document the requirements formally

  • Show how you prioritized (MoSCoW, for example)

Portfolio Piece #3: Analysis & Recommendations

  • Pick a problem you've analysed

  • Document your analysis (data, root cause, options)

  • Show your recommendation and the outcome

Step 4: Update Your CV

Don't wait to change your job title.

You can position yourself as having BA skills today.

Before (Admin CV):

  • "Processed invoices"

  • "Coordinated meetings"

  • "Maintained spreadsheets"

After (BA-positioned CV):

  • "Analysed invoice approval process across Finance, Procurement, and Operations; identified bottleneck causing 2-week delays"

  • "Proposed process improvements reducing approval time from 2 weeks to 3 days, saving 40 hours/month"

  • "Documented As-Is and To-Be process maps, presented business case to senior leadership"

Same work. Different framing.

Step 5: Target the Right BA Roles

Don't apply for Senior BA roles if you're transitioning from admin.

Target:

  • Junior BA roles (if you have 0-2 years of relevant experience)

  • BA roles at smaller companies (they're more flexible on background)

  • Industry-specific BA roles (if you have domain expertise, e.g., finance, healthcare, retail)

Example:

  • If you've worked in finance for 5 years (even in admin), you have valuable domain knowledge. Target Finance BA roles.

Step 6: Handle the "No BA Experience" Objection

In interviews, you'll hear: "But you don't have BA experience."

How to respond:

"You're right, my title wasn't Business Analyst. But I've been doing BA work for [X years].

I've:

  • Mapped processes and identified inefficiencies

  • Gathered requirements from multiple stakeholders

  • Proposed and implemented process improvements

  • Analysed data to inform decisions

Here's an example: [tell story from your portfolio]

What I'm looking for is a formal BA role where I can apply these skills full-time."

Position it as:

  • You've been doing BA work (just not with the title)

  • You have proven results (portfolio proves it)

  • You're looking to formalize it

Step 7: Fill Knowledge Gaps

You don't need a degree. But you might need to learn some BA frameworks.

Learn:

  • Process mapping (BPMN, swimlane diagrams)

  • Requirements techniques (MoSCoW, user stories, use cases)

  • Business case development

  • Stakeholder analysis

Free resources:

  • YouTube (search "BA process mapping tutorial")

  • IIBA (International Institute of Business Analysis) free resources

  • Bridging the Gap (free BA guides)

Optional:

  • BCS Foundation certification (£500-£2,000)

  • IIBA CBAP/CCBA (if targeting senior roles)

But: Don't wait to get certified before you apply. Certifications help, but experience matters more.

Timeline: Admin/PM/Support → Junior BA

Month 1-2: Build portfolio

  • Identify 3 projects from your current role

  • Document them as BA work

  • Create portfolio website or PDF

Month 3: Update CV and LinkedIn

  • Reframe your experience as BA work

  • Add keywords: process improvement, requirements gathering, stakeholder management, business analysis

Month 4-6: Apply strategically

  • Target Junior BA roles

  • Apply to 20-30 jobs (quality > quantity)

  • Tailor your CV for each role

Month 6-9: Interview and land role

  • Practice telling your transition story

  • Walk through portfolio in interviews

  • Land your first BA role

Total: 6-9 months from starting to transition to landing your first BA role.

(Some do it faster. Some take longer. But this is realistic.)

The Bottom Line

You don't need a BA background to become a BA.

You need to:

  1. Identify the BA work you're already doing

  2. Build a portfolio proving you can do BA work

  3. Position your experience as BA skills

  4. Target the right roles (Junior BA, smaller companies, domain-specific)

The transition is possible. I've seen hundreds of people do it.

You just need to start.

Need help transitioning into BA work?

→ CV & Portfolio Audit (£75): We'll review your current experience and show you how to reframe it as BA work

→ BA Career Accelerator (£2,000+): 8-week mentorship where we build your BA portfolio, update your CV, and position you for BA roles

Book a free call to discuss your transition.