The case that has been open for months

The problem it solves

The case has been open for months, and everyone in the company knows who it is about. A person whose work or whose conduct has been generating friction for a long time, about whom everyone holds a settled opinion and nobody holds a file. The subject comes up in hallways, gets postponed in meetings, and returns every time the team complains.

The waiting has its own logic. The supervisor does not want an open conflict, fears that a badly handled conversation will make things worse, and every week that passes without action turns what is tolerated into what is normal. Meanwhile the rest of the team pays for it: the people who do their jobs absorb what the other person does not, learn that falling short carries no consequence, and the best of them, who also have the most options, start looking elsewhere. By the time someone decides to intervene, the person has spent months receiving a clear signal that this was acceptable, and the intervention arrives looking like arbitrary punishment.

Then comes the least comfortable part. A share of these cases are not problems with a person: they are management problems carrying a person's name. Expectations that were never stated, a role that changed while its description did not, two bosses asking for different things, or a team where the same behavior is tolerated depending on who does it.

What it covers

The workshop works the long case rather than the isolated incident. An incident gets corrected on the spot and a pattern calls for a conversation, but a case, which is a pattern that has already outlived several conversations, calls for method. It begins with diagnosis, because what to do next depends entirely on which problem you have: a gap in skill, a gap in clarity, a gap in willingness, or a conduct matter that does not belong in an improvement plan at all. And before anything is done to the person, the session asks which part of the problem management itself produced, because an improvement plan built on an expectation nobody ever communicated is unfair, and it does not work either.

From there the session follows the sequence over time: the first conversation and the verifiable agreement it has to leave behind, the record of what happened and when, the review that was agreed, and the escalation when that review shows no change. Escalation is also worked across supervisors, since what one boss tolerates and another sanctions has stopped being a standard. Participants bring real cases without names, and the group orders them with the same method until each person knows their next concrete step and the date it happens. On their own case, each participant writes the diagnosis, assembles the timeline of what is on record and what is missing, and rehearses in pairs how the next conversation opens.

One boundary is drawn precisely and out loud. What the session covers is management practice: how to diagnose, how to hold the conversation, how to document and how to follow through. The decision to separate someone, the drafting of documents with legal effect, and any situation involving serious allegations or retaliation belong with your legal counsel. The session teaches you to recognize that point before crossing it rather than afterwards.

By the end, each participant has the case classified, the next conversation prepared along with the agreement that has to end up documented, a timeline that separates what is on record from what is not, and an escalation criterion with review dates and an owner at every step. Roles that changed without being redefined, bosses who contradict each other and standards that bend depending on who breaks them cannot be fixed one case at a time: they are organizational decisions, and ALUD takes them up through its People engine.

What participants learn

• Tell apart a problem of skill, of clarity, of willingness or of conduct.
• Examine which part of the problem management itself produced before acting on the person.
• Hold the first conversation so that it leaves a verifiable agreement and a date.
• Record observable facts with the precision a decision taken months later will demand.
• Identify when a case exceeds management practice and belongs with legal counsel.

Agenda

1. 01Incident, pattern and case: three different things, handled differently
2. 02Diagnosis: skill, clarity, willingness or conduct
3. 03Which part of the problem the organization created, not the person
4. 04The first conversation: a verifiable agreement and a review date
5. 05What goes on the record: what was observed, when, and what was agreed
6. 06Progressive escalation and consistency between supervisors
7. 07What an open case does to everyone else on the team
8. 08Where management practice ends and legal counsel begins

What the organization leaves with

• A written diagnosis of the case you brought, with its classification.
• A script for the next conversation, including the agreement that has to end up in writing.
• A timeline of the case showing what is on record and what is missing.
• An escalation criterion with review dates and an owner for each step.