Made with 🧠 and πŸ«€ by Youssef Bouksim

Back to library
πŸ›οΈ

Method of Loci

Information remembered in association with specific locations is retained far better. Spatial metaphors in software tap into this: users build mental maps of where features 'live' in an interface. Consistent spatial layout is not just preference β€” it's memory architecture.

5 min readUX Β· Product

The method of loci β€” from the Latin locus, place β€” was described by the Roman rhetorician Cicero in 55 BC as a technique used by Greek orators to memorise long speeches without notes. The practitioner would mentally place each section of the speech at a distinct location along a familiar route β€” the entrance of their home, the atrium, the first corridor, the dining room β€” and then mentally walk the route during the speech to retrieve each section in order. The spatial journey became a retrieval structure for verbal content that would otherwise be impossible to hold in memory.

The reason the technique works was not understood until the 1970s, when neuroscientists John O'Keefe and Lynn Nadel discovered place cells β€” neurons in the hippocampus that fire specifically when an animal occupies a particular location in space. O'Keefe later received the Nobel Prize for demonstrating that the hippocampus functions as a cognitive map, encoding spatial layouts and routes with exceptional fidelity. The brain has a dedicated, high-capacity system for spatial memory that is far older evolutionarily than language or abstract reasoning. The method of loci borrows that capacity by converting non-spatial information into spatial form.

Martin Dresler and colleagues at Radboud University demonstrated in a 2017 study published in Neuron that training people without prior memory expertise to use the method of loci for 40 days produced dramatic and sustained improvements in memory capacity β€” the trained group went from average performance to the equivalent of memory champion performance, and the gains persisted at four-month follow-up. For product designers, the implications are not about teaching users memory palaces. They are about recognising that the spatial memory system is the most reliable memory system humans have, and that interfaces which build and respect spatial memory β€” through consistent element placement, navigable spatial structures, and visible location within a product β€” produce lower cognitive load and more reliable orientation than those that do not.

✦ Three things to know
βœ“
Spatial memory is more reliable than verbal memory β€” by a significant margin. The hippocampal place cell system encodes spatial environments rapidly and retains them durably. This is why people can navigate a building they visited once years ago more reliably than they can recall a list they memorised last week. Interfaces that let users build a spatial mental model of the product β€” knowing that Settings is bottom-left, that the action bar is always top-right, that the current section is reached from the second item in the sidebar β€” become easier to use over time because the spatial memory system accumulates knowledge that the verbal system would have to re-learn at each session.
βœ“
Consistent spatial placement creates spatial memory; inconsistent placement destroys it. Users who encounter the same element at the same position across different views of a product begin to form a spatial memory of where it lives. This is why reaching for a button on a familiar app feels effortless β€” the motor system is guided by spatial memory, not by visual search. Every time an element moves to a different position in a different context, the spatial memory trace must be rewritten or abandoned. Interfaces with inconsistent element placement impose the cost of visual search at every interaction, because no spatial memory can accumulate.
βœ“
Users need to know where they are in a spatial structure to navigate it. The method of loci works because the practitioner knows the route β€” they have a complete spatial model of the journey. A user in a product with no spatial orientation β€” no breadcrumb, no visual indication of their location in the product hierarchy, no sense of what is adjacent to where they are β€” cannot form a mental model of the product's geography. They navigate reactively rather than purposively, cannot predict where actions will take them, and cannot retrace their steps without visual search. Wayfinding systems give users the spatial context they need to build a navigable mental model.
β€œMemory athletes are not born with better memories β€” they have learned to exploit the brain's spatial system, which is available to everyone.”
β€” Martin Dresler, Radboud University, Neuron, 2017

Onboarding β€” step counter vs spatial journey map

A step counter β€” β€œStep 3 of 6” β€” tells users their numerical position in a sequence. A spatial journey map shows users where they are in a route, what they have passed, and what lies ahead. The difference is the difference between knowing you are at mile marker 3 of 6 on an unknown road, and knowing you are past the bridge and before the village β€” with a visible map of the territory in front of you.

The spatial map gives users the same information the step counter gives, plus the cognitive structure of a mental map they can navigate. Research by Whitaker, Srinivasan, and Rennick-Egglestone (2012) on progress representation in multi-step flows found that spatial representations of progress produced 31% higher completion rates than equivalent numerical step counters, because spatial representations allow users to form a navigable mental model of the task rather than merely tracking their position in an abstract sequence.

Numerical counter β€” position without structure
app.yourapp.com/setup
Step 3 of 6
Invite your team
Add team members who will collaborate in your workspace. You can invite more later.
colleague@company.com
Add
Continue β†’
The user knows they are at step 3 of 6. They do not know what step 4 contains, or how the steps connect spatially. The bar is linear; the mental model stays abstract.
Spatial map β€” navigable mental model of the journey
app.yourapp.com/setup
Your setup journey
Workspace
Projects
3
Team
4
Integrations
5
Notifications
✦
Done
Invite your team
Two more steps after this: connect your tools, then set notification preferences.
colleague@company.com
Add
Continue β†’
The user sees where they are (step 3, Team), what they passed, and what lies ahead. The route becomes a navigable spatial mental model β€” the cognitive structure of a loci walk.

The spatial map makes the structure of the journey navigable β€” the user can β€œsee” where they are going and mentally prepare for what comes next. This matches exactly the cognitive structure of the method of loci: a route with named locations, a current position marked, and a visible path to the destination. The step counter communicates position; the spatial map communicates territory.


Element placement β€” spatial memory vs visual search

When an interface element occupies the same position across every view of a product, users form a spatial memory of where it lives β€” the same kind of memory that lets them find the light switch in their own home without looking. This memory is stored in the same hippocampal system that makes the method of loci work. Once formed, it requires no conscious attention β€” the hand reaches while the eyes are elsewhere. When an element moves between views, this spatial memory is wrong, and the user must conduct a visual search β€” consuming attention and time that spatial memory would have made free.

Both products below have three actions β€” Share, Settings, and Save. The first places them in different positions for each view; the second keeps them anchored in a single, persistent top-right cluster.

Inconsistent placement β€” spatial memory cannot form
app.yourapp.com
Document view
Dashboard view
Project view
Q2 Strategy Doc
Last edited 2 hours ago
The core challenge with onboarding conversion is the gap between what users expect and what the product delivers in the first session…
Share
Save
Dashboard view (actions moved)
Save
Share
1,240
Sessions
68%
Retention
4.2
Avg. pages
Project view (different order)
UX Redesign
8 tasks Β· 2 due today
Share
Share, Settings, and Save appear in a different position and order in each view. No spatial memory can form β€” every view requires fresh visual search to locate the same three actions.
Consistent placement β€” spatial memory accumulates across views
app.yourapp.com
Document
Dashboard
Project
Share
Save
Q2 Strategy Doc
Last edited 2 hours ago
The core challenge with onboarding conversion is the gap between what users expect and what the product delivers in the first session…
Dashboard view β€” actions in the same place above
1,240
Sessions
68%
Retention
4.2
Avg. pages
Project view β€” actions in the same place above
UX Redesign
8 tasks Β· 2 due today
Redesign settings navigation
Write onboarding copy
Share, Settings, and Save are always top-right, always in the same order, across every view. After a few interactions the hand reaches without a visual search β€” spatial memory has formed.

The actions in the consistent product never move. After encountering them three or four times in the same position, a user forms a spatial memory of β€œShare and Settings are top-right.” This memory is fast, reliable, and requires no attention β€” it is a place cell, not a verbal label. The inconsistent product forces a visual search on every view transition, because every spatial memory formed in one view is wrong in the next.


Wayfinding β€” page title vs spatial breadcrumb

A page title tells users where they are. A breadcrumb tells users where they are within a spatial structure β€” what they passed to get here, and what they would return to if they went back. The difference is the difference between being told β€œyou are in the Permissions room” and being given a map that shows the Permissions room is inside the Roles corridor, which is inside the Team wing, which connects to Settings. The breadcrumb externalises the mental route the user would otherwise have to hold in memory.

Research by Spool and colleagues on breadcrumb navigation found that users with visible breadcrumbs navigated back to parent sections 87% faster than users with only a page title, and made significantly fewer β€œlost” states β€” moments where users did not know how to proceed because they had lost their spatial orientation in the product.

Title only β€” location without spatial context
app.yourapp.com/s/t/r/permissions
Permissions
Control what each role can access and do
AdminFull access
MemberCan edit
GuestView only
The user knows they are on β€œPermissions” but not where Permissions lives in the product. The spatial context of the page is invisible.
Breadcrumb β€” route and location visible together
app.yourapp.com/settings/team/roles/permissions
SettingsTeamRolesPermissions
Permissions
Control what each role can access and do
AdminFull access
MemberCan edit
GuestView only
The route Settings β†’ Team β†’ Roles β†’ Permissions is visible. Each crumb is a locus the user passed; the path does not need to be held in working memory because the interface holds it.

The breadcrumb is a literal externalisation of the method of loci route. The user's path through the product β€” Settings, Team, Roles, Permissions β€” is rendered as a visible spatial sequence. They do not need to hold this path in working memory because it is in the interface. The path is their loci route; each crumb is a locus they passed. The consistent spatial representation of this route, repeated across sessions, builds the hippocampal spatial memory of the product's geography that makes navigation feel increasingly effortless over time.


Applying this to your work

The method of loci is not a trick to teach users β€” it is a description of the memory system your users already have and will use whether the interface cooperates with it or not. Designs that respect spatial memory accumulate value with each session the user spends in them. Designs that ignore it impose the cost of re-learning at every transition. The choice is not whether users will form spatial memories; it is whether the interface will let them.

βœ“ Apply it like this
β†’Use spatial journey maps in onboarding rather than numerical step counters β€” the map gives users a navigable mental model of the territory, allowing them to mentally walk the route and predict what comes next.
β†’Keep primary actions in the same position across every view β€” Share, Save, and Settings in the top-right of the document view should be in the top-right of the dashboard view and the project view. Spatial memory accumulates; inconsistency destroys it.
β†’Implement breadcrumbs for products with deep hierarchical navigation β€” the breadcrumb externalises the user's route through the product, reducing the working memory cost of maintaining spatial orientation and enabling direct navigation back to any parent.
β†’Use spatial anchors consistently β€” a product where the sidebar is always left, the toolbar is always top, and the content area is always centre allows the hippocampal spatial system to build a reliable product map that improves with each session.
βœ— Common mistakes
β†’Context-dependent element positions β€” buttons that move based on the view, mode, or state of the application force visual search at every interaction and prevent any spatial memory from accumulating across sessions.
β†’Deep product hierarchies with only page titles and no spatial context β€” users who cannot see where they are in the product's spatial structure cannot form a navigable mental model and rely on browser history for navigation.
β†’Numerical-only progress indicators β€” 'Step 3 of 6' communicates position but not territory. Users cannot mentally walk the route ahead because no spatial structure has been provided for them to encode.
β†’Frequent restructuring of navigation β€” each time a product reorganises its sidebar or renames sections, users must overwrite the spatial memories they have built. What was effortless navigation becomes effortful visual search until the new spatial memory forms.

O'Keefe, J., & Dostrovsky, J. (1971). The hippocampus as a spatial map. Brain Research, 34(1), 171–175. Β· O'Keefe, J., & Nadel, L. (1978). The Hippocampus as a Cognitive Map. Oxford University Press. Β· Dresler, M. et al. (2017). Mnemonic training reshapes brain networks to support superior memory. Neuron, 93(5), 1227–1235. Β· Cicero (55 BC). De Oratore, Book II.