MDIA1091 Chap.6 Affordances, Attention and Belonging
Affordances, Attention and Belonging
Affordance analysis links design to action without claiming that a feature mechanically causes behaviour. An affordance is a possibility that emerges between a feature and a situated user, so perception, ability, device, knowledge, norms and setting all matter. A reaction button can invite low-effort endorsement, autoplay can remove a stopping decision and an identity field can make some categories more visible than others.
Repeated invitations may contribute to patterns of attention, sociality and belonging, while platform owners retain greater capacity to change defaults and data flows.
What this chapter covers
- 01
An affordance belongs to a feature-user relation rather than existing as a fixed property inside an interface element
- 02
Designed cues invite action by changing visibility, effort, sequence, feedback or the availability of alternatives
- 03
Defaults and absences can structure action as strongly as visible buttons or menus
- 04
Accessibility reveals how the same feature affords different actions for differently situated users
- 05
Repeated invitations can contribute to norms of attention, recognition, obligation and belonging
- 06
Power enters when one institution can redesign the environment while users mainly adapt, appropriate or refuse within it
Worked example · free
Reading a neighbourhood reaction feature
- +1Identify the invitation: the button makes positive endorsement quick, public and countable, while disagreement requires more effort or silence.
- +1Trace visibility: the border turns accumulated reactions into a community cue that can direct further attention.
- +1Explain the possible pattern: repeated use may support a norm of practical helpfulness while making dissent less visible or moving it into comments.
- +1Qualify the effect: user practice, accessibility and moderation shape outcomes, so the feature does not guarantee harmony or uniform response.
Key terms
- Affordance
- An affordance is a possibility for action that emerges in the relation between a designed feature and a situated user.
- Default
- A default is a preselected state that structures action by making one path available without an additional decision.
- Friction
- Friction is the effort, time, knowledge or risk attached to completing or refusing an action.
- Visibility cue
- A visibility cue is a sign that directs attention by marking content, status or activity as especially noticeable.
- Situated user
- A situated user is a person whose capacities and interpretations depend on body, knowledge, device, culture and context.
- Sociality
- Sociality is the patterned form of relation, interaction and belonging through which people live with others.
Affordances, Attention and Belonging FAQ
Is an affordance the same as a feature?
No. A feature is a designed element, while an affordance is what that element makes possible for a situated user. The same feature may afford different actions depending on ability, knowledge, device and context. Analysis therefore links feature, user and setting rather than listing interface components.
How do defaults shape attention?
A default removes or relocates a decision. Autoplay, enabled notifications or preselected sharing settings can make continuation, interruption or disclosure the path requiring least effort. The default invites rather than guarantees action, so claims about resulting behaviour need comparison and user evidence.
How can affordances affect belonging?
Features classify identity, display reactions, connect users and organise group visibility. Repeated interaction through those possibilities can support recognition and community while excluding people whose identities or practices were not anticipated. Examine who can use the feature easily, which norms it rewards and who can redesign it.
Assessment move
For each interface case, write five items: feature, invited action, situated user, repeated practice and wider social pattern. Add the missing alternative and compare the effort attached to each path. Test accessibility by imagining different devices, sensory capacities and knowledge. Use diary notes that capture the moment before and after an action, including what cue appeared and what changed.
Practise turning causal language into relational language: replace 'the button caused' with a statement about what the button made more available, visible or costly. Close by identifying who can alter the feature and how the invitation connects to attention, data or belonging. Perform an action walkthrough without relying on memory. Start before the target action and note every cue, default, delay, confirmation and route back.
Repeat on another device or with an accessibility setting changed. Ask which knowledge the design assumes and what errors are easy to repair. Compare the visible action with an unavailable or costly alternative, then trace how repetition could affect attention or group membership. Keep individual variation in view by describing at least two situated users rather than an abstract average user.
End with a redesign proposal and a testable expectation, such as reduced accidental continuation or more equal participation, so evaluation follows from the diagnosed affordance.
