Voice — how the Present Expert is written

Voice: how the Present Expert is written

Status: draft · Owner: Head of Design · Scope: patient, employee, and partner communication — the form of the message, not its clinical substance · Version: v1.0-draft · Updated: 2026-06-07

Author: Torfinn Almers · Audience: writers, designers, the assistant/LLM layer, and the viewports that render brand-os Supersedes: foundation/voice.md (the explanation) · Related: [[constitutional/voice-is-the-present-expert]], [[constant-and-contextual]], [[emotional-modes]], [[_examples/voice-examples]]

Draft — meta-refactor probe output. Provenance is marked so the content boundary stays visible: (verbatim) is Torfinn's existing voice copy, relocated unchanged; PROPOSED marks new brand-voice text drafted as a starting point for Torfinn's voice pass, not final; everything else is structural scaffolding. The non-negotiable core lives in constitutional/voice-is-the-present-expert.md; the concrete examples live in _examples/voice-examples.md and are cited here, not embedded. Each principle now leads with the question it answers, so a writer — or an LLM — facing a situation the manual never named can reason from the question instead of looking for a matching rule.

PROPOSED — hook. The voice is the most recognisable property of Aleris. The logotype is seen and the colours are seen, but the voice is felt — and it is felt through ordinary choices about what comes first, what is named, and what is left out. This file explains those choices as five principles. The question each principle answers is printed above it, because the question is the part that transfers to a new case; the answer is only its application here.

The Present Expert

(relocated from en-draft/voice.md — an unverified EN translation of the canonical Swedish; the rendering of the identity is Torfinn's to confirm)

Aleris is the Present Expert: a specialist who has time for you. A knowledgeable colleague who meets you where you are and explains clearly, directly, and with genuine interest in you specifically — not an authority that informs, and not an inventive salesperson.

The voice holds even when the content is difficult: payment terms, complication risks, cancellation rules. The Present Expert uses plain language and leads you to the next step toward your goal.

The test

(PROPOSED — Dec 1 wording; replaces the three Swedish variants, which read as AI-ish or organisation-centred)

Every text, every interface, every message can be held against one question:

Does it feel like the sender has time for me, in a way that feels genuine and attentive?

If the answer isn't an unambiguous yes, the message needs more work.

1. Whose world does the sentence see from?

Is the patient acting, or being acted upon? Is the text written from the viewpoint of the organisation or the person reading?

The patient is a subject, not a recipient.

The patient has needs and is looking to complete a job — they are preparing for something, making plans and decisions, asking questions. Our communication must reflect that. Passive phrasing ("you will be summoned to") makes the patient an object. Active phrasing ("you will receive a summons") makes the patient a person.

This isn't just about grammar, but about perspective. A text that begins with "the clinic offers" sees the world from inside the organisation. A text that begins with "you can" sees the world from the person reading.

Test: Is the patient the one acting in the sentence — or the one something happens to?

Anti-pattern: The organisation-as-subject sentence. "The clinic offers…", "the patient is summoned…", "applications are processed…". Symptom: the patient appears only as the thing things are done to; the sentence reads from inside Aleris looking out.

Evidence: The summons example — see [[_examples/voice-examples]].

Implication: Consider the perspective of the patient and make them the one who acts.

2. What does the reader need in the first three sentences?

If the text were cut to its opening, would the reader still know what applies to them?

Structure follows the patient's journey, not the clinic's needs.

The information that is useful for the patient should come first. Often, care texts are organised by the clinic's logic: first the department, then the routine, then what the patient should do. The patient's question is the reverse: what happens to me, in what order, and what do I need to do?

The same principle applies in every format. A website, a sign, an app, a letter — the structure should follow the person reading, not the one sending.

Test: If I read only the first three sentences — do I then know what applies to me?

Anti-pattern: Clinic-logic ordering. Department, then routine, then — last — what the reader has to do. Symptom: the reader's own next action is buried below information that serves the sender.

Evidence: See [[_examples/voice-examples]] for ordering before/after.

Implication: Order the text by the reader's questions, not the organisation's need.

3. How do you stay warm while saying something hard?

Is the distance in this sentence protecting the reader, or protecting the writer's comfort?

Directness without distance.

The Present Expert is direct without being cold, verbose or dehumanising. "You need to fast" is direct. "Please note that the patient is expected to fast" is bureaucratic. The difference isn't politeness — it's distance.

Directness doesn't mean harshness. It means we respect the recipient's time and attention enough to say what applies without detours.

Test: Can I remove words without losing meaning or sounding like a robot? Then I should.

Anti-pattern: Distancing politeness. "Please note that…", "kindly be advised…", the third-person hedge that turns an instruction into an announcement. Symptom: courtesy words add distance without adding meaning.

Evidence: The fasting example — see [[_examples/voice-examples]].

Implication: (PROPOSED) Say the thing plainly, then check whether any word can go.

4. Does the reader get a reason, or only an order?

Would the instruction survive a situation that doesn't match it exactly — because the reader understands why?

Clinical information is explained, not dumped.

A list of preparations before surgery isn't communication — it's a checklist. Communication explains why: why you should fast, why you shouldn't take Trombyl, why you need to bring your referral. The explanation lets the patient follow the instruction even when the situation doesn't match exactly.

Explaining doesn't necessarily take more room: a single sentence can carry both the instruction and its reason. See the Trombyl example in [[_examples/voice-examples]].

Test: Would the patient understand why — not just what?

Anti-pattern: The dumped checklist. Instructions with no reason attached. Symptom: the reader can comply only when the situation matches the list exactly, and is stranded the moment it doesn't.

Evidence: The Trombyl one-sentence example — see [[_examples/voice-examples]].

Implication: Give the reason with the instruction; one sentence usually carries both.

5. Whose purpose does this sentence serve?

Does this sentence help the reader feel safe and informed about their care — or is it here to protect the organisation, for appearance, or for politics?

Legal and contractual content earns its place only when it serves the patient.

The patient guide exists for one purpose: to help the patient feel safe and informed. That purpose is the test for everything in it. Legal or contractual content is not banned — when a payment term, a cancellation rule, or a consent point genuinely helps the patient understand their situation and their choices, it belongs, stated plainly. What does not belong is legal or administrative text that serves the organisation rather than the patient: caveats added to look thorough, or wording shaped by organisational anxiety or need for completeness. That is theatre, and the patient pays for it in clarity.

When protective content does belong, give it its own clear place rather than threading it through the care text — patient information is about the patient, terms are about the agreement, and both can be clear, but not in the same paragraph. The privacy and data-protection dimension is not restated here: it is owned by the data work (Niclas's privacy-by-design / data-meta) and referenced, not duplicated.

Test: (PROPOSED) Does this sentence help the patient feel safe and informed — or is it here to protect us, for appearance, or for politics? If the latter, it doesn't belong in the patient's flow.

Anti-pattern: Protection-as-theatre. Legal caveats or politically-shaped wording smuggled into care text, present to reassure the organisation rather than inform the patient. Symptom: the reader can't tell help from terms, and the text serves a need that isn't theirs.

Evidence: See [[_examples/voice-examples]].

Implication: Keep the legal content that serves the patient's safety and understanding; give it its own place; refer the privacy rules to the data work rather than restating them.

5. Whose purpose does this sentence serve?

Legal and contractual content earns its place only when it serves the patient.

Test: Does this sentence help the patient feel safe and informed — or is it here to protect us, for appearance, or for politics? If the latter, it doesn't belong in the patient's flow.

Anti-pattern: Protection-as-theatre — legal or political wording smuggled into care text to reassure the organisation. Symptom: the reader can't tell help from terms.

Evidence: See [[_examples/voice-examples]].

Implication: Keep the legal content that serves the patient's safety and understanding; give it its own place; refer the privacy rules to the data work rather than restating them.

Contextual: how the voice adapts.

(verbatim) The character is constant. The register is contextual.

(verbatim) The Present Expert sounds fundamentally the same — whether it's a website, an SMS, a sign, or a presentation. But how we apply the principles depends on the situation. A patient before a cardiac assessment needs predictability and structure. A patient booking a health check-up out of curiosity needs affirmation and a focus on outcome. The voice is the same. The information architecture adapts.

(verbatim) See Emotional Mode as a Design Entry Point and Constant and Contextual for the framework. Baseline, Communication, and Physical document how the voice is applied in their respective contexts.

From patient information to patient guide

PROPOSED — concept relocated from the core guide (KG), drafted in English for your pass.

This is not a rename. It is a shift in mental model.

Patient information starts from the sender: we have something we need to convey, and the structure follows what the organisation needs to cover. A patient guide starts from the reader: you have something you need to navigate, and the structure follows the patient's journey, questions, and needs — in the order they arise.

Patient information	Patient guide
Organised by what Aleris needs to say	Organised by what the patient needs to know — and when
Covers every case and exception	Answers the most common questions clearly
Legal and clinical cover in the same text	Separates patient benefit from organisational protection
The patient reads and understands what applies	The patient knows what to do next

The shift changes more than tone — it changes structure, headings, and what belongs in a document at all.

Across audiences

PROPOSED — scaffold for Torfinn's voice pass. The structure and the analytical table are drafted; the framing prose and any audience-specific wording are yours.

[Author prompt: one or two sentences. The voice — the character and the five principles — holds across every audience Aleris addresses; the patient is the primary and hardest case, not the only one. What changes between audiences is vocabulary, what we lead with, and the emotional state we're meeting — not the register. Suggested framing to rewrite in your voice: "if it works for an anxious patient, it works for a procurement officer — the reader changes, the principle doesn't."]

The voice is constant; audience is a contextual axis, alongside channel and emotional mode (see [[constant-and-contextual]]). What shifts between audiences is the application, not the voice:

Audience	What shifts (the application, not the voice)
Patient	The primary case. Worry or curiosity modes; lead with their situation, what happens to them and the next step.
Next of kin	Lead with how they can help and what to expect, without centring the text away from the patient.
Care practitioners	Colleague-to-colleague inside the medical and health care field. Shared clinical vocabulary, not explained down. Lead with what's changed and what it means for their work.
Coworkers (internal)	"We". Respect for time and clarity; lead with the decision or action and why. No talking-down, no corporate padding.
Decision-makers, private	Peer-expert, not salesperson — the strongest version of the character. Lead with the value case and the evidence; persuasion is legitimate here (see boundary below).
Decision-makers, public	As above, with scrutiny and accountability front of mind. Lead with reliability, evidence, and how risk is handled.

[Author prompt: confirm or rewrite the right-hand column in your own words — these are analytical starting points, not brand phrasing.]

Two edges where it is more than vocabulary:

Internal audiences flip the pronoun. For coworkers and practitioners, "we" and "you" partly merge — they are inside Aleris. The principles hold, but the relationship is colleague-to-colleague. The Present Expert holds the same space for colleagues as for patients: patiently guiding and supporting, direct and truthful, pleasant but not pleasing.
Emotional mode is audience-specific — but don't invent modes that aren't there. Worry and curiosity are patient modes. The next of kin is better read through the jobs they're doing — using a digital service, arranging travel to and from the clinic, translating, filling in forms — than through an emotional state: "helplessness" is an edge case, not their defining mode, and casting them as helpless contradicts Principle 1 (they are a helper who acts). A public-sector or B2B buyer's mode is closer to scrutiny and accountability. [[emotional-modes]] currently describes only the patient modes.

One boundary the audience lens forces: the non-negotiable "no sales or marketing in care or clinical communication" is scoped to clinical and care contexts. Partner-facing and public-sector communication legitimately makes a value case — that is not the banned sales tone.

Across markets (culture and language)

The voice is constant; how it is expressed is calibrated per market, making this the fourth contextual axis for voice (see [[constant-and-contextual]]). Two things shift:

Language. Norway, Sweden, and Denmark have similar, but ultimately very different languages and cultures, The voice is realised natively in each, not translated word-for-word. The "no borrowed translations of idioms" (calque) rule generalises: no source-language idiom carried directly into another.
Culture. The norms for how directness, warmth, and formality are expressed and received differ between the three countries. For example, the same principle — "directness without distance" — may need a slightly different calibration to land as intended in each market.

Calibrating the Present Expert for each country requires native speakers to synthesize the voice.

Anti-pattern (global)

The character failures that aren't tied to a single principle. The hardest of these are promoted to the non-negotiables in [[constitutional/voice-is-the-present-expert]]; the rest are guidance.

Not superficially warm. The warmth sits in the structure — that we have thought through what the recipient needs — not in exclamation marks or affected phrases. "How lovely to hear from you!" isn't warmth. It's filler.

Not an affirming chatbot. Empty pleasantries ("Thank you for your question!", "Absolutely!") is an affordance in human to human converstions that is hollow and synthetic in LLMs. The Present Expert goes straight to the answer.

Not a disembodied voice that depersonalises. We never write about the patient in the third person ("the patient should avoid..."). We write to the patient: "avoid."

Not verbose and complete for the sake of completeness. Simplifying is not the same as omitting, but rather an integral part of effective and respectful communication.

Not inside-out. (verbatim) We don't begin with the clinic, the department, the process. We begin with the person reading and what they need.

The guide's reach (scope)

This voice owns the form of the communication — not the substance of the content. Audit reports, medical records, legal agreements, ISO documents, and clinical protocols have their own requirements and their own technical language. This voice can help with setting the Aleris tone for the communication surrounding material that is ruled by other conventions, but stops shy of when an expert is bound by certain formats and protocols related to their professional field.

For example: The voice guide governs how we communicate with patients, employees, and partners. It does not govern how a surgeon documents a procedure.

Origin

Harvest provenance: foundation/voice.md and its English working copy foundation/en-draft/voice.md; the brand-os voice workstream (planning/f4-voice-briefing.md, planning/voice-pass-1-merge-map.md, planning/voice-pass-2-prep.md). Re-slotted into the meta file grammar by the probe, 2026-05-31.

External lineage: (PROPOSED — confirm or correct the debts you actually drew on) Jobs-to-be-done (Christensen) — the principle-1 reframe toward a patient "looking to complete a job". Person-centred care and the patient-as-subject tradition. Plain-language and information-ordering practice (lead with the reader's question). Schön's problem-setting — the question-first framing of each principle mirrors aleris-meta/patterns/problem-framing-is-a-practice.md.

Open

The question leads. Five questions are proposed above. They are the load-bearing new content and need Torfinn's voice. Keep, sharpen, or replace each.
The English rendering of the identity. "Present Expert" is the current working choice for den nära experten; this file inherits it. Lock or revisit.
Where the evidence physically grows. _examples/voice-examples.md is the agreed home (chosen for ease of adding over time). Decide whether it stays one file or splits per principle as it grows.
The AI-systems block. Removed from this page to the viewport viewports/voice-for-ai-systems.md. Confirm the viewport owns it and the source no longer maintains it by hand.
Across audiences. New scaffold section added (2026-05-31). Needs your voice pass on the framing line, the per-audience "what shifts" column, and the three author-prompts. Depends on two upstream moves: naming audience as a contextual axis in [[constant-and-contextual]], and extending [[emotional-modes]] with audience-analogous modes (or a note that each audience has its own).
The two freshly-applied decisions (2026-06-07). The single test (Dec 1) and Principle 5 (Dec 2, reframed around purpose — serves-the-patient vs theatre/politics, privacy referred to the data work) are newly drafted and marked PROPOSED. These are the two pieces most in need of your voice — the structural decision is made; the wording is yours.
Relocated content to confirm. The definition is lifted from the EN translation draft, and the patient-information → patient-guide shift is drafted in English from the core guide. Confirm or rewrite both.
Quick reference. F4's "problem phrase → better phrase" table was not carried into this essay — its micro-copy-style rows belong in the patterns (Pass 5), and the per-principle anti-patterns already cover the reasoning. Decide whether a short reference block still earns a place here or lives only in the examples/patterns.

[[constitutional/voice-is-the-present-expert]] — the non-negotiable core this essay explains
[[_examples/voice-examples]] — the evidence this essay cites
[[constant-and-contextual]] — the reasoning tool the contextual section relies on
[[emotional-modes]] — what governs which register leads
[[viewports/voice-for-ai-systems]] — the agent adapter generated from this source