VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

How to Simplify Life | Locality — Keep What You Use Near Where You Use It

There is a reason the scissors are never where you need them.

It is usually not because the family owns too few scissors.

It is because the storage logic has been designed around where things fit, not where actions happen.

The charger is in the bedroom, but the device is used in the study.

The school forms live in a drawer far from the place where bags are prepared.

The reference document is buried six folders deep, though it is opened every day.

The cleaning cloth is stored neatly in a utility cabinet, while the surface that needs wiping is across the house.

Each arrangement may be perfectly tidy.

The system is still expensive to use.


Quick Read

In one sentence: locality simplifies life by placing frequently used tools, information and supplies close to the action they support, reducing repeated search, travel, setup and memory work while keeping rare, archival or risky items out of the active surface.

Locality is not minimalism.

It is not “put everything where you can see it.”

It is not “one copy of everything.”

It is a topology question:

How far must the user travel—physically, digitally or cognitively—from the point of need to the thing that makes the next action possible?

Research on spatial organisation helps explain why this matters. Experimental work on everyday-style object arrangement found that people reorganise environments in ways that can reduce distance between likely targets and facilitate action. A related study on search strategy notes that people routinely organise environments—such as placing keys in designated locations—to reduce physical and cognitive demands. Scene-processing research also shows that spatial layout and spatial relations influence attention, memory and search.

Industrial 5S literature offers a second, applied line of evidence. Reviews associate organised, standardised workplaces with reduced waste, easier retrieval, better utilisation of space and improved safety, although successful implementation depends on context, monitoring and sustained use rather than one-off tidying.

The general principle is simple enough to use at home:

Store by use, not only by category.

Locality Is Different From Single Source of Truth

Single Source of Truth asks where the authoritative current answer lives.

Locality asks how close the useful representation or tool should be to the point of action.

These are not the same.

The airline remains the authoritative source for a live flight time.

Your calendar may hold a convenient operational copy because that is where travel coordination happens.

A password manager remains the source of truth for credentials.

A browser can provide a shortcut without duplicating the password itself.

Authority can stay central while access becomes local.

Locality Is Different From Friction Placement

Friction Placement owns the broader question of making useful paths easier and costly paths harder.

Locality owns one specific mechanism inside that design space:

distance to the required resource.

Distance can be metres.

It can be clicks.

It can be folders.

It can be social distance to the person who knows.

It can be cognitive distance between seeing a problem and remembering the rule that solves it.

The Locality Equation

You do not need mathematics to use the idea, but a useful mental model is:

retrieval cost ≈ frequency of use × distance to resource × uncertainty about location.

A rarely used passport can tolerate greater storage distance.

A calculator used every school day should not require a search expedition.

A critical emergency item may deserve high locality even if use is rare because consequence matters.

This gives us three drivers:

  • frequency;
  • consequence;
  • retrieval uncertainty.

High values justify shallower access.

Node 1: Point-of-Use Storage

The simplest form of locality is physical.

Put the thing near the action.

Stationery near the study surface.

Reusable bags near the exit.

Cleaning supplies near the zone they serve when safety allows.

Charging cables where devices are actually charged.

Medication in an appropriate safe location that supports correct use without compromising child safety or storage requirements.

Point-of-use does not mean every item sits on the surface.

It means the path from need to resource is short and predictable.

Node 2: Frequency Bands

Good storage has depth.

Daily: immediate reach.

Weekly: shallow storage.

Monthly or seasonal: deeper storage.

Archive: remote but indexed.

This prevents a common mistake: giving rarely used items the most convenient real estate simply because they look important.

The active surface should belong to active life.

Node 3: Use-Site Duplicates

Minimalism often treats duplication as failure.

Systems design asks a different question.

Does a duplicate remove enough repeated travel or failure to justify its maintenance?

A pair of inexpensive scissors in two frequent work zones may reduce more friction than one “perfectly minimalist” pair constantly travelling through the house.

A spare charging cable at a stable second work site may be sensible.

But duplication has a maintenance cost.

Too many copies create inventory, uncertainty and clutter.

Use duplication only where frequency and travel cost pay for it.

This connects with Maintenance Budget. Every duplicate must still be stored, replaced and understood.

Node 4: Digital Locality

Digital distance is real even when physical distance is zero.

A file can be on the same laptop and still be far away.

Six nested folders.

An ambiguous filename.

A login wall.

A search query you have to reconstruct.

A dashboard hidden behind several menus.

Digital locality uses:

  • shortcuts;
  • stable bookmarks;
  • shallow active folders;
  • predictable naming;
  • recent-project surfaces;
  • links from the workflow to the source of truth.

Do not move authoritative records merely to make them local.

Prefer references and shortcuts when duplication would create version risk.

Node 5: Information at the Decision Point

Useful information should appear near the decision that needs it.

A packing checklist belongs near packing.

A maintenance interval belongs near the maintenance record.

A student’s recurring error cue belongs near the next practice set, not buried in a reflection notebook opened once a month.

A food-allergy instruction belongs where the relevant caregiver can retrieve it quickly and appropriately.

The principle is:

Put the smallest useful piece of information at the point where it changes action.

This is not permission to cover every surface with labels.

Local information must earn its visibility.

Node 6: Preparation Locality

The best time to place a resource is often immediately after the previous use.

Finish studying.

Leave the next worksheet at the study point.

Finish a trip.

Return travel documents to their authoritative home and replenish the small items that belong in the travel kit.

Finish cooking.

Restore high-frequency tools to their use-site homes.

Locality is therefore not only storage.

It is reset.

Node 7: Social Locality

Knowledge also has distance.

If every small question requires locating one unavailable expert, the system has poor social locality.

A team can improve locality by placing common knowledge closer to the people who repeatedly need it:

  • short operating notes;
  • decision records;
  • shared templates;
  • clear escalation paths;
  • training for recurring tasks;
  • defined expert ownership for non-routine questions.

Do not turn every expert into a document factory.

Localise the knowledge that repeatedly blocks ordinary work.

Node 8: Locality for Exceptions

Rare high-consequence items are special.

Frequency alone would push them into deep storage.

Consequence pulls them closer.

Emergency contacts.

Critical medical information.

Fire-safety equipment.

Backup access information.

These need locality calibrated to safety and accessibility requirements.

This is why locality is not simply convenience.

It is the design of access under expected use and consequential exception.

Locality and the Search Tax

Search is often treated as free because each episode is short.

Where are the keys?

Where is the file?

Where did we put the spare battery?

Which folder holds the school receipt?

Repeated across years, search becomes a tax.

Locality reduces that tax by making location predictable and close to action.

The 2021 experimental work on search-strategy preferences is useful here because it treats spatial organisation as an external strategy that can reduce physical and cognitive demands. People do not always choose the best organisation spontaneously, which is why deliberate environmental design can matter.

Locality and Attention

Every retrieval can become an opportunity for distraction.

Open the phone to find a note.

See a message.

Answer the message.

Forget the note.

A local resource can reduce exposure to unrelated choice surfaces.

This is particularly useful for students.

A printed formula sheet or authorised reference card at the study point can sometimes be cognitively cheaper than repeatedly entering a general-purpose device full of competing signals.

The correct medium depends on the learning job and examination rules.

The Danger of Over-Locality

Locality can be overdone.

If every room contains every possible tool, the house becomes inventory.

If every project duplicates every document, version control collapses.

If every dashboard contains every metric, attention fragments.

If every person stores private copies of shared information, the organisation loses a source of truth.

Locality therefore needs a counterweight:

bring the access path closer without multiplying the authoritative object unnecessarily.

The Reverse Test: What Happens When the Usual Location Fails?

A beautifully local system can become fragile if there is only one path.

What if the study room is unavailable?

What if the laptop fails?

What if the person who holds the knowledge is absent?

What if the drawer is inaccessible during an emergency?

For low-consequence items, no backup may be needed.

For important functions, locality should coexist with a fallback path.

The Rotation Test: Local for Whom?

An item can be local for one person and remote for everyone else.

A parent stores all school documents on their own phone.

Convenient for the parent.

Impossible for the other caregiver.

A manager keeps the latest plan in a private folder.

Convenient for the manager.

Remote for the team.

Rotate the viewpoint:

Who actually performs the action, and is the resource local to that person at the moment of use?

The Time Test: Locality Changes With Seasons

What is local in examination season may not need to remain local after examinations.

Travel documents become highly local before a trip, then return to protected storage.

Tax documents become active during filing season, then return to archive.

Seasons therefore changes the active geography of life.

Good locality is dynamic enough to follow use.

Locality for Students

A student’s environment can be organised around learning actions rather than subjects alone.

  • Current practice materials at the study point.
  • Calculator, ruler and stationery in stable reach.
  • Correction log linked directly to the next practice set.
  • Frequently used digital references bookmarked shallowly.
  • Archive materials moved away from the active surface.
  • Phone placed outside immediate reach when it is not required.

The aim is not aesthetic perfection.

It is to make the next correct learning action cheaper than wandering.

Locality for Families

Family life has repeated zones.

Exit.

Study.

Meals.

Laundry.

Administration.

Recovery.

Ask what each zone repeatedly needs.

Then keep the smallest useful kit near that action.

This can make the home quieter without making it emptier.

Locality for Work

At work, locality can reduce handoff and search delays.

  • Current project decisions linked from the project workspace.
  • Common operating instructions near the work they govern.
  • Frequently needed tools at the point of use.
  • Expert escalation routes visible where routine work meets exceptions.
  • Archive kept searchable but away from active work surfaces.

Lean workplace methods such as 5S are often used to make location, order and standardisation visible. Reviews report benefits in organisation, waste reduction and safety, while also noting that sustainability depends on staff engagement, leadership, monitoring and context.

That caveat matters.

A labelled cupboard is not a working system if people cannot or do not use it.

The Locality Map

ResourceUse frequencyConsequence if missingBest locality
Daily school calculatorHighModerateImmediate study/bag route
PassportRareHigh when neededSecure authoritative storage; moved local before travel
Current project planHighHigh coordination costOne source, shallow access
Old tax archiveRarePotentially importantIndexed deep storage
Emergency contact informationRareHighAppropriately accessible at need point

When Locality Fails

  • Category obsession: everything of one type is stored together even when use occurs in different places.
  • Over-duplication: convenience creates inventory and version confusion.
  • Surface saturation: too many “frequent” items occupy immediate reach.
  • Authority confusion: local copies compete with the source of truth.
  • Security failure: sensitive or hazardous items are made too accessible.
  • Static geography: storage ignores changing seasons and use patterns.
  • Wrong-user design: the organiser optimises location for themselves rather than the actual user.
  • No reset: useful locality decays because items are not returned after use.

A Seven-Day Locality Experiment

  • Day 1: mark five things you searched for or walked to repeatedly.
  • Day 2: identify the action point for each.
  • Day 3: move one high-frequency low-risk tool closer to use.
  • Day 4: replace one duplicate file with a shortcut to the authoritative source.
  • Day 5: move one rare item away from valuable active space.
  • Day 6: test the system from another family member’s or colleague’s viewpoint.
  • Day 7: measure whether search, travel and setup actually fell.

Further Reading and Evidence

Frequently Asked Questions

Does locality mean keeping everything visible?

No. Frequently used items need predictable shallow access, not necessarily visual exposure. Rare items can move deeper while remaining indexed.

Is duplication always bad?

No. A low-cost duplicate can be rational when it removes substantial repeated travel or protects a critical use site. Count its maintenance and version cost first.

How does this work digitally?

Use shortcuts, shallow active folders, stable names and workflow links so frequently used information is close without creating unnecessary competing copies.

How does locality help students?

It reduces setup and search before study, makes correction information easier to reuse and keeps active learning resources from being buried under archives and distractions.

Final Thought: Distance Is a Design Choice

We often accept retrieval cost as though it were a law of nature.

It is not.

Some distances are necessary for safety, security and authority.

Others are merely inherited arrangements.

The simplest useful question is often not:

Where does this category belong?

but:

Where does this action happen, and what must be close enough for the action to remain easy?

Discover more from eduKate Singapore

Subscribe now to keep reading and get access to the full archive.

Continue reading