Story structure

Stories follow a simple, structured format that captures three essential elements:

• Who — The Persona who needs this capability (e.g., "As the Chief Risk Officer...")
• What — What they need to do or know (e.g., "...I need to know our current Risk Position...")
• Why — The business Outcome or purpose (e.g., "...so that I can Assess the Risk")

Start simple

In the early phases of a use case, we only ask for these three elements. Don't worry about how it will be implemented — that comes later.

Examples

A business user could specify requirements as follows:

• As the Chief Risk Officer, I need to know our current Risk Position against party B, so that I can Assess the Risk
• As an Auditor, I need to get a list of all current board members of legal entity X, so that I can Verify Stakeholders
• As an Employee, I need to get a list of all my colleagues in my unit, so that I Know my Colleagues
• As a customer, I need to get a list of all products, so that I can make a product selection

And so forth. That's all we ask in the early phases of a given use case.