On why workplace processes fail, and where the case usually lives.
We tell ourselves stories about process.
An employer tells herself that because the letter was correctly drafted, the process it describes must have been correctly followed. An employee tells himself that because the letter arrived on firm letterhead with statutory references, the institution behind it must have been thorough. A human resources manager tells herself that because the steps appear in the file in the right order, they must have occurred in that order.
These are stories. They are the stories people tell in order to proceed: to sign the letter, to file the document, to move on.
They are not, in my experience, reliable descriptions of what happened.
···
The employer was referred to me by his accountant. He was a reasonable man. He had dismissed an employee and believed the process had been properly conducted. The letter was correctly drafted. The statutory references were accurate. The tone was appropriate.
Who conducted the investigation?
The operations manager.
Who made the final decision?
The operations manager.
The employer did not see the problem. He was not evasive or defensive. He simply did not see it.
When the same person investigates an allegation, evaluates the evidence and makes the final decision, the risk is not only one of appearances. The distinction between testing the evidence and defending an emerging view can collapse. By the time the employee is invited to respond, the decision-maker may already have travelled too far down the path to hear the answer freshly.
In this case, the structure of the process made that risk visible.
The letter was fine. What the letter described had not occurred in the way the letter described it.
We had approximately three weeks. We did not rewrite the letter. We rebuilt what was underneath it.
···
There is always a gap.
Between what a formal document claims and what the system behind it can actually support. Between the policy as written and the policy as followed. Between the process that was promised and the process that was experienced. Between what an organisation says it does and what it does on an ordinary Tuesday, when the pressure is real and no one is watching.
The gap is not a technicality. It is not a loophole. It is the distance between the story an organisation tells about itself and what the organisation actually does. That distance is where many employment disputes begin. It is also where many of them become possible to resolve, once the gap has been found, measured and placed on the table in a way that neither side can explain away.
Not every gap is a case. Part of the work is telling the difference.
What happens next depends on which side of the table is looking at it.
For an employer, the gap is something to identify and correct before it hardens into a dispute. For an employee, the gap may be the case itself: the distance between what was supposed to happen and what did.
The same gap. Two uses. That is the work.
···
The letter arrives on a Tuesday morning.
It is formal. It carries statutory references, procedural language, the particular weight of institutional correspondence. It was reviewed before it was sent. The language implies thoroughness. The letterhead implies resources. The overall effect is to convey that the matter has been carefully considered and that the institution is prepared to defend its position.
Most people read a letter like that and feel the ground shift. They feel the weight and assume the weight is structural, that the process behind the letter is as sound as the language suggests.
This is worth examining.
The formality of the language does not tell you whether the person assessing the response remained genuinely open to it. The statutory references do not tell you whether the employee’s response was treated as an input capable of changing the outcome. The letterhead does not tell you whether the documentation reflects the real sequence of events or a narrative assembled afterwards to make the sequence appear more coherent than it was.
None of the things that make a letter feel heavy are the things that make a process sound.
···
Some processes are built backwards.
Sometimes the documentation is assembled after the decision. Sometimes a performance improvement plan is calibrated to produce a particular failure. Sometimes a restructure is designed around one position held by one person. The examples differ, but the structure is recognisable: evidence is organised around an outcome instead of the outcome being reached from the evidence.
Not all of this is deliberate. A conclusion that arrives early can organise everything that follows it, whether or not anyone decided that it should.
A process built that way may still look immaculate. That is part of the problem. A genuinely open process has room for mess: uncertainty, disagreement, information that does not fit neatly, and moments when the decision could still go either way.
Backward construction has a different quality. Sometimes the neatness is the tell. The process is not testing a conclusion. It is supporting one.
A process that can affect someone’s livelihood without genuine openness to the answer is not merely vulnerable as procedure. It has stopped doing the work a fair process exists to do.
···
The question underneath all of this is simple: how does a structural failure become visible when the document itself is sound?
My legal formation began in Colombia, in a civil-law tradition. What stayed with me from that training was an architectural way of reading. Before approaching a case, you learn to look for the framework underneath it: the principles carrying the weight, the places where elements connect, and the places where they should connect but do not.
That habit shapes how I read legal and institutional documents.
An investigation report, read this way, is not simply a narrative about what happened. It is an architecture. The question is not whether it is well written. The question is whether the structure underneath the writing holds.
That reading also changes the correspondence that follows. There is little value in matching formality with more formality, or volume with more volume. The structural failure is identified, placed against the evidence, and described with enough specificity that it can be tested.
The person receiving it does not simply see an opposing position. They see their own position reflected back, including the part of the structure that does not hold.
What follows is usually a different kind of conversation.
···
There is a thing that happens when you spend years moving between sides of the same table.
From the employer’s side, a process can look like a sequence of reasonable decisions made under pressure. The investigation was conducted. The meetings were held. The documentation was completed. The letter was sent. Each step feels, from inside the organisation, as if it happened in good faith and in the right order.
From the employee’s side, different things become visible. The step that was compressed because someone was busy. The meeting where the outcome was already evident in the room before anyone spoke. The document that appeared in the file at a moment that does not survive examination. The response that was received, filed and given no discernible weight.
Working from both sides changes what you notice. The failures recur. They appear in organisations that otherwise have little in common.
Once you learn to look there, the patterns are not particularly hidden. They are simply difficult to see from one side of the table alone.
···
The gap is always there.
Sometimes it needs correcting quietly, before it becomes the foundation of someone else’s case. Sometimes it needs to be placed on the table, clearly and without drama, so that everyone can see where things actually stand.
The document may be immaculate. The question is whether the system underneath it can support what the document claims.
That is where I look first.
Provenance
Originally published on avaneal.co.nz. The original publication date could not be recovered from the surviving public record. Revised for By Ava in September 2026.