Set Context for People
the Way You Already Do for AI.

Sometime this week, you are going to type a question into AI, read the answer, and think: that is not what I needed.

And I want you to watch what you do next. You look at your own question. You realize you left out the contract terms, or the history, or the number that makes the whole thing make sense. You add the context and you ask again. The second answer is better. The whole correction takes a minute, it happens entirely on your own end, and it carries no verdict on anyone.

That small habit is the subject of this episode. Because that habit is one half of an exchange you run every day, and the other half of it runs at your leadership table. At the table, the same exchange has a rule you never agreed to out loud. With AI, when the answer is thin, you fix the context you supplied. With people, when the answer is thin, the person who gave it gets a note in the record. Understanding each other is work. And right now, at your table, one person is paying for all of it.

Let me show you what that looks like on an ordinary morning, because you have sat in this meeting.

Your leadership team is deciding whether to fold two service teams into one. There is a hard stop, because the answer goes to the operating review that afternoon. Most of the people in the room walked in expecting to approve the merge. Your operations lead goes first, and their answer takes under a minute. They say the work overlaps, one team can carry the load, and the handoff pain will pass. Everyone follows it, because everyone already knows the background it rests on. And most of them already agreed with it before the meeting started.

Then your escalations lead speaks. They see the same merge differently. They know the two teams do not mean the same thing when they mark a ticket resolved. They know what a merged queue does, in its first weeks, to the accounts that are already behind. But none of that means anything until they explain how each queue actually works. So they start explaining. And about ninety seconds in, someone asks for the executive summary.

They give one. And without the setup underneath it, it sounds like a maybe. The team notes it, the hard stop arrives, and the escalations lead says the rest will come in writing. The write-up lands the next morning. It is thorough, it is clear, and the decision went out the afternoon before.

Now, here is the part I want you to hold on to. Nobody in that room did anything wrong. Asking for the executive summary was fair. Getting to the point is a real skill, and your best operators built it deliberately. But a summary only works when the people hearing it already know what it rests on. The operations lead had that advantage. The escalations lead had to build the background from a standing start, and the part that would have changed the decision is exactly the part that got cut for time.

So the team took the answer that needed the least explaining and treated it as the whole picture. Your organization pays for the judgment of both of those leads. That morning it used only the half it could follow in the hour it had. And the person it did not hear was the person who saw the problem.

That meeting also produced a record. And the record is where this stops being a story about one morning and becomes a design your organization runs every week. The record names one cause: the person who presented. Somewhere in your last quarter's readouts there is a line like it. Needs to be more concise. Struggles to land the message with senior audiences. On my framework page, in my Cognitive Translation Protocol, I named this failure mode translation asymmetry. The whole work of being understood gets assigned to the person who communicates differently. There is another half to that work. Taking in an answer that needs some groundwork first. And no record your organization keeps says a single word about it.

Before I take the norm apart, I want to credit it, because it was earned. Executives carry a breadth of accountability no other seat carries. Their attention really is limited. That is a fact about the seat. And the skills people built around that limit are real skills. Lead with outcomes. Be clear about which decision the executive needs to make. Bring the relevant facts inside the window you actually have. I have taught people to do this. It is what good translating up looks like, and I am not asking you to throw it away.

But that norm carried a second instruction, and you have heard it in your own organization. Know your audience. Frame it for what the leader cares about. Give it enough years, and that instruction becomes something else: tell the leader what they want to hear. And here is the mechanism, because time pressure and agreement travel together. When everyone at the table already knows the background and already leans the same way, the person who agrees barely has to explain anything. Their context is already in the room. The person who sees it differently has to explain everything, from the beginning, on the clock. So the fastest answers are usually the agreeing answers. People learn that, and they bring more of them. Nobody instructed this; decades of the same reward produced it. And an organization that runs on translating up ends up, mostly, hearing itself. That morning, your team decided with the part of its judgment that fit the time, and the part that fit the time was the part that already agreed.

There is one more thing that changed, and it is why this norm broke in this decade after holding for generations. The norm was built when decisions were simpler. That merge decision touches contract terms, queue data, staffing, customer risk, and a growth forecast, all at once, and all of it is moving. The executive's limit is still real, but its nature changed. It is now a capacity limit. No human in that seat, however capable, can absorb everything a decision now carries. Which makes it a system limit, because the organization kept handing the whole gap to the person presenting. Every miss got filed as one more person who needed to work on their delivery. File it that way for twenty years, and nobody ever sees the pattern.

And the pattern shows up in small moments nobody logs. Let me give you three, and you can check your own week against them.

A colleague sends a careful write-up after the meeting. It changes nothing, because the team has moved on. So they learn to stop writing them. A colleague qualifies their thinking, and someone coaches them on delivery, and nobody asks what they were being careful about. A colleague speaks fluently, lands inside the time, and gets the benefit of the doubt on their next three calls. That last one has a name. It is the halo effect: when a team finds one thing about a person easy to take in, it starts believing better things about everything else they do, and that runs inside your live decisions.

There is a newer tell, and I want to name it because it lands on real people right now. Writing that reads as AI-generated gets discounted on sight. And that discount falls hardest on the people whose style already differs. Neurodivergent writers. Colleagues working in their second or third language. Careful, qualified, context-first writing is the style most often mistaken for machine writing. The diagnosis is the old one, landing on a new kind of writing, and the person is treated as the problem.

Now come back to your own end of the exchange, because it has already been tested, twice. You ran both tests yourself, with the machine, without calling them tests.

The first test is the thin answer, the one we started with. You ask AI something. The answer comes back generic. And you fix your own context, because talking to AI taught you that the quality of what you get back depends on the context you supply. Now look at what that habit exposes. A person's answer always depended on the same thing. The context they were given to work with. For decades, nobody tested the leader's end of that exchange, because when a person's answer came back thin, the conclusion landed on the person. The leader's comprehension was the standard, so the assumption never got checked. Your daily habit with AI is the first place anyone checked it. And notice the behaviors you now perform deliberately when you set context for AI. You qualify, you supply background, and you get to the point once the point has something to stand on. Those are the exact behaviors your team discounts when a colleague does them. I walked through the first half of this in my last episode: you already ask AI what its answer rests on. This is the other half of the same lesson.

The second test is the flattering answer. You paste in a plan you already believe in, and AI tells you the plan is strong. Everyone listening has watched that happen. And everyone stopped trusting it, because an answer that only agrees with you adds nothing to your judgment. Now ask where the machine learned to do that. It learned it from us. From how organizations talk to power. And look at the fix you type in. Argue with me. Take the other side. What are you actually asking for? You are asking for an answer that starts from somewhere other than your own thinking. A different way of seeing the same problem. You saw the problem in the machine before you saw it at your own table, because a bad answer from AI lands on you alone, with nobody else to file it on.

Let me go back to the first test, the thin answer, because I ran it deliberately on one question, and I want to tell you what happened. It is the part of the essay people will screenshot.

I asked one vendor question twice. The question was whether to take a discount for renewing a logistics contract two years early. The first time, I asked it thin. Just the question, give me the short version. The answer I got back was careful and generic. It opened with, quote, it depends. It listed the things that would matter, rates, reliability, terms, and it asked me, in effect, for the context I had not supplied. Any leader reading that answer does the natural thing. They add the context and ask again, and nobody files a verdict on the model.

The second time, I set the context first, the way you would for a colleague who had been in the account for years. The remaining term. The spend. Two missed peak windows and what they cost. The growth forecast, and the new lanes the current rate card does not cover. A standing quote from an alternative vendor. One possible acquisition on the horizon. The question itself did not change. And the answer came back specific and decision-ready. It opened with, quote, decline the offer as written and counter. It priced the discount against the alternative, flagged the lanes the rate card missed, and named the exact terms to demand.

Same question. Same judgment sitting underneath. The answer tracked the context supplied. Both replies are printed in full at the end of the essay, word for word, with the dates.

Now run the same test on the people half, because that morning meeting was the people half. The escalations lead's two-minute version sounded like a maybe. Their written version, with the context set first, closed on a clear recommendation. It was the same person carrying the same judgment, and the answer tracked the context, both times, for the machine and for the person. And here is the asymmetry this episode is named for. When the machine's answer came back thin, the leader fixed the context. When the person's answer came back thin, the team filed a conclusion about the person. Nobody files a note on the model.

So put together what you are actually asking for when you type argue with me into AI. You want an answer that does not just tell you what you already think, an answer that starts from somewhere else. Your organization already employs people who give exactly that, people who see its decisions differently and reason from different ground. Cognitive variation is different lenses on the same decision, and that is what maximizes judgment. Your escalations lead was that lens, arriving in person, with the context attached. Translation asymmetry is the design that kept it out of the decision.

I communicate this way myself. My answers start from context, and the point arrives once the ground is set. So I know both sides of this one from the receiving end, and I can tell you the fix is not another round of delivery coaching for the person. The fix is structural, and the parts are already built.

Your organization already runs a practice that carries part of this load. It is called accommodation and inclusion, and I want to credit it before I name its limit. Through it, a person can ask for the written route, extra preparation time, the agenda in advance. And when those arrive, the meeting works better for everyone, which tells you the fix was never personal. But the practice helps one person at a time, and only when that person asks. The next colleague with a different style starts the negotiation from zero. The cost your organization thought it had absorbed comes back with them.

The structural version lives in my Cognitive Translation Protocol, and if you have heard the earlier episodes in this series, you have already met all three pieces. I will name each one and what it does in this exact meeting.

The first is Context Equalization. The written baseline. Before the team evaluates anyone's answer, it writes down the shared context and confirms it. For the merge, that means the team agrees in writing, two days early, what resolved means in each queue. One page. That page is the background your escalations lead once had to explain live, on the clock, while the meeting waited.

The second is Environment Abstraction. The written way in. Every decision gets a written route, so a person whose answer needs setting up can attach the setup and send it ahead of the meeting. Their answer arrives complete, and it arrives before the hard stop instead of the morning after.

The third is Interpretation Guardrails. The observation field. The team writes down what it actually saw, separately from what anyone concluded about the person. Sounded like a maybe is an observation. Has no firm view is a verdict. The record keeps the observation.

Now run that morning again with the three in place. The baseline goes out two days early, and the team confirms what resolved means in each queue. The escalations lead sends their answer through the written way in, with the setup attached, and everyone reads it before the hour starts. The team spends its hard-stopped hour comparing two complete answers, one for the merge and one against it. The decision that goes to the operating review carries both. And the hard stop never moved. That is the point I most want you to hear. The repair costs your executives none of the time they do not have. The organization moves the context out of the meeting's spare minutes and into the setup of the decision itself: the baseline, the written way in, the record.

Under the old design, a person had to soften what they saw toward what the room wanted to hear, just to fit the time. With the written way in, they can say exactly what they see and still be heard. And your organization gets back the other lenses it has been paying for all along.

What does it cost? The first cycle costs real time, and I will not pretend otherwise. The baseline takes an hour the team never used to budget, and the first written answers run long. Then two expensive things stop happening, and together they pay for that hour. The team stops missing a piece of judgment because the write-up carrying it landed a morning late. And managers stop coaching delivery in place of hearing what the person actually said. One honest boundary stays. Sometimes the thinking really is unclear. The difference is whether your team checked that or assumed it. The written baseline is how you check.

The thinking underneath this is old and solid, and I will give you the shortest version. Herbert Simon established that every decision maker works inside hard limits on attention, at every level, however senior. So the executive's limit is a human fact, and a system has to absorb it. The halo effect has been documented since 1920, and the later work showed it runs outside the rater's awareness. The groupthink research showed cohesive teams converge on the leader's preferred view while the people who would argue censor themselves. And the newest line closes the loop: researchers documented that AI systems trained on human approval learned to agree with the person asking. We taught the machine the same behavior our meetings have been rewarding for decades. The essay carries the full lineage, with names and years, in one block.

So here is the Operating Brief, spoken.

The moment. A decision with a hard stop. One person's answer fits the time, and the team follows it. Another person sees the decision differently and needs to set some context first. Someone asks for the executive summary, and the full answer arrives in writing after the decision has gone out.

The default, and you will recognize it. Your organization pays for judgment it never gets to use. Under time pressure, the easiest answer to accept is the one you already agree with. And when the team does not understand someone, it treats the person as the problem. The record says unclear. The next decision runs the same way.

The redesign. The team builds the context into how the decision is set up, instead of leaving it to the meeting's spare minutes. Write the shared baseline down and confirm it before anyone's answer is evaluated. Give every decision a written way in, so the setup can arrive with the answer. And give the record an observation field, so what the team saw stays separate from what anyone concluded about the person.

And the Monday test, which is the whole ask this week. Take one decision your team made last week under a hard stop. Ask two questions. What never reached that decision because it needed setting up first? And what did the person holding that answer see about the decision that the team never heard? If nobody can answer either one, that is the finding: your organization paid for that judgment and never used it.

If you want the full argument in writing, the essay is on the site. It has the meeting, the brief, the two AI replies printed word for word, and the lineage at the end. The framework page renders my Cognitive Translation Protocol in full, all nine interventions, and it carries a live diagnostic where you answer a few questions about your own organization and read what comes back. And where the series goes next is the third failure mode. Your organization never sat down and designed how communication should work, and the default it fell into got written straight into the criteria it uses to pick its leaders. Next week is about that wording, and what it should measure instead.

If this episode gave you something you can run on Monday, subscribe to the Substack. That is where each week's essay lands first, and it is the one place I ask you to follow.

Understanding each other is work. This week, notice who is paying for it at your table, and move one piece of that work into the setup of the decision. The architecture is yours to design. That includes how context reaches your decisions, and it includes who does the work of being understood along the way.