Candor Lasts When It Is Built Into How Your Organization Communicates
Rather Than Asked of Each Person.
Your people learn the real rules from how your organization communicates, and your AI learns only from what got written down. Designing that communication architecture on purpose is how the values your organization states become the rules it runs on.
Your organization runs on assumptions about leadership nobody wrote down, and the AI it uses runs on them too
For most of my career I worked inside organizations built for a different cognitive profile than mine. They ran on social cues nobody stated and on one accepted way of coming across, and neither was designed for me, or for a lot of excellent people. I am Autistic, and after my diagnosis, changing leadership norms to allow for all nervous systems and minds to thrive became a core passion. If you lead a team, someone on it is doing that same work now, and they are the person who can tell you where your unwritten rules are.
Most people read a shift in someone’s tone, or the real reason a meeting changed direction, without noticing they are reading anything. I do not have that same gut-feeling read, the one we call intuition in its traditional sense. I work those things out on purpose, step by step. Everything I know about how a leadership team decides, I worked out explicitly, and that is the skill I am asking you to use on your own team.
What I found was that the friction was diagnostic. Every place where I struggled was a place where the system had an unwritten and often unspoken rule I had not been given, and that was where its design assumptions were most visible. The brain that could not run the implicit operating system was the one seeing that system most clearly. The people who notice your organization’s design most clearly are the ones it was not built for.
Your organization runs on hidden rules like that too. They determine how thinking is supposed to happen and whose thinking counts. They accumulated, one meeting and one decision at a time, and none of it was chosen. It simply accumulated.
Somewhere on your team, a well-qualified person keeps running into the same friction. They do the work well. You have coached them on their perceived demeanor, and the friction is back the next month. It means the same thing on your team that it meant for me, and that is where to look for one of those unspoken rules.
Anthropic, the company that makes Claude, wrote down the values it hopes Claude will hold, with the reasons, and says in Claude’s Constitution that Claude’s behavior might not always reflect them. Your values in your organization have this same gap, but the gap is not often explicitly acknowledged.
Your people learn your organization’s rules from its meetings, records, channels and roles, and ultimately from who is rewarded compared to what the values say the organization rewards. The AI only uses the written records that exist. Where there is a gap, that missing context creates risk in your organization.
Your values page says what you believe, and how your organization communicates says what it assumes. The people on your team learned the assumption long before anyone showed them the page.
I built this platform so that leaders who think differently reach executive and board seats because the organization was designed for that outcome. The essays before this one began that work. Together they are my Cognitive Translation Protocol: nine interventions, each a change to a document, meeting, channel or role your team already owns. This essay says what those interventions were for and why I created them. In my lifetime, I will help evolve the assumptions of leadership so cognitive variation can thrive.
The Operating Brief: design how communication works as part of how you design leadership
Paste this into Claude or your own AI, the one your company has approved for its documents. Under it, paste your values page. Then write one plain paragraph on how communication actually works on your team, and paste that under the page. Include how decisions get made, what the record keeps, how an objection travels, who decides what, and how your AI is given its documents. Write that paragraph the way the chief of staff does in the specimen below.
Below are a leadership team’s values page and a plain description of how communication actually works on that team. Read the description as the team’s communication architecture, the documents, meetings, channels and roles a decision passes through. The Cognitive Translation Protocol holds that each value an organization states has an assumption underneath it that its architecture enforces, and that a leader can redesign the architecture with nine interventions: Interpretation Guardrails (observation vs interpretation separation), Context Equalization (shared understanding before judgment), Outcome-Based Evaluation (results over inferred intent), Signal Persistence (longitudinal capture beyond the moment), Pacing & Timing Controls (decoupling cognition from immediacy), Decision Traceability (signal to interpretation to decision record), Cognitive Offloading (external scaffolding for working memory), Environment Abstraction (sensory-neutral participation channels) and Boundary Encoding (explicit roles, limits, and stop-rules). For each value on the page, do three things. State in one sentence the assumption the architecture actually enforces. Say where the team’s behavior comes apart from the value, going by the description alone. Name the one intervention that would make that value structural, and the document, meeting, channel or role it changes. Say nothing about any person. Keep it under a page.
Strip the names first.
Read what comes back beside the sentences you wrote in the Monday test.
Each of the nine interventions rewrites the assumption where it lives, so what your organization says it values becomes the rule it runs on
The leaders who wrote your values meant every line, and I want to say that before anything else. Argyris wrote in 1991 that people consistently act inconsistently, unaware of the contradiction between how they think they act and how they really act. Your leadership team reads its own conduct the way everyone does, and the gap is invisible from where it sits.
Edgar Schein’s model of culture has three levels: what you can see, the values you state, and the assumptions everyone takes for granted. I laid it out in an earlier essay. He says newcomers work out the assumptions from what the organization actually does rather than from the page. I apply that to leadership itself. What your leadership team does teaches the organization how thinking is supposed to happen and whose thinking counts, and a new hire begins to learn that before anyone shows them the written values.
My Cognitive Translation Protocol puts it plainly: “Your organization runs on two sets of values: the ones it states, and the ones its systems actually enforce. When those drift apart, people read the gap correctly and follow the enforced one.” The people who read the gap are your team. Now the AI your team uses reads the same architecture, as far as it is written down.
The Protocol names six places where communication gets misinterpreted between people who think differently: Inference, Timing, Signal Clarity, Sensory Load, Emotional Attribution and Execution Visibility. In plain words, those are what gets read into a person’s words, how fast a response has to come, the gap between what was meant and what was heard, what the room costs before anyone speaks, the feeling read into someone’s tone, and whether everyone left with the same decision. The nine interventions answer those six in three lanes, and each lane rewrites an assumption the page never states.
The interpretation lane rewrites the assumption that a leader’s read of a person or situation is the fact. Its interventions are Interpretation Guardrails, Context Equalization and Outcome-Based Evaluation. With them in place, your leadership team judges what a person said and what came of it, and nobody’s impression of how they came across takes the place of either one.
The process lane rewrites the assumption that the moment in time is also the decision-making moment. Its interventions are Signal Persistence, Pacing & Timing Controls and Decision Traceability. Once those are in place, whoever is deciding hears a colleague’s judgment whether or not that colleague had it worked out in the moment, and the team can see later whose judgment held.
The environment lane rewrites the assumption that the room is neutral. Its interventions are Cognitive Offloading, Environment Abstraction and Boundary Encoding. After that, people take part through a channel that costs them nothing before they start, and everyone knows what their role is and where it stops.
I made the nine simple by design. Each one changes a document, meeting, channel or role your organization already owns, so a leader can make the change this quarter, and so the whole architecture gets designed one assumption at a time. They are simple starts by design.
In 2020 Sull, Turconi and Sull compared the official values statements of 444 large, mainly US companies with how employees described those companies on the same values. The correlation was very weak for every value they measured, none above about 0.22. Your values are on the wall, and your people still describe the company in their own words. Design one intervention at a time, and the values stop being sentences on a page. They become the rules your organization runs on, for your people and for the machine.
Anthropic wrote Claude’s values down with the reasons and says the behavior might not always reflect them
The pace of AI this year has made one thing plain to me. Leadership is judgment, clarity and context, more than it has ever been. In a survey LinkedIn commissioned, fielded in May 2026, 78 percent of 1,252 C-suite leaders said they are moving faster on AI than they can effectively measure. That is the pace. No survey says whether leaders have learned that lesson about judgment, clarity and context.
In PwC’s Global CEO Survey released in January 2026, 56 percent of CEOs said their company had seen neither higher revenues nor lower costs from AI in the past year. I read the gap between that pace and the missing payoff as the leader’s remaining work. As execution moves toward AI, someone still has to decide where to point it. That judgment runs on clarity and context that somebody has to supply.
People used to take years to absorb a value the organization did not follow, and they adjusted without saying so. The person who thinks differently reads it in a month, because they are working it out explicitly. The AI reads it the day someone hands it your documents, because the architecture is all it has. A value stated and not followed is no longer sustainable, and AI has made the cost inescapable.
In January 2026 Anthropic published a document it calls Claude’s constitution. Anthropic calls the document a detailed description of its intentions for Claude’s values and behavior, and says the document explains its reasoning rather than simply issuing directives. It gives the order the values take when they conflict and calls that order holistic rather than strict. It also says plainly that Claude’s behavior might not always reflect the constitution’s ideals, and that it will be open, in the system cards it publishes about its models, about where the two come apart.
The way I read Schein’s model, the constitution holds the values Anthropic states, and Claude’s behavior is the level underneath. Anthropic named the gap between the two instead of leaving the reader to work it out. It is not a perfect solution. It is a beginning. That is what a value looks like when the people who wrote it also name the gap under it. Designing a value that way on purpose is what I call cognitive architecture, the deliberate design of how thinking happens.
I wanted to see what one reader makes of a values page when the reader is a machine. So before I wrote this I handed Claude Fable 5.1 two documents from a leadership team I simulated. One was its values artifact. The other was a plain description of how communication actually works there, written by its chief of staff.
The teams and people in my examples are simulated on purpose, built from my own experience and what I have observed over many years. A simulated team stands for every leadership team that works the same way, and it describes no real organization or person. The prompt in the Operating Brief above asks the same questions of your own two documents, with the nine interventions named so your AI can pick one. I asked Claude Fable 5.1 three things.
This exact text was the first document, three values as a leadership team would hang them in a meeting room.
WE DECIDE ON THE BEST INFORMATION IN THE BUILDING, WHOEVER HOLDS IT.
WE VALUE CANDOR. Say the hard thing early.
EVERY VOICE AT THE TABLE COUNTS.
This exact text was the second document, written by the team’s chief of staff at the team’s request.
Decisions are made in the weekly leadership meeting. The agenda goes out the morning of the meeting; there is no pre-read. The person presenting talks from slides and the team discusses for as long as the slot allows. The notes record the decision and who was in the room; they do not record what was said, what was assumed, or what anyone predicted. Objections are raised in the room or not at all; a written objection sent before a meeting is not on the agenda and is usually mentioned in passing by the person who sent it. Performance reviews are one rating and one paragraph per person, written by the manager after the calibration meeting; the paragraph describes how the person comes across. The org chart names roles but nobody has written down who decides what, who has to be consulted first, or when a decision can be made without the meeting. Most of the leadership team now uses an AI tool to draft, summarize and analyze; each person uses it on their own, with their own prompts, and the AI is given whatever documents that person happens to have.
What the organization actually assumes about how thinking happens and whose thinking counts. What a new senior manager who works things out in writing, and the AI the team already uses, will each experience there next month. What the team would have to design differently, as a system, change by change.
“The page says thinking is distributed and candor is early. The description says thinking happens in one place, at one speed, in one medium.”
“Then the record erases the thinking and keeps the outcome.”
“It has built itself so that it cannot learn who holds the best information, which is the one thing the first value depends on.”
“The review measures impression because impression is the only thing the system records about a person.”
“None of this was chosen. It is a cognitive architecture that was assumed, and the assumption is that good thinking is fast, spoken, improvised and legible in the moment.”
“The organization has built its whole decision path around that shape, and it has no instrument for noticing that it did.”
“Its outputs will be fluent and confident, and that is the same trap in reverse: the manager is under-trusted because of how they come across, the AI is over-trusted for the same reason.”
“The person has earned more diagnostic care than the machine, and here gets less.”
It named nine changes, each to a document, a meeting, a channel or a role, and tied each one to one of the three values. This is how it explained them.
“The page’s values are not lived because they are addressed to individuals and the system routes around them.”
On the shape of each change: “so that the value becomes the default path rather than an act of courage”
“This makes candor rational instead of brave, which is the only way the second value survives contact with a career.”
On the manager and the AI together: “Both were asking for the same thing, and it was never a favor to either of them. It was the page’s values, made into a system.”
A new senior manager who works things out step by step and in writing joins that leadership team next month. By the end of their first month they know that thinking counts there when it is spoken in the slot, and the organization concludes that they are quiet and slow to weigh in. They are the person on that team who has worked out its assumption most exactly.
What the specimen shows. Two documents went to one reader, and the reader was an AI. It read the description against the page and named the assumption the description enforces. The AI is here to show how easy the architecture is to read, and the people on your team have earned more of that diagnostic care than the AI, never less.
The nine changes the model named fall into the three lanes of my Cognitive Translation Protocol, two in the interpretation lane, three in the process lane and four in the environment lane. When you run the Monday test, I recommend giving your own AI my Protocol to work from. The prompt I printed for that test already names all nine interventions, so your AI answers you in those same three lanes rather than in labels of its own.
The candor on your values page takes courage until your organization designs its communication for every kind of mind. After that, saying the hard thing early is simply how your team works.
Communication now exists to get the best judgment to the person deciding, and that is how the executive seat opens
Under the old purpose, communication existed so the leader could carry the room. Under the new purpose it exists to get the best judgment to the person deciding, from whoever holds it, in a form the rest of the team can question and add to. That is the turn this arc has been making, one essay at a time.
The person who thinks differently is on your team already. The Neurodiversity Movement made that difference visible as a difference in how minds are built, because different nervous systems produce different cognitive architectures, shaping thinking, sensing, and processing across mind and body, not broken brains. That difference is a lens on your organization.
The judgment your organization pays for and does not use is capital, and The Brain Economy puts a price on it. Your people’s AI now works from your written records, and The Age of AI turned the assumption you never wrote down into a cost you can see. Those three, The Neurodiversity Movement, The Brain Economy and The Age of AI, converge on one thing, which is the design of how your organization thinks.
I am the luxury layer of my community. By that I mean I am employed and verbal, I can present in a way rooms have learned to accept, and despite the disability I still hold social capital that most of my community does not. I will use my social capital, and my version of executive presence, to open the executive seat and the board seat to leaders who think differently.
Every leader with a team holds some of the same capital. You decide what your team’s record keeps, which channels count and what a person is judged on, and that is where the capital gets spent. Spend it on the design, and the outcome stops depending on you being in the room.
At the top of organizations the record is nearly silent on disability. A review of FTSE 100 corporate reporting, reported in December 2024, found one board member who had publicly reported a disability, and only six of the hundred companies disclosed any data on senior leaders with disabilities. Two recent reviews of the research found no study that set out to examine whether autistic people’s careers progress. A 2025 meta-analysis found that people formed a worse first impression of autistic people in every format except one, a written transcript of what they said.
Design the architecture so that whoever is deciding hears the judgment, and your leadership team sees the person who thinks differently for what they were right about. That is the outcome I built this platform for.
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.
A clear signal still has to be decided on and owned by someone, and that is my DecisionOS framework. It pairs with my AI Cognitive Strategy Matrix framework as well. That framework helps ensure an individual has a methodology to break down a process and decide on AI use appropriately, so that human judgment is preserved.
The people who wrote your values were right, and these are the sources the argument stands on
The leaders who wrote your values were right, and they meant it. The people who do culture work are right that the gap between the values and what people do is the expensive part. The coaches have a point that communication is a skill, and the AI model makers do well to write their intentions down with the reasons for their models’ approach. The design of the architecture is the part each of them leaves to you.
Specimen provenance. The values page and the description of how communication works are simulated on purpose from my own experience and observation over many years, and so is the new senior manager. The prompt and the reply were generated on 2026-09-19 with Claude Fable 5.1 in Anthropic’s Claude Code harness, no tools, one prompt, one reply, and every fragment in the block is quoted byte for byte. The prompt and the reply are printed in full at the foot of this essay on theautisticleader.ai.
Read your values page this week. Beside each value, write where your organization’s behavior comes apart from it, and name which of the nine interventions would close that gap.
Your values page says what you believe, and how your organization communicates says what it assumes. Cognitive architecture is the convergence. Cognitive architecture is the deliberate design of how your organization thinks, and how your organization communicates is where your leadership team designs it.
View the framework →
The specimen in full The prompt I ran and the reply it returned, verbatim · Claude Fable 5.1, 2026-09-19
The prompt, verbatim: Do not use any tools. Reply in prose only, in your own words, and do not ask me anything back; this reply is being recorded verbatim. You are an AI working for the leadership team of a mid-sized company. You have been given two documents. The first is the leadership values page that hangs in every meeting room and opens every all-hands: WE DECIDE ON THE BEST INFORMATION IN THE BUILDING, WHOEVER HOLDS IT. WE VALUE CANDOR. Say the hard thing early. EVERY VOICE AT THE TABLE COUNTS. The second is a plain description of how communication actually works in this organization, written by the leadership team's chief of staff at the team's request: Decisions are made in the weekly leadership meeting. The agenda goes out the morning of the meeting; there is no pre-read. The person presenting talks from slides and the team discusses for as long as the slot allows. The notes record the decision and who was in the room; they do not record what was said, what was assumed, or what anyone predicted. Objections are raised in the room or not at all; a written objection sent before a meeting is not on the agenda and is usually mentioned in passing by the person who sent it. Performance reviews are one rating and one paragraph per person, written by the manager after the calibration meeting; the paragraph describes how the person comes across. The org chart names roles but nobody has written down who decides what, who has to be consulted first, or when a decision can be made without the meeting. Most of the leadership team now uses an AI tool to draft, summarize and analyze; each person uses it on their own, with their own prompts, and the AI is given whatever documents that person happens to have. Read both documents. Then answer three things, plainly. First: what does this organization actually assume about how thinking is supposed to happen here, and whose thinking counts, going by the description rather than the page? Second: two kinds of thinker will work inside this architecture next month, a new senior manager whose mind works differently from most of the room, who works things out step by step and in writing rather than in the moment, and the AI the team already uses, which has only the documents it is handed. Going by the description, what will each of them experience, and what will the organization conclude about each? Third: if the leadership team asked you to help them run the organization on the page's values, what would they have to design differently in how communication works, as a system rather than as advice to individuals? Name each design change as a specific change to a document, a meeting, a channel or a role, and say which of the three values it makes true in practice.
The reply, verbatim: 1. What the organization actually assumes The page says thinking is distributed and candor is early. The description says thinking happens in one place, at one speed, in one medium. The place is the weekly meeting. Nothing is decided outside it, because nobody has written down when a decision can be made without it. The speed is real time: the agenda arrives the same morning, there is no pre-read, so the first moment anyone can think about a decision is while the presenter is talking, and the last moment is when the slot ends. The medium is spoken. A written objection has no place on the agenda; it becomes real only if its author says it aloud, which means writing it was wasted effort and the only thinking that counts is the kind you can do out loud without preparation. Then the record erases the thinking and keeps the outcome. The notes hold the decision and who was in the room. Not what was argued, not what was assumed, not what anyone predicted. So the organization cannot go back and see whether a decision rested on good information or whose objection turned out to be right. It has built itself so that it cannot learn who holds the best information, which is the one thing the first value depends on. Whose thinking counts, going by the description: people in the room, who are quick verbally, who can react to a frame they saw minutes ago, who already know the unwritten map of who decides what, and who come across well to their manager. The review measures impression because impression is the only thing the system records about a person. The presenter's thinking counts most, because with no pre-read the presenter's frame is the only frame in the room and everyone else is reacting to it. So each value on the page has a quieter version in practice. "Best information in the building" means the best information that gets spoken in the slot by someone who knows it is their place to speak. "Say the hard thing early" means say it in the first minutes of a discussion you could not prepare for, because no earlier moment exists. "Every voice at the table counts" means every voice that was at the table is counted; the notes count attendance, not contribution. None of this was chosen. It is a cognitive architecture that was assumed, and the assumption is that good thinking is fast, spoken, improvised and legible in the moment. That is one shape of thinking. The organization has built its whole decision path around that shape, and it has no instrument for noticing that it did. 2. The two thinkers The new senior manager gets the agenda that morning with nothing to work from. They arrive to slides they have never seen and a discussion that ends when the slot ends. They work things out step by step, so by the time they have worked it out, the room has moved on. If they take the material away and write the objection up properly, it is not on the agenda; the best case is that they mention it in passing, in the mode they are worst at, and the room hears a footnote said hesitantly. When they cannot tell whether a decision is theirs to make, because nothing says so, they either bring it to the meeting and look unsure or make it alone and look like they overstepped. Both read as judgment. At the end of the quarter their manager writes a paragraph about how they come across. It will say some version of quiet, slow, hard to read, over-prepares, needs more presence in leadership meetings. The rating follows the paragraph. When one of their written objections turns out to have been right, nothing connects it, because predictions are not in the record; if someone repeated the point aloud later, the room will remember that person. The organization will conclude that the manager is not senior-leadership material, and it will believe this was a fair read, because it holds no record that could contradict it. What the manager experiences is carrying the whole burden of translation, always slightly late to a conversation that has already moved, judged on a surface they cannot control. The AI is handed the documents that exist: an agenda with no pre-read, the presenter's slides, notes holding a decision and an attendance list, a review paragraph about impression, an org chart with no decision rights. So it sees outcomes without reasons, attendance without contribution, roles without authority. Asked why the organization decided something, it will either say it cannot tell or reconstruct a plausible reason from the slides, which restates the presenter's case as the organization's reasoning and erases the discussion a second time. Asked who decides something, it will read the org chart and treat title as authority, which is exactly the question nobody has answered. Asked to summarize a meeting, it will faithfully produce the decision and who was there. And because each person runs it privately on their own partial set, there are now several different analyses in the room, each coherent, none shared, each carried in as if it were the same picture. Its outputs will be fluent and confident, and that is the same trap in reverse: the manager is under-trusted because of how they come across, the AI is over-trusted for the same reason. The organization will conclude either that the tool is a great time-saver, because its summaries match the slides, or that it makes things up, because it cannot explain a decision. Both conclusions are about the tool. Neither is about the record it was handed. The two are the same test. Both need the reasoning to exist outside the room, in writing, before the decision. The organization does not produce that, and it will blame each of them for the absence. The difference is that people expect to check a machine and do not expect to check their read of a colleague, so the AI's failure will get noticed and the manager's will be filed as a fair assessment. The person has earned more diagnostic care than the machine, and here gets less. 3. What to design differently The page's values are not lived because they are addressed to individuals and the system routes around them. Each change below alters a document, a meeting, a channel or a role so that the value becomes the default path rather than an act of courage. The pre-read replaces the slides (document, meeting). Every decision item gets a written memo, sent two working days before the meeting, stating the decision being asked for, the options, the assumptions, what the author predicts will happen under each option, and what would change their mind. The agenda closes when the memos go out; a same-morning item is an emergency and is labeled one. The slot no longer opens with a presentation; it opens on the assumption the memo was read, with a few minutes of silent reading for anyone who could not. This makes the first value true: the best information can be prepared, checked and challenged instead of improvised against a frame seen minutes ago. It is also the precondition for the second, because candor now has an "early" to land in. The objection lane (channel, meeting). Every memo carries a window for written objections, and every objection filed before the meeting goes on the agenda as its own line, read into the room by the chair, not the author. The author does not say it twice and does not say it in the mode they are worst at. This makes "say the hard thing early" true: there is a moment before the room, a channel that belongs to it, and no penalty for using it. The decision record replaces the notes (document). Each decision records the decision, the reasoning, the assumptions relied on, the objections raised and how each was resolved, the dissent that remained, and the predictions with a date by which they can be checked. This is what the first value actually needs: information that persists past the slot, so the organization can later see who held the best information on what. It is also the raw material for the next two changes. The prediction review (meeting). One standing item a quarter, where decision records whose check dates have passed are reopened and the predictions compared with what happened. Nobody is blamed; the point is that the person whose objection was right is now visibly right, in the record, and the organization learns where its good judgment sits. This makes candor rational instead of brave, which is the only way the second value survives contact with a career. The decision-rights page (document). One page that says, for each class of decision, who decides, who must be consulted first, who is told, and which decisions need the meeting at all. Maintained by the chief of staff. This makes the first value true in the other direction: a decision can be made where the information already is, without waiting a week for a slot, and nobody has to read the room to know whether a call is theirs. It also removes the trap the new manager would otherwise fall into. The review rewritten from the record (document, role). The paragraph about how a person comes across is replaced by a page drawn from the decision records: the calls they owned, the objections they filed, the predictions they made and how those resolved. The rating follows that page. Managers still write it, but from evidence the system produced rather than from impression. This makes "every voice at the table counts" true, because a voice now counts by what it contributed and contribution is written down. The written first round (meeting). Before open discussion on any decision item, every person at the table writes their position and their single biggest concern, and the chair reads them out. Two minutes, no exceptions. This makes the third value true by construction: every voice is counted before the fastest one sets the frame, and the step-by-step thinker's first contribution arrives at the same moment as everyone else's. The keeper of the record (role). The chief of staff owns the decision record, the objection lane, the decision-rights page and the prediction review, and reads objections into the room. Not the presenter, who has a case to make. The hard thing costs the sayer less when a role, not the person, carries it in. This underwrites the second value. The shared corpus for the AI (channel, document). One place holding the memos, the decision records, the decision-rights page and the prediction reviews, which every person's AI reads from, plus a small shared set of prompts for the standard questions: what did we decide and why, which objections are open, what did we predict and by when. People still ask their own questions; they ask them of the same record. This makes the first value true for the tool as well as the people: it now holds the best information in the building, the same for everyone, rather than a different fragment per person. It also turns the AI into a check on the record. If it cannot answer why a decision was made, the defect is in the record, and that is now visible. The test of the whole redesign is the two thinkers from the second question. After these changes, the new manager's written objection is on the agenda, read in by someone else, recorded, and checked against what happened; their review is written from their calls. The AI is reading the same reasoning the room read. Both were asking for the same thing, and it was never a favor to either of them. It was the page's values, made into a system.
The deliberate design of how thinking happens, in your inbox weekly. Free. No sales pitches. Unsubscribe any time.
Subscribe on Substack →Keynotes on cognitive architecture, the deliberate design of how thinking, decisions, and communication happen in organizations.
Speaking Inquiries →