This is the old Design Jam site. Visit the new site here.

Flu Fighters

From Design Jams
Jump to: navigation, search

Contents

Team members

Research & explore

The brainstorming

Analyzing the Problem: Skimming relevant info

People are often annoyed and stressed by information that it is not relevant otherwise need information to accomplish tasks or stay up to date, but they find demanding to skim the relevant information from less relevant one. This problem is becoming unmanageable with the real time web application massive usage.

Finding out main filtering criteria .JPG

Finding_out_main_filtering_criteria_



Idea: A smart agenda based on routines, behaviours, time and space as filters and frames

The smart agenda can help people to skim information by using Routines, behaviours, time and space as filters and frames. The application shapes and manage the information stream according and combining some criteria of relevance: routines, behaviours, time and space as main filters and frames. GPS tech is required. Other criteria related with data of digital identities (profession, sex, work place, home place, etc), behaviors (like/don't like, saving etc..) and historical data are utilized for the agenda setting, agenda learning and further filters.Other criteria related with data of digital identities (profession, sex, work place, home place, etc), behaviors (like/don't like, saving etc..) and historical data are utilized for the agenda setting, agenda learning and further filters.

Primary target: professional people

What are routines?

We have chosen the routine concept to predict information needs: 1. When the user is getting to workplace he could prefer listening music or news 2. When the user is working he could prefer info related with profession 3.When he is shopping he could prefer info related with shopping 4.When he is relaxing and in spare time could prefer info related with entrainment 5.When he is attending an English class could prefer info related with language learning

And so on The agenda is built by routines

Information source: FB, Twitter, LinkedIn, Google (News, Gmail, Search)

These sources compose the information flow and the can be used to extract further filter

Criteria of relevance

1. What the user is doing and what he has planned to do is the core criteria to weight the incoming information.

2. Space and Time

Space: user localization, routine/planed/actual actions localization and the movement tracking increase the relevance

Time: the ‘posting’ time of information closer to user time increases the relevance. Close does not mean necessarily in the same time


Agenda design brainstorming process 1.JPG

Agenda_design_brainstorming_process_1




Finding out activities and routines brains.jpg Finding_out_activities_and_routines_brains

Interim presentations

[[1]]

Design

Users stories / Sketching / Wireframes

Smart Agenda Functionalities



The agenda and routines setting:

   user can choose the information sources from which receiving info: the agenda imports digital identities data  
   for each source imports the user can choose a personal menu of routines, starting by a default configuration he can drag and drop ‘routines’ collocating them at favourite time
   the agenda set the most important  localized  landmark as home place, workplace etc..
   the agenda can detect when the user is out of usual pattern analysing and comparing positions
   the agenda setting could be made in progress


Getting Information

   the agenda displays incoming info stream in each interval grouped by source. The default number of ‘conversations displayed is 10. The agenda manages priority applying the routine and other criteria already described  


User Interaction and feedback

   The user can scroll, save, ignore, marks info/feed/conversations: depending on the kind of action accomplished the agenda learns to topics/facts/persons more important and start to use this information to tune further the incoming flow.
   the user can save conversation regarding future events, the agenda will fill the correspondent interval then will start to use this info to prioritize
   the agenda can import entities from e-mails to fill the interval
   the agenda allows to filter flows by routine where each routine, defined by time and place , is also defined by keywords, tags (working routine: professional topics, colleagues, etc)
   user can choose event/activities and send invitation to network member


Bob is looking trought the agenda and saving info use case I r.jpg Bob_is_looking_trought_the_agenda_and_saving_info_use_case_I_r


Scenario A: Working Context Use Case: looking through info and saving ‘conversation’

Persona: Bob is a garden designer working, 40 y, loves improving his professional expertise and to stay up to date, he likes travelling, is single

   It is Monday at 10 in the morning, since Bob is in the Working Time routine
   Bob looks through the agenda all incoming info are relate to professional- work
   Bob finds out a relevant ‘conversation’ about a exhibition where is possible get new business deals
   Bob saves the conversation
   The agenda uses the keywork/topic/entities  related with the saved event to filter and weight new information 


Agenda paper prototyping source filtering r.jpg Agenda_paper_prototyping_source_filtering_r



Scenario B: Dating Context Choosing place/event to date and sending invitations

Persona: Mark

Mark is dating chosing place and sending invitation use case III.jpg

Mark_is_dating_chosing_place_and_sending_invitation_use_case_III


Scenario C: Choosing/organizing shopping for dating

Persona: Julie

Julie is going for shopping use case II r.jpg

Julie_is_going_for_shopping_use_case_II_r


Prototypes - on paper or on screen

Final presentation

After thoughts

About the Smart Agenda'idea' The mains challenging points are:

A) Scrapping and merging info from different sources (for legal and tech issues)

B) Building the taxonomies and rules to describe routines and activities (expansive?)

C) Building parsing tools and entities extractions tools (enough scalable?)


About Design Process

Just a note about methodology: Using false 'users' and 'personas' as we did, without carring out a real user research or a user requirement analysis, just to be compliant to formal methodology does not make sense, in my opinion. It might be more right and trasparent assuming that we are designing for ourselves and ideally extending requirements to a similar target. (?) In someway we did it, we thought about a sort of 'professional' target. I had this methodological doubt during the jam, but I did't get any clarification because of tight time.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox