Stop 12 · AI & Modern BA PracticesTopics · 4/7

Prompt Engineering for BAs

In short

Type 'write requirements for an app' and you get mush. Type five clear lines with context, rules and a format, and you get something useful. Prompting is just good briefing, which BAs already do for a living.

Writing clear, structured prompts to get useful, business-relevant output from an AI tool — providing context, constraints, and examples rather than a single vague sentence.

The purple blob leans into an auto-rickshaw, pointing ahead and counting directions on his fingers.

Think of it like this

Directions to the auto driver

'Bhaiya, station chalo' gets you to some station by some route. 'East gate of the railway station, via the flyover, I have a 6:10 train' gets you exactly where you need to be. Same driver, better instructions.

Watch it happen

Building a prompt, piece by piece

Role

Context

Task

Constraints

Format

Iterate

1/6Say who the AI should act as: 'You are helping a BA at a bank'.

The big ideas

What you need to know

Context beats clever words

The AI only knows what you tell it. Business rules, users and goals matter more than magic phrases.

Show an example

Paste one good user story or table row. The AI copies its style and level of detail.

Ask it to flag assumptions

Add 'list any assumptions separately'. You get a ready list of questions for stakeholders.

It's a conversation

The first answer is rarely the best. Follow-up prompts that correct and narrow usually do the real work.

See it in code

Walk through the code

text

1You are assisting a business analyst at a bank.2Context: [paste anonymised interview notes here]3Task: List the pain points customers mention4  about opening a savings account online.5Constraints: use only the notes above. If you6  infer something, mark it "ASSUMPTION".7Format: a table with columns Pain point,8  Who said it (role only), How often, Quote.9Then list 3 questions I should ask next.

1/4Role plus your real, anonymised notes as context.

Role, context, task, constraints and format in nine lines. The last line turns the answer into your next elicitation step.

Save yourself the pain

Common mistakes

Oops

Writing one vague line and blaming the AI for a generic answer.

Do this instead

Brief it like a new colleague: context, task, limits and the format you want back.

Oops

Cramming five different tasks into one prompt.

Do this instead

Do one task per prompt, then chain them. You can check each step properly.

Your mission

Vague vs briefed

~20 min

Quick check

Your prompt gives good stories but the AI keeps adding features you never mentioned. Which addition helps most?

Go deeper

1Practice iterating on a prompt 3-4 times to see how wording changes shift output quality.
2Learn to provide relevant business context in a prompt for more accurate, usable output.
3Build a small library of prompt templates for recurring BA tasks (requirements drafts, meeting summaries).