Experience threads, flows, or user stories enable designers to represent bigger ideas about various forms of user needs that the interface ought to support. It is a form of abstraction of requirements but also a way of envisioning in the form of scenarios. More so, designers should be allowed to own and interpret requirements which this feature allows for. Here I am referring to use representation as threads, as to step away from the misleading, inflexible and superficial idea that use happens in a predictable and linear way. Instead I would like to offer up the possibility to allow for complex threading of use representation.
More so, after interviewing a few designers, it was found that there is a definite preference for presenting wireframes as opposed to just sharing them (which results in important ideas being misunderstood or ignored). Hence, during presentation mode, experience threads could also be used as to guide the presentation with the stories the interface supports (visible in alternative G). Also, during presentation mode, comments could be captured about the feedback gathered which is visible in alternative (I).
[Updated June 10]. The new ideas starting from (Q) and on, explore the possibility of creating experience threads by means of taking screen snapshots of the interface (and various object states). More so, these screen snapshots can be intertwined with representations of user activity to tell rich and visible stories of interaction that can be used to fuel the presentation mode.
[...] is a second attempt at the Experience Threads functionality. I’m also thinking of simply calling it “Scenarios” as that might [...]