Active Redundant Convocation Syndrome, presenting atypically

Classification MM-001.4

Presenting complaint: A meeting that could have been an email
Onset: Sunday 20:00, the dread hour
History: Happens most weeks
Severity: 4 of 10, Urgent
Aggravating factors: Standup · A calendar with no gaps

Clinical note

Patient reports 60 minutes of their finite life converted into a calendar entry. No agenda was circulated. None existed.

Recurs most weeks. Patient has developed a tolerance that should not be mistaken for recovery. Aggravation is entirely work-sourced, led by standup. Contained, at least, to one building.

Requires monitoring. Do not leave patient alone with their inbox.

Prescription

Look at the wall behind the camera, not at your own face. Nobody should watch themselves work.
Decline one (1) meeting this week. Any meeting. Chosen at random if necessary.
Do the fifteen-minute version of the repair. Fifteen minutes, then stop.

Follow-up

Follow up once you have told somebody. Not before.

Dr. O. Mbeki

Consultant in Recursive Convening

Book your own visit

Save image

Preview of the story card for this note — The story card, as the buttons above save it. Both cards are drawn from the note itself. The link is the whole record. .

After your visit

Ref 7EDHWF4 · Retain for your records

Contribute to the audit

The published statistics only describe the generator, because nothing anybody answers is kept. You can change that for this one note.

What exactly gets sent

Sent, and nothing else:

the complaint you ticked, and any others you added
when it started, and how often it happens
your severity rating
the aggravating factors you ticked
which ISO week it is, and no finer than the week

Not sent:

anything you typed in the last box: not in this row, either way
this note’s reference in readable form, or the link to it
your browser, your chart, or any account or session
nothing that lets one row be tied to another, or to you

Kept as one row holding those six answers together, which is what makes it possible to ask whether the people who rate a ten tick different factors from the people who rate a three. Nothing in the row identifies you and nothing links it to any other row.

The row is keyed by a one-way fingerprint of this note’s reference, which is what stops it being counted twice. The reference itself is not stored, and your address reaches the server the way it does for any request on the internet; we simply do not write it down. Anyone holding this link can recompute that key, which is why this can be undone.

Name the culpritOptional

Companies only, never colleagues. A name reaches the public board once 8 people have named it independently AND it matches an organisation in the global business register, so a person’s name cannot get there. It is never shown as your row.

Pressing it is the consent.