Designing for the Invisible
description
Transcript of Designing for the Invisible
Designing for the InvisibleUser-Centered Design of Infrastructure Awareness Systems
Juan David Hincapié-Ramos – [email protected]élien Tabard – [email protected] E. Bardram – [email protected]
Mini-Grid
2
Infrastructures
Infrastructures are Invisible!
Problems of Invisibility– Use (trust)– Adoption– Capacity (Mini-Grid)
Vizualizations
Seamful Design Intelligibility
3
GridOrbit
4
Designing GridOrbit
• Future Workshop• Paper Protoryping• Short Iterations –
Evaluations
• Designing for the Invisible
• Lack of understanding– Nature of the
Infrastructure– Characteristis– Potential
5
Problems for Design
6
AMCard Technique
AMCardmatching of the users’ interests with the information the infrastructure awareness system can provide
Infrastructure Awareness Model
O
NimbusWhat the entity projects about itself
Focus:What the entity is interested in
7
A B
8
A
UI
IA
9
IA
AMCard Technique
UI
10
Focus CardsThe users’ interests
Nimbus CardsThe infrastructure’s features
Inspiration Cards
11
Picture taken from the original paper: Halskov, K. and Dalsgård, P. 2006. Inspiration card workshops. In Proceedings of the 6th Conference on Designing interactive Systems (University Park, PA, USA, June 26 - 28, 2006). DIS '06. ACM, New York, NY, 2-11. DOI= http://doi.acm.org/10.1145/1142405.1142409
User Focus Cards
Infrastructure Critique, Implications for Redesign
Infrastructure Awareness System’s Features
Fieldwork
Infrastructure
User Focus Cards
Nimbus Cards
AMC Workshop
Design Concept+ Closure
Infrastructure Awareness Prototype
12
Design Presentation Matching Closure
Technique Stages
The InfAwareness
System
AMC – Design
13
AMC – Presentation
14
AMC – Matching (1/2)
15
AMC – Matching (2/2)
16
AMC – Closure
18
MatchedThe interests can be met
MissedEither interests orinfrastructure are insufficient
DiscardedIrrelevant for the solution
• 15 groups• 11 matches• 4 missed• 13 cards discarted• 9 focus• 4 nimbus
Results
19
To evaluate how relevant is the information displayed by infrastructure awareness systems.A
To identify which of the users interests infrastructures awareness systems do not take into account.BTo identify elements of re-design in the infrastructures themselves so as to improve their adoptability.C
Relevant: machines and people associated to them No Relevant: the details of task distribution.
Algorithms, input data and parameters
Task execution results (numeric or graphical)
Closure Analisys
• Which of the infrastructure features being shown, but not relevant (e.g. bidding activity);
• Which of the infrastructure features not being shown, but relevant (e.g. the data used to execute a task);
• Which elements of interest the awareness system could display to engage people even though not supported by the infrastructure (e.g. latest publications).
• Which elements of the infrastructure were missing to answer users’ interests (e.g. sharing of results).