There was a moment, early in the transition, when the CEO had believed the culture could be transferred. Not naively. Not with the uncomplicated optimism of someone who had not thought carefully about what culture is and how it works and why organisations that try to specify it in documents almost always produce something that looks like the culture and does not feel like it. The CEO had thought carefully about all of these things. Had added the Cultural Alignment Obligations clause to the contract. Had pushed back on the Handling Difficult Customers section of the script. Had approved the empathy-led resolution workshop. Had read Appendix C and identified what was missing from it. All of this was real thinking. None of it had been enough. The CEO understood now why it had not been enough and the understanding was uncomfortable in the specific way that understanding is uncomfortable when it arrives after the cost of not understanding has already been paid. Culture is not a document. Culture is not a training programme. Culture is not a set of values on a wall or a mission statement in an employee handbook or a rubric with eleven categories that scores customer interactions on a defined scale. Culture is what people do when the situation is not covered by any of those things. When the script runs out. When the rubric does not apply. When the customer's problem is partly the company's responsibility and partly not and the agent has to decide, in real time, without a policy to reference or a team lead to consult, what kind of company they are representing. In those moments the culture is visible. Or it is not. The harassment training had taken place the previous week. The CEO had attended. Not because the CEO was required to attend. Because the CEO had decided, before the training was scheduled, that the first signal the company sent about the training was whether the person at the top of the organisation was in the room for it or had sent someone in their place. The room was full. Forty-three people. Marco was in the second row. Iris was near the back, near the door, with the specific positioning of someone who needs to be able to leave without being noticed if leaving becomes necessary. The facilitator was direct and specific. She did not use the case studies as abstract exercises. She used them as opportunities to ask the room what they would have done and why, and the room answered with the particular honesty of people who are thinking about real situations rather than hypothetical ones. At one point the facilitator asked: what is the difference between persistence and harassment? The room was quiet for a moment. Then Owen, who was in the third row with the pen behind his ear, said: "Intent doesn't change impact." The facilitator looked at him. "Say more," she said. "The impact on the person being persisted with is real regardless of what the person persisting intends," said Owen. "The question isn't whether the person meant harm. The question is whether the harm is there." The facilitator said that was exactly right and moved on. Owen did not say anything else for the rest of the session. But the room had shifted slightly after what he said, in the way that rooms shift when something has been put into words that people were thinking but had not yet said.

The CEO had been thinking about a conversation from the early days. Not a significant conversation at the time. The kind of conversation that happens in small companies between people who are working closely together and who talk about the work in the way that people talk about things they find genuinely interesting, which is to say without agenda, following the thought wherever it goes, arriving at conclusions that were not planned at the beginning of the conversation. The conversation had been with Maya. They had been talking about a customer who had called with a problem that was unusual, the kind of problem that revealed something about how the product was being used that the team had not anticipated. Maya had resolved the problem and had added an entry to the green notebook and had then said something that the CEO had not thought about again until now. "The interesting thing is not the problem," said Maya. "The interesting thing is that she found a way to use the product that we did not design for, and the way she found is actually better than the way we designed. She is solving the problem we were trying to solve in a way we did not think of." "What are you going to do with that?" said the CEO. "Tell the product team," said Maya. "And add it to the notebook so the next person who talks to a customer trying to do the same thing knows what the best approach is." "What if we built that into the product directly?" said the CEO. "I was going to suggest that," said Maya. That conversation had led to a product feature that was now one of the most used in the entire product. A feature that existed because a customer had found a better way to solve her own problem, and Maya had been curious enough to understand what the customer was doing rather than simply resolving the immediate issue, and the CEO had been in the habit of walking through the support area and stopping to talk to the people doing the work. The CEO thought about this conversation now and thought about whether a version of it was happening anywhere in the current structure. Whether the provider's agents, working from a script, measured against Appendix C, managed by team leads who were accountable to an account director who reported through a corporate structure that was several layers removed from the CEO, were having conversations with customers that revealed something new and important about how the product was being used. Whether those conversations, if they were happening, were being captured anywhere. Whether there was a green notebook equivalent. Whether there was a Maya equivalent. Whether there was a moment in the provider's operation where someone said: the interesting thing is not the problem, and then followed that thought to a product feature that three years later half the customers would consider essential. On the provider side, Gil had been capturing them. Not because anyone asked him to. Because he had read the Cultural Alignment Obligations clause on page eighty-nine three times and had understood it to mean something specific, which was that the conversations his agents were having with customers were not just transactions but sources of information, and that the information was not being sent anywhere, and that this was a problem. He had created a simple document. A shared file that he had described to his twelve agents as a place to put the interesting thing. Not the resolution. Not the outcome. The interesting thing. The thing the customer said that was not in the script. The thing the customer was doing with the product that was not in the user guide. The thing that made the agent think: I don't know what to do with this, but someone should. By the third month there were forty-seven entries in the document. Gil read all forty-seven entries every week. He had added comments to eight of them that he thought were significant enough to warrant attention from the product team or the client's operational team. He had sent the document to his manager. His manager had acknowledged it. Had said he would pass it to Jonathan. He did not know what happened after that. Three of the forty-seven entries would have significantly improved the product if they had reached the product team. One of them described a use case that would have prevented the processing error if it had been incorporated into the testing framework. The document sat in a folder.

The CEO called Dom. Dom was the account coordinator from the provider who had forwarded Elena's email with the note that said thought you should see this one. The CEO had been thinking about that note. About the judgment it represented. Dom had not been required to forward the email. The email had arrived through the general contact address and would have been routed through the normal triage process and would have received a professional and appropriate response drafted according to the established guidelines. Dom had made a decision, independently, that this particular email warranted a different kind of attention and had acted on that decision. That was a small thing. It was also exactly the kind of small thing that defined what a culture was or was not. The CEO asked Dom to come in for a conversation. Dom arrived at the arranged time and sat across the desk with the slightly cautious expression that most people brought to unscheduled conversations with a CEO, the expression that contains the question: is this good or not good, and the effort to remain professionally neutral while the question is being answered. "I want to ask you about the email you forwarded," said the CEO. "Elena's email." "Yes," said Dom. "Why did you forward it?" said the CEO. "She was not complaining," said Dom. "She was explaining. There is a difference and it is easy to miss if you are looking for the complaint rather than listening to what the person is actually saying. She was describing something she had noticed changing and she was describing it carefully and in good faith and I thought the right person to read it was the person who could actually do something about what she was describing." "That is not in your job description," said the CEO. "No," said Dom. "And it is not in the operating procedures," said the CEO. "No," said Dom. "I checked afterward, actually. It is not." "So why did you do it?" said the CEO. "Because it seemed like the right thing to do," said Dom. The CEO looked at Dom for a moment. "How long have you been with the provider?" said the CEO. "Three years," said Dom. "This is my fourth client assignment." "And in the previous three assignments," said the CEO. "Did you do things that were not in your job description or the operating procedures because they seemed like the right thing to do?" Dom thought about this. "Sometimes," said Dom. "Not often. It depends on the client and on what the situation requires and on whether the structure makes it possible." "What does that mean?" said the CEO. "Whether the structure makes it possible." "In some assignments the structure is very clear about what is expected and very clear about the boundaries and the expectation is that you operate within those boundaries and escalate anything that falls outside them," said Dom. "In those assignments you learn quickly that acting outside the boundaries, even with good intentions, creates friction. So you stop." "And in this assignment?" said the CEO. "This one feels different," said Dom. "I am not sure I can explain exactly why. Something about the company. About the way the people here, the ones who are left, talk about the work. I wanted to be part of that and the way I knew how to be part of it was to do things that seemed right rather than things that were specified." "The people who are left," said the CEO. "Meaning Maya and Joel." "And others," said Dom. "But yes, mostly them. They talk about the company in a way that makes you want to be useful to it in a real way rather than a contracted way." The CEO sat with this for a moment. Then Dom said something he had not planned to say. "There is someone on our team you should know about," said Dom. "Tell me," said the CEO. "Gil is the team lead for the agent group," said Dom. "He has been doing things that nobody above him in our structure knows he is doing. He built a coaching supplement for the script gaps. He created a shared document for agents to capture the things customers say that don't fit the script. He escalated the account type issue that produced the processing error three weeks before the error occurred." The CEO was quiet. "Why are you telling me this?" said the CEO. "Because he is trying to do the thing the Cultural Alignment Obligations clause is asking for," said Dom. "And nothing is getting to you from his level. The structure between him and you has too many layers and the wrong incentives and he is doing the work without any of it being visible." The CEO sat with this. "If the structure changed," said the CEO. "If this company made a decision that changed what your role here looked like and what the relationship between you and the company looked like. Would you want to be part of that?" "I would want to understand what you mean," said Dom. "I know. I am not in a position to be specific yet. I am asking in principle," said the CEO. "In principle. Yes. I think so," said Dom. "Thank you. That is what I needed to know," said the CEO. Dom left the office and the CEO sat thinking about the conversation. About the thing Dom had said. Something about the company. About the way the people here talk about the work. That was the culture. Not the values document. Not the mission statement. Not the Cultural Alignment Obligations clause on page eighty-nine of a contract. The way people talked about the work when they were not being assessed on what they said. That thing had not been transferred. It had been maintained, residually, by the people who were still here. By Maya and Joel and the handful of others who had been part of the original company and who were still, in the way that Dom had described, talking about the work in a way that made other people want to be part of it in a real way rather than a contracted way. The culture had not been transferred to the provider. But it had not been entirely lost. It was still here. Diminished. Reduced to the people who carried it. But here.

There is a theory about culture that the CEO had held for a long time without ever quite articulating it. The theory was this. Culture is not created by leadership. Leadership creates the conditions in which culture either emerges or does not. The conditions are specific. They include proximity, meaning the people who define what good looks like are close enough to the people doing the work that the definition can travel through direct contact rather than through documents. They include consistency, meaning the behaviours that the culture values are visible in the decisions that leadership makes, especially the decisions that are difficult and where a different decision would have been easier. And they include time, meaning the culture has been present long enough that it has accumulated the kind of institutional depth that makes it self-sustaining, that allows it to survive the departure of individuals because it has become embedded in the practices and expectations of enough people that no single departure can dislodge it. The original company had all three of these conditions. The transition had disrupted all three simultaneously. Proximity was gone. The people doing the support work were in a different building, under a different management structure, accountable through a different chain. The people who defined what good looked like were no longer close enough to transmit the definition through direct contact. It had to travel through documents and training programmes and quality frameworks and coaching sessions, all of which were imperfect carriers of a thing that had originally traveled through presence. Consistency had been compromised. Not through dishonesty. Through the ordinary inconsistency that is produced when a decision is made, for legitimate reasons, that contradicts the values the organisation has been demonstrating through its behaviour. The company had valued people who stayed with a problem until it was sorted. The transition had created a structure in which staying with a problem until it was sorted was not what the people doing the work were incentivised to do, was not what Appendix C measured, was not what the script supported. Time had been reset. The provider's team was new to the work. New to the product. New to the customers. New to the specific texture of the problems the support function was designed to solve. They were accumulating experience at the pace that experience is always accumulated, which is to say slowly and through the particular education of making mistakes and seeing what happens and adjusting. The institutional depth that the original team had built over three years was not available to them. It was in the green notebooks and in the cabinets and in the heads of people who had left. The CEO understood all of this now. The question was what to do with the understanding. The CEO called a conversation with Maya and Joel together. Not a meeting. The distinction mattered. A meeting has an agenda and a purpose that is defined before it begins and outcomes that are measured against that purpose. A conversation follows the thought wherever it goes and arrives at conclusions that were not planned at the beginning. "I want to talk about what it would take to rebuild the conditions," said the CEO. "Which conditions?" said Maya. "Proximity. Consistency. Time," said the CEO. "Time is the one we cannot accelerate," said Joel. "I know," said the CEO. "I am asking about the other two." "Proximity means bringing the support function back inside," said Maya. "It means the people doing the work being physically and organisationally connected to the people who define what good looks like." "And consistency?" said the CEO. "Consistency means making decisions that are visible expressions of the values," said Maya. "Not just saying the values. Making decisions that cost something and that the organisation makes anyway because the values require it." "Give me an example," said the CEO. "Bringing people back who left," said Maya. "Offering them something real. Not a retention bonus. A genuine share in what gets built. That would be a decision that cost something and that expressed something about what the company actually believes about the people who built it." "Profit sharing," said the CEO. "Yes," said Maya. "And the people who would come back?" said the CEO. "Some of them," said Maya. "Not all. But some." "Priya," said Joel. "I know," said the CEO. There was a pause. "I do not know if Priya will come back," said the CEO. "I am going to ask her. But I want to be clear about something before I ask her. I am not asking her to come back to the same company that let her leave. I am asking her to help build a different one. That is a different conversation and it requires me to be honest about what was wrong with the first one." "That is the right way to ask," said Maya. "Yes," said the CEO. "The board," said Joel. "Joel is building the financial case," said the CEO. "When the case is ready we will have the conversation with the board. But I want to be clear about something. The financial case is how we get the board to say yes. It is not why we are doing this. We are doing this because it is the right thing to do for the customers and for the people and for the company that this was supposed to be." Maya and Joel were quiet for a moment. "I have not heard you say something like that since the first week," said Maya. "I know," said the CEO. "I should have said it more." "You are saying it now," said Maya. "Yes," said the CEO. They sat with that for a moment, the three of them, in the meeting room with the whiteboard and the four chairs, which was where the important conversations had always happened and which had been, in a way that none of them had ever articulated, the physical location of the culture that everyone else had been trying to transfer. It had been here all along. Smaller than it used to be. Quieter. But here. The CEO looked at the whiteboard. Joel's diagrams from months ago were still faintly visible underneath whatever had been written since. The layered writing on a whiteboard that is used regularly, the earlier marks never quite erased, always present beneath the current layer, visible if you knew where to look. The CEO thought: that is what culture is. The earlier marks never quite erased. Always present beneath the current layer. Visible if you know where to look. And if the people who can see it are still in the room.

End of Chapter 11

Writer's Thought:

The culture has not been transferred. It has not been lost either. It has been waiting. I do not know if waiting is enough.

Here is What is Broken. The CEO. The Culture Nobody Transferred.

MarvinPro | March 2026

marvinpro.com

Think Simple.