NOTES: i usually type some notes before i begin design; just to assemble all available information and organise my thoughts
A Biometric Authentication ------------------------------------------------------------------------------------------------------------------------------------------------------------------------B Pre-meeting (leverage previous work done; make more robust)
“What’s my day look like” - provides a summary of planned activities / events. include information on the next appointment scheduled & meeting attendees
“Read my Feed” - provides a feed-reader ; gives a text-to-speech output of news, social media feeds or other long-form text objects like notes from a previous meeting
“Tell me more about this account” - provides other account & deal information ------------------------------------------------------------------------------------------------------------------------------------------------------------------------C Post-meeting (follow up from meeting - update info) - update sales phase on the deal (hard-coded)
Nina: “Based on your meeting I estimate the probability of deal closure to now be 90%. Do you agree?“ (using updated deal info & predictive analysis) Sales person: “Yes” Nina: “Do you want to update your forecast and send this information to your boss?” Sales person: “Yes”
the premise of this project was to create a voice-interaction scenario for a larger ux ecosystem; of lead generation, sales and workflow / productivity processes that can be used as individual apps, or aggregated into the ‘Fiori’ suite (which i was one of the original designers of, when i created the ‘MyView’ concept / ecosystem) i saved some screenshots that accompany voice interaction with Siri; just to have assets to rely on for familiarity as i begin the whiteboard concept process
this is all the same whiteboard; and all one concept for the entire voice interaction. i wanted to ‘brainstorm’ the task flow, as well as include a few ideas for interaction design mechanisms (notice that i’m borrowing from the google ‘cards’ idea; since voice interaction should provide short, memorable ‘packets’ of information, if the user is only looking at their phone to view the information that is accompanying their voice interaction scenario)
a ‘stitched together’ version of the photos of my whiteboard concepts
another ‘stitched together’ version of the photos of my whiteboard concepts
when i’m happy i have a solid concept / task flow, together with one or two good ideas for interaction mechanisms, i save my photo of my whiteboard to use as a background screen for what i’ll start to wireframe (i use omnigraffle, or keynotopia, or axure, or flinto, it just depends what the timeline and delivery method is supposed to be)
when people describe their experience of anything, they tell a story; usually in an anecdotal and sequential format. i like to make sure i understand the story correctly and that it has stakeholder agreement, so that everyone is telling the same story to each other, and are in agreement on the solution i’m supposed to design for
having done most of the problem-solving on the whiteboard, sometimes (it doesn’t always work this way) you can use it as your background screen, to build wireframes on top of. if your whiteboard solutions are close to what will be feasible in a real prototype, your next steps are to design the details of your interaction designs
just more wireframes; describing interaction design possibilities (bottom). and refining the design of the voice interaction sequence (top) which now includes some design artefacts from the Fiori ecosystem (from larger project - also designed by me)
assembling the parts: screens including Fiori ux pattern in a sequence representing the voice interaction scenario
refining the overall design with some ux artefacts
just illustrations of Fiori ux screens to show what the finished product looks like, which is where the voice scenario would be contained