Draft the business requirements document from workshop notes
Generative AI already produces a competent first-draft BRD, so your value moves to what the draft misses.
Expected horizon: 0-2y
TECHNOLOGY AND DIGITAL
Business analysts sit in an uncomfortable spot. Generative AI drafts requirements documents, summarises workshops and writes user stories, which covers a large share of a BA's visible output. The ILO's exposure index places documentation-heavy professional work among the most affected by generative AI [S6]. But the Gulf context changes the calculation. Government digital programmes and ERP rollouts across the UAE and Saudi Arabia depend on analysts who can sit between Arabic-speaking business owners and English-speaking delivery teams, extract what people actually need and get it signed off. AI can write the document. It cannot run the room. Analysts who define themselves by artefacts face pressure. Analysts who define themselves by alignment between stakeholders will stay in demand.
A job is a mix of tasks. The title alone cannot show your personal risk.
Generative AI already produces a competent first-draft BRD, so your value moves to what the draft misses.
Expected horizon: 0-2y
AI drafts stories quickly, but sharpening acceptance criteria until testers and developers agree remains analyst work.
Expected horizon: 0-2y
Drawing real requirements out of a mixed Arabic-English stakeholder room is the core skill AI cannot perform.
Expected horizon: 10y+
Process mining tools generate as-is maps from system logs, yet the to-be design still needs your judgement.
Expected horizon: 2-5y
The fit-gap workbook decides cost and timeline on ERP programmes, and vendors respect analysts who defend it with evidence.
Expected horizon: 2-5y
Traceability is exactly the structured, linked-record work that modern ALM tooling automates end to end.
Expected horizon: 2-5y
AI can draft UAT scripts, but chasing busy department heads to actually test and sign remains stubbornly human.
Expected horizon: 5-10y
Conflicting requirements are a political problem wearing a technical costume, and resolving them needs a person.
Expected horizon: 10y+
Prioritisation trade-offs between departments carry accountability that no scoring model absorbs.
Expected horizon: 5-10y
Steering committees in Gulf government programmes expect a named analyst to stand behind the impact assessment.
Expected horizon: 10y+
Split your task list into artefacts and agreements. The artefacts, meaning the BRD, the traceability matrix and first-draft user stories, carry high exposure because generative AI produces them fast and cheaply. The agreements, meaning workshops, conflict resolution, sign-off and steering committee work, carry low exposure because they run on trust and accountability. PwC's barometer shows demand shifting within AI-exposed professions rather than simply disappearing [S8], and that is your situation precisely. Employers will expect fewer hours spent typing documents and more hours spent securing decisions. One warning: junior BA roles built mainly around documentation are the ones being thinned. If your CV leads with document types rather than delivered programmes, treat that as the first thing to fix.
Make AI your drafting junior and keep the judgement work. Use it openly to produce first-cut BRDs and user stories, then spend the saved hours in rooms with stakeholders, because facilitation is now the differentiating skill. Anchor yourself to a domain. An analyst who knows government service journeys, or ERP finance modules, or HR processes in depth beats a generalist every time. Get comfortable presenting in mixed Arabic-English settings even if you work through a translator, since bilingual programmes dominate Gulf public sector work. Add process mining and basic data literacy so you can interrogate the evidence behind requirements. Certifications such as CBAP or an agile BA credential help at screening stage, but a named, delivered programme helps more.
Saudi Arabia's transformation programmes make it the region's largest single source of business analysis work. SDAIA's National Strategy for Data and AI drives data platforms and digital services across ministries [S3], while Vision-era programmes and giga-projects run continuous ERP and process change. Requirements gathering here is deeply bilingual, and analysts who can facilitate in Arabic, or partner effectively with those who can, hold a clear advantage. The labour market itself is shifting as Saudi professional participation grows [S4], so expatriate analysts increasingly work alongside and develop Saudi national colleagues. Domain depth in government services, finance or HR processes decides who wins the senior seats.
Regional guidance reflects published national strategies and the practical view of a Gulf HR Career Specialist.
It replaces the drafting portion of the role. Requirements documents and user stories are increasingly AI-produced, while stakeholder facilitation, conflict resolution and sign-off remain human and are becoming the job's real core.
Large digital and ERP programmes, bilingual stakeholder groups and formal steering governance. The UAE's national AI strategy supports continued public-service digitisation, which creates requirements and process work for analysts [S1].
Jira or Azure DevOps for stories, Visio or a BPMN tool for process maps, and at least one ERP ecosystem. Familiarity with AI drafting assistants is now assumed rather than optional.
No. A business analyst defines requirements, processes and acceptance criteria for change programmes. A data analyst builds analysis and reporting from datasets. The roles overlap on evidence but differ in output.
runs the delivery lifecycle your requirements feed into
supplies the evidence base behind requirements and benefits cases
owns the business processes you map and redesign
This page uses a reviewed task profile, not a generic job-title probability. Read the full methodology and limitations.