HAAM doctrine / Summer Season '26

Human limits

Design begins with limits.

Attention, memory, confidence, time, data, institutions, and the living world are finite. Good design does not pretend otherwise. It decides what the system should absorb, what evidence people must see, and where human judgment must remain.

JudgmentHumanSystemLiving world
A map of human, system, and living limits around human judgment

The starting point

Limits are not edge cases. They are the material.

A product is always used under real conditions: someone is distracted, tired, unfamiliar with the subject, moving through a slow connection, using assistive technology, worried about consequences, or simply short on time. These are not unusual users. They are people.

Human limits are not defects to fix. They are conditions a responsible system must respect.

Three fields of constraint

Design has to fit more than the screen.

Human capacity is only one part of the picture. Systems are uncertain and organizations are finite. Products also consume energy, materials, labor, maintenance, and ecological capacity.

01 / Human limits

People cannot carry the whole system in their heads.

Attention, working memory, perception, confidence, expertise, sensory and motor ability, time, and energy all vary by moment and person.

attentionmemoryperceptionconfidenceabilitytime and energy

Sequence demands, preserve context, use plain language, support assistive technology, protect important decisions, and make recovery obvious.

02 / System limits

Technology does not know, predict, or recover perfectly.

Data is incomplete. Models are uncertain. Permissions, latency, ownership, maintenance, organizational capacity, and accountability shape what a system can safely do.

missing datauncertaintypermissionslatencyownershipaccountability

Show provenance and uncertainty, define boundaries, design failure paths, preserve human handoff, and never hide responsibility behind automation.

03 / Living limits

Every digital product is also a physical arrangement.

Software depends on energy, minerals, devices, logistics, human labor, maintenance, ecosystems, and consequences that may appear far from the interface.

energymaterialslabormaintenanceecosystemsfuture consequences

Treat extraction, consumption, longevity, repair, and ecological cost as design constraints rather than invisible externalities.

Field note / Environmental UX / Sep 2026

The building needs a harness.

When people bring parasols, face coverings, humidifiers, purifiers, headphones, fans, and heaters to survive a room, the interesting design signal is not the gadget. It is the missing interface to the building itself.

A September 2026 South China Morning Post story showed Chinese office workers improvising around harsh lighting, dry air, smoke, and perceived poor air quality. It framed the behavior through the social-media idea of "office ageing." That phrase is not a medical diagnosis. The more useful observation is behavioral: people are constructing private infrastructure because the shared environment is difficult to inspect and difficult to control.

Product research treats repeated workarounds as revealed requirements. A workaround appears when the system keeps producing a condition the person cannot adequately see, explain, or change. In that sense, the parasol is an interface to the building, just not one the building designed.

Most office workers can see the desk, thermostat, lights, and vents. Much of the actual system state stays hidden: carbon dioxide, particulate matter, humidity, temperature, illuminance, glare, noise, ventilation, and how those conditions change over time.

Why does the occupant have to adapt to the building rather than the building adapting to the occupant?
Building state
CO₂ · PM2.5 · humidity · temperature · light · noise · ventilation
Human experience
comfort · fatigue · concentration · irritation · perceived control
Harness
sense · correlate · explain · recommend · verify

The workaround is the signal.

A personal humidifier, purifier, umbrella, fan, or pair of noise-cancelling headphones is evidence about where the shared system stops serving the person. The object matters less than the condition that made it necessary.

Infrastructure is becoming individual.

When glare, dry air, noise, temperature mismatch, and air-quality concerns are solved one desk at a time, collective infrastructure is decomposed into tiny private defensive systems. The cost and cognitive burden move from the building to the occupant.

Sustainability needs a human constraint.

Energy use cannot be optimized in isolation from comfort and indoor air quality. The useful target is lower environmental cost while maintaining conditions people can actually work in, with the tradeoffs visible rather than silently pushed onto them.

What a phone can contribute

Sound level estimates, some light measurements, location, duration, motion, and user-reported experience can make the environment more legible without adding much hardware.

What still needs sensors

A phone does not directly measure CO₂, PM2.5, VOCs, or ventilation rate. Those require external sensors, building systems, or trusted environmental data. The interface should be explicit about what is measured, estimated, and unknown.

Important systems should expose their actual state to the people inside them.

Research note: EPA's BASE study explicitly connects environmental measurements, building and HVAC characteristics, and occupant symptoms and perceptions. FDA guidance also notes that typical fluorescent lamps emit very low UV levels, which is why the design opportunity here is broader than sunscreen or a single health claim.

What design decides

The human should not have to carry what the system can responsibly hold.

The goal is not to remove the human. It is to remove avoidable cognitive and operational burden while keeping judgment, evidence, permission, and accountability in the right places.

01

Remember

What context should the product preserve instead of asking the person to reconstruct it?

Keep state, history, progress, and the next step visible.

02

Understand

What does someone need to know before they can act with confidence?

Explain enough for the decision, then reveal depth progressively.

03

Notice

What genuinely deserves scarce attention right now?

Protect important signals and quiet everything that can wait.

04

Decide

Where is human judgment necessary because values, risk, or tradeoffs remain?

Do not compress consequential choices into an opaque default.

05

Delegate

What can be automated safely, and inside which explicit boundaries?

Move from observing to recommending to acting only as permission grows.

06

Question

Can the person inspect evidence, interests, uncertainty, and why the system intervened?

Keep provenance, independence, and contestability visible.

07

Recover

What happens after misunderstanding, failure, or a wrong model output?

Provide stop, correct, undo, retry, and human escalation paths.

Proportional friction

Friction is not always the enemy.

Remove friction from reversible, low-risk work. Add a deliberate pause where consequences are high, evidence is weak, or permission is changing. The aim is not a frictionless product. It is a product whose friction matches the decision.

Low consequence
Fast defaults, continuity, automation
Uncertain evidence
Explanation, sources, comparison
Changing permission
Preview, approval, visible boundary
High consequence
Pause, confirmation, human review

Research lineage

This doctrine was not invented in one afternoon.

It emerged through reading, participatory design, fieldwork, a six-year research project, and the practical work of keeping products understandable and working.

2020Reading

Algorithmic experience

Coursework on human-algorithm interaction connected transparency, fairness, accountability, validity, uncertainty, and trust. The underlying model belongs to the cited researchers; the durable lesson was that model output is only one part of the experience.

2020-21Field research

People are experts in their own lives

Participatory and service-design work in Tainan foregrounded situated context, different levels of technological confidence, mutual learning, autonomy, clear information, and the right of affected people to shape decisions.

2020-25Original research

Green Filter

A survey retaining 675 Taiwanese student responses and 30 individual prototype sessions showed that discoverability, trust, timing, information density, and action labels could matter more than generative capability. Useful information still fails when people do not notice it, understand it, or trust why it appears.

2026Practice

HAAM

Attention design, interaction contracts, accessible product states, governed automation, evidence trails, and designed failure paths now apply the same principle across products and organizations.

Use the doctrine

Start with eight questions.

A human-limits audit turns the philosophy into product decisions. It asks what the person is being required to carry, what the system can absorb, and what must remain visible.

What must the person notice?
What must they remember between steps?
What knowledge or confidence does the flow assume?
What burden can the system responsibly absorb?
What evidence and uncertainty must remain visible?
Where does permission need to change?
How can the person stop, correct, or recover?
Which human and living costs have been pushed outside the interface?

Follow the argument

Design for actual humans

Bring the system that asks people to carry too much.

HAAM can map the demands, remove avoidable burden, preserve the decisions that need a person, and make the limits of the technology visible before they become failures.

Start a project ↗

Help improve this website?

Optional analytics. Google Analytics and Clarity load only if allowed; form, email, and chat content are excluded.