Sleep Culture

Boundary: the individual-in-a-sleep-culture — the person, their tracker, their work schedule, their chronotype, the stimulants/sedatives they use, and the social/employer pressures that price their rest. Out of scope: clinical sleep disorders (apnoea etc.) as medical conditions, which need clinical treatment, not this analysis.

Suspected central tension (to become a loop): the more we measure and optimise sleep, the more anxious we get about it, and anxiety is the one thing guaranteed to wreck sleep.

Try it yourself

Fix the system boundary in a sentence. Name the central tension you
already suspect (here: measuring sleep → anxiety → worse sleep). It
becomes the core loop.

---

Variables

1. Sleep tracking / quantification
2. Awareness of "sub-optimal" sleep
3. Sleep anxiety (orthosomnia)
4. Actual sleep quality
5. Daytime fatigue
6. Stimulant use (caffeine, etc.)
7. Sedative / sleep-aid use (melatonin, etc.)
8. Productivity/performance pressure
9. Work schedule rigidity (early-start norm)
10. Chronotype mismatch / social jetlag
11. Sleep-as-status / optimisation culture

Signed edges (selected)

• Sleep tracking +→ awareness of sub-optimal sleep
• Awareness of sub-optimal sleep +→ sleep anxiety
• Sleep anxiety −→ actual sleep quality
• Poor sleep quality +→ daytime fatigue
• Daytime fatigue +→ stimulant use
• Stimulant use −→ actual sleep quality (esp. late-day)
• Poor sleep +→ sedative use
• Sedative use +→ sleep tracking (checking if it "worked")
• Productivity pressure +→ optimisation culture
• Optimisation culture +→ sleep tracking
• Work schedule rigidity +→ chronotype mismatch
• Chronotype mismatch −→ actual sleep quality
• Poor sleep quality +→ awareness of sub-optimal sleep (closes the loop)

Named loops

R1 — The Orthosomnia Spiral (reinforcing, vicious). Tracking → awareness of imperfection → anxiety → worse sleep → (worse data) → more tracking and more anxiety. The tool meant to help is inside the loop that harms. (1)

R2 — The Stimulant–Sedative Seesaw (reinforcing, vicious). Poor sleep → daytime fatigue → stimulants → worse sleep that night → sedatives → groggy day → more stimulants. A chemical oscillation that degrades the underlying sleep.

R3 — The Optimisation Treadmill (reinforcing, vicious). Productivity pressure → sleep reframed as a performance input → optimise/track it → status attached to "good sleep numbers" → more pressure. Sleep stops being rest and becomes a KPI.

B1 — Exhaustion Forces Collapse (balancing, grim). Eventually the body crashes and sleeps. A balancing loop — but it "stabilises" through breakdown, not health.

B2 — Chronotype Mismatch (structural drag). Rigid early-start schedules −→ sleep quality for late chronotypes (social jetlag). Not a loop the individual can close — it's imposed by institutional schedules. This is the structural variable the individual-level loops can't fix.

Reading the diagram

The system is held in a bad place by three reinforcing vicious loops (R1, R2, R3), "stabilised" only by grim B1 (collapse), with B2 (chronotype mismatch) as an exogenous structural pressure that individual behaviour can't touch. The finding: the individual is trapped in loops partly created by the tools and culture sold to help them — and the one genuinely structural lever (work-schedule rigidity / chronotype) sits outside their control entirely.

Try it yourself

Build a sleep CLD: 8–12 variables, signed edges, named R/B loops.
Identify which loops the individual is trapped inside, and which
variable is *exogenous* (imposed structurally — here, work-schedule
rigidity). Write the "reading": what holds the system in a bad place?

---

On Meadows's ladder, weakest to strongest: (4)

• Weak (parameters): better trackers, more accurate sleep scores. Stays inside R1 — often makes orthosomnia worse.
• Medium (feedback/information): CBT-I (cognitive behavioural therapy for insomnia), which directly targets the anxiety edge in R1; "trackers that hide the score" / relaxation-first design. (1)
• High (rules): chronotype-aware work schedules; flexible/late start times; banning the use of sleep data in employment/insurance. This addresses B2 (the structural one) and pre-empts the dystopia.
• Highest (paradigm): re-decoupling sleep from performance — restoring rest as a biological right and a non-productive good, not an optimisable input. This drains R3 (the optimisation treadmill) at the source.

The CLD shows why "buy a better sleep tracker" disappoints: it's a parameter tweak inside the very loop (R1) that's hurting you. The real leverage is the paradigm (sleep ≠ performance) and the rule (chronotype-aware schedules; data firewalls).

Try it yourself

Place 5–7 sleep interventions on Meadows's ladder. For each, name which
loop it acts on. Notice how many "solutions" (better trackers) sit
inside the vicious loop they claim to fix.

---

We cross into design. The CLD's darkest possibility is R3 + the loss of the data firewall: sleep data becoming performance-and-insurance-relevant. We build into a 2040 where that happened, and draft the artifact. Constructed — fictional.

---

MERIDIAN GROUP — Workforce Wellbeing

Sleep & Recovery Performance Summary — Q1 2040

Employee: R. Calder · ID: MG-22841 · Role: Logistics Coordinator (rotating shift) Device: employer-issued Recovery Band (consent on file, 2038)

Metric	You	Cohort median	Status
Mean sleep duration	6h 02m	6h 48m	⚠ Below
Sleep consistency score	61	78	⚠ Below
Recovery index	64	80	⚠ Below
Caffeine-window flags	14	5	⚠ High

Recovery Tier this quarter: AMBER.

Employees in AMBER for two consecutive quarters are enrolled in the Recovery Support Pathway (mandatory). RED tier may affect eligibility for safety-critical duties and the wellbeing premium rebate.

Note

Your chronotype assessment (2038) indicates a late circadian preference. Your current shift pattern (05:30 starts) is not aligned. A chronotype-aligned roster may be requested via your team lead, subject to operational need. Requests are not guaranteed.

Your Recovery data is shared with: your team lead (summary tier only), Meridian Wellbeing, and (in aggregate) your health-plan provider.

---

Why this artifact pulls weight. It never says anything cruel; it's a wellbeing report. The horror is in the plausibility:

• "Recovery Tier: AMBER" / "may affect eligibility for safety-critical duties" — sleep, the most private biological function, is now a tiered performance category with employment consequences. R3 institutionalised.
• The chronotype note — the system knows Calder is a late chronotype on a 05:30 roster (the B2 structural mismatch) and offers a realignment "subject to operational need… not guaranteed." It diagnoses the structural cause and declines to fix it.
• The data-sharing line — the firewall is gone; sleep data flows to employer and health plan.

A reader argues not about sleep, but about a world that scores rest. That's the conversation 2026 isn't having as wearables creep into workplace wellness programs.

Try it yourself

Draft a Design Fiction artifact from your CLD's darkest loop. Make it a
benign-sounding "wellbeing" document. Include: a tiering/scoring
mechanic with consequences; a line where the system diagnoses the
structural cause and declines to fix it; a data-sharing disclosure.
Bureaucratic register only.

---

Object from the World. The personal object this system produces: Calder's Recovery Band — a slim matte wristband, no screen (the score lives in the app), with a single amber LED that others at work have learned to read. Colleagues glance at each other's wrists. A green band is a quiet flex; an amber one invites unsolicited advice. The object made sleep visible on the body — and therefore social, competitive, and slightly shaming.

Bodystorming. A 10-minute enacted scene: Monday stand-up, 2040. Roles:

• Calder (amber band, 05:30 start, late chronotype, tired).
• A team lead who "just wants to check in about your Recovery Tier," kindly.
• A green-band colleague who shares an unsolicited optimisation tip.
• A new hire who hasn't consented to the band yet and is deciding whether to.

Prompts to enact (not discuss): Where does Calder put the amber wrist? What does the new hire's body do when they see the others compare bands? Where does the team lead stand to "check in"?

Bodystorming surfaces what the form can't: that the body-visibility of the band turns a private function into a workplace status hierarchy — the shaming is physical, not textual.

Try it yourself

Describe the personal Object your artifact's system produces — what it's
made of, what it reveals on the body. Then bodystorm a 10-min scene
where the object becomes social. Use body/movement prompts, not
dialogue. Debrief on what the body knew that the document didn't.

---

• Participants: 6 — a shift worker, an HR/wellbeing manager, a sleep scientist, a privacy lawyer, a late-chronotype "night owl," a wearable designer.
• Setup: Each gets the Sleep & Recovery Summary with their own (fictional) tier; some get AMBER, some GREEN, one gets RED. Wristbands (props) with matching LEDs.
• Run: 10 min — read your report, put on your band. 10 min — a mock "stand-up" where the facilitator (team lead) checks in on tiers. 15 min — debate: what does this get right that current wellbeing programs claim to want? Where's the line it crosses? 10 min reveal & debrief.
• Looking for: How RED-tier participants feel being visibly marked; whether GREEN participants enjoy it (the status pull is the point); whether the chronotype "request not guaranteed" clause angers the night-owl most. The privacy lawyer's reaction to the data-sharing line is the legal canary.
• Harm note: Sleep struggles and shift-work exhaustion are real and present for many; brief and offer an out.

Try it yourself

Design a 45-min prototype. Give participants different tiers (incl. a
RED). Use the physical band-prop so the visibility is embodied. Two
facilitator questions. A reveal. Watch who enjoys GREEN and who's shamed
by AMBER/RED — the status dynamic is the finding.

---

1. What did the cascade surface that the CLD didn't? — That the body-visible score (the band) turns R3's optimisation culture into a workplace status hierarchy, and that the chronotype clause (B2) is where the system's bad faith is clearest: it knows the structural cause and won't fix it.
2. What's the counter-world? — Design the opposite artifact: a 2040 where chronotype is a protected characteristic and sleep data is firewalled from employment by law — a "chronotype accommodation order" rather than a "recovery tier." Drafting it tests the dystopia.
3. Where did the dystopia overreach? — It assumes workers consent to employer bands. The new-hire role (deciding whether to consent) is where the world could fork.
4. What 2026 action does this surface? — Firewall sleep/wearable data from employment and insurance now; treat chronotype mismatch as a real occupational-health issue; design trackers that follow the CBT-I logic (hide the score) rather than feeding R1.
5. What does this refuse? — To tell you how to sleep better (that framing is the trap). To treat sleep as a performance metric.

Try it yourself

Reflect in <60 words each: what did the cascade surface that the CLD
didn't; what's the counter-artifact; where did the dystopia overreach;
what 2026 action follows; what does this refuse to do?

---