Designing Software for Collaboration - Computerphile

TL;DR

Effective collaborative software is designed around who will use it, when they will use it, and why they will collaborate. A four-quadrant framework distinguishes same or different times and places, while common ground, willingness, technology readiness, and clear interface feedback help compensate for missing cues such as body language. Read on to see how these principles shape practical design decisions.

Transcript

we're going to do a maybe a few episodes i'm not sure exactly how it'll come as but on um the design of social software or collaborative software we're going to kind of do a bit of a mix so there we go with a less spinny chair let's see if i stay still so we're going to start with the kind of 20 plus years of research that have underwritten uh the ... Read More

Key Insights

• 🏛️ Understanding common ground is essential for building social connections and facilitating collaboration on social platforms.
• 👯 Collaboration thrives when people are willingly engaged, and technology is designed to be user-friendly.
• ⌛ Different quadrants of collaboration require tailored approaches to address the challenges presented by time and place constraints.
• 💁 The design of collaborative software should aim to provide adequate feedback and feed-through to keep users informed about their own actions and the actions of others.
• 🤽 Telepresence, the recreation of a person's physical presence, plays a role in conveying collaborative actions and intentions.
• 👤 Balancing the need for telepresence and supporting multiple users in collaborative software can present design challenges.
• 💁 Collaborating with large crowds often requires summarizing and presenting aggregated information about activities performed at different times and places.

Questions & Answers

Q: What should designers consider when creating collaborative software?

The most important starting point is to consider who will use the software, when they will use it, and why. Designers should also account for users’ willingness to collaborate, their common ground, and how ready the technology is to support them.

Q: What does common ground mean in collaborative software?

Common ground is knowledge that people share and know the other person also shares. It helps determine social connections and makes collaboration through software easier.

Q: What are the four time-and-place quadrants of collaboration?

The four quadrants are same time and same place, same time and different places, same place and different times, and different times and different places. Examples include coding together in one room, joining a Skype call from separate countries, handing a project to someone working later, and collaborating across time zones on the same system.

Q: What is lost when collaborators are in different places or working at different times?

They lose subtle communication such as nodding, body language, and nonverbal sounds that signal approval. Their interaction can become limited to exactly what people type or say, so the software must provide other ways to convey that missing information.

Q: Why does willingness matter in software-supported collaboration?

Collaboration works better when people are ready and willing to participate. If people are forced to collaborate, other parts of the experience need to be easier to make participation worthwhile.

Q: How has technology readiness improved collaborative software?

The transcript describes more than 20 years of research and progress in software for collaboration. That progress has focused on making the technology better and easier for people to use when working together.

Q: Why is feedback important in a collaborative user interface?

Feedback tells users whether an action actually happened. For example, after someone presses save in a word-processing document, the interface should confirm that it was saved; without that confirmation, the user may worry that the action failed.

Q: What separates a collaborator from the shared document or code?

The user interface sits between the person and the artifact being edited, such as a document or code. Treating the person, interface, and artifact as separate elements helps designers focus on how actions are performed and how their results are communicated back to the user.

Summary & Key Takeaways

• The content delves into the research behind social and collaborative software design and its connection to modern communication platforms like social networks and Snapchat.

• It emphasizes the significance of common ground, which refers to shared knowledge, in determining collaboration dynamics and strengthening social connections.

• The content also highlights the importance of people's willingness to collaborate and the continuous improvement of technology to promote effective collaboration.