For Business Analyst / Process Improvement Analysts ·
What you'll accomplish
Your most repetitive documentation task (converting meeting notes into user stories, acceptance criteria, and BRD sections) takes under 10 minutes with a ChatGPT Plus workflow. This guide builds that workflow.
What you'll need
What you should see: Your ChatGPT interface shows "ChatGPT Plus" in the header.
Example context to paste at start of every session:
"You are helping me, a business analyst, create requirements documentation. All user stories should follow this format: 'As a [user role], I want to [action], so that [benefit].' Acceptance criteria should use Given/When/Then format. Requirements should be specific and testable. Do not use vague words like 'should,' 'easy,' or 'fast' without quantifying them."
After your context setup, paste your raw meeting notes and say:
"Here are notes from a requirements workshop. Extract the user needs and write user stories with acceptance criteria for each. Notes: [paste your notes]"
What you should see: ChatGPT returns a numbered list of user stories, each with 3-5 acceptance criteria in Given/When/Then format.
In the same conversation (same context is maintained):
"Now convert the same notes into a formal requirements section for a BRD. Include: Functional Requirements (numbered), Non-Functional Requirements, Assumptions, and Open Questions."
"Review the functional requirements you just wrote. Identify any that are: ambiguous, untestable, missing edge cases, or contradictory. List each issue with a fix."
"Reformat the user stories as a JSON list so I can import them to Jira. Each story should have: title, description (the user story), acceptance_criteria (array of strings), priority (default 'Medium'), and story_points (estimate 1, 2, 3, 5, or 8 based on complexity)."
User story generation:
Write user stories with acceptance criteria for: [feature/function description]. User roles involved: [list roles]. Must include edge cases for: [list edge cases if known].
Acceptance criteria from requirements:
Write 5 acceptance criteria in Given/When/Then format for this requirement: "[paste requirement]"
BRD section from notes:
Convert these workshop notes into a BRD section: Functional Requirements (numbered), Non-Functional Requirements, Assumptions, and Open Questions. Notes: [paste]
UAT test cases from acceptance criteria:
Generate UAT test cases for each acceptance criterion below. For each: Test Case ID, Description, Preconditions, Steps, Expected Result, Pass/Fail criteria. Criteria: [paste]
Requirements gap check:
Review this requirements section: [paste]. What user scenarios or edge cases are NOT covered? What should we go back and ask stakeholders?