|
|
|
Personas
|
|
|
|
|
|
|
|
Fred (OG) MAIN ACTOR
|
|
|
|
|
|
|
|
Jack (OG)
|
|
|
|
|
|
|
|
Inna
|
|
|
|
|
|
|
|
Mike
|
|
|
|
|
|
|
|
Anthony
|
|
|
|
|
|
|
|
Background
|
|
|
|
|
|
|
|
OG has been hired by the CTO of KPMG to create a new mobile app for a compliance process.
|
|
|
|
|
|
|
|
KPMG wants to hold a 2 day workshop with 5 people in it.
|
|
|
|
|
|
|
|
The main leader for the client will be Anthony the business client manager
|
|
|
|
|
|
|
|
Those 5 people are a mix of Inna, Mike and Anthony types.
|
|
|
|
|
|
|
|
OG has not engaged with KPMG or this group before (they are coming in cold).
|
|
|
|
|
|
|
|
They are hired for a 2 day workshop for envisioning then build a prototype over the course of 2 weeks.
|
|
|
|
|
|
|
|
They have been hired for 3 weeks in total.
|
|
|
|
|
|
|
|
OG is going to send in Fred to facilitate and Jack to prototype.
|
|
|
|
|
|
|
|
Jack is on another project so he can't be there for the workshop.
|
|
|
|
|
|
|
|
Narrative
|
|
|
|
|
|
|
|
3.1 |
Client Set up
|
|
|
|
|
|
|
|
3.2 |
Project set up
|
|
|
|
|
|
|
|
3.2.1 |
adds the exercise he wants to do for this workshop and can edit the descriptions
|
|
|
|
|
|
|
|
3.2.1 |
|
He could add new exercises from this screen if he wanted to
|
|
|
|
|
|
|
|
3.2.1.1 |
The system creates an agenda from these exercises with the descriptions
|
|
|
|
|
|
|
|
3.2.1.2 |
System sends out all emails to all participants with user names and passwords for the workshop
|
|
|
|
|
|
|
|
3.2.1.2 |
|
Should send out a simplified agenda and remind them to bring a lap top.
|
|
|
|
|
|
|
|
3.2.1.2.1 |
Might be cool if users could log in before the workshop and get to start ideas but see the workshop waiting for them
|
|
|
|
|
|
|
|
3.2.2 |
Downloads the agenda via PDF and attaches it to an email to send to Anthony
|
|
|
|
|
|
|
|
3.3 |
Workshop day 1
|
|
|
|
|
|
|
|
3.3.1 |
Introductions
|
|
|
|
|
|
|
|
3.3.1.1 |
All the workshop participants come in and sit with their lap tops
|
|
|
|
|
|
|
|
3.3.1.2 |
Screen shows the welcome message and asks them to log in
|
|
|
|
|
|
|
|
3.3.1.3 |
Clients log in
|
|
|
|
|
|
|
|
3.3.1.3.1 |
Client see welcome page and an agenda
|
|
|
|
|
|
|
|
3.3.1.3.2 |
If they had not previously loged in, system asks them to set up a user name and password. and pick an avatar
|
|
|
|
|
|
|
|
3.3.1.4 |
Shows an agenda on the screen and explains the tool
|
|
|
|
|
|
|
|
3.3.1.5 |
Reviews the day and what the Occom Group does (done on slides
|
|
|
|
|
|
|
|
3.3.2 |
Current state review
|
|
|
|
|
|
|
|
3.3.2.1 |
Reviews the current state of systems
|
|
|
|
|
|
|
|
3.3.2.2 |
takes notes in a note section of the tool
|
|
|
|
|
|
|
|
3.3.2.2 |
|
These notes would not be visible to the client (a pop out window) that could be thrown to a different screen (anyone can add their own notes as they go)
|
|
|
|
|
|
|
|
3.3.2.2.1 |
Would be cool if we could record where we are in the process, so all notes are under the current state review section then go under the problem statement. If you went back, notes would just be entered under the correct heading
|
|
|
|
|
|
|
|
3.3.2.2.1 |
|
Should work exactly like the text engine for the narrative tool
|
|
|
|
|
|
|
|
3.3.2.3 |
Records a few points and questions
|
|
|
|
|
|
|
|
3.3.2.4 |
Asks questions and records the answers
|
|
|
|
|
|
|
|
3.3.3 |
Problem statement
|
|
|
|
|
|
|
|
3.3.4 |
Inspiration Exercise
|
|
|
|
|
|
|
|
3.3.5 |
Idea exercise
|
|
|
|
|
|
|
|
3.3.5 |
|
Hit the parking lot
|
|
|
|
|
|
|
|
3.3.6 |
Customer definition
|
|
|
|
|
|
|
|
3.3.6.1 |
Exactly the same as the problem statement
|
|
|
|
|
|
|
|
3.3.6.2 |
Shoes definition, examples and directions for the idea statement exercise
|
|
|
|
|
|
|
|
3.3.6.3 |
Shows exercise timer
|
|
|
|
|
|
|
|
3.3.6.4 |
Enters demographic groups statements
|
|
|
client customer definition statement entry
|
|
|
|
|
3.3.6.4.1 |
For each demographic group, has a number of different demographic distinctions they can choose from:
|
|
|
|
|
|
|
|
3.3.6.4.1.1 |
Gender, age, life events, income, geography, need, want, department, role, position
|
|
|
|
|
|
|
|
3.3.6.4.2 |
clicks on an distinction it will ask her to type something in or choose from a list
|
|
|
|
|
|
|
|
3.3.6.4.2 |
|
Example: age = please supply an age range from ______ to ____
|
|
|
|
|
|
|
|
3.3.6.4.3 |
chooses more distinctions it builds a sentence
|
|
|
|
|
|
|
|
3.3.6.4.3 |
|
For example: women between 30 and 40 who are in HR
|
|
|
|
|
|
|
|
3.3.6.4.4 |
hits submit and that becomes the demographic group
|
|
|
|
|
|
|
|
3.3.6.4.4.1 |
editing would transfer it back to the demographic box
|
|
|
|
|
|
|
|
3.3.6.4.5 |
Eventually would be cool to choose a number of different databases we could query to show how many people are included in that group they have selected
|
|
|
|
|
|
|
|
3.3.6.4.6 |
Would be great to show a graphic representation of how they are doing, like a password strength indicator that shows "too broad" to "too specific"
|
|
|
|
|
|
|
|
3.3.6.4.6 |
|
For example, it they entered an age range but only included 1 year, maybe the indicator could say, might want to reconsider, that is a very small group
|
|
|
|
|
|
|
|
3.3.6.5 |
Curates customer statements
|
|
|
|
|
|
|
|
3.3.6.6 |
Sees the customer statement he just added and could add another
|
|
|
|
|
|
|
|
3.3.6.7 |
Completes the customer statement exercise by clicking on the customer statement to activate it
|
|
|
|
|
|
|
|
3.3.7 |
Persona Creation
|
|
|
|
|
|
|
|
3.3.8 |
User Narratives
|
|
|
|
|
|
|
|
3.3.8 |
|
If we have a screen naming thing, would need to have auto complete
|
|
|
|
|
|
|
|
3.3.9 |
Workshop is completed for the day and all clients leave
|
|
|
|
|
|
|
|
3.3.10 |
Clean up
|
|
|
|
|
|
|
|
3.3.10.1 |
Adds screen shots to each of the pecies for inspiration in the curated list
|
|
|
|
|
|
|
|
3.4 |
Workshop Day 2
|
|
|
|
|
|
|
|
3.4.1 |
Review
|
|
|
|
|
|
|
|
3.4.1.1 |
Day 2 of the workshop, client is in the room again and ready to go
|
|
|
|
|
|
|
|
3.4.1.2 |
reviews the last day's work by clicking through each step in the nav for the project
|
|
|
|
|
|
|
|
3.4.2 |
Paper prototype
|
|
|
|
|
|
|
|
3.4.3 |
Wrap-up
|
|
|
|
|
|
|
|
3.4.3.1 |
thanks everyone and explains what is going to happen next
|
|
|
|
|
|
|
|
3.5 |
Prototype creation
|
|
|
|
|
|
|
|
3.6 |
Deliverable creation
|
|
|
|
|
|
|
|
3.7 |
Hand-off to client
|
|
|
|
|
|
|
|
3.7.1 |
Sends link in an email to the wiki
|
|
|
|
|
|
|
|
3.7.2 |
What else could we do to encourage reuse or more engagement with the tool?
|
|
|
|
|
|
|
|
3.8 |
notes
|
|
|
|
|
|
|
|
3.8.1 |
We should look at makeing each object reusable. If you wanted to resuse a persona on a new project, how would you do it?
|
|
|
|
|
|