Description
Imagine the user could complete a task by magic, then compare with the current steps to expose which steps are artefacts of technology rather than parts of the goal.
The magic principle is a thought experiment for escaping technology-driven design. The team decomposes a current task into its concrete steps, then describes how the user's goal would be met if magic were available. Comparing the two marks the steps that vanish as artefacts of the technology rather than of the goal. Taking magic to the extreme (no camera at all) is unhelpful; keeping some real elements makes the artefactual steps stand out. In Scott and Neil's example, sharing photos meant finding a cable, importing, uploading with a second program, copying a link and emailing; with magic, the camera would know it was a birthday and share the photos itself. Wi-Fi memory cards later removed the cable. The same lens exposes artefactual pages in multi-step web flows.
Attributes
- Discipline
- Design & Product Practice
- Loss type
- Latent
- Goal
- Generate ideas, Understand why
- Stage
- Design, Definition
- Data
- Analytical / expert
- Effort
- Hours
Steps
- Decompose the current task into its concrete steps, ideally from observation.
- Describe how the user's goal would be met if magic were available, keeping the key real objects in place.
- Compare the two lists and mark the steps that disappear as technology artefacts.
- Rank artefactual steps by frequency and effort.
- Design to remove, automate or merge the artefactual steps, and check the result against the user's goal.
Sources
- Designing Web Interfaces (Scott & Neil, 2009)
Also known as
- Magic principle
- What-if-magic task analysis
Categories
- Design
- Design & Product Practice