The document discusses the process of defining user stories in product development, emphasizing their importance in clarifying what functionality is needed and the business value it provides. It presents examples of user stories for riders and drivers in a taxi app, detailing acceptance criteria for logging in and viewing available taxis. Additionally, it highlights the distinct roles of various stakeholders, such as UX designers, in determining how the defined requirements will be implemented.

1. LEAN APPS
BUILD PRODUCTS AT 5x SPEED
Innovate, Design, Develop, Measure, Automate, Repeat
User Stories

2. Narjeet Soni,
Co-Founder and CEO
#LeanInnovation #Designthinking #Agile
#Digitaltransformation

3. DEFINE MVP

4. User Story
As a <user role>,
I want to … <functionality>
So that … <business value>

5. User Story
As a <user>, I want to do <X>, so that <Y>
• <user> is the person who will use the product to
do some task
• <x> is the task <user> will achieve by this
story/feature
• <y> is the business reason or value <user> will
gain by doing task <X>

6. User Story
External apps
<user> = rider
<user> = driver
Internal products
<user> = customer support
<user> = data analytics expert
<user> = marketing manager
Common mistake - people working on
developing products are not the "users"
<user> <> developer
<user> <> ux designer
<user> <> technical architect
<user><> business analyst

7. User Story 1
Login and Registration
As a rider, I want to login into the Rider app, so that I can access the app and book a taxi for
my next ride
Acceptance criterion
1. I should be able to Register with my mobile number
2. After entering my mobile number I should receive a 6 digit unique number as an SMS
3. I should be able to enter this 6 digit unique number in the app to confirm the mobile
number and continue with registration
4. I should be able to set the password for myself after the mobile number is confirmed
5. I should be able to login using my mobile number and password
6. I should have an option to reset my password in case I forget it. The reset should work
via SMS and unique code, similar to registration
Note: A user story tells us WHAT is required, WHY it is required and for WHOM it is required
for. It does not answer HOW the WHAT should be done? HOW is defined by UX designer,
who creates a visual experience of HOW the defined story should be developed

8. User Experience - Uber

9. User Experience - Snapchat

10. Another example
As a driver, I want to login into the driver app, so that
I can start taking bookings from the riders

11. Another example
List taxis around me
As a rider, I want to see the list of taxis around me, so that I can see which taxi I want to
book for my journey from my current location to another part of the city
Acceptance criterion
1. The app should be able to see my current location via GPS - and take that as pick
up location
2. I should be able to change my pick up location if required
3. I should see the list of taxis around me - based on distance from me
4. I should see in time it would take them to reach me
5. I should see the distance of the taxi from me
6. I should also see the registration number of the taxi
7. I should also see the brand of the taxi - Mercedes, BMW, Tesla etc.
8. I should see the picture of the driver if available
See again, this story explains WHAT needs to be done, WHY it is required and for WHOM
is this required? UX Designer will define HOW this will be

12. Narjeet Soni
ns@theleanapps.com
+49 – 173 194 2045
Torstr. 33-35, 10119, Berlin, Germany
www.theleanapps.com