The  “role-feature-reason” is a template intended to starters (for teams and product owners) of user stories. It’s the most recommended to help and once past the novice stage it also outgrows.

It looks something like this :

As a [type of user] I want [some feature] so that [some reason]”

Also Known As

It’s common to hear things like ” user story format” or “Connextra Format” when referring to Role-Feature-Reason template, also the diminutive “RGB” that means  role, goal, benefit.

The role (who) The feature (what) The reason (why).

Expected Benefits

This template serves as “training wheels”, reminding people in conversation about user stories to pay attention not just to “what” the desired software product is to do, but also “for whom” it does it and in pursuit of “what objectives”.

Common Pitfalls

Most teams new to this, fall into rote application when they are using this or other user story format. In fact, such formats are intended more as checklists.


 2001: the “role-feature-reason” format for expressing user stories is invented at Connextra in the UK.