Example · Business Analyst (IT / systems)
The documents generate themselves now. Knowing what the business meant, and what the system actually does, is still yours.
25 of your 40 hours still need you
- 19 stay yours
- 6 faster with AI
- 15 tools could take
A typical week at the middle pace. Your plan uses your own tasks.
Is business analyst a dying role?
By our task-by-task count, 25 of a typical 40-hour week as a business analyst still need a person. Tools could already take about 15 hours. 37% of your week is the writing-up half of business analysis, and it is the half you were hired for. That means the requirements document from the workshop transcript, the stories from the signed document, the swimlane from the walkthrough and the status deck.
Read more
If you have tried a drafting tool on a transcript, you have seen it. It writes a full requirements document in minutes, and it looks finished.
The same test shows what holds. A generated draft tends to invent one requirement nobody asked for and miss the one that mattered. You catch both because you were in the room when it was said. Your job now is to be the person who knows what the business meant, what the system actually does, and who has to agree before anything changes. About 47% of your week is already that work. It is also the part people in this role find hardest, because rounding up UAT (user acceptance testing) testers and getting change-board sign-off are where you carry the risk without the title. This report helps you hold the pen in those rooms.
The hard truth
Data and analytics postings have fallen more than any other.
Of the 47 job categories Indeed tracks, data and analytics postings are down the most since early 2020. That can mean more people competing for each analyst opening, and a longer search when you move.
Sources (1)
- Data and analytics postings were 36% below February 2020 in October 2026, the lowest of 47 categories. Indeed Hiring Lab job postings tracker, 2026-10
What stays yours
Knowing what the system actually does versus what the manual says
You know the old customization, the rule table nobody documented and the reason a feed drops a field on Fridays. A model can read the vendor documentation, but it cannot read the history that explains why your instance diverges from it.
Sitting in the room with the business during elicitation
Elicitation takes more than a transcript. The requirement that matters is often said once, in passing, by the quietest person at the table. You notice because you know what their job is.
Reconciling three business units that want three different things
A requirement that satisfies everyone on paper and breaks a downstream calculation looks identical to a good one until month-end. Somebody who knows the people has to tell which stakeholder's "must have" is actually a "would like."
Standing up at the change board and saying the release is good
Where your employer is audited, the change-board minutes, the UAT sign-off and the traceability matrix are control evidence that auditors sample. A named human has to be answerable for it. Often, informally, that is the BA (business analyst).
Running UAT and getting busy testers to take part
Getting a busy supervisor to test a workflow in a bad week is a negotiation. A tool cannot make that call. The acceptance evidence is only as good as the humans who actually tested.
What's next after business analyst?
Plan A is your best move inside the work you do now. Most sessions in the 13-week plan build toward it.
- A
Become the named change owner for your platform
Why it fits
Why you. If you already stand up at the change board, already run UAT, and already hold the undocumented history of the system, the audit evidence has your work in it with someone else's name on the control. The gap between what you do and what your title says is the smallest of the three moves.
The gap. There is usually no written impact assessment template. The UAT sign-off is a spreadsheet, and the configuration history exists only in your head. Nobody has named a BA-level change owner, so it can be anybody, including the vendor.
The trade-off. You become the person blamed, in writing, when a release breaks something in a bad week. The stress stays the same, but you have more authority on paper. You will write fewer documents for a quarter, and the practice measures documents.
Other moves that fit
These are also good bets in this field. Read them if Plan A doesn't suit you.
Own the quality of machine-written requirements
Why it fits
Why you. Finding the invented requirement and the missing one is a skill with no name yet. Enterprise assistants are already on every transcript in most companies, and vendor assistants are one signature from being enabled.
The gap. You have no written standard for what a requirement must trace to, no tally of generation errors and no guidelines for the tools, and nobody has asked the BA manager for any of it.
The trade-off. You will read more than you write, and some weeks it feels like proofreading for a machine. It sits close to the BA manager's territory; if they want it, you need the change owner move more than this. An executive can still buy a "requirements quality" feature from the vendor; the plan makes that deal worse than keeping you, though it stays possible.
The portable hedge: platform specialist in your vertical
Why it fits
Why you. Every company running the same packaged platform in your vertical needs someone who knows how it diverges from the manual, and the platform's vendor ecosystem hires for exactly that. Domain BA is the corner of this occupation where the hiring bar is what you know about the system rather than how many documents you can produce.
The gap. You have no public artifact and no idea what the market pays. It is also unconfirmed whether customer staff can sit the vendor's own certification (Guidewire publishes an analyst path, for example).
The trade-off. Leaving resets the asset this report says protects you. Your first year anywhere new is your most exposed: context starts at zero and document output is all anyone can measure. The specialist route also ties you to one vendor's product cycle.
What's a plan B for IT business analysts?
Plan B is a job AI is creating that these skills already fit. One session a week in the plan trains you for it, so it is ready if your job shrinks or you want a change.
BPlan B, picked for this role
AI workflow builder
Mapping how the business actually runs a process is the hard part of automation, and the tools to build it are now approachable.
Other options
AI deployment strategist
Translating between business users and the system during rollout is what AI deployment strategists do for each new customer.
AI product owner
Since you already write and refine requirements, owning the backlog for an AI feature on your platform is a realistic later step if you choose the product owner route.
In your own plan you can switch to any of the 47 roles.
The first two weeks
The first 2 of 13 weeks. Most weeks have three sessions of 45, 60 and 90 minutes, plus one 40-minute Plan B session (45 minutes in week 4). Weeks 6 and 10 assume a UAT week, so the third session is UAT itself; shift them to fit your release calendar. Week 12 has no third session. By week 13 you'll have a configuration ledger for your platform, signed impact statements and a UAT acceptance report with your name as author, and a memo asking to be the named change owner.
- Week 1: Measure your week
What you do
- ATrack your time for one week against the task list. Write down the hours each task takes.
- ALook at your last three releases. For each, count the requirements, change requests after sign-off, UAT (user acceptance testing) defects and production incidents in the first 30 days.
- ARun your company's approved drafting tool on your last two workshop transcripts. Sort every requirement it writes into asked for, invented, missed or wrong detail.
- BTake the first half of AI Fluency: Framework & Foundations, Anthropic's free course. Keep a running list of BA tasks you would hand to AI.
- Week 2: Check the tool policy
What you do
- AAsk your manager in writing which AI tools may touch which systems and data types, and who decided.
- AFind who owns the change-management IT general control, the audited check on system changes. Ask for last year's control description and the audit sample.
- ACompare the control text with what you actually do at the change board and in UAT. Write one page.
- BFinish AI Fluency and its final assessment.
Three courses from the plan
Checked 2026-10-11.
- Entry Certificate in Business Analysis (ECBA)IIBA · Bundle "$395 or less" including first-year membership, exam, practice exam and learning journey; student rates from $315; exam-only price not clearly shown
Not if you are already in the role. Sending it to a new graduate is fine.
- Certification of Capability in Business Analysis (CCBA)IIBA · $145 application + $250 exam (member; first-year membership included) or $405 non-member; rewrite $195 / $350
Not this quarter. Check the Week 10 postings; if your vertical screens for it, sit it in months 4 to 6.
- Certified Business Analysis Professional (CBAP)IIBA · $145 application + $350 exam (member) or $505 non-member; rewrite $295 / $450
Most people under four years in are not eligible yet. Revisit at year five.
Risks beyond AI: highRetitling and offshoring risk
This risk comes from reorgs and offshoring. The BA seat is the one most often folded into a product owner or project manager title when an organization goes agile, and it is one of the most offshored roles in bank and insurer IT. We treat this separately because it predates every model and because the remedy is different. For most people in this role, it outranks the AI risk.
Where this could be wrong
- Configuration may be more exposed than we assumed. We assumed the vendor's AI assistant stays turned off. If IT enables it early next year and it handles rule-table changes well, configuration becomes much more exposed and the share of your week that holds up drops.
- We assumed the change-board sign-off is yours informally. If the PO or a release manager already presents and you merely prepare the pack, the change owner move means joining the sign-off rather than owning it, and your accountability there is lower.
- The offshore risk may be the whole story. If your program's leadership has already decided to move BA work to a capability center, no plan inside the building changes that; run Weeks 10, 11 and 13 first and treat the rest as evidence for the application.
- The BA manager could take the requirements quality move by Friday. A whole practice and its standards in hand is a stronger claim than yours. If they want it, run only the change owner move and the job market hedge.
Also matched: business analyst, ba, it business analyst. Research checked 2026-10-11. Page updated .