𝗪𝗵𝗮𝘁 𝗖𝗵𝗮𝗻𝗴𝗲𝗱 𝗳𝗼𝗿 𝗕𝗔𝘀 𝗕𝗲𝘁𝘄𝗲𝗲𝗻 𝟮𝟬𝟮𝟬 𝗮𝗻𝗱 𝟮𝟬𝟮𝟱
A senior Business Analyst asked me what changed in the last five years. He wanted a simple list.
The list exists. Five things changed visibly. Three things stayed the same. Most people focus on the wrong list.
𝗪𝗵𝗮𝘁 𝗖𝗵𝗮𝗻𝗴𝗲𝗱
- AI tools are now standard. BAs use AI to draft criteria, summarize transcripts, and write meeting notes. It handles the boring documentation.
- Async work is the norm. Requirements move from workshops to Slack threads and Loom videos.
- Job titles shifted. Many companies relabeled BAs as Product Owners to match Scrum trends.
- Tool variety increased. Jira is no longer the only option. Linear, Notion, and ClickUp are everywhere.
- Speed expectations rose. Stakeholders want answers in hours instead of days.
𝗪𝗵𝗮𝘁 𝗦𝘁𝗮𝘆𝗲𝗱 𝘁𝗵𝗲 𝗦𝗮𝗺𝗲
- Requirements are still often wrong. Stakeholders still ask for solutions instead of stating problems.
- Problem understanding matters most. Writing stories is easy. Understanding why a feature exists is hard.
- Discovery is still iterative. You still need to show prototypes to find out what users actually need.
𝗧𝗵𝗲 𝗗𝗮𝗻𝗴𝗲𝗿
Many BAs focus only on surface changes. They get better at AI prompts and tool fluency. This makes their CV look modern, but it does not make them better at the craft.
AI is excellent at surface work. It drafts stories and formats documents. If your only value is documentation, you are competing with a $20 tool.
𝗜𝗻𝘃𝗲𝘀𝘁 𝗶𝗻 𝘁𝗵𝗶𝘀 𝗶𝗻𝘀𝘁𝗲𝗮𝗱
- Problem decomposition. Break vague statements into real needs.
- Stakeholder interrogation. Ask what they are trying to achieve, not just what they want.
- Judgement. Know when to push back and when to accept a requirement.
- Domain depth. Become an expert in a specific field like finance or healthcare.
The tools change how you work. They do not change what the work is. The goal remains the same: turn vague ideas into solutions that solve real problems.
Focus on the craft, not just the tools.
Optional learning community: https://t.me/GyaanSetuAi