Business Analysis

This is a remote position.

Simulation-Based Work Experience Programme — Founding Cohort

Opportunity Overview

Business Analysts are frequently given messy problems rather than neatly documented requirements. Participants may enter a scenario where stakeholders disagree about the problem, existing processes are poorly understood, requirements conflict, operational pain points have not been investigated or somebody has already selected a solution without establishing the underlying need.

The participant's job is to create clarity from ambiguity.

The responsibilities below represent the breadth of professional work available across the simulation library. Individual participants will encounter different combinations depending on the simulations they activate and may undertake simulations across other disciplines.

Workplace Responsibilities & Jobs to Be Done

• Problem investigation: You may receive an initial request for change and investigate the underlying business problem rather than automatically accepting the proposed solution.
  

• Stakeholder identification: You may determine which individuals, teams or user groups are affected and assess their influence, needs and potential contribution to requirements.
  

• Requirements elicitation: You may analyse stakeholder information, prepare elicitation approaches and identify questions required to uncover genuine business, user and operational needs.
  

• Requirements analysis: You may evaluate collected requirements for clarity, completeness, consistency, feasibility, duplication and alignment with business objectives.
  

• Requirements challenge: You may identify when stakeholders have presented solutions as requirements and reframe those requests around the underlying need.
  

• Current-state analysis: You may investigate how an existing process, service or system operates and identify inefficiencies, bottlenecks, failure points and unnecessary complexity.
  

• Future-state analysis: You may develop recommendations describing how a process or service could operate differently to achieve the intended outcome.
  

• Gap analysis: You may compare current and desired states and identify capabilities, process changes, technology, data or organisational changes required to close the gap.
  

• Process analysis: You may analyse workflows across multiple stakeholders or systems and identify opportunities for simplification, automation or improved control.
  

• User-story development: You may translate requirements into structured user stories communicating user need and expected value.
  

• Acceptance-criteria development: You may define clear, testable conditions establishing when a requirement or user story has been satisfactorily delivered.
  

• Requirements prioritisation: You may determine which requirements are essential, valuable or deferrable when delivery capacity or budget is constrained.
  

• Conflict resolution: You may encounter stakeholders with incompatible requirements and analyse the conflict before recommending an appropriate resolution.
  

• Impact assessment: You may evaluate how a proposed change could affect people, processes, systems, data, policies and operational responsibilities.
  

• Solution assessment: You may compare potential solution approaches against agreed business needs and provide an evidence-based recommendation.
  

• UAT and readiness support: You may determine how a proposed solution should be validated and whether the organisation is sufficiently prepared for implementation.
  

Requirements

Professional Artefacts & Evidence of Work

• Business Requirements Document: You may define the business problem, objectives, stakeholder needs, requirements, constraints and expected outcomes and demonstrate how requirements relate to the underlying need.
  

• Requirements Catalogue: You may create an organised set of functional, non-functional, business and user requirements with appropriate prioritisation, categorisation and traceability.
  

• User Stories and Acceptance Criteria: You may develop structured user stories accompanied by clear, testable acceptance criteria demonstrating how each requirement can be validated.
  

• Current-State Process Analysis: You may document how an existing process operates and identify pain points, bottlenecks, inefficiencies, control weaknesses and operational risks.
  

• Future-State Process Design: You may propose a future workflow demonstrating how identified problems could be addressed and desired outcomes achieved.
  

• Gap Analysis: You may compare current and desired states and identify required changes across processes, technology, people, data or organisational capability.
  

• Stakeholder Analysis: You may assess key stakeholders, their needs, influence, interests and likely concerns and recommend an engagement approach.
  

• Options Assessment: You may compare potential solution approaches against defined criteria, analyse benefits, risks and constraints and provide a reasoned recommendation.
  

• Change Impact Assessment: You may evaluate how a proposed solution or change will affect organisational areas and identify preparation, communication or mitigation required.
  

• UAT Scenario or Acceptance Plan: You may produce a structured approach for validating that delivered functionality satisfies agreed requirements and user needs.
  

The artefact is evidence of analysis performed, not simply evidence that the participant knows how to fill in a template.

Capabilities You Can Demonstrate

Requirements Engineering • Stakeholder Analysis • Process Analysis • Problem Solving • Requirements Elicitation • User Stories • Acceptance Criteria • Facilitation • Business Change • Critical Thinking • Communication • Solution Assessment

Who Should Apply?

Aspiring Business Analysts, Junior Business Analysts, career changers, Product or Project professionals developing BA skills, graduates, career returners and trained Business Analysts seeking stronger applied evidence.