Data · Job description template

Business Analyst job description template

Projects often fail because nobody wrote down what the business needed before work began. The Business Analyst works out what the business needs, maps how work happens today and turns that into clear requirements that developers, vendors and testers can act on. They are accountable for changes that solve the real problem and can be shown to have worked.

First-year outcomes

What should be visibly different a year from now. Results, not tasks.

  • Every project the analyst supports starts with signed-off requirements that include acceptance criteria testers use.
  • Current and future process maps exist for the three business processes leadership ranks as most important.
  • Every change request after sign-off is logged, assessed for effort and impact, and approved before work starts.
  • At least one delivered change has a measured before and after result, such as fewer manual steps or a shorter processing time.
  • Business users sign off acceptance testing for each release, and no critical defects are found in the first month after go-live.

The work

Recurring work

  • Run workshops and interviews with users to understand their needs.
  • Write user stories, requirements and acceptance criteria.
  • Map business processes in a tool such as Miro, Lucidchart or Visio.
  • Answer developer and vendor questions during delivery.
  • Plan and support user acceptance testing.

Projects

  • Map the order-to-cash or another core process end to end.
  • Gather requirements for a new system, such as a CRM or ERP selection.
  • Set up a simple change request log and approval routine.

Decisions they own

  • How requirements are written, structured and prioritised for review.
  • Whether a request is in scope or a change request.
  • When requirements are clear enough to hand to delivery.

People they work with

  • Business users and process owners, to understand needs and pain points.
  • Developers, product owners or vendors, who build from the requirements.
  • Project sponsors, to agree scope and sign off requirements.
  • Testers and end users, to plan and complete acceptance testing.

Requirements

Essential on day one

  • Experience gathering and writing requirements that a team built from.
  • Skill at running workshops and asking questions that uncover the real need.
  • Process mapping using a standard notation, such as BPMN or swimlanes.
  • Clear, precise writing.

Helpful, but can be learned

  • The systems the company uses and how data flows between them.
  • The project or ticket tool the team uses, such as Jira.
  • The specific business domain and its vocabulary.

How to assess it

One piece of evidence for each first-year outcome.

OutcomeEvidence to look for
Signed-off requirements with acceptance criteriaWork sample: write three user stories with acceptance criteria from a short brief. Good is testable, unambiguous and free of solution design.
Current and future maps for three core processesAsk them to sketch a process from a five-minute description. Good shows roles, handoffs, decisions and where delays happen.
Change requests logged and approved before workAsk about a project where scope kept growing. Good describes logging requests, sizing impact and getting sponsor decisions.
One change with a measured before and after resultAsk for a project they can show results for. Good gives a baseline measure taken before the change and the result after.
User sign-off and no critical defects after go-liveAsk how they planned user acceptance testing. Good names test scenarios from the acceptance criteria and real users testing them.

Opening for the job ad

Before we build or buy anything, we want to be sure it solves the real problem. In your first year you will map how our key processes work, write the requirements every project starts from and show that the changes we make actually improve things.

Turning this into an ad? See how to write a job ad that gets applicants.

Next: interview for these outcomes

Eight structured questions for this role, each tied to an outcome above.

Business Analyst interview questions

Similar roles

Your next hire, start to finish, in one place.

Free workspace. No card. Full scoring free for 7 days.