March 14th, 2006: Design Session:Stamping and Communications*
Goal:
- Review use cases to nail down user's mental model
- Surface implementation questions and issues. And brainstorm around that.
Non-Goal 1. Solve all our problems
Agenda
Walkthrough use cases - as if there
- Book club -book list
- Book club - Invitation scheduling a session
Katie Implementation Issues & Braistorm
Katie's Book Club
Julie
Lizzy
Niko
Caroline
Trish
Katie
Beth
Feedback on the list -- >Book suggestions --> People (creator: katie to: Book Club members)
- The know it all *
- Plot v. America *
- Gun, germs and steal (note Lizzy didn't like it) *
- Read the book -liked it?
- Fiction/Non-fiction (genre)
- Amazon link, synopsis/review
- Lizzy responds saying, "Guns, germs & steel" was really repetitive. -->Alec: I thumbs up/down
- Caroline suggests Time Traveler's Wife --> *
- Beth says - I hate this genre, how about romatic thriller's --> Chatter
- Julie says (researched TTW-SciFi fans hate (Niko re:
)�SciFi fans loved it --> [*Chatter*]/*
Provides a link
- Trish suggests a new book that is available on line --> *
- Katie Enough- we have a list
- Let's pick one for the next session:
-->Consensus -->Likes-added up, dislikes are subtracted | $10--> distribute $10 among the books
TTW is the winner -->I
Julie
- Event - instance --> 2nd Wednesday of the Mo. 7:30 - PA, CA
- Stamps Event: Media Kind Book
- Event Stuff --> single occurrence
- * - Book-related schema -- > Title/event title?-- >*, author #page -- >*
- Amazon link cover image
Task: Get a copy of the book
Read book
OI
How does the user know if they should stamp an event as a task or create a separate task?
- Host/Organizer: Julie *--> edited time, propose new time -->
- Invitee: Katie, Niko
- Information re: book
- Can't host session @normal
- Visitor-->rescheudle here's the book
--
- Katie wants to invite[*Chatter*] [Priss - *]
- Add [* 1/2 hour] so she can ask questions [*Chatter]
- others reply: sure sounds fun [*Chatter*]
- * 2 people: kids will be sick for a ling time on vacation-can't come
- Julie - propose [*keep time]/location?
- * Lizzy? --> OK! here are directions
- Niko finds books online
- Share link with people*
Observers: husbands, Friends
Scenario 1: Constucting a list of books that may be a book to read (book suggestion feedback list)
- By person feedback
- Feedback - next book on booklist
- Each book - seperate piece of paper feedback
Example: delicious library
DM: Stamping
DM: Communcations
Edited time -->
Propose new time
Legend
- * = Item
- [*Chatter*] = Chatter
- sketch of stamping comm:
Questions
- Communications 2 media items - how fit with stamping?
- media item
- multiple communications
- how does that fit?
- book & multiple meetings?
- book & multiple tasks?
- does stamping always imply uniqueness? Event & book always is this other event? (I think not)
- Does stamping solve all use cases? Which use cases
- Does 1:1 us1: many affect how people think about stamping?
- Deso domain model have to match "identity" property of stamping? of Linking under the hood?
- Is it just usual?
- What are the items involved?
- What shows up w/ searches
- What gets shared?
- What does it mean to unstamp something? Split into tow items?
Jeffery's Q
- Stamping int he users mental model, is a tight compling of silos
- In some cases, stamping may be a statemnt of identity & uniqueness
- In other cases, while to the user, it looks like adding attributes, it's actualy adding a reference to cover many other items
- The key is that stamping is one easy mechannism for the user to obtain this tight coupling
- Strong linking (displayed together)
- Weak linking (display reference)
- Identity linking (cause to be the same)
- Key idea when appropriate, use thing itself as a reminder
Next steps
- Storyboards
- Write up jeffery/alec from engineering
- Some discussion with the write ups
- Not just 0.7-->Long term details
- terminology (rubber stamping, not postage stamping--> you can't unstamp it)
- If you have a point of view please do a write up and send it to the list.
- first sketch of stamping and comm: