Empathetic Product Story For Readability

There was some interest on the last product post so I figure I follow up with some clarification on some of the ideas.

Empathetic Product Story For Readability is a formal proposal of user story. It contains 3 stories of user journeys for the proposed new context.

For information on the interesting formatting decisions of the previous positing, please join the discussion at the common room.

Empathetic Product Story For Readability frames the goals of a software program from the perspective of a role identity which interacts with the software. For practicality, three roles are always mapped. The Target Audience Member, The Owner Admin, and The Developer Admin.

The Target Audience Member Is the One Who Just Wants A Button To Do The Function They Thought Of. (p:Make A Product Video)

The Owner Admin Is A Dedicated Team Member To The Universe. This interface may be defined as multiple product stories; one for each care owner. (p:w-2 employee)

And The Developer Admin Product Story Defines The Software Owner Interface. (p:cli dev)

Perfect Product Definition is the collection of Product Stories by role.
OwnerGroup1 is Owner Admin.
Owner Group 2 is Target Audience.

Perfect Product Understanding is a collection. It is the understandings of "How is it possible for me to" from the perspective of the identified roles.

How is it possible for me to book vacation as a user?
How is it possible for me to manage bookings as an intern?
How is it possible for me to oversee bookings as a software dev?

The Next Step

An Engineer takes over after that answer and produces specifications answering "What Infrastructure Makes That possible Scenario Possible?"

The Specifications Document Is A Major Milestone

(the previous post)