AI for Business Analysts

Draft the business requirements document for [project]. Sections: the executive summary, the business context with the strategic driver, the business objectives tied to the strategic driver, the scope with the in-scope and out-of-scope inventory, the stakeholder register with the RACI assignment, the business requirements numbered for traceability with the MoSCoW priority and the rationale per requirement, the functional requirements derived from the business requirements with the source-traceability, the non-functional requirements (performance, security, compliance, usability, scalability) with the measurable acceptance criteria, the assumptions, the constraints, the dependencies, the risk register, the acceptance criteria in Given-When-Then format, the glossary. Voice: substantive, the IIBA BABOK quality bar (atomic, complete, consistent, concise, feasible, modifiable, traceable, testable, unambiguous). Project context and stakeholder-interview transcripts: [paste].

Generate the user-story set for [feature] in As-A-I-Want-So-That format with the acceptance criteria. Inputs: the feature description, the user personas, the business value drivers, the existing user stories the new stories integrate with, the team's definition of ready and definition of done. Output: the user stories at the appropriate granularity (epic, feature, story, task) per the team's hierarchy, each story with the As-A-I-Want-So-That statement, the acceptance criteria in Given-When-Then format, the story-point or t-shirt-size estimate guidance for the engineering grooming session, the dependencies between stories, the priority ordering with the rationale. Feature context: [paste].

Document the as-is process for [process]. Inputs: the stakeholder-interview transcripts, the current process owner's description, the existing process documentation if any, the system inventory the process touches, the regulatory or compliance constraints (SOX if financially material, HIPAA if PHI, GDPR or CCPA if personal data, the industry-specific constraint), the volume and frequency metrics. Output: the as-is process narrative in BPMN-aligned form ready for diagramming in Lucidchart or Visio or Miro or Confluence, the swim-lane structure with the actor-per-lane, the decision-gateway documentation, the system-interaction inventory, the data-and-handoff inventory between actors, the pain-point inventory from the stakeholder interviews. Voice: rigorous, the format a change-management review accepts. Process context: [paste].

Map the as-is to the to-be process for [process change]. Inputs: the as-is process documentation, the to-be vision from the project sponsor, the regulatory or compliance constraints the to-be must respect, the technology platform the to-be runs on, the change-management capacity of the affected teams. Output: the gap analysis with each as-is step mapped to (a) preserved as-is, (b) modified with the specific modification, (c) automated with the specific automation, (d) eliminated with the rationale, the change-impact assessment per affected team, the training-and-communication plan, the transition-state mapping if the change ships in waves, the success metrics. Voice: substantive, the format the project sponsor and the change-management team work from. As-is and to-be context: [paste].

Write the SQL query for [analytical question] against the data warehouse. Inputs: the question in business language, the available tables with the relevant columns and the join keys, the dialect (Snowflake, BigQuery, Databricks, Redshift, Postgres, the team's dialect), the existing semantic-layer conventions the team uses, the performance expectation, the data-classification of the columns the query touches. Output: the query with the CTEs structured for readability, the comments explaining the business logic per CTE, the index or partition hints if the dialect supports them, the verification approach the BA runs before sharing the result, the dashboard-or-export format the result lands in. The BA verifies the result against the business question before sharing. Question and schema: [paste].

Generate the Power BI DAX measure or the Tableau LOD calculation for [metric]. Inputs: the metric definition in business language, the existing data model with the table relationships and the cardinality, the filter context the measure responds to, the existing measures the new measure relates to, the dashboard the measure appears on. Output: the DAX or LOD expression with the syntax the platform requires, the comments explaining the business logic, the test cases that verify the measure returns the expected value across filter contexts, the documentation entry for the data-dictionary, the dashboard placement recommendation. Platform and model context: [paste].

Generate the stakeholder-interview guide for [stakeholder role] on [project]. Inputs: the project charter, the stakeholder's role and likely concerns, the prior-related project history with this stakeholder if known, the time budget for the interview (typically 45-60 minutes), the discovery questions the project sponsor wants answered. Output: the interview guide with the opening framing, the warm-up questions, the substantive discovery questions sequenced from broad to specific, the probing follow-up questions that surface the actual requirement when the stakeholder states the wishlist version, the wrap-up with the confirmation summary the stakeholder validates, the post-interview deliverable the stakeholder receives. Voice: respectful of the stakeholder's time and expertise. Project and stakeholder context: [paste].

Synthesize this stakeholder-interview transcript into the structured requirements-extraction summary. Inputs: the transcript, the project charter, the prior-stakeholder-interview synthesis if other interviews preceded this one. Output: the extracted requirements with the source-quote citation per requirement, the conflict with prior-stakeholder accounts flagged, the open questions the next interview needs to clarify, the priority signal the stakeholder communicated, the political-context inference about how this stakeholder's department interacts with the affected business process, the follow-up confirmation email draft the BA sends the stakeholder to validate the extraction. Voice: rigorous, the BABOK-aligned requirement-quality standard. Transcript: [paste].

Draft the business case for [investment]. Sections: the executive summary with the recommendation, the problem statement with the supporting business data, the opportunity sizing with the TAM-SAM-SOM framing where applicable plus the realistic capture assumption, the recommended approach with the implementation plan, the alternatives considered with the rejected-rationale per alternative, the financial-projection narrative anchoring the spreadsheet model with the assumption rationale and the sensitivity analysis on the 2-3 most-impactful assumptions, the risk register with the mitigation per risk, the implementation roadmap with the milestones and the dependencies, the success metrics with the measurement plan, the governance plan. Voice: rigorous, the format the executive committee and the CFO read with care. Investment context: [paste].

Research the regulatory and industry landscape for [project domain] in 2026. Output: the controlling federal regulatory authority (the relevant agency: SEC, FDA, FCC, FTC, CFPB, HHS, the relevant agency), the recent rulemaking notices in the last 24 months, the state-level regulatory variation if material, the international regulatory equivalent if the business operates cross-border, the industry-association guidance, the major consulting-and-research-firm coverage (McKinsey, Bain, BCG, Deloitte, PwC, EY, KPMG, Accenture, Forrester, Gartner, IDC) with the most-relevant recent reports, the SEC-filing language from the 5 largest competitors on the topic with the 10-K and proxy-statement citations, the primary-source links the BA verifies before citing in the business case. Project domain: [paste].

Generate the data-flow narrative for [system or feature]. Inputs: the system or feature description, the affected systems inventory, the data-classification of the data the system touches, the integration-point inventory, the existing data-flow documentation if any, the security and compliance constraints. Output: the data-flow narrative ready for the data-flow diagram, the source-system-to-target-system mapping per data element, the transformation logic between source and target, the data-quality control per flow, the privacy and security control per flow, the open questions for the data-governance and security review. System or feature context: [paste].

Help me think through this scope-management decision. Inputs: the original project scope, the change request, the impact on schedule with the realistic implementation effort, the impact on cost with the realistic resource effort, the impact on the related requirements, the impact on the project sponsor's stated outcomes, the political reality of the change request's stakeholder source. Walk through: the realistic merit of the change request against the project's strategic outcomes, the 3 options (accept, defer to a follow-on project, reject) with the trade-offs, the project-sponsor and the affected-stakeholder conversation script, the documentation discipline for the change-request log, the recommendation with the reasoning. Frame as advice from a senior BA and a PMO leader I would actually trust.