Home/Knowledge Base/Knowledge Worker Playbooks/Business Analyst

PATHKnowledge Worker Playbooks · Learning path

AI for Business Analysts

The BA’s craft is turning what people say into what they mean, and what they mean into something buildable. AI accelerates the writing. The listening is still yours.

The role today

Business analysts live between the business and the build: eliciting requirements, mapping processes, writing the documents everyone else works from. It’s heavy synthesis work — workshops become notes become requirements become specifications — and every step of that chain is text AI can help produce.

How AI changes this role

AI helps you with

  • Workshop notes into structured requirement drafts
  • Process documentation first passes
  • User story generation from feature descriptions
  • Consistency checks across large document sets

You provide

  • Eliciting what people mean, not what they say
  • Challenging the requirement that doesn’t add up
  • Negotiating conflicting stakeholder needs
  • Knowing which detail matters and which is noise

This is The Knowledge Worker AI Framework™ applied to this role — AI takes the production, you keep the bookends.

Liza’s take

Every SharePoint project I’ve worked on had analysis at the front of it — workshops, process walk-throughs, requirements nobody could quite agree on. The pattern I’ve seen for twenty years: the analysis documents that survive are the structured ones. The rest get rewritten from scratch by the next analyst.

Where AI genuinely helps

Workshop to draft in a day

Record the session, generate the structured summary, sort into candidate requirements — then spend your time on the gaps and contradictions, which is the actual analysis.

Process documentation that keeps pace

First-draft process descriptions from your walk-through notes, in a consistent template, every time.

Requirement quality checks

Ask AI to find ambiguity, duplication and untestable statements in your own requirements set. It’s a tireless reviewer of exactly the things reviewers skim.

Reusable analysis assets

Requirements and process maps stored structured — tagged by system, process and status — become an organisational asset the next project can query instead of rewriting.

A day with AI

Morning workshop on the intake process: recorded, summarised, and sorted into draft requirements by early afternoon. You spend the productive hours where the value is — two requirements contradict each other, and only a conversation with both stakeholders will resolve which reflects reality. That conversation is the job. The typing never was.

The risks

AI will happily generate plausible requirements nobody actually stated — treat every generated statement as a claim to verify against your sources. Workshop recordings carry consent and confidentiality obligations; know your organisation’s rules. And keep your analysis in governed storage, not personal drives: requirements that vanish with an analyst are a pattern I’ve seen end badly.

Where the role is heading

The writing layer of analysis is compressing fast, which exposes the real differentiator: elicitation, challenge and judgement. I expect BAs to move closer to product and decision roles — and analysts who can also assess where AI fits safely in a business process will find that skill in demand everywhere.

Your learning path

Start with the cards below, in order — each one is a five-minute read built for a task this role repeats. The full K-Series (ten foundations, ten workflow cards) lives on the Knowledge Worker Playbooks hub.

Will AI replace Business Analysts?

It replaces the transcription and first-draft layer. The elicitation, challenge and negotiation layer — the part that decides whether the right thing gets built — moves further into human hands, not out of them.

Can AI write requirements from a meeting recording?

It can produce structured candidates. Treat them as raw material: verify every statement against what was actually meant, and expect to find the contradictions yourself — that’s the analysis.

What should a BA learn first?

Synthesis prompting: turning messy raw input into a structured draft in your template. It’s the highest-frequency task in the role and the fastest win.