Affordance Theory (Gibson / Norman)
Overview
Affordance Theory explains how actors perceive and realize action possibilities offered by objects or environments. Gibson's ecological view holds that affordances are relational properties existing between actor and environment, independent of perception. Norman adapted the concept for design — perceived affordances guide user interaction, and signifiers communicate where action is possible. In IS research, affordance theory explains how technology enables (or constrains) organizational action.
When to Use
- Analyzing why users can or cannot effectively use a technology
- Designing interfaces that communicate functionality clearly
- Explaining how the same technology produces different outcomes in different organizations
- Bridging the gap between technology features and organizational practices
When NOT to Use
- Predicting adoption likelihood (use TAM/UTAUT)
- Measuring usability metrics quantitatively (use SUS or heuristic evaluation)
- When the focus is purely on aesthetic design without functional implications
Assumptions
IRON LAW: An affordance exists in the RELATION between actor and artifact —
it is neither a property of the object alone nor of the user alone.
Key assumptions:
- Affordances are relational — they depend on both artifact properties and actor capabilities
- Affordance existence differs from affordance perception differs from affordance actualization
- The same technology affords different actions to different actors (role, skill, goal-dependent)
- Constraints are the complement of affordances — what the artifact prevents or discourages
Methodology
Step 1 — Identify actors and artifacts
Specify the technology artifact and the actor groups. Characterize actor capabilities, goals, and context. The same artifact affords different things to a novice versus an expert.
Step 2 — Enumerate affordances
For each actor-artifact pair, identify:
| Affordance Type |
Description |
| Existence |
What action possibilities objectively exist in the relation |
| Perception |
Which affordances actors actually perceive (Norman's focus) |
| Actualization |
Which perceived affordances actors act upon |
Include constraints (actions the artifact prevents) alongside affordances.
Step 3 — Analyze gaps
Identify three critical gaps:
- Perception gap: affordances that exist but are not perceived (design/signifier problem)
- Actualization gap: affordances perceived but not actualized (motivation/skill/resource problem)
- False affordance: actions perceived as possible but that do not actually exist
Step 4 — Recommend design or organizational interventions
For perception gaps: improve signifiers, onboarding, or documentation. For actualization gaps: provide training, resources, or remove organizational barriers. For false affordances: fix misleading cues in the interface.
Output Format
## Affordance Analysis: [Artifact] x [Actor Group]
### Actor Profile
- Role: ...
- Capabilities: ...
- Goals: ...
### Affordance Map
| Affordance | Exists? | Perceived? | Actualized? | Gap Type |
|-----------|---------|------------|-------------|----------|
| | | | | |
### Constraints
- [constraint]: [effect on actor behavior]
### Gap Analysis
- Perception gaps: ...
- Actualization gaps: ...
- False affordances: ...
### Recommendations
1. [Gap type]: [intervention]
2. ...
Gotchas
- Do not conflate Gibson's affordances (relational, objective) with Norman's perceived affordances (subjective, design-focused) — state which lens you are using
- "Feature" is not "affordance" — features are artifact properties; affordances emerge from the actor-artifact relation
- Affordance theory is explanatory, not predictive — it helps interpret why things happen, not forecast adoption rates
- In IS research, affordance actualization depends on organizational context (norms, routines, power structures), not just individual perception
- Beware affordance creep — listing every conceivable action possibility without prioritizing those relevant to the research question
- Norman later preferred "signifier" over "perceived affordance" to reduce confusion — use current terminology
References
- Gibson, J. J. (1979). The Ecological Approach to Visual Perception. Houghton Mifflin.
- Norman, D. A. (1988). The Design of Everyday Things. Basic Books.
- Markus, M. L., & Silver, M. S. (2008). A foundation for the study of IT effects: A new look at DeSanctis and Poole's concepts of structural features and spirit. Journal of the AIS, 9(10/11), 609-632.
- Volkoff, O., & Strong, D. M. (2013). Critical realism and affordances: Theorizing IT-associated organizational change processes. MIS Quarterly, 37(3), 819-834.
1---2name: grad-affordance3description: Apply Affordance Theory (Gibson, 1979; Norman, 1988) to analyze the action possibilities that an artifact provides to an actor. Use this skill when the user needs to evaluate technology design from an affordance perspective, identify why users struggle with an interface, analyze IT-enabled organizational change through affordance actualization, or when they ask 'what does this technology afford', 'why can't users figure out this feature', or 'how does technology enable new practices'.4---56# Affordance Theory (Gibson / Norman)78## Overview910Affordance Theory explains how actors perceive and realize action possibilities offered by objects or environments. Gibson's ecological view holds that affordances are relational properties existing between actor and environment, independent of perception. Norman adapted the concept for design — perceived affordances guide user interaction, and signifiers communicate where action is possible. In IS research, affordance theory explains how technology enables (or constrains) organizational action.1112## When to Use1314- Analyzing why users can or cannot effectively use a technology15- Designing interfaces that communicate functionality clearly16- Explaining how the same technology produces different outcomes in different organizations17- Bridging the gap between technology features and organizational practices1819## When NOT to Use2021- Predicting adoption likelihood (use TAM/UTAUT)22- Measuring usability metrics quantitatively (use SUS or heuristic evaluation)23- When the focus is purely on aesthetic design without functional implications2425## Assumptions2627```28IRON LAW: An affordance exists in the RELATION between actor and artifact —29it is neither a property of the object alone nor of the user alone.30```3132Key assumptions:331. Affordances are relational — they depend on both artifact properties and actor capabilities342. Affordance existence differs from affordance perception differs from affordance actualization353. The same technology affords different actions to different actors (role, skill, goal-dependent)364. Constraints are the complement of affordances — what the artifact prevents or discourages3738## Methodology3940### Step 1 — Identify actors and artifacts4142Specify the technology artifact and the actor groups. Characterize actor capabilities, goals, and context. The same artifact affords different things to a novice versus an expert.4344### Step 2 — Enumerate affordances4546For each actor-artifact pair, identify:4748| Affordance Type | Description |49|----------------|-------------|50| Existence | What action possibilities objectively exist in the relation |51| Perception | Which affordances actors actually perceive (Norman's focus) |52| Actualization | Which perceived affordances actors act upon |5354Include constraints (actions the artifact prevents) alongside affordances.5556### Step 3 — Analyze gaps5758Identify three critical gaps:59- **Perception gap**: affordances that exist but are not perceived (design/signifier problem)60- **Actualization gap**: affordances perceived but not actualized (motivation/skill/resource problem)61- **False affordance**: actions perceived as possible but that do not actually exist6263### Step 4 — Recommend design or organizational interventions6465For perception gaps: improve signifiers, onboarding, or documentation. For actualization gaps: provide training, resources, or remove organizational barriers. For false affordances: fix misleading cues in the interface.6667## Output Format6869```markdown70## Affordance Analysis: [Artifact] x [Actor Group]7172### Actor Profile73- Role: ...74- Capabilities: ...75- Goals: ...7677### Affordance Map78| Affordance | Exists? | Perceived? | Actualized? | Gap Type |79|-----------|---------|------------|-------------|----------|80| | | | | |8182### Constraints83- [constraint]: [effect on actor behavior]8485### Gap Analysis86- Perception gaps: ...87- Actualization gaps: ...88- False affordances: ...8990### Recommendations911. [Gap type]: [intervention]922. ...93```9495## Gotchas9697- Do not conflate Gibson's affordances (relational, objective) with Norman's perceived affordances (subjective, design-focused) — state which lens you are using98- "Feature" is not "affordance" — features are artifact properties; affordances emerge from the actor-artifact relation99- Affordance theory is explanatory, not predictive — it helps interpret why things happen, not forecast adoption rates100- In IS research, affordance actualization depends on organizational context (norms, routines, power structures), not just individual perception101- Beware affordance creep — listing every conceivable action possibility without prioritizing those relevant to the research question102- Norman later preferred "signifier" over "perceived affordance" to reduce confusion — use current terminology103104## References105106- Gibson, J. J. (1979). *The Ecological Approach to Visual Perception*. Houghton Mifflin.107- Norman, D. A. (1988). *The Design of Everyday Things*. Basic Books.108- Markus, M. L., & Silver, M. S. (2008). A foundation for the study of IT effects: A new look at DeSanctis and Poole's concepts of structural features and spirit. *Journal of the AIS*, 9(10/11), 609-632.109- Volkoff, O., & Strong, D. M. (2013). Critical realism and affordances: Theorizing IT-associated organizational change processes. *MIS Quarterly*, 37(3), 819-834.
asgard-ai-platform