Tech roles beyond coding

Stage 1 · Lesson 5 of 9

Business analyst: turning needs into clear requirements

The landscape of non-coding tech roles

A , or BA, works out what a change must achieve and describes it clearly enough that a team can build and test it. On a normal day a BA interviews people, watches how work is really done and maps processes. They write requirements and user stories, check data, answer developers' questions and help business users test the result.

BAs are common in banks, telecoms, insurers, government and IT services firms, and in product teams. The role differs from product management: a PM decides which problems are worth solving, while a BA makes sure the chosen change is understood, specified and delivered correctly.

The 's BABOK Guide describes the work in six knowledge areas. People who do well are curious, patient with detail and calm amid disagreement.

Common trappicturing the job as writing long documents. Most of the value comes from asking the question nobody asked.

A question to check yourself, an AI practice session and 3 cheat sheet entries come with the full roadmap. Unlock

Resources for this stage

Start with

  • GuideFree
    The Business Analysis Standard

    IIBA · Beginner

    IIBA's free, short standard: the core concepts and knowledge areas of business analysis in plain terms

Keep handy

Mark this stage as not done?