Key Principle
Sociability in ARGs must be a first-order structural property, not an emergent byproduct or feature layer. The term originates from Ducheneaut et al. (2004), who described social architecture in Star Wars Galaxies that promotes casual online relationships. Chapter 10 extends this from spatial architecture to temporal architecture: sociability emerges not just from where players gather but from how the game sequences their challenges.
The core mechanism is a three-phase escalation framework, each phase solving a specific retention problem:
- Attraction (Assisting) — Accommodate varied "game capital" (Consalvo, 2007) through silent onboarding. With 51.52% casual gamers and ARGs "almost unknown to most" players, slow scaffolding is structural necessity, not aesthetic choice.
- Group Formation (Uniting) — Split players into opposed teams kept mutually unaware. Information asymmetry forces inward bonding before outward competition. Predefined team names become identity anchors that players organically elaborate into collective meaning.
- Competition (Rivalry) — Reveal the rival team's existence mid-game, converting internal cohesion into external rivalry. Only one team can succeed.
The causal logic: constrained information creates dependency, dependency creates identity, identity enables rivalry, rivalry demands organization. Skipping or compressing phases collapses this chain.
Why This Matters
When sociability is left to emerge, player communities are fragile and dissolve at friction points. Players plateau at shallow cooperation and never develop the collective identity that sustains long-term engagement. Deliberate phase escalation produces groups that self-organize rapidly, generate their own governance norms, and persist even after the game ends.
The chapter also demonstrates that the same competitive mechanic produces different motivational effects depending on the social structure that receives it. The vertically-led Shujaa team was indifferent to their rivals because their leader redirected focus toward enjoyment, while the horizontally-led Waliochaguliwa team instantly pivoted to "search and destroy" upon learning of competition. Designers cannot predict competitive outcomes without accounting for group topology.
Good Examples
- The Trail (Greece, 2014): Near-zero budget ARG using Facebook groups as primary platform. PhD candidates, student actors, a director, a music composer. Demonstrated that sociability design, not production budget, drives ARG engagement. Both winning and losing teams requested a sequel. (Ch. 10)
- Narrative twist as social mechanic: Revealing a rival team's existence via steganography served simultaneously as plot development and as a mechanism forcing in-group coordination (shift schedules, role specialization). Story beats became load-bearing social infrastructure. (Ch. 10)
- Emergent governance: Players spontaneously produced instrumental codes of conduct — forensic evidence photography, systematic uploading — without designer prompting, demonstrating Taylor's (2006) "built-in social facilitators, norms through which they negotiate social action." (Ch. 10)
Counterpoints
- Vertical leadership creates dependency traps: The Shujaa team's leader scored 79 on leadership indicators vs. 36 for his nearest lieutenant. Informational conformity (Martin and Hewstone, 2010) created a self-reinforcing loop: perceived competence gap led to trust-based deference, which reduced initiative, which deepened dependency. Single points of failure are a structural risk of unmanaged sociability. (Ch. 10)
- ~20% attrition occurred between phase one and phase two, suggesting that even well-designed escalation loses players at transition points. The authors treat this as acceptable but acknowledge it as a cost. (Ch. 10)
- Reality has the last word: Real-world obligations (work shifts, physical presence) interrupt and constrain play. ARGs parasitize the existing world rather than simulating one, making friction between game urgency and life obligations an unavoidable design constraint. (Ch. 10)
Key Quotes
"Sociability is thus interpreted here as game design strategy aiming to the formation of effective online goal-orientated groups." (Ch. 10)
"This narrative twist had a tremendous game effect: each team now had its own narrative (a visible identity and a specific mission), its own alliances (game agents on their side), and different challenges to accomplish." (Ch. 10)
"Their assumption that the leader knew something that they did not, that was informational conformity (Martin and Hewstone, 2010) in the group, resulted in their putting their trust in their leader because they mistrusted their judgment and wanted to prevent mistakes from being made." (Ch. 10)
"As game designers it is our responsibility to provide the best possible experiences and in order to achieve that we ought to evaluate and re-examine our design choices." (Ch. 10)
Rules of Thumb
- Treat sociability as temporal architecture (sequenced phases), not spatial architecture (chat rooms, social spaces).
- Never skip the bonding phase before introducing rivalry. Groups thrown into competition without internal cohesion fracture rather than cohere.
- Use information asymmetry as a bonding accelerant: teams unaware of rivals develop stronger internal identity.
- Pre-game profiling (questionnaires, personality sorting) turns group composition from an emergent accident into a design variable.
- Competition awareness acts as a behavioral switch, not a gradient — it snaps group orientation from exploratory to eliminative.
- Monitor for vertical leadership concentration; a single dominant leader insulates a group from competitive pressure but creates bottleneck risk.
- Constructive dissent (the "Teaser" role) strengthens teams when paired with high engagement and solution-offering. Heterogeneous roles are functional load-bearers, not noise.
- Facebook-style closed groups serve triple duty: coordination headquarters, puppet master surveillance channel, and post-game social space.
- Iterative post-hoc evaluation is a designer obligation, not an afterthought — ARGs engineer social experiences with real emotional stakes.
Related References
- ARG Design Principles - Broader design framework
- Player Agency and Co-Creation - How social structures enable agency
- ARG Implementation Playbook - Practical execution of sociability design