Hi all, I think we can do much better with this and I want to take the chance to show you quickly how a more structured appoach to desgin using artifacts might help. I only do rough outlines of the artifacts to get the point.
### Vison We will support presenters to impress their audience with their talks by providing a small screen touchinterface to control their visiual presentation. ### Restrictions Target device / OS: - android smartphone - any minimal or maximum sreen suport? ### Persnas [P1] Nelly, 28, Phd-Student in social sciences. Used to tdo presentations, but still a little stressed when she has to talk. Works with LibreOffice. ### Situationas [SI1] Preparing a presentation [SI2] Giving a presentaion ### Restrictions [R1]: own or ownknown Presentation computer [R2]: own or ownknown presentation device [R3]: stable or instable connection between comupter and device (I wont use the restriction later on, you could challenge each storyboard with them) ### Storyboards / Goals [SB1]: [P1] in [SI1]: Tomorrow Nelly has to present her thesis. She will use a presentation and has made a lot of notes. She is already a bit nervous, but everything is well prepared, so all she wants now is to sleep well. She makes sure she does not have to hassle with technology tomorrow and everything works and goes to bed. -> [G1] Make sure Nellys smartphone will immedeately connect when she opens the presentation [G2]: Make sure Nellys notes will be shown to her in the presentation [SB2] [P1] in [SI2]: Nelly is giving her presentation. She is quite nervous but it gives her a good feeling that she can easily read the notes and navigate through the slides. without ever showing the wrong slide. Then her professor asks a question, and she suddenly has to go back to a certain slide. She really like that she does not have to flip through all the pages, but simply opens the desired slide and then effortlessly continues her talk at the last slide again.... [G3]: Avoid errors when while moving through the sildes [G4]: Make sure switching between slide and notes is easy [G5]: Make notes are supportive even with a lot of notes [G6]: Make it easy to to show slides that shortly interrupt the presentation flow .... now we could rate the relative importance of these goals and then we have a measure to actually inter-subjectively judge how good our design proposals are. Doing this I would immeadetely say that the current solution does not (fully) support the above derived goals. We can do user resaerch on most of the aritfacts to get "real" priorization of the importance of the goals and hence are able to challenge our design with approximations of real users and their needs... So all of this of course has to be done more thoroughly. Hope this can be of any help... Cheers, Björn Am Mittwoch, 16. Mai 2012, 20:12:24 schrieb Alexander Wilms: > Hi Mirek, > > these suggestions sound reasonable. I integrated them, if anybody has > another opinion, please mention it. > > >These things might be useful somehow in the future -- that's > >why we even keep an archive of finished whiteboards. > > We could still access the proposals after removing the <!-- --> > tags, and it would remove quite some clutter. > > Alex -- www.OpenUsability.org www.OpenSource-Usability-Labs.com -- Unsubscribe instructions: E-mail to [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/design/ All messages sent to this list will be publicly archived and cannot be deleted
