A couple of years ago, the idea of a tool helping me write user stories or summarise a 50-page requirements document in minutes would have sounded like wishful thinking. Now, it\u2019s just another Tuesday. Generative AI (GenAI) is no longer some distant \u201cfuture tech\u201d \u2014 it\u2019s quietly becoming part of our daily workflows, whether we\u2019ve embraced it or not.<\/p>\n
As Business Analysts (BAs), our role has always been about connecting the dots: understanding business needs, translating them into clear requirements, and making sure solutions deliver real value. But in a world where AI can \u201cwrite,\u201d \u201canalyse,\u201d and even \u201csuggest\u201d solutions, it\u2019s natural to wonder \u2014 where do we fit in?<\/p>\n
The answer is simple: we fit right at the centre.<\/p>\n
1. Framing the Problem \u2014 Still a Human Job<\/strong> That\u2019s where BAs come in \u2014 we filter the noise, validate assumptions, and make sure the problem is worth solving before drafting a single requirement.<\/p>\n 2. Using AI in Everyday BA Work<\/strong> Writing User Stories:<\/strong> Requirement Clean-Up:<\/strong> Data Insights:\u00a0<\/strong> Workshop Prep:\u00a0<\/strong> Writing Stakeholder Summaries:<\/strong> Drafting Survey Questions:<\/strong> Building Quick Visual Aids:<\/strong> Competitor & Market Research:\u00a0<\/strong> The trick here isn\u2019t just using AI \u2014 it\u2019s knowing when to trust it, and when to double-check.<\/p>\n 3. AI Won\u2019t Replace Core BA Skills<\/strong> BAs do more than gather requirements \u2014 we interpret context, manage conflicts, and bridge the gap between technical teams and business users. AI can draft a user journey map, but it won\u2019t pick up on the subtle user frustration you notice in a stakeholder interview.<\/p>\n 4. Collaborating Across Roles<\/strong> 5. Adapting Without Losing Your Edge<\/strong> If a BA spends less time formatting a document, they have more time to challenge assumptions, validate requirements, and explore alternative solutions \u2014 all the things that actually create business value.<\/p>\n Final Thoughts<\/strong> \u201cThe future of the BA role isn\u2019t written yet \u2014 and that\u2019s the most exciting part.<\/em>\u201d<\/p>\n","protected":false},"excerpt":{"rendered":" A couple of years ago, the idea of a tool helping me write user stories or summarise a 50-page requirements document in minutes would have sounded like wishful thinking. Now, it\u2019s just another Tuesday. Generative AI (GenAI) is no longer some distant \u201cfuture tech\u201d \u2014 it\u2019s quietly becoming part of our daily workflows, whether we\u2019ve […]<\/p>\n","protected":false},"author":2110,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":15},"categories":[5869],"tags":[7751,7750,7752,5405,5914,5792,5733,5918,6841],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/73921"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/2110"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=73921"}],"version-history":[{"count":3,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/73921\/revisions"}],"predecessor-version":[{"id":73939,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/73921\/revisions\/73939"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=73921"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=73921"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=73921"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nFrom experience, I\u2019ve found AI great for sparking ideas, but it still can\u2019t judge whether we\u2019re tackling the right challenge. In one project, for instance, a client requested a reporting dashboard. Before jumping in, I used AI to map out possible features \u2014 but then had a conversation with stakeholders that revealed the real issue was inconsistent data entry. A dashboard would have been useless without fixing that.<\/p>\n
\nOver the past year, I\u2019ve started weaving AI into my BA toolkit, not as a replacement, but as a sidekick. Here are some real examples from my work:<\/p>\n
\nWhen drafting user stories, I sometimes start by giving AI a short project brief and a couple of acceptance criteria. It spits out a rough draft, and then I rework it to reflect the project\u2019s language, priorities, and the nuances only a human BA would notice. It saves lot of my time and effort.
\nTools I\u2019ve used: ChatGPT, Microsoft Copilot (Word \/ Excel)<\/p>\n
\nWhen my requirement matrix starts to look like alphabet soup, AI helps me spot inconsistencies and standardise formatting.
\nRequirement docs have a way of getting messy \u2014 different formats, phrasing, and a few half-written lines from several people. Instead of spending hours fixing it by hand, I paste the content into an AI tool and ask it to put everything into one consistent structure.
\nThe cleaned-up doc is much easier for the team to scan and review.
\nTools I\u2019ve used: ChatGPT, Microsoft Copilot (Word \/ Excel)<\/p>\n
\nI\u2019ve pasted raw defect logs into AI tools to quickly see patterns \u2014 like a spike in errors after a particular release. It\u2019s not the final analysis, but it gives me a head start.
\nLarge defect logs or feedback lists can be overwhelming. I run them through an AI assist to flag trends or spikes \u2014 for example, a jump in errors tied to a single API after a release. That gives me a clear starting point for a deeper investigation.
\nTools I\u2019ve used: ChatGPT (with data prompts), Copilot for Excel \/ Power BI<\/p>\n
\nIn a recent discovery workshop, I used Miro\u2019s AI to sort sticky notes from our brainstorming into clear themes. It shaved off about half an hour of manual work and let the team stay in the flow of the conversation.
\nTools I\u2019ve used: Miro<\/p>\n
\nAfter long workshops or calls, I drop my rough notes or transcript into an AI summariser to get a tidy first draft of decisions and action items. I make sure to tweak the tone and check facts. It actually saves a lot of rewriting time.
\nTools I\u2019ve used: Fireflies (for transcripts), ChatGPT or Grammarly for summarising and polishing<\/p>\n
\nIf I need to run a quick survey, I tell AI the goal and the audience and it suggests a list of questions I can reuse or edit. It\u2019s a fast way to get a helpful first-pass set of questions.
\nTools I\u2019ve used: ChatGPT, Google Forms (templates)<\/p>\n
\nA simple diagram can clear up confusion faster than paragraphs. I give AI a short description of the process and it suggests a draft flow or diagram that I refine in the usual tool. It speeds up stakeholder alignment.
\nTools I\u2019ve used: Miro AI, Lucidchart, Whimsical<\/p>\n
\nWhen I need to understand what competitors are doing, I collect their product pages, reviews, or updates and feed them into AI. It gives me a fast snapshot so I can go into stakeholder meetings with sharper questions.
\nTools I\u2019ve used: Perplexity AI, ChatGPT (with browsing), plain Google searches<\/p>\n
\nYes, tools like ChatGPT can produce a neat-looking set of requirements, but they don\u2019t know the \u201cwhy\u201d behind them. They don\u2019t see the tension between two departments, or understand that a certain workflow was kept in place to meet a regulatory rule.<\/p>\n
\nA surprising advantage of AI is its ability to help me connect people who speak completely different \u201cwork languages.\u201d Something I didn\u2019t expect is how AI can smooth communication between very different stakeholders. For example, if I\u2019m working with a developer who talks in API calls and a business manager who only cares about getting their report on time, AI can help me translate \u2014 creating a quick diagram or plain-English summary that everyone understands.<\/p>\n
\nI know some BAs are nervous about AI \u201ctaking over,\u201d but here\u2019s how I see it: the professionals who learn to work with AI will outpace those who ignore it. This doesn\u2019t mean blindly accepting everything AI produces \u2014 it means using it to get past the grunt work so we can focus on strategic thinking and relationship building.<\/p>\n
\nFor Business Analysts, the job isn\u2019t disappearing \u2014 it\u2019s just taking on a new shape. We\u2019re still the ones who dig into the real problems, check if the fixes will hold, and translate between the people building the solution and the people who\u2019ll use it. What\u2019s new is simply a tool that lets us pick up the pace. So keep your curiosity sharp and your eyes on value, and the road ahead feels full of opportunities.<\/p>\n