Awareness and Coordination in Shared Workspaces
A paper by Paul Dourish and Victoria Bellotti
SUCCESSFUL COLLABORATION
Ingredients:
- Information sharing
- Knowledge of the group
- Individual activity
- Coordination
Awarness
What is it?
- "Understanding of the activities of others, which provides a context for your own activity"
Why is it important?
- "individual contributions are relevant to the group’s activity as a whole"
WhAT WAS STUDIED?
3 different collaborative writing systems
Quilt
PREP
PREP & Quilt
Content of Activity
Activity
GROVE
How to Support awareness?
- Collaborators inform each other about their activities
- Define roles
in case of Quilt and PREP
What was discovered?
- Overhead to the user
- not clear where/when information is needed
- Roles restriction slows down the collaboration
ShrEdit
What was DISCOVERED this time?
High-level awareness
- characteristics of the other's actions
Low-level awareness
- content of other's actions
it boils down to
Shared feedback
Discussion
What's your favorite collaboration tool today in comparison to ShrEdit?
Why?
What are the essential features/feedback?
What's missing?
Would you change your collaborative writing behavior based on what is being shared about your activity?
Would you feel better if you have already met face-to-face with other collaborators?
Where do you think the line between awareness and stalking is?
Developers in the classroom
How's this relate to you?
