35 ChatGPT Prompts for Business Analysts: Requirements, User Stories, and Stakeholder Docs Done Faster

Create a detailed BRD outline for [project name]. Business objective: [goal]. Stakeholders: [list]. Scope: [what's in / out]. Known constraints: [budget, timeline, technical]. Sections to include: executive summary, business problem, proposed solution, functional requirements, non-functional requirements, assumptions, risks, and success metrics. Suggest 3-5 sub-points under each section I'll need to address.

Write functional requirements for [feature or system]. The user needs to: [describe what users need to accomplish]. The system must: [business rules]. Edge cases to address: [list]. Write each requirement in the format: "The system shall [action] when [condition] so that [business value]." Number them. Flag any that are ambiguous or likely to generate developer questions.

Here are my raw notes from a stakeholder interview: [paste notes]. Extract and convert these into structured business requirements. For each requirement: write a clear "The system shall…" statement, identify the stakeholder who raised it, flag any that conflict with each other, and mark any that need clarification. Organize by functional area.

Write acceptance criteria for the following user story: [paste user story]. Use Gherkin format (Given / When / Then) for each criterion. Cover: the happy path, at least 2 edge cases, error handling, and any business rule validations. Each criterion should be independently testable. Flag any ambiguity in the original user story that needs stakeholder clarification.

Create a requirements traceability matrix template for [project name]. Include columns for: requirement ID, requirement description, source (stakeholder/document), priority, linked user story, test case ID, and status. Write 5 example rows using these requirements: [list 5 requirements]. Explain how to maintain this document through the project lifecycle.

Write non-functional requirements (NFRs) for [system name]. Business context: [description]. Focus areas: performance, security, availability, scalability, usability, compliance. For each NFR: write a specific, measurable requirement (not "the system should be fast" — give actual thresholds), explain the business rationale, and flag how it should be tested.

Write user stories for [feature]. User personas: [list]. For each story use the format: "As a [persona], I want to [action] so that [benefit]." Write stories for: the primary happy path, the main alternative flows, and error/exception cases. Include a story point estimate rationale (1/2/3/5/8) based on complexity. Flag any epics that should be broken down.

Write an epic for [feature area]. Include: epic title, business objective, success metrics, list of child user stories (titles only), dependencies on other epics, risks, and estimated effort (t-shirt size: S/M/L/XL). The epic should describe what we're trying to achieve for [user type] without prescribing the technical solution.

Refine this backlog item so it's sprint-ready: [paste raw ticket]. Add: a clear user story format, acceptance criteria in Gherkin format, definition of done checklist, technical notes the dev team will need, and estimated complexity notes. Flag anything that requires a spike or clarification before estimation.

Write a sprint goal for Sprint [X]. Committed user stories: [list story titles]. Business context: [what we're trying to accomplish]. The sprint goal should: capture the business outcome in 2-3 sentences, be achievable without completing every story (in case of scope changes), and give the team a north star for decision-making during the sprint. Avoid listing individual features.

Write a Definition of Done (DoD) for [team/project type]. Include criteria for: code complete, unit tests, integration tests, code review, documentation updated, acceptance criteria met, non-functional requirements checked, and stakeholder sign-off where required. Format as a checklist that can be applied to every user story before calling it done.

Document the current (as-is) state of [process name]. Here are my process notes: [paste notes from observation or interviews]. Create: a numbered step-by-step process description, a list of systems/tools used at each step, pain points and inefficiencies observed, handoff points between teams, and decision points. Format for stakeholder review.

Design the future (to-be) state of [process name]. Current state pain points: [list]. Business goals for improvement: [list]. Constraints: [technology, budget, org]. Create: the improved process flow step by step, how each pain point is resolved, what changes for each stakeholder group, and estimated effort to implement each improvement. Flag assumptions.

Write a gap analysis for [area — e.g., "our order management process"]. Current state: [description]. Desired state: [description]. For each gap: name it clearly, describe the business impact of not closing it, prioritize it (High/Medium/Low), suggest an approach to close it, and estimate rough effort. Format as an executive-ready table.

Write a process improvement recommendation for [process]. Problem statement: [current pain]. Root cause analysis: [what's causing it]. Proposed solution: [description]. Expected benefits: [quantified where possible]. Risks: [list]. Implementation steps: [high-level]. Estimated ROI: [if you have the data]. Format for presentation to [stakeholder level].

Draft a stakeholder update email for [project name]. Audience: [stakeholder level — C-suite / department heads / end users]. This week's progress: [list]. Decisions needed: [list with deadlines]. Risks/issues to flag: [list]. Next week's plan: [list]. Keep it scannable — use bullets, not paragraphs. Lead with what they need to act on, not project history.

Write a business case for [initiative]. Problem being solved: [description]. Proposed solution: [description]. Financial impact: [cost savings / revenue increase / cost to implement]. Non-financial benefits: [list]. Risks of doing nothing: [list]. Risks of the proposal: [list]. Recommendation: [what you're asking them to approve]. Format for executive review — 1-2 pages maximum.

I need to have a difficult conversation with [stakeholder] about [issue — e.g., scope creep, missed deadline, rejected requirements]. Their likely position: [describe]. My goals: [what I need to achieve]. Help me: anticipate their objections, prepare data-based responses, identify common ground, and plan how to open the conversation constructively. Suggest a 3-minute opening statement.

Here are my raw notes from a [meeting type] meeting: [paste notes]. Convert them into structured meeting minutes with: attendees, decisions made (with rationale), action items (owner + due date), open questions, and next meeting agenda items. Keep it concise — decision-makers should be able to read this in 2 minutes.

Create a RACI matrix for [project or process]. Stakeholders involved: [list]. Key activities/decisions: [list]. For each activity, assign: Responsible (does the work), Accountable (owns the outcome), Consulted (provides input), Informed (kept in the loop). Flag any activities where accountability is unclear or overlapping — these are common sources of project conflict.

Write a data requirements document for [report or dashboard]. Business questions it must answer: [list]. Data sources available: [list]. Key metrics needed: [list with definitions]. Filters/dimensions: [list]. Refresh frequency: [real-time/daily/weekly]. Audience: [who will use it]. Flag any data quality issues or gaps that need to be resolved before this can be built.

Define KPIs and success metrics for [initiative or feature]. Business objective: [goal]. For each KPI: name, definition, formula (if applicable), target value, data source, measurement frequency, and who owns tracking it. Include leading indicators (predict future performance) and lagging indicators (confirm outcomes). Flag which metrics we can measure today vs. which require new data collection.

Write data dictionary entries for the following fields in [system/database]: [list field names]. For each field: technical name, business name, definition, data type, allowed values or range, business rules, source system, and any known data quality issues. Format for a shared data catalog that both technical and business teams will reference.

I have the following data analysis results: [paste results or describe findings]. The audience is [stakeholder type — non-technical business leaders]. Write an executive summary of: what the data shows, what it means for the business, what action it recommends, and what additional analysis would strengthen the conclusion. Avoid statistical jargon.

Write a User Acceptance Testing (UAT) test plan for [feature or system]. Business requirements being tested: [list]. User personas conducting testing: [list]. Test scenarios to cover: [describe key flows]. For each scenario: write a test case with steps, expected result, and pass/fail criteria. Include a defect logging process and sign-off criteria for go-live approval.

Write UAT test cases for the following user story: [paste story]. Cover: happy path (step by step with expected result at each step), alternate flows, error conditions, boundary cases, and any business rule validations. Format as a test script a non-technical business user can follow without interpretation.

Write a defect report for the following issue found in UAT: [describe what happened]. Include: defect title, severity (Critical/High/Medium/Low), steps to reproduce, expected behavior, actual behavior, business impact, environment where it occurred, and suggested priority for fix. Write clearly enough that a developer who wasn't there can reproduce it independently.

I'm facilitating a project kickoff for [project name]. Stakeholders attending: [list with roles]. Project objective: [goal]. Duration: [X weeks/months]. Help me: create a kickoff agenda, write 5 icebreaker/alignment questions to open the session, draft the project charter overview slide, and prepare a "what I need from each of you" section. Target: 60-minute meeting.

Design a retrospective for [team] after [project or sprint]. The team has [X] people and worked on [description]. Create: a retrospective agenda (60 min), facilitation questions for each phase (What went well / What didn't / What we'll change), a method to collect input (anonymous vs. open), and a template for the action items we'll commit to. Avoid blame-heavy formats.

Write a lessons learned document for [project]. What went well: [list]. What didn't go well: [list]. Root causes: [analysis]. Recommendations for future projects: [list]. Format for the project archive — future BAs and PMs should be able to read this and avoid the same mistakes. Be specific and honest; vague lessons learned are useless.

Write a project charter for [project name]. Business problem: [description]. Objectives: [SMART goals]. Scope: [in/out]. Stakeholders: [names and roles]. Budget: [amount or TBD]. Timeline: [key milestones]. Risks: [top 3]. Success criteria: [how we'll know it worked]. Approvals needed: [who must sign off]. Keep it to 1 page — this is a decision document, not a plan.

Review this requirements section for quality: [paste section]. Flag: ambiguous language ("should," "may," "user-friendly"), untestable requirements, missing edge cases, requirements that are actually solutions (prescribing implementation), conflicting requirements, and missing business rationale. Rewrite each flagged item with a specific improvement.

I'm preparing a BA skills self-assessment for my performance review. My experience: [brief description]. Key projects: [list]. Skills I want to highlight: [list]. Help me: articulate my strengths with specific examples, identify growth areas to mention proactively, and frame my accomplishments in terms of business value delivered rather than activities completed.

I'm interviewing for a Business Analyst role at [company type]. The role focuses on [area — e.g., "digital transformation projects"]. Prepare me for the following question types: behavioral (STAR format), technical BA skills (requirements, process modeling), stakeholder management scenarios, and case study / analytical questions. For each, give me a structure and a sample response template.

Write an impact summary of my BA work over the past [quarter/year]. Projects I contributed to: [list]. Key deliverables: [list]. Business outcomes my work supported: [describe — cost saved, revenue generated, process improved, risk reduced]. Format for a leadership audience who won't know the project details — focus on business value, not BA activities.