Skip to main content
sociable systems.
Case Studies

Proof of method, without pretending every story is public.

This page is the growing proof layer for Sociable Systems: verified cases when they can be shared, anonymised examples where confidentiality matters, and clearly labelled scenarios where the point is to show the method at work.

Proof rule

If it is not verified, it gets labelled as a scenario. Trust depends on that line.

Plain-language summary
Case studies show the method at work in verified engagements, anonymised engagements, or carefully labelled scenarios. The label tells you which is which. The point is to make the method legible without overclaiming what is actually publishable.
Verifiedreal + clearedAnonymisedreal + blurredCompositepatternedIllustrativehypotheticalHIGHER PUBLICATION CONFIDENCEMETHOD SHOWN, NO CLIENT CLAIMED

Verified case

A real engagement with cleared details, publishable outcomes, and confidentiality boundaries agreed.

Anonymised case

A real engagement with identifying details removed or blurred to protect clients, workers, and affected communities.

Composite scenario

A pattern drawn from multiple contexts, useful for showing the method without implying a single client result.

Illustrative scenario

A hypothetical example used to explain how the method works before public case material is available.

Proof objects

What proof can look like before client names are public.

A buyer does not always need a logo wall. Often they need to see the quality of the artifact: what gets named, what gets preserved, and what decision the work makes easier.

Field examples

The kinds of problems the method is built to handle.

Where a card reads Anonymised, it is a real engagement with identifying details blurred. The rest are representative patterns rather than published client claims, showing what the work looks for and what a fuller case study will document once details are cleared.

Anonymised advisory engagement
Anonymised real

A pledge that locked the obvious exits and left the quiet ones open

A small, sovereignty-minded firm was days from publishing a voluntary commitment limiting how it could ever grow into a dominant position. The draft closed the obvious exits and left the quiet ones open: who convenes, and who decides what 'compliant' means once the word is tested. A bounded first-pass audit read each clause for claim, signal, compression, and authority, separating the vectors already closed from those left to discretion. The firm folded the findings in before legal review, then commissioned a second pass.

Systems Briefing / Advisory ->
Anonymised watchdog engagement
Anonymised real

A tool that measured how people were doing, and quietly decided who got to know

A system was being built to read the human state of a workforce upstream, flagging strain before it surfaced as a complaint or a resignation. The promise is care arriving early. The exposure is who the reading serves once it exists: a wellbeing signal becomes a management signal the moment it is scored, and the person measured rarely controls what their own state now authorises. The work mapped where consent, escalation, ownership of the signal, and the right to be read at all had been assumed rather than designed, and where a human still had to stand between the score and the decision it invited.

Watchdog / Advisory ->
Representative advisory scenario
Composite

A dashboard that made field reality look cleaner than it was

An AI-assisted monitoring workflow can make qualitative field notes appear resolved because the summary sounds coherent. The advisory move is to trace what the dashboard preserves, what it drops, and where human review must re-enter before the summary becomes institutional fact.

Systems Briefing / Advisory ->
Representative GrieVoice scenario
Composite

A reporting channel where silence was being misread as safety

Low complaint volume can mean low harm, but it can also mean fear, language barriers, poor access, or distrust. GrieVoice-style pilots test whether the channel itself is capable of hearing the people most affected by the system.

GrieVoice / Watchdog ->
Representative training scenario
Illustrative

A team asked to trust AI summaries without shared review habits

When AI enters audit, ESG, social evidence, or reporting work, teams need more than tool confidence. H∞P Training builds shared language for evidence trails, stop-work authority, escalation, and the judgment points that must stay human.

H∞P Training ->
What a full case study will include

Context, risk, intervention, outcome, and what can safely be said.

The system or workflow under pressure.
The human consequence at risk of being flattened.
The advisory, training, GrieVoice, or Watchdog intervention used.
The artefact or decision support produced.
What changed in evidence, escalation, authority, or review.
What remains confidential, uncertain, or not yet publishable.