Three Interventions That Change
What Gets Written Down.

What happens once an interpretation is written down

An interpretation of a person stops being one person’s read the moment it is written into a record, and becomes a fact that other people act on. Once that interpretation is written, it starts being treated as fact despite what might have actually happened. This is something that many Neurodivergents have experienced directly, affecting their ability to obtain jobs, keep jobs, experience career progression, and fundamentally receive dignity in organizations. So every cycle you run without applying the interpretation interventions puts more interpretations in written records that turn into significant consequential actions that impact lives.

Your organization already trains people not to do this, and the training does not hold, because it asks a leader to keep the split between observation and evaluation in their own head while the form in front of them asks only for a rating and a paragraph.

My Cognitive Translation Protocol sets nine structural interventions against the six failure dimensions, in three lanes. An intervention is a change to an artifact, which means the form, the meeting record, the agenda, the field that someone has to fill in. This is the interpretation lane. All three of these changes are to artifacts you already own, and any one of them can be made inside a single review cycle.

Interpretation guardrails change what the form asks first

Open the last set of performance reviews you signed off on and read the comments rather than the ratings. You are likely to find sentences that look like descriptions but are really conclusions. For example, struggles to influence senior stakeholders, comes across as defensive when challenged, needs more executive presence. None of those comments tells you what the person said, what they were asked, or what happened next, and every one of those comments will be read by the next person who opens the performance file as though it were a record of a factual event. The form setup itself invites those sentences, because the form asked for an assessment but did not provide a way to separate the observation from the assessment that was based on it.

The guardrail is a field. It sits before the assessment field and it asks what was said and done. In a talent or calibration meeting it is the rule that a claim about a person does not go into the record until the person making the claim has said what they observed. What it requires is that the observation and the interpretation are kept in separate places, so that someone reading the file six months later can see them as two separate things and decide whether the interpretation follows from the observation.

Building this costs you very little and running it is nearly the same amount of time you spend today. The field already exists on most review platforms as an open comment box, so the work is in what you require of that field and what you decline to accept while that field is empty. The expense sits in the first two review cycles, where people write “seemed disengaged” in the observation field and have to be sent back to write what they actually saw and heard.

A direct answer then stops being recorded as reluctance, because the answer sits on the page next to the conclusion drawn from it and the distance between the two is visible to whoever opens the file. The same field takes the state of mind out of the record, because “came across as frustrated” does not survive a line that asks what was said. And when an instruction has to go into the observation field exactly as it was given, that instruction stops arriving in the file as the other person’s failure to follow it.

Context equalization changes what the agenda does first

Think about the last decision meeting where the discussion got worse the longer it went on. A proposal is presented, and around the table three people have read the churn analysis from six weeks ago and four people have not, and nobody says which group they are in. The three evaluate the proposal against the churn numbers and the four evaluate the proposal against the revenue plan they last saw, and every objection each group raises is correct from where that group is sitting. What the room experiences is disagreement about the proposal, and what is actually happening is that half the exchange is people reasoning from different starting facts. The agenda created that gap, because the agenda went straight to the proposal without establishing what the room already knew.

The change is a written baseline that exists before the evaluation starts and that everyone has actually read. Amazon’s six-page narrative memo and the silent reading period at the top of the meeting is the version of this most leaders have heard of, and what makes it work is the shared baseline rather than the prose. You do not need six pages. What you need is a block at the top of the material that states what is known, what is assumed, and what has changed since the last time this group looked at the question, and a first agenda item that confirms that block rather than presenting it.

This one takes real effort, and that effort is why most rooms skip it. Someone has to own writing the context block, and the first few meetings run long because the gaps surface out loud instead of staying in people’s heads. Those meetings were already running long, and the time was going into an argument that had a fact gap underneath it.

Everyone then evaluates against the same written baseline, so the version of the situation in your head and the version that reaches the room stop being two different things. The person who works literally gets the starting facts in writing rather than having to assemble those facts from tone and hallway history. And a challenge that comes out of a fact gap stops being recorded as resistance, because the baseline is on the page and anyone in the room can see which fact the challenge is about.

Outcome-based evaluation changes what the review scores

Take the same review file and look for the field that records what the person was right about. In most forms there is not one. Your organization can tell you that a director did not carry the room in March, and it cannot tell you that she was the only person in that room who said the migration date would not hold, and that it did not hold. The form has a place for the delivery and no place for the result, so the delivery is what gets scored and the result never enters the record at all.

The change is a field that asks what this person’s calls turned out to be worth, filled in with the calls, the dates, and what happened after them. The reads that were right and were acted on. The reads that were right and were not acted on. The reads that were wrong. It sits alongside the competency ratings rather than replacing them, because how someone works with other people is real information and you are not giving that up.

This is the most expensive of the three, and the expense is in keeping a record through the year rather than in money. Someone has to write the call down when it is made, which means the artifact is a running record as well as the review form. Most organizations already have somewhere that record could live, in the decision log or the meeting minutes, and the work is deciding that a named person’s read goes into it with their name attached.

A read that turned out to be right then stops being invisible, because something in your organization holds it. A person’s worth stops being estimated from how they present, because there is now something else on the page to weigh it against. And the reads you were getting for free from people your reviews were quietly marking down stop walking out of the building with them.

The Operating Brief: change one artifact

Why this works, and where it comes from

A version of this is something you have already been taught. Think back to feedback workshops you have taken in your career and commission now for your teams. Marshall Rosenberg’s Nonviolent Communication and the Center for Creative Leadership’s situation, behavior, impact both start in the same place, which is separating what you observed from any evaluation you may have made.

This separation is critical and worth every penny of these trainings. An observation is something that can be checked, whereas an evaluation is subjective and cannot be checked without context. An evaluation assumes verified context, so without making this split explicit, an evaluation is an unsupported argument about who someone is. Most leaders who have truly put in the effort to turn this into practice can name how conversations went better because they held that line.

So what about when the training ends? Rosenberg built a great personal discipline, but it is exactly that, a personal discipline that a leader under pressure needs to hold in their own head where others in the room may not have had the training or have not learned how to apply it. This creates an organization where some leaders are good at observation vs. evaluation and others may not be and it relies on those leaders always having the cognitive capacity to exercise that in their own minds and influence everyone else in the organization. The organizational benefit as a result is uneven and hard to trace.

This is where Schein’s cultural pyramid we talked about last week comes into play. Culture is measured by the alignment between artifacts, espoused values, and tacit assumptions, and you can redesign the artifact layer and use it to train espoused values and tacit assumptions explicitly. You already do this by training the observation vs. evaluation split at the artifact and espoused values layers, but the tacit assumptions remain unspecified. But how does this translate to your situational feedback as a leader, including up to writing performance reviews? The reality is the form itself is set up to rate an individual and attribute an evaluation to them, and so the incentive to carry the training to organizational design already faces an artifact barrier. That artifact barrier is the design problem, and it is what the three changes above are aimed at.