Case 1 · Payments mapping
Two payment rules, one record. Which one wins?
Two rules that can't both be true. Find the conflict before build.
Start the payments caseFree practice · no sign-up
Find the gap before the developers do.
Three free cases. Two from a mock UK bank: write your questions, then compare them with a senior BA's. One where AI plays the stakeholders you interview.
Case 2 · Service desk
Should every request close after seven days?
Today a coordinator checks each request is resolved before it closes. Find the conflict and the two details nobody has decided.
Start the service-desk caseCase 3 · Interview practice
Three stakeholders. Nobody knows everything.
An AI chatbot you are allowed to use plays the Head of Repairs, a sceptical adviser and the data protection lead at a fictional housing association. Find what each one knows, including what nobody volunteers, then compare with the debrief. A caveat: the AI plays the stakeholders, so it can be more agreeable and more consistent than real people and can carry biases from its training. Use it to practise your questions, not to predict how real stakeholders behave.
Download the interview case
Free playbook · PDF
Review AI output on a payments exception.
A settlement case worked through with the free requirements-review playbook.
Download the playbookThe brief
"Retry failed settlement-file imports."
Some records may already be accepted. How could a retry duplicate them?
Work through the review
Ask whether imports can partially succeed, what identifies a record across retries, and who investigates rejected records.
Request sample files and an import log. Leave retry behaviour unresolved until the accountable owners decide.
If they decide to retain accepted records and prevent duplicates, check partial failure, retry and re-sent files. This is a conditional example, not an approved production rule.
Fictional firm