Design Communication for Every Mind,
and Candor Stops Being an Act of Courage.

Think about the last time someone on your team said the hard thing early. They said it to someone more senior, and they said it before the call was made. In that moment, your organization found out what it actually values.

Your organization also says what it values before any hard thing comes up. Somebody wrote that short list down. It is on your website, or on the wall of your meeting room, or on the first slide at your all-hands. Most people call it the values page.

Candor may be one of the things your organization says it values. Your organization may name it candor, or it may use a related name, like honesty, speaking up, or saying the hard thing early.

Now go back to the person on your team who said the hard thing. Think about what they weighed before they spoke. Maybe they weighed how the hard thing would sound. Maybe they weighed whether it was their place to say it.

If saying it took courage, then candor on your team is an act of courage. Your organization is asking each person to be brave on their own. So the hard thing arrives late or softened, and sometimes it never arrives.

The cost is the judgment inside the hard thing. Someone on your team worked it out, and whoever made the call never heard it. Your organization paid for that person's judgment, and did not get to use it.

So your organization can say it values candor, and saying the hard thing early can still take courage on your team. Your values page says what you believe. How your organization communicates says what it assumes. By what it assumes, I mean the unwritten rules people on your team actually follow.

By how your organization communicates, I mean the documents, the meetings, the channels and the roles a decision passes through on its way to whoever decides. I call that your communication architecture.

My claim in this episode is about how you design it. When you design communication on your team for every kind of mind on the team, candor becomes the way the work normally goes. Nobody needs courage to say the hard thing early. That is what I mean when I say candor can be a norm, not an act of courage.

Near the end of the last episode, I said my next essay would start with a document Anthropic published about Claude. This is the episode for that essay, so that is where we start. Keep your own organization's values in mind while I describe it.

Anthropic published that document in January this year, under the name Claude's constitution. In it, Anthropic writes down the values it intends for Claude, its reasons for them, and which should generally come first when two of them seem to conflict.

I read it in the terms of Edgar Schein, whose levels of culture I laid out in an earlier essay: the constitution is the stated values, and how Claude actually responds sits underneath them. Anthropic says plainly that how Claude responds may not always match those values, and Anthropic wrote that into the constitution itself. It is not a perfect solution. It is a beginning. Designing a value that way on purpose is part of what I call cognitive architecture, the deliberate design of how thinking happens.

Come back to your own organization's values. Your organization has the same kind of distance between what it says it believes and what people on your team actually do. That distance is rarely named out loud. Candor is where it is easiest to hear.

The leaders who wrote those values down meant every word. In a 2020 article in MIT Sloan Management Review, Sull, Turconi and Sull looked at more than four hundred large companies, mostly in the US. They compared what each company said it valued with how its own employees described the company. For every value they measured, the link between the two was very weak.

I built a framework for how communication works between people who think differently, and I call it my Cognitive Translation Protocol. Its page on my site says it in one line. "Your organization runs on two sets of values: the ones it states, and the ones its systems actually enforce."

The people on your team notice that distance before anyone else does. And now the AI your people use reads your documents too, and it gets only the part that someone put in writing.

Think of someone on your team who does good work and keeps running into the same friction, month after month.

I am Autistic. After my diagnosis, I made it a core passion of mine to change leadership norms so every nervous system and every kind of mind can thrive. I do not have the fast, gut-feeling read that most people call intuition, in its traditional sense. When someone's tone shifts, most people catch it without noticing. The same goes for the real reason a meeting changed direction. I work those things out on purpose, one step at a time.

For most of my career, the organizations I worked in were built for a different kind of mind than mine. The friction I met in them turned out to be diagnostic. Every place I struggled was a place where the organization had an unwritten rule that nobody had given me. Those places were where its design was easiest to see. The people who notice an organization's design most clearly are the ones it was not built for.

Take that back to candor, on your team. A value like candor carries unwritten rules of its own: when early actually is, who gets to say the hard thing, and how it has to sound. Nobody wrote those rules down, and your team follows them anyway. The person who keeps running into friction is showing you which of those rules your team actually runs on.

So what was this series for? This is the last episode on my Cognitive Translation Protocol. My Protocol is where my work on the unwritten rules of leadership begins. The earlier episodes walked through its nine interventions, and I made each one a simple start on purpose. Each one changes a document, a meeting, a channel or a role your team owns today, so a leader can make the change this quarter.

This episode says what the nine were for. Designing how communication works is part of designing leadership. That matters more now, because every kind of human mind in your organization works beside the AI your people use.

Go back to the hard thing someone on your team needs to say. It can get lost before anyone says it, while it is being said, or afterward, when nobody remembers who said it.

My nine interventions fall into three groups, and I call each group a lane. I will take the lanes one at a time, and come back to candor in each one.

The first lane is the interpretation lane, and it deals with how people on your team make sense of each other. It has three interventions. Interpretation Guardrails means keeping what someone observed separate from what they read into it. Context Equalization means everyone shares the same understanding before anyone judges. And Outcome-Based Evaluation means judging results, and leaving guessed intent out of it.

In this lane, your team gives up the unwritten rule that a leader's read of a person is the fact. From then on, your team judges what a person said and what came of it. Nobody's impression of how that person came across gets to replace either one. A good point stops getting marked down because of its tone.

Put candor through that lane. The hard thing gets judged on whether it was right. And the tone someone read into it stops counting against the person who said it.

That is the first lane. The second one is the process lane, and it is about time, and about what your team keeps in writing.

Signal Persistence means keeping what someone contributed, past the moment they said it. Pacing & Timing Controls means separating how good someone's thinking is from how fast they answer. And Decision Traceability means your team can trace any decision back. You can see what someone raised, how the team read it, and what the team decided.

Here, your team drops the unwritten rule that the moment something is said is the moment it counts. Whoever makes the call hears a colleague's judgment, whether or not that colleague worked it out on the spot. And later on, your team can see whose judgment held up. A good point no longer disappears because it arrived a day late.

For candor, this lane changes the timing. The hard thing still counts whenever it arrives. Afterward, everyone can see who raised it first, and who was right. So saying it early becomes the sensible thing to do.

That is the second lane. The third one is the environment lane, and it is about the conditions people work in.

Cognitive Offloading means putting what people would otherwise hold in their heads somewhere everyone can see it. Environment Abstraction means giving people ways to take part that do not depend on the sensory cost of the room. And Boundary Encoding means writing out roles, limits and stop points.

In this lane, your team stops assuming that taking part costs everyone the same. Nobody has to push through a loud room or a fast back-and-forth before they can contribute. A written channel counts the same as speaking up. And everyone knows what their role is, and where it stops.

For candor, nobody pays the cost of the room before they can say the hard thing. And nobody has to guess whether it is their place to say it.

So that is all three lanes, and I have followed candor through each of them. The same choices about your documents, meetings, channels and roles carry every other value your organization states too. That includes the best information winning, and every voice counting. With all three lanes in place, whoever makes the call hears from every kind of thinker on your team. And in each lane, your team changes an unwritten rule your organization actually runs on.

While I was writing the essay, I ran a test. I handed two documents to Claude Fable 5.1, the AI I use. I ran the test in Anthropic's Claude Code harness. The harness is the software around the model. It gives the model its tools and its files. It was one prompt and one reply.

The two documents came from a leadership team I simulated. I build teams like that one on purpose, from my own experience and what I have observed over many years. A simulated team can stand for every leadership team that works the same way, and it describes no real company and no real person.

The first document was that team's values page. It had three lines on it. One said the team decides on the best information in the building, whoever holds it. One said the team values candor, and asked people to say the hard thing early. And one said every voice at the table counts.

The second document was a plain description of how communication actually works on that team, and the team's chief of staff wrote it. Decisions get made in one weekly meeting. The agenda arrives that same morning. What the team keeps in writing afterward is the decision and who attended, and nothing about what anyone said. An objection counts only if someone says it out loud, in the meeting. Nobody has written down who decides what. And each person runs AI on their own, with whatever documents they happen to have. That is the simulated team's own account of how it works.

Claude Fable 5.1 read the two documents side by side. It named the distance between the values page and the description in the first two sentences of its reply. It wrote, "The page says thinking is distributed and candor is early. The description says thinking happens in one place, at one speed, in one medium."

Now add a simulated person to that team. A new senior manager joins next month. They work things out step by step, and in writing. By the end of their first month, they know that thinking counts on that team only when it is spoken, in the meeting's time slot. The organization concludes that they are quiet and slow, and all the while they have worked out that team's unwritten rule.

The AI that team uses works from what the team keeps in writing, which is the decision and who attended. So it sees decisions without the reasons behind them. An AI only has what someone wrote down. In my test, Claude Fable 5.1 could name the distance because the chief of staff had written down how that team actually works.

Then Claude Fable 5.1 named nine changes to that team's documents, meetings, channels and roles. Two of them fall in my interpretation lane, three in my process lane, and four in my environment lane. If you try this on your own two documents, hand your AI my nine interventions to work from. Then your AI answers you in these same three lanes.

Claude Fable 5.1 also said what every one of those changes was for. It said each change alters a document, a meeting, a channel or a role, "so that the value becomes the default path rather than an act of courage." And on candor, the second value on that team's values page, it wrote this. "This makes candor rational instead of brave, which is the only way the second value survives contact with a career." Its reason for every change is the one this episode is about.

Once someone looks with care at that team's documents, meetings, channels and roles, the team is easy to read. When you set up an AI, you look closely at what it has to work from. And the people on your team have earned more of that diagnostic care than the AI, never less.

I want to say why this matters now. With the pace of AI this year, one thing became plain to me. Leadership is about judgment, clarity and context, more than ever.

LinkedIn commissioned a survey that ran in May this year, and nearly eight in ten of the C-suite leaders in it said they are moving faster on AI than they can effectively measure.

In PwC's Global CEO Survey, released in January this year, more than half of the CEOs said their company had seen neither higher revenues nor lower costs from AI in the past year.

Turning that pace into a payoff is the work left for leaders. Somebody still has to decide where to point AI, and that call needs clarity about what the work is for, and context about how your team decides.

Think about a value your organization states and does not follow. For a long time, people on a team absorbed that quietly, and adjusted. Your people follow the rule your team actually runs on. The AI your people use works from your documents, so it follows the values you state. Your people and your AI pull apart inside the same piece of work, and that is where you can see it. So a value you state and do not follow is no longer sustainable.

This series has been making one turn, essay by essay. Communication in an organization used to exist so the leader could carry the room. Now it exists to get the best judgment to whoever is deciding, from whoever holds it. And that judgment has to arrive in a form the rest of the team can question and add to. Larger movements in the world are behind that turn.

Someone on your team right now may be able to tell you the unwritten rules your team runs on. Their mind works differently from the one your organization was built around, and The Neurodiversity Movement made that difference visible. The premise I start from is that different nervous systems produce different cognitive architectures, shaping thinking, sensing, and processing across mind and body, not broken brains.

The judgment you pay for and never hear is capital, and The Brain Economy puts a price on it. Brain capital, in its terms, is brain health plus brain skills, quantified infrastructure with measurable return. So the thinking your people do is an asset, and what it returns can be measured.

And the unwritten rule your team runs on now carries a cost you can see, because the AI your people use works from what your team keeps in writing. That is The Age of AI.

Those movements all meet in one place. Cognitive architecture is the convergence. For your organization, that means designing how thinking happens, and your leadership team does much of that through how the organization communicates.

I am what I call the luxury layer of my community. By that I mean I am employed, I am verbal, and I can present in a way rooms have learned to accept. Despite the disability, I still hold social capital that most of my community does not have. I will use my social capital, and my version of executive presence, to open a seat on the executive team and a seat on the board to leaders who think differently. That is what I built this platform for.

You hold some of that same social capital. Every leader with a team decides what the team keeps in writing about a decision, which channels count, and what a person is judged on. That is where your capital gets spent. Spend it on how those things are designed. Then a good point gets heard no matter who happens to be in the room.

In my lifetime, I will help evolve the assumptions of leadership so cognitive variation can thrive.

A review of what FTSE 100 companies publish, reported in December 2024, found just one board member, across all of those companies, who had publicly disclosed a disability. That number counts only the people who chose to say so. Even so, you can see from it that the public record at the very top is nearly silent on disability.

A 2025 meta-analysis in the journal Autism Research pooled many earlier studies of first impressions. It found that people formed a less favorable first impression of autistic people than of people who are not autistic. That held in every format except one, a written transcript of what the autistic person said. That is part of why my interpretation lane and my process lane are there. With those two in place, your team keeps what a person said, and what came of it, in front of whoever decides.

I picture the outcome this way. One day a non-verbal autistic leader who speaks through assistive technology, or a Deaf leader who speaks through an ASL interpreter, sits in the executive seat and sits on the board. No story gets written. The architecture was simply designed for it.

There is one step after all of this. Once the best judgment reaches whoever is deciding, someone still has to make the call and own it. That is my DecisionOS framework. It pairs with my AI Cognitive Strategy Matrix, which gives a person a method to break a process down and decide where AI is used, so that human judgment is preserved.

That brings me to the Operating Brief, which is the short version of this whole episode, in four parts. You can act on it this week.

The moment. Your organization holds every kind of human thinker, and beside them, the AI its people use. All of them work from the same communication architecture, meaning the documents, meetings, channels and roles a decision passes through. Your values page says what you believe. How your organization communicates says what it assumes. Your people read the rules your team actually runs on, like the rule that the hard thing only counts if someone says it out loud, fast, on the spot. Your AI may miss those rules.

The inherited design. Leadership was built around one cognitive style. Communication got treated as a skill each person brings. Coaching people in that skill was right to do, and it was also as far as anyone went in designing communication. Your meeting formats grew up on their own. The same is true of what your team keeps in writing, which channels count, and who decides what. So candor stays a value that takes courage. And the cost is the judgment you never hear.

The redesign. Design your communication architecture on purpose, as part of how you design leadership. My Cognitive Translation Protocol gives you nine interventions in three lanes to do it. The interpretation lane is about how your team reads what a person contributes. The process lane is about when a contribution counts, and whether your team's written account of a decision keeps the reasons for it. The environment lane is about what it costs a person to take part, and about writing down who decides what. All nine are set out on my Cognitive Translation Protocol page on the site.

The Monday test is one thing you can do this Monday. Take your values page, and start with candor if it is on there. Next to each value, write one sentence: where your team's real behavior comes apart from it. Then name which of my nine interventions would make that value part of how your team works. And name the document, meeting, channel or role it would change. It takes one afternoon, and it needs nobody's permission.

The essay also prints a prompt. Paste it into Claude, or into the AI your company has approved for its documents. Under it, paste your values page and one plain paragraph on how communication actually works on your team, with the names stripped out. For each value, the prompt asks what unwritten rule your team runs on, where your team comes apart from the value, and which of my nine interventions would build that value into how your team works. Then put what comes back next to the sentences you wrote.

The full argument is in the essay on the site, with the whole reply from Claude Fable 5.1 printed at its foot. Every source I named here is there too, with what it does and does not show. And my Cognitive Translation Protocol page lays out each of the nine interventions.

If you want each week's essay as it comes out, subscribe to the Substack. That is how each one reaches your inbox.

The Monday test costs you one afternoon. Your values page says what you believe. How your organization communicates says what it assumes. Start with the value your people still need courage to live up to.