Mapping Customer Job Stories – Adding the pain

Protegra

cache_sw_340_256_0_0_100_amplify-a-need „amplify a need“ from @gapingvoid

In his excellent blog post „Replacing The User Story With The Job Story“ Alan Klement provided a very compelling argument to move away from mapping based on personas of users and instead focusing on what jobs need to be accomplished. I cannot do his post justice here, so please check it out here . The difference between the two is briefly illustrated as follows:

1-lwr2g0HvLOVr5IPVNoYxLg Typical User Story map (from Alan Klement)

1-ua_egpJ6K1fCAQ_hY5UHAA Job Story map (from Alan Klement)

I started using this framework immediately with Butterfly (more here), as well as some other products we were developing here at Protegra, as we felt that it was a novel and straightforward way to build empathy with customers and drill deeper into their motivations and expectations. Also, as illustrated above, the user story map is laden with far to many unspoken assumptions; whereas the assumptions with the…

Ursprünglichen Post anzeigen 234 weitere Wörter

Advertisements

Kommentar verfassen

Trage deine Daten unten ein oder klicke ein Icon um dich einzuloggen:

WordPress.com-Logo

Du kommentierst mit Deinem WordPress.com-Konto. Abmelden /  Ändern )

Google+ Foto

Du kommentierst mit Deinem Google+-Konto. Abmelden /  Ändern )

Twitter-Bild

Du kommentierst mit Deinem Twitter-Konto. Abmelden /  Ändern )

Facebook-Foto

Du kommentierst mit Deinem Facebook-Konto. Abmelden /  Ändern )

Verbinde mit %s