Difference between revisions of "Framework Design"
From Organic Data Science Framework
(Added PropertyValue: Participant = yolanda) |
(Added PropertyValue: Participant = felix) |
||
Line 27: | Line 27: | ||
<!-- Do NOT Edit below this Line --> | <!-- Do NOT Edit below this Line --> | ||
{{#set: | {{#set: | ||
+ | Participant=Felix| | ||
Participant=Yolanda| | Participant=Yolanda| | ||
SubTask=New_Features_Discussion}} | SubTask=New_Features_Discussion}} |
Revision as of 21:36, 15 May 2014
Contents
Social Design Principles
Starting Communities
- Create mechanisms to match people to activities
- Highlight more active tasks
- Inactive tasks should have „expected active times“
Timeline Tracking, Progress Tracking, Timeline
Encouraging Contributions through Motivation
- Make it easy to see and track needed contributions
Task Representation, Explorer Navigation, Worklist, Task Alert, Timeline, User Tracking - Ask specific people on tasks of interest to them
User Tracking - Simple tasks with challenging goals are easier to comply with
Task Representation - Specify deadlines for tasks, while leaving people in control
Timeline Tracking, Progress Tracking, Worklist, Task Alert - Give frequent feedback specific to the goals
- Requests coming form leaders lead to more contributions
- Publicize that others have complied with request
- People are more willing to contribute: 1) when group is small, 2) when commited to the group, 3) when their contributions are unique
Encouraging Commitment
- Cluster members to help them identify with the community
User Tracking - Give subgroups a name and a tagline
- Put subgroups in the context of a larger group
Explorer Navigation - Interdependent tasks increase commitment and reduce conflict
Timeline