So, What Does a Business Analyst Actually Do?
Photo by CherryDeck on UnSplash
Ask five Business Analysts what they do, and you’ll probably get five different answers — and all of them will be right. The truth is, “Business Analyst” is one of those job titles that sounds both super important and completely vague at the same time. To some people, we’re spreadsheet wizards. To others, we’re glorified notetakers. In some orgs, we’re seen as the people who figure out how to build the thing. In others, we’re the ones trying to keep the chaos under control.
So what do we really do?
At the core, we translate human chaos into structured, buildable things. We work across different parts of the organization, including leadership, operations, developers, end users, marketing, sales, customer service, and finance, to figure out what’s not working, what people actually need, and how to turn that into a plan the technical team can build from without losing their minds.
Sometimes that means writing requirements. Sometimes it means sketching workflows, building process maps, or poking around in data. Sometimes it’s spreadsheets, SQL queries, or drawing a system diagram on a whiteboard while someone tells you, “I think that arrow should go the other way.” And honestly, a lot of times, it’s just sitting down and listening really carefully and then gently helping someone realize they don’t actually know what they’re asking for yet.
A big part of the job is asking questions and lots of them. Not to be annoying, but to get underneath the assumptions, cut through buzzwords, and make sure we’re solving the right problem. We don’t ask to play “gotcha.” We ask because businesses are full of unspoken rules, outdated processes, and unclear goals. Good BAs help bring that into the light.
You’ll hear us ask things like:
- "Why do we do it this way?"
- "What’s the actual goal here?"
- "What would happen if we didn’t do this step at all?"
- "Who else is involved in this?"
- "How do we know this is working?"
We also build bridges between people, departments, and systems. That might look like facilitating a conversation between the accountants who need a report from the ERP system and the developers who built it. Or helping sales and operations agree on what a “customer” actually is. (You’d be surprised how many definitions exist.) We sit in the middle, translating needs, smoothing friction, and helping teams understand each other.
Once a project starts, we’re often the ones keeping it grounded. We track progress, clarify scope, and guard against “just one little change” creeping in from all directions. (Spoiler: there’s never just one.) Change is part of the job, but each one needs to be documented, validated, and prioritized. We help manage expectations, keep people talking, and provide updates that keep stakeholders informed and developers from being interrupted every five minutes with new requests.
That’s not all we do and it doesn’t look the same in every company. Some BAs live in Excel and data dashboards. Others are deep into process design. Some have technical backgrounds and work alongside engineers. Others are more strategy-focused and support leadership with decision-making. The variety is kind of the point.
So, what does a Business Analyst actually do?
- We help people figure out what they need, not just what they say they want.
- We bring structure to messy conversations and clarity to confusing projects.
- We ask better questions, connect the dots, and help teams move forward together.
- We don’t have all the answers, but we make it easier for the answers to show up.
And if we’re doing it right, most people won’t notice the magic. They’ll just notice that things are working a lot better than they used to.
Sources:
Some information in this post was adapted from the following sources: