r/businessanalysis

Hey everyone! I’m a junior BA currently working with a team of seniors. My experience hasn’t been bad by any means, but lately, I’ve had this nagging feeling that something just isn't clicking for me.

I’m trying to figure out if what I’m feeling is just standard growing pains, or if it’s a common dynamic when you're the only junior in the room. Has anyone else been in this boat? I'd love to hear what your experience was like!

Hi all, Trying to understand the real-world side of business analysis beyond certifications and LinkedIn buzzwords  
Currently learning:
Excel
SQL basics
documentation
process mapping
Meanwhile my actual setup is still:
WPS Office + old laptop + random microsoft office download leftovers. What skills genuinely helped you the most early in your BA career? Thanx in advance..

Like are you and the PO typically meeting stakeholders together, are you splitting up the requirements you cover? how does it look

I have exited the BA career since 5 years ago, so I'm genuinely curious nowadays, in real work settings, which part of the work do you use AI the most or do you think should be handled by AI?

If I were to speak about it, I feel like the note-taking, meeting minute, document reading, deck making, data analysis can all be done by AI. The only part which cannot be done by AI is probably the communication with stakeholders?

Hi,

I’m a new a business analyst (1-2 YOE) and I wanted to ask if certain things that happen at my job are normal or not.

I’m not familiar with all the lingo of a business analyst and I come more from the business side than the IT side but I have a good understanding of tech and software.

When I first started, I really enjoyed my job, I was tasked with improving a process and that’s exactly what I did. I listened to the stakeholders and asked the right questions and altered the process so it made sense with our goals and had the IT department develop the things we needed.

Now, I started working with more people across departments and I’m running into so many challenges and roadblocks and I dont know if its a lack of support from leadership or just maybe I’m doing something wrong.

I’m tasked with analyzing a department and even though I do, it’s like no one wants to hear my recommendations. The people doing the job think there can be no improvements to the process. The people above me want to come up with the ideas themselves. Meanwhile, im the only person who knows the full story but no one wants to know my thoughts. Im just asked to produce endless quantities of documentation that no one reads. I’ve spent so much time revising a massive flow chart that covers the processes of this department end to end. It took me a day or two to create but 2 to 3 weeks almost to actually finalize it because I had 5 other managers involved.

The guy who hired me as a business analyst keeps having so many other people give me direction and it’s getting very painful to work with all of them. I feel pulled in 20 directions and I just do work while they sit in a meeting room and discuss, I have to try and get all 5 managers focused on the same topic it’s like trying to ride a cart being pulled by 5 horses and cows.

I thought I was supposed to gather the information, make recommendations, meet with leadership, and execute their vision. I have so many people involved who don’t know what they’re doing and I really hate this.

Can someone give me some advice?

hii, everyone I am currently 22, just started a job in bpo but i this is not something i want to do my entire life. so i am looking to make a change as soon as possible. I want to become BA, so to be accepted by industry please tell me requirements and also sources or certifications relevant for the same...

Hi, this question may have been asked in this forum multiple times and I went through some older posts, but I will still put this here as I need some affirmation to decide whether I go for it or not.
I want to understand if it is advisable that I take this exam with only 3 years of experience in business analysis. I have been a test engineer for 8 years before that so I have done a lot of UAT if that matters.
If you have taken CBAP previously, how has it benefited you?
How long did it take for you to prepare for the exam?
Did you take IIBA membership and then registered for the exam?

Any other suggestions are welcome.

Option 1
100% onsite
~30% higher salary
More tech-focused environment
Stronger team, newer technologies, AI adoption
Better learning/growth potential
But workload and pressure seem much higher
Unstable, easy to layoff after 2 year
Option 2 - current company
Fully remote (~$2.7k/month)
Comfortable and stable
Good WLB (maybe also depends on project stage)
But company is not tech-focused
Older team
Domain feels repetitive/boring
I feel like my growth is slowing down

I’m 28F from Vietnam, BA/Product side role, and trying to think long-term about career growth vs comfort/stability.
For people who made similar moves:
Did joining a stronger tech environment significantly improve your career?
Was giving up remote worth it?
Or is this just “grass is greener” thinking?

we just finished the dev phase of an internal enterprise system, and now we’re entering the usual handover stage: creating user guides, SOPs, training materials, and supporting UAT/business users.

Traditionally we would:
- Write detailed user guide documents
- Create screenshots/manual flows
- Conduct training sessions
- Answer repeated questions during UAT/go-live

I’m wondering how teams are using AI to speed this up or even replace parts of this process.

Some ideas I’m thinking about:
- Auto-generating user guides from requirements/screens/recordings
- Using AI to summarize flows into SOPs
- Building an internal chatbot so users can ask questions instead of reading huge PDFs
- AI-generated walkthroughs/training materials
- Recording UAT sessions and converting them into knowledge docs

Questions:

1. Which parts we can use AI for this stage?
2. Any practical workflow/methodology you recommend?
3. Is chatbot-style support actually effective for enterprise users?
4. What tools/ AI are people using for this?

Main limitation:
My company only allows Microsoft Copilot 365 currently, so options feel pretty limited compared to using external AI tools/platforms.

Would love to hear real experiences, best practices, or architectures that worked for your team.

Tried something at work this week that worked better than I expected, and I want to share where it broke down because that's the more useful part.

Context: I'm a Tech BA on a payments API project at a Canadian bank. ISO 20022 backend, Kafka, AWS, the usual stack. New integration coming in, and I needed to produce a functional analysis page in Confluence that matched the team's reference format.

The setup was two agents in sequence. Agent 1 had access to the legacy services codebase and I asked it for the complete flow of the existing integration. Request mapping, validations, Kafka topics, error handling, the lot. Agent 2 had MCP access to Confluence with my PAT, plus the new API contract, plus a link to a reference page that represented "good" in our team. I gave it Agent 1's output, my own writeup of what the new service needs to do, and asked it to produce the new page.

The draft was honestly close to ship-quality on the technical mapping. Giving it the contract was the unlock there, it stopped hallucinating field names and the request/response examples actually validated. Field-by-field, it was solid.

Where I spent my cleanup time was somewhere else entirely.

The agent treated the reference page as inspiration instead of as a contract. It added sections that weren't in the reference (an assumptions block, a risks block, a glossary it invented). It drifted on the color scheme for the Confluence panels and lozenges, which I think is because I gave it the rendered page instead of the storage format. And it put code snippets inside a functional analysis page, which on our team is a hard line, code lives in the technical analysis page, not this one. The agent doesn't know that's a team convention, it just knows "technical documentation usually has code blocks."

Lesson I'm taking from this: the reference page is doing double duty as both the template and the example, and agents can't separate those two roles. Next time I'm going to maintain a stripped-down template with empty sections and inline notes like "field mapping table goes here", separate from a finished example for tone. Then the prompt becomes "fill the template, use the example for tone only, do not copy its structure."

The other thing I'll change is the prompt order. Constraints first (no added sections, no code blocks, match these macros), task last. Agents weight recent instructions heavier, so burying the constraints above the task lets them survive the generation.

PS, audit traceability is a thing worth thinking about if you do this in a regulated shop. Every edit Agent 2 made to Confluence shows up under my name in the page history. Fine for a draft, less fine if it's pushing directly to a page devs reference.

Curious if anyone else has run this kind of two-agent setup for spec work. Especially interested in how you handle the "follow the format exactly" problem, because that's where mine still leaks.

I f27 have been working as lead BA for 3 months now, managing a team of 3 BAs, handling C level stakeholders, checking user stories, brainstorming features, thinking of edge cases and assumptions, doing basic data analysis, EDAs and checking data reports of data team. On which i make decisions for tech feasibility. Etc etc

I generally like the part where I am more in the thinking mode, rather than taking stakeholders meetings. I am good at playing political strategies but feel tired of it.

I was thinking about what's next for a lead BA? What all options do i have ?

I guess I have streams like,

domain expert BA

Data/ BA

Product/ BA

Product owner

Consultant

As a BA I’ve started using AI for the repetitive drafting work — user stories, BRD sections, meeting summaries — and it’s genuinely saved me hours every week. The parts it can’t touch are the stakeholder relationships, the organisational context, and knowing which requirement is actually hiding a political landmine. Would love to know where others are using it and where it’s let them down — feels like we’re all figuring this out in real time

Step 1: Start with a Bachelor’s degree in Business, IT, Economics, or Engineering. While not mandatory, formal education helps you understand business processes, data, and systems, which are core to a Business Analyst role.

Step 2: Develop the ability to work with data and extract insights. Focus on Excel and Advanced Excel, SQL for data querying, Basic Statistics and Data Interpretation, and Data Visualization tools like Power BI or Tableau

Step 3: Learn Stakeholder Analysis, Business Process Mapping, Requirement Gathering and Documentation, and a basic understanding of domains like Finance, Healthcare, or E-commerce

Step 4: Apply your knowledge in real-world scenarios. Work on tasks like creating reports and dashboards, documenting business requirements, analyzing workflows, and identifying improvements, and focus on solving real business problems. Start with internships, freelance projects, or entry-level roles.

Step 5: Showcase your skills through a portfolio by including case studies of business problems you solved, dashboards and data analysis projects, and documentation samples like BRDs or user stories. Use platforms like GitHub or portfolio websites to present your work professionally.

Step 6: Validate your expertise with recognized certifications like CBAP® Certification Training. Certifications help you stand out and build credibility in the job market.

Step 7: As you gain experience, choose a specialization: Data Analyst or Analytics-focused BA, Product or Agile Business Analyst, or a Domain Specialist, like Finance or Healthcare.

Career Path and Growth in Business Analysis:

• Entry-Level Roles: Junior Business Analyst or Associate Analyst
• Mid-Level Roles: Business Analyst or Product Analyst
• Senior Roles: Senior Business Analyst or Lead Analyst
• Advanced Roles: Business Analysis Manager or Consultant

I recently accepted a BA position in a new department and I’m going absolutely crazy. Have a lot of big projects in the pipeline but nothing gets delegated around here so I’m constantly meeting with only directors, chiefs, etc. of the organization and their calendars are too hectic to put any meaningful amount of time into discussing requirements, workflows, etc. Apparently they are the only ones that know enough about any of these initiatives or projects to speak on them.

I don’t know how sustainable this is. I’ve been very communicative with my supervisor that my blockers are literally just these people’s calendars- they don’t have time to meet. But I feel like at some point this excuse is going to get old.

I’ve even resorted to trying to gather requirements asynchronously via emails, but it’s just so inefficient.

A lot of people think verification starts and ends with KYC.

But once you onboard a business, things get more complicated.

KYC helps verify the individual while KYB looks at the legal entity behind them. That means looking beyond basic company details. 

Teams also need to understand whether the business legally exists, who owns or controls it, and whether there are risk signals like sanctions exposure, adverse media, or links to high-risk jurisdictions. 

And this matters because a company can look clean on the surface, and the person applying can pass KYC, but the real risk might be hidden in the company structure.

For example, the person you see might not be the real decision-maker. The company could be owned through several other companies in different countries. Or there could be a nominee director, meaning someone is listed officially, but someone else controls things behind the scenes.

So the risk is not always tied to one visible person.

Corporate registries vary by country, disclosure requirements are not always consistent, and ownership structures can stretch across multiple layers and jurisdictions.

Automation helps reduce manual work, but it does not make the process perfect. Corporate data can still be uneven, outdated, or based on self-reporting.

That’s why KYC and KYB are becoming more continuous. A business might look fine during onboarding, but its ownership, sanctions exposure, or risk profile can change later. This is a tactic often used by fraudsters: look legitimate at onboarding, then introduce risk later through changes in ownership, control, or business activity.

So the bigger point is simple: trust in financial systems now needs layers.

KYC and KYB together give teams a clearer picture of who they’re dealing with. KYC helps identify the people behind a business, while KYB adds context around the company itself. Ongoing monitoring then shows how that risk profile changes over time.

I just made an internal transition to a BA role after working up through operations over several years. The role has never existed in this company. Devs have met directly with the business until now. I will skip the personal details but my experience and trajectory at the company make me a perfect fit, and I’ve been working toward this for a long time. I’d love to hear from experienced BAs: If you had to build the role from the ground up at a company that’s never had a BA - and has needed one for too long - what would be your approach?

Looking for recs on incrementality testing platforms. Currently evaluating options for measuring true lift against baseline performance across our mobile campaigns. Need something that can handle holdout groups properly and integrate with existing attribution stack.

What tools have given you the most reliable incrementality reads?It will be a plus if they play nice with complex funnel analysis and don't break the bank.

Trying to position myself for Business Analyst / Product Operations roles — would appreciate honest feedback

Hi everyone,

I’m currently trying to position myself more clearly toward Business Analyst / Functional Analyst / Product Operations roles, and I’d really appreciate some honest feedback from people already working in these areas.

My background is somewhat hybrid:

• functional analysis
• QA collaboration
• operational/process workflows
• stakeholder communication
• documentation
• product delivery coordination

I also independently shipped 2 small mobile products to better understand product lifecycle, iteration, requirements, QA and user flows end-to-end.

One thing I realized recently is that I was applying too broadly before (PM, QA, Support, BA, etc.) and probably presenting an unclear profile. I recently rewrote my CV to focus more on BA / Product Operations style positions.

Main questions:

• Does this profile feel coherent for BA-type roles?
• What type of Business Analyst positions would fit best?
• What skills/certifications would strengthen this profile the most?
• Is there anything recruiters or hiring managers would immediately see as a weakness/red flag?

I can share anonymized CV screenshots privately if anyone is willing to take a look.

Thanks a lot to anyone willing to help.

Hi everyone,

I’m currently working as an administrative assistant and I’m trying to figure out how realistic it is to transition into business analysis, especially within finance.

In my current role, I’m already doing quite a bit of data and reporting work, including:

• Building an interactive Excel dashboard and updating it weekly/monthly for management review
• Feeding and maintaining data regularly for reporting purposes
• Creating and automating multiple Microsoft Forms for internal workflows
• Building an automated ordering/products tracking chart
• Doing bank reconciliations and supporting financial reporting tasks
• Handling various reporting and data organization tasks for management decision-making

Alongside this, I’ve also completed the Canadian Securities Course, and I’m very interested in eventually moving into financial analysis — ideally roles where I can look at investment opportunities, whether in commercial real estate or broader investment analysis.

My main question is: does this type of admin + reporting + Excel-based experience realistically translate into business analysis or finance-related analyst roles?

And if anyone has made a similar transition, what skills or certifications helped you bridge that gap?

Would really appreciate honest feedback on how to position myself better.

I want to follow up on something I talked about earlier. It is about the requirements for a project that had a lot of data. I learned something from the same project.

When we started working on the requirements I spoke with two groups of people separately.

The managers told me that they had a workflow:

the operator enters production data at the end of their shift

the system checks to make sure the entry is correct

the inventory updates on its own

a report is made the morning

if there are any problems they go to the managers queue

The operators told me that things actually work differently:

the operator makes an estimate of the number during their shift if they are too busy to count

they count again at the end of their shift if they disagree with their supervisor

sometimes they enter the number from the shift first because the form keeps the old value

they call the floor manager if the system does not accept the entry

they ask the operator what to do if the part code is missing

Both groups thought they were talking about the same process.. They were not wrong. They were just talking about parts of the same workflow.

I wrote the requirements document using the manager workflow first. That document was reviewed three times. Then it was approved and the build started.

The build failed when it was tested. It was not because the code was bad. It was because the system was built for the manager workflow. The operators were going to use it in a different way.

We had to change 40% of the screens to make them work with the real way things are done. We had to add form fields that could handle entries. We had to add validation that would warn of reject. We had to add a path for the supervisor to override things, which was not in the plan because the managers did not know it existed.

The thing I keep thinking about as a Business Analyst is that managers describe how things should work. The operators describe how things really work. The requirements document has to include both or the build will be correct but not useful.

There are three things I would do differently on the project that has a lot of data:

1. I would interview the operators first the managers. The manager workflow is like the limit. The operator workflow is like the limit. The requirements document has to be in between.

2. I would ask the operators what they do when the system does not agree with them. Their answers would show the paths that the plan did not include.

3. I would show the draft requirements to both groups separately before they are approved. If the operators say "we do not work like that". The managers say "yes you do" then that difference is the real requirement.

For Business Analysts who work on software for operations, ERP or workflow projects:

How do you handle the difference between the workflow that managers describe and the workflow that operators actually use? Do you make two maps of the process and then combine them or have you found a way to capture both in one document?

For those who have had problems with this: at what point in the project did you usually realize that the plan was capturing the wrong workflow? Was it, during the review of the requirements when the build was being done, during testing or after it was launched?