Business Analyst Job Description: Responsibilities, Skills and a Real Week

The BA job description is the most abstract in technology. Here is the concrete version, including what you actually produce and who you spend your week with.

Ask five UK employers what a business analyst does and you will get five answers. The title covers everything from writing user stories in a Scrum team to leading a multi-year operating model redesign.

What follows is the common core that appears in nearly every UK BA job description, and the version that is actually true.

The role in one sentence

A business analyst works out what an organisation actually needs, and specifies it clearly enough that someone can build or change it.

The emphasis on actually is the whole job. Stakeholders bring solutions rather than problems: "we need a new CRM", "we need a dashboard", "we need to automate this". The BA's first task is establishing what problem those requests are attempts to solve, which is frequently something different.

The responsibilities that appear in every advert

Elicit and document requirements. Interviews, workshops, observation and document analysis, turned into something unambiguous. This is the definitional activity of the role.

Map processes. Current state and future state, usually in BPMN or a similar notation, identifying where work breaks down, duplicates or waits.

Write user stories and acceptance criteria. In Agile environments this is the primary output format, and writing acceptance criteria that are actually testable is a distinguishing skill.

Manage stakeholders. Keeping people with conflicting priorities informed, aligned and willing to make decisions. This consumes more of the week than newcomers expect.

Support delivery. Answering developer questions, clarifying edge cases, attending refinement and stand-ups, adjusting requirements when reality intervenes.

Support testing and rollout. Defining test scenarios, coordinating user acceptance testing, sometimes writing training materials and supporting the change itself.

Analyse impact. What breaks elsewhere if we change this, and who is affected.

What you actually produce

Data analysts produce dashboards and analyses. Business analysts produce documents, and the quality of those documents is the job.

Requirements documentation, functional and non-functional
Process models, as-is and to-be
User stories with acceptance criteria, in a backlog
Gap analyses between current capability and target
Data mappings, particularly on system migrations
Business cases, at more senior levels
Test scenarios and UAT plans

If writing precisely is not something you enjoy, this is important information. Ambiguous requirements produce the wrong system, and the BA owns that ambiguity.

A realistic week

Roughly: two days in meetings and workshops, a day and a half writing and modelling, half a day answering delivery questions, and the remainder on analysis, testing support and stakeholder follow-up.

The meeting load is the most commonly underestimated part of the role, and it is the main reason people move between BA and data analyst roles in either direction. If you want to spend the day investigating data, this is not the job. If you find the politics of getting a decision made genuinely interesting, it is.

How the role varies

BA in an Agile product team. Often overlapping with a product owner. Heavy on user stories and backlog refinement, light on formal documentation, close to developers.

BA on a change or transformation programme. Heavy on process mapping, business cases and formal requirements. Common in banking, insurance and the public sector, and typically the best paid.

Systems or technical BA. Closer to the technology, involving data mappings, integrations and interface specifications. Advertised medians for Business Systems Analyst sit lower at £45,000, while IT Business Analyst roles carry a £72,500 median, so job titles here are a poor guide to level.

Data-focused BA. Growing quickly, sitting between the business and a data team, defining reporting and analytics requirements. This is where the BA and data analyst paths converge, and where SQL becomes genuinely valuable.

Skills, ranked by how much they matter

Elicitation and facilitation. Getting the real requirement out of people who have not articulated it.
Written clarity. Requirements are read by people who were not in the room.
Process modelling. BPMN or equivalent, well enough to model something complex.
Stakeholder management. Including the ability to say no to a senior person constructively.
Agile practice. Scrum ceremonies, backlog management, working with delivery teams.
Domain knowledge. The fastest route to being valued, and the hardest to fake.
Data literacy. Basic SQL and comfort with data, increasingly expected and a genuine differentiator.

Frequently asked questions

What does a business analyst do day to day? Runs stakeholder sessions, documents requirements and user stories, maps current and future processes, works with delivery teams on clarifications, and supports testing and rollout. The role is considerably more meeting-heavy than data analysis.

What are the main deliverables of a business analyst? Requirements documentation, process models, user stories with acceptance criteria, gap analyses, and supporting artefacts such as data mappings and test scenarios.

What skills do business analysts need? Elicitation and facilitation, clear written communication, process modelling, requirements engineering, Agile delivery practice, stakeholder management, and increasingly data literacy including basic SQL.

Is a business analyst a technical role? Semi-technical. You need to understand systems well enough to specify changes and talk credibly to developers, but you are not usually building anything.

Sources: ITJobsWatch job trend pages for Business Analyst, IT Business Analyst and Business Systems Analyst, 2026.