Designing for wellbeing, not engagement

Sweatty is the methodology case study in this set — different from the other six because there’s no live shipped product to point at. The work is a versioned design system (v4.0) and a 22-principle ethical-design framework for wellbeing technology. The artefact is the system; the case study is the discipline of designing for wellbeing rather than engagement.

Why methodology counts as a case study

Most “case studies” surface code and outcomes. This one surfaces a refusal.

Sweatty’s brief is wellbeing-tech — software whose stated purpose is to help users feel better, sleep better, move more, be more present. The dominant pattern in that category in 2026 is dark wellbeing-tech: apps that promise wellbeing while monetising attention via streak mechanics, notification floods, social comparison, and rewards optimised for retention rather than user benefit. Strava-style.

Sweatty refused that pattern from the brief level. The framework codifies the refusal. Sub-points the design system enforces:

• No streak-based shame mechanics
• No social-comparison leaderboards by default
• No “your friends are using X” notification patterns
• No dark-mode-only at night (light-mode-by-day discipline)
• No “wake the user up” engagement loops
• No infinite scroll on content surfaces
• No “would you like to enable notifications” deferred prompts that resurface after dismissal

These are negative requirements — what the product must not do. The design system encodes them as token-level rules: certain animations are forbidden, certain notification cadences are blocked at the component layer, certain visual reward patterns aren’t in the library.

What’s in the artefact set

Two source documents anchor the case study:

• Sweatty Design System v4.0 — the fourth major iteration. The version number is the proof of investment: this is multi-year methodology work, not a one-pass style guide. Each version is documented; the changelog between v3 and v4 was the point at which the ethical-design principles became enforceable via component constraints rather than just aspirational in prose.

• 22 Ethical Design — Wellbeing — a framework document with associated media. The 22 principles cover dark patterns to avoid, light patterns to prefer, and a decision tree for ambiguous cases (“when is a streak okay?”, “when is social comparison constructive vs harmful?”).

The deliverable shape is unusual but defensible: many wellbeing-tech products would benefit from importing the principle set wholesale, regardless of their actual UI framework.

Why a design system needs to be at v4.0

If you’re designing for wellbeing seriously, you have to test your principles against real product decisions repeatedly. Each test surfaces edge cases the previous version didn’t anticipate.

A naive design system says “use the right colours, use the right typography, follow the patterns.” That’s a v1.0 statement. By v4.0 you have:

• Component-level constraints encoded in code (button variants that can’t express dark patterns)
• Animation tokens that bound the system’s sense of “delight” (no celebration explosions; no haptic pump)
• Notification primitives that respect cadence rules at the platform layer (you can’t send the 5th push of the day even if you try)
• A visual language that signals calm by default (low-saturation palette, generous whitespace, slow animations)
• Documentation that records why each constraint exists, not just that it exists

The “v4.0” label is shorthand for “this has been tested against real product pressure for years.”

What this signals for UK Web Marketing clients

If you’re building anything in the wellbeing or healthcare-adjacent space — a fitness studio booking site, a yoga teacher’s directory, a mental-health practice’s enquiry flow — the Sweatty methodology is the lens worth borrowing.

Concrete things UK Web Marketing imports from the framework:

1. No streak-shame copy. The /clinics, /schools, and /accountants pillar pages don’t use “365 days of compliance” or “don’t break your streak” framing.
2. No social-proof carousels that imply other users are watching. “As featured in” logo strips are fine; “127 people booked this week” counters aren’t.
3. No dark patterns in the form flow. The contact, audit, and lead-magnet forms have a single primary action, no pre-checked consent boxes, no “are you sure you want to leave?” exit-intent dialogs, no “limited time” countdown timers.
4. Calm by default. The brand palette uses violet + ink + cream + soft amber — saturated only where attention is genuinely warranted. The OG images for blog articles match the same restraint.

If those discipline choices are the kind of work you want — particularly if you’re in wellbeing, mental health, fertility, paediatric care, or any sector where engagement-optimised dark patterns would be ethically wrong — WhatsApp me. Same developer, same pricing tiers, same Sweatty-informed editorial discipline.

What this case study isn’t

It isn’t a story about a launched consumer product with growth-chart screenshots. There is no MAU number, no revenue figure, no “we hit profitability in month 6” milestone. The work is upstream of any of that — methodology that could be applied to a wellbeing product, documented at v4.0 maturity.

That’s a case study worth publishing because it answers a different question than “what does your code look like?” It answers: what does your design discipline look like when nobody’s watching?

The answer is on file at v4.0.