Surface Temperature & Escalation — Design Token Architecture
Status
Conceptual framework, ready for token implementation. Derived from design analysis — not yet validated against live products.
Surface Temperature
Core Concept
Surface temperature describes two modes of Aleris's visual language. It is not a user-type distinction (patient vs staff) — it describes the type of situation the interface supports.
Both modes are warm. Aleris's brand identity ("den nära experten — personlig vård med ansvar och precision") applies everywhere. Temperature modulates how the brand expresses itself, not whether it does.
Two Surface Modes
Communicative surface — Aleris berättar, guidar, förklarar, välkomnar.
Use cases: patientguider, aleris.se content, marketing, onboarding, confirmation messages, newsletters, information pages.
Characteristics:
- Generous spacing and whitespace
- Softer visual hierarchy
- Sand tones dominate backgrounds
- Typography has room to breathe
- Images and illustration belong here
- Full expression of "den nära experten"
Instrumental surface — The user is working, navigating, configuring, monitoring.
Use cases: booking systems, dashboards, journal review, health declarations, CMS interfaces, administration views, treatment plan management, scheduling tools.
Characteristics:
- Tighter spacing and stricter grid
- Higher contrast for scannability
- Reduced visual decoration
- Typography optimized for efficiency
- Minimal visual noise
- Expresses the precision dimension of "den nära experten" — responsibility and efficiency
Key Principles
The user determines nothing; the situation determines everything. A patient managing their treatment plan in MyAleris is in instrumental mode. A staff member reading an internal newsletter is in communicative mode. The mapping is situation→mode, never role→mode.
A flow owns its mode. Temperature does not shift between steps within a single flow. An onboarding flow is communicative throughout, even if individual steps vary in complexity. A booking flow is instrumental throughout, even if it contains informational content. Mixing modes within a flow creates incoherent experience.
Transitions between modes should be perceptible but not dramatic. When a user moves from reading about their upcoming surgery (communicative) into the preparation checklist (instrumental), the shift should register without requiring mental adjustment. Both modes share the same base palette and typographic family — they vary in spacing, density, background temperature, and visual rhythm.
What temperature affects
Surface temperature is not only a color concept. A complete mode shift involves:
- Color: Background warmth, contrast levels, accent usage
- Spacing: Density, padding, margins, gap between elements
- Typography: Size relationships, line-height, weight distribution
- Composition: Grid strictness, decorative elements, whitespace rhythm
- Content density: Information per viewport area
A warm layout with cool colors (or vice versa) reads as inconsistent. All dimensions move together.
Escalation Levels
Core Concept
Escalation describes the intensity of the interface moment — the level of attention required from the user. It operates independently of surface temperature: both communicative and instrumental surfaces can escalate.
Three Levels
Business as usual — Default state. No special attention required.
The vast majority of what Aleris interfaces display. Standard navigation, routine content, regular workflows. The design system in its resting state. Warmth is the default — it does not need to be argued for.
Important — Attention needs to be raised. The user is expected to engage with something that has consequences.
Triggering principle: Important activates when the user is expected to take a position on something that has consequences beyond the current moment. Reading a patient guide has no consequences — you can close it and return. Signing a consent form does. This distinguishes business as usual (consequence-free to interrupt) from important (consequence-carrying to interrupt) without subjective judgment about difficulty.
Examples: consent forms, health declarations, payment steps, lab results requiring action, treatment plan confirmations, configuration changes with downstream effects.
Design expression: The interface reduces the decorative, increases precision and clarity. Still Aleris, but noticeably "nu gäller det."
Urgent — Immediate attention required.
System warnings, clinical alerts, missed steps that block a flow, time-critical actions. These situations are self-identifying and rare.
Design expression: Minimal visual noise, maximum contrast and clarity. The interface clears everything except what matters right now.
Escalation Principles
Business as usual is not a lesser state. It is the primary state — the one users spend 90%+ of their time in. It should feel considered and complete, not like a blank canvas waiting for escalation.
Escalation is a property of the view or context, not individual elements. Avoid escalating single fields or steps within an otherwise calm interface. If a consent form is important, the entire consent view is important — not just the signature field.
De-escalation should be deliberate. After completing an important action (e.g., signing consent), the transition back to business as usual should feel like resolution — a return to calm, not an abrupt context switch.
How the Two Dimensions Interact
Surface temperature and escalation are independent axes:
| Business as usual | Important | Urgent | |
|---|---|---|---|
| Communicative | Patient guides, aleris.se, newsletters, confirmations | Critical patient information, pre-operative instructions requiring acknowledgment | Emergency communication, service disruption notices |
| Instrumental | Standard dashboards, routine scheduling, regular data entry | Consent signing, payment, clinical configuration changes | Clinical alerts, time-critical system warnings |
Each cell in this matrix can have its own token set, derived from the combination of surface mode + escalation level.
Token Architecture Implications
This framework maps to the three-tier token model:
Primitive tokens — The complete Aleris palette. Unchanged by surface or escalation. Petrol, sand, orange, neutrals, feedback colors, Museo Sans/Arial, spacing scale, radius scale.
Semantic tokens — Where surface temperature and escalation are encoded. These tokens carry the design decisions:
surface.communicative.background.default→ references sand primitivessurface.instrumental.background.default→ references lighter/neutral primitivessurface.communicative.spacing.section→ generoussurface.instrumental.spacing.section→ tighterescalation.important.border→ more definedescalation.urgent.feedback→ high contrast
Component tokens — Individual components inherit from the semantic layer. A button in instrumental/important context gets its properties from the semantic tokens above, not from component-specific overrides.
Open Questions
- How do we handle the boundary between communicative and instrumental within a single product (e.g., MyAleris where patients move between information and tool contexts)?
- What is the minimum set of token categories needed to make each surface mode feel distinct? (Hypothesis: background color, spacing scale, and content density may be sufficient — typography and palette stay shared.)
- How do escalation levels express differently in communicative vs instrumental surfaces? (Important-in-communicative may need different expression than important-in-instrumental.)
- Should "important" have sub-gradations, or does the binary trigger principle (consequence-free vs consequence-carrying) hold?
Design Decision Record
Decision: Surface temperature is based on situation type (communicative vs instrumental), not user role (patient vs staff). Why: Aleris's brand promise applies to all users. A role-based split would create a two-tier experience and wrongly assume patients only consume information while staff only use tools.
Decision: Temperature is a property of an entire flow or view, not individual steps. Why: Shifting temperature within a flow creates perceptual inconsistency that users cannot meaningfully interpret. The system should be invisible.
Decision: Escalation uses a consequence-based trigger rather than subjective complexity assessment. Why: "Is this cognitively demanding?" varies by assessor. "Does interrupting this have consequences beyond the current moment?" has more objective criteria and prevents inconsistent application across teams.
Decision: Warmth is the default state, not a conscious design choice. Why: Aleris's brand essence is warm. Escalation and instrumental mode are departures from warmth under specific conditions — not alternatives to it.