Business Analysis

Business analysts bridge the gap between business stakeholders and delivery teams, ensuring that what gets built solves the right problem. This role is common in large enterprises, public sector digital programmes, and consultancies. Unlike a Product Manager who owns the product direction, a Business Analyst typically focuses on a project or change programme: capturing requirements, modelling processes, defining acceptance criteria, and supporting testing.

Responsibilities

• Run structured workshops with stakeholders to elicit and document requirements.
• Process mapping using BPMN or swimlane diagrams.
• Write user stories, use cases, and acceptance criteria.
• Manage a requirements traceability matrix.
• Support User Acceptance Testing (UAT): write test scripts, coordinate testers, and manage defect logs.
• Conduct change impact assessments to identify affected people, processes, and systems.
• Facilitate stakeholder communication and resolve conflicts when requirements are contested.

Skills

• Workshop facilitation
• Process modelling
• Requirements documentation
• Agile ceremonies
• Basic SQL (helpful)
• Stakeholder diplomacy

Pay

UK Salary Range:

• Entry level (0-2 years): £25,000 to £35,000. Common in consultancies, public sector bodies, and large enterprises. Consultancies often pay slightly more but with high travel expectations.
• Mid-level (2-5 years): £38,000 to £55,000. Ownership of a workstream within a programme. Expected to facilitate workshops independently and produce deliverables without supervision.
• Senior (5+ years): £55,000 to £75,000. Lead BA, BA Manager, or Head of Business Analysis roles. Consultancy principals and directors can reach £80,000 to £110,000.
• Contracting: Experienced BAs contract at £350 to £550 per day. Public sector contracts (NHS, HMRC, Home Office) are consistent and often last 6 to 12 months.

Qualifications

Strong communication and structured thinking matter more than tools alone. This career path is ideal for people moving from operations, support, or domain expert roles into structured change roles.

Portfolio Artefacts

Employers look for evidence of structured thinking, clear documentation, and stakeholder communication. Since most junior BA candidates lack real project experience, demonstrating the process is more important than the outcome.

• Process improvement case study:
  • Choose a process you have experienced (e.g., a workplace workflow, customer journey, or service).
  • Draw the as-is process using swimlane notation.
  • Identify three pain points with evidence (observations, data, or user feedback).
  • Design a to-be process and document what changed and why.
  • Keep this to two pages plus diagrams.
• Requirements document:
  • Write a mock requirements document for a small system (e.g., a booking system, notification service, or reporting dashboard).
  • Include: background and objectives, stakeholder list, functional requirements (user story format), non-functional requirements, and assumptions and constraints.
• User stories with acceptance criteria:
  • Write ten user stories in standard format (As a... I want... So that...) for a real product you know well.
  • Add three acceptance criteria to each in Given/When/Then format.

Where to Apply

• NHS Digital, HMRC, DWP, Cabinet Office, and local government digital teams regularly hire BAs.
• Management consultancies (e.g., Accenture, Deloitte, PA Consulting) run graduate programmes.
• Financial services firms (banks, insurers) hire BAs for change programmes.
• LinkedIn filters for Business Analyst, Requirements Analyst.

Certifications

• BCS Foundation Certificate in Business Analysis: Widely recognised and worth pursuing.
• IIBA CBAP: For senior practitioners. Neither is required at entry level, but the BCS Foundation demonstrates commitment.

CV Tips

Highlight any experience in documentation, process improvement, or stakeholder communication, even in non-tech roles. Operations managers, project coordinators, and customer service leads often have BA-relevant skills without realising it.

Interview Preparation

Common BA interview questions and how to approach them:

• "Walk me through how you would elicit requirements from a reluctant stakeholder."
  • Prepare, not just attend: research their role and what they care about.
  • Ask open questions and listen more than you talk.
  • Document and validate what you heard before the next session.
• "What is the difference between a functional and non-functional requirement?"
  • Functional: What the system does (e.g., a user can submit a form).
  • Non-functional: How it does it (e.g., the page must load in under two seconds).
• "How do you handle conflicting requirements from two stakeholders?"
  • Understand both positions fully.
  • Identify the underlying business goal each requirement serves.
  • Find the common ground.
  • Escalate to a decision-maker only when the conflict cannot be resolved at team level.
• "What is a use case and how is it different from a user story?"
  • A use case describes a complete interaction sequence between an actor and a system, including alternative flows and exceptions.
  • A user story is a short description of a feature from the user perspective, with acceptance criteria confirmed through conversation.
  • Use cases are more formal and complete.
• "How do you manage scope creep?"
  • Document agreed scope in a requirements baseline.
  • Log change requests separately.
  • Assess impact on cost and timeline.
  • Escalate formally.
  • Never quietly absorb changes without recording them.

Common Mistakes to Avoid

• Documenting requirements without validating them: Writing down what stakeholders say is not the same as understanding what they need. Always play requirements back, ask "what would prevent this from working?", and test edge cases.
• Vague acceptance criteria: "The system should be easy to use" is not an acceptance criterion. "When a user submits the form with all required fields completed, they receive a confirmation email within two minutes" is specific.
• Being a passive note-taker in workshops: A BA facilitates, not records. If you only take notes and never challenge, clarify, or synthesise, you are not doing the job. Practice facilitation skills explicitly.
• Ignoring non-functional requirements: Performance, security, accessibility, and audit requirements are frequently forgotten until late in delivery and are expensive to retrofit. Ask about them early.
• Not learning the domain: A BA who does not understand the business they are analysing cannot spot when a requirement is technically correct but practically wrong. Invest time in understanding how the organisation makes money and what its constraints are.

Tools

• Jira
• Confluence
• Miro
• Visio
• Excel

Entry-Level Job Titles

• Junior Business Analyst
• IT Business Analyst
• Requirements Analyst