The contract was one hundred and twelve pages long. This was not unusual. Contracts between companies and outsourcing providers are long by necessity, because the relationship they are describing is complex and the consequences of misunderstanding are expensive and the lawyers on both sides are paid to anticipate every possible version of things going wrong and to describe, in language precise enough to survive a dispute, exactly what happens when they do. The CEO had read all one hundred and twelve pages. Not because the CEO always read contracts in full, though the CEO had a habit of reading more than most people in the same position considered necessary, a habit formed early in a career that had included one experience of not reading something carefully enough and paying a price for it that was educational in the specific way that expensive mistakes are educational. The CEO had read this contract because the contract was describing something important and because the lawyers could tell you what it said but could not tell you what it meant, which are different things and the difference matters. What the contract said was comprehensive. What it meant was more complicated.

The service level agreements occupied fourteen pages of the contract and three appendices. They covered response time. First contact resolution rate. Customer satisfaction score, measured by a post-interaction survey that the provider would administer using a methodology they had developed and that had been reviewed and approved by both parties. Quality assurance, measured by a sampling process in which the provider would review a defined percentage of interactions each month and score them against a rubric that was attached as Appendix C. The CEO had spent a long time with Appendix C. Appendix C was a scoring rubric for customer interactions. It had eleven categories. Each category had a defined score range and a description of what good performance in that category looked like. The categories covered things like greeting the customer correctly, identifying the issue accurately, providing an accurate resolution, following the correct escalation process when the issue could not be resolved at first contact, closing the interaction in the approved manner. The CEO read through all eleven categories twice. Then looked for the category that covered staying with a problem for forty minutes because leaving it unsorted was not something the person considered. It was not there. Not because the people who wrote Appendix C were incompetent. Because the thing it was trying to measure is not measurable in the way that Appendix C was designed to measure things. The instinct that Priya had, the genuine ownership of a customer's problem that extended beyond the defined scope of the interaction, is not a category. It is a culture. And cultures do not fit in appendices. The CEO made a note in the margin of the contract. The note said: this is what we are not measuring. Looked at the note for a moment and then closed the contract and thought about whether there was a way to add what was missing and concluded, correctly, that there was not, not in a way that the contract could enforce, not in a way that a monthly quality review could assess, not in a way that any external provider could be held accountable for in a quarterly business review. The CEO did not add anything to the contract. The intellectual property clauses were on pages forty-seven through fifty-three. They established that the customer data processed by the provider in the course of providing the service remained the property of the company. That the provider would implement appropriate technical and organisational measures to protect that data. That the provider would notify the company within seventy-two hours of becoming aware of any data breach or security incident. That the provider would not use the data for any purpose other than the provision of the contracted service. The CEO read these clauses carefully. They were standard. They were appropriate. They reflected the legal requirements of the jurisdictions in which the company operated and the additional protections that the company's own lawyers had negotiated into the standard terms of the provider. What they did not cover was the gap between what the clauses required and what happened in practice in a large outsourcing operation where the people handling customer data were employees of the provider, working in facilities operated by the provider, using systems owned and maintained by the provider, supervised by managers whose primary accountability was to the provider and only secondarily, through the contract, to the company. The CEO knew this gap existed. Every company that outsources its customer-facing operations knows this gap exists. The contract describes the required standard. The distance between the required standard and the actual practice is filled by the culture and the management and the specific operational decisions of the provider, none of which the company controls and most of which the company cannot see. The CEO had asked Jonathan about this in one of the preliminary conversations. "Our data protection practices are certified to ISO 27001 and we undergo annual third-party audits," said Jonathan. "We take our obligations to our clients' data extremely seriously." "I am sure you do," said the CEO. "I am asking about the gap between the standard and the practice." "I am not sure I understand what you mean," said Jonathan. The CEO had let it go. Not because the question had been answered. Because some questions produce a certain kind of non-answer that is itself informative, the non-answer being: we are not going to have this conversation in a way that threatens the deal, and the information being: the gap exists and we both know it and we have agreed, implicitly, to proceed anyway. The CEO had proceeded anyway.

The knowledge transfer provisions were on pages sixty-one through sixty-eight. They required the provider to complete a discovery process of no less than four weeks. They required the provider to develop a knowledge transfer plan within two weeks of the contract signing. They required the company to provide reasonable access to documentation, systems and personnel during the discovery period. They required both parties to agree on a knowledge transfer completion standard before the parallel operation phase began. The CEO had negotiated these provisions carefully. More carefully than the provider had expected, which Jonathan had mentioned, diplomatically, in one of the later rounds of negotiation, framing it as a reflection of the company's admirable commitment to a thorough transition process. The CEO had not corrected Jonathan's interpretation. The careful negotiation was not about administrative thoroughness. It was about the green notebooks. About the three years of accumulated knowledge that Maya had spent two weeks organising and annotating and contextualising in preparation for the discovery phase. About the specific and irreplaceable understanding of why the support function worked the way it did that lived in the heads of Sandra and the fourteen people who would be leaving and in the institutional memory of the thirty-one people who had been offered positions with the provider and had not yet decided whether to take them. The contract required the knowledge to be transferred. It did not, could not, specify what transferred knowledge actually looked like. It described a process. It described a standard. It described consequences if the standard was not met. What it could not describe was the difference between a team that had absorbed three years of institutional context and a team that had completed a four-week discovery process and could correctly answer the questions on the knowledge transfer assessment. Those are different things. The CEO knew they were different things. The CEO had tried, within the constraints of what a contract can specify, to make them less different. Had added provisions requiring the discovery team to spend time not just with the documentation but with the people. Had required the knowledge transfer plan to include sessions with Sandra, with Maya, with the senior members of the support team who had been there long enough to carry the kind of knowledge that does not live in documents. Jonathan had agreed to all of these provisions with the ease of someone agreeing to things that sound significant and are not unreasonable and that will be implemented with the level of rigour that a busy transition team implements things that are not on the critical path. The CEO had signed the contract. There was one clause the CEO had added personally, over the objection of the company's own lawyers, who considered it unusual and potentially difficult to enforce. The clause was on page eighty-nine. It was titled: Cultural Alignment Obligations. It said, in language that the lawyers had made more precise than the CEO's original draft but that still contained the essential intention: the provider acknowledges that the company's customer service culture is a material component of the value being delivered to customers and agrees to take reasonable steps to understand, preserve and transmit that culture within the provider's team responsible for delivering the service. The lawyers had pointed out that cultural alignment obligations were difficult to measure, difficult to enforce and unlikely to survive a dispute in a way that produced a meaningful remedy. "I know," said the CEO. "Put it in anyway." The lawyers had put it in. Jonathan had signed it without comment, which was either a sign that Jonathan understood what the company was trying to protect and was committed to protecting it, or a sign that Jonathan had seen clauses like this before and knew from experience that cultural alignment obligations are the kind of thing that appears in contracts and does not appear in practice, the way many things appear in contracts and do not appear in practice, which is why the contract is one hundred and twelve pages long and the relationship it describes is still, ultimately, a human one. The CEO believed, at the time of signing, that it was the former.

Nora came to the CEO's office on a Tuesday in March. She sat down in the chair across the desk with the deliberate manner of someone who has decided to say something and has decided how they are going to say it. She was wearing a dark red cardigan over a white shirt. She had a small notebook on her knee that she did not open. "You said to ask again in the spring," said Nora. "I did," said the CEO. "I had the check-up," said Nora. "And then I had a follow-up. And then I had another one." She paused. "It is lymphoma. The slow kind, which is both the reassuring word and the wrong one to use because slow does not mean it is not there." The CEO did not say anything immediately. This was not avoidance. It was the recognition that there are moments that require a pause before a response and that the pause is itself a form of response. "What do you need?" asked the CEO. "For now, nothing," said Nora. "Treatment starts in six weeks. It will make me tired. There will be some days I am not here. I wanted to tell you before the absence became something you noticed and needed explained." "You don't need to explain anything," said the CEO. "I know," said Nora. "I am telling you anyway because I think you should know and because I would rather you know it from me than from someone else or from a pattern of empty desk days." "We will work around whatever you need," said the CEO. Nora looked at the CEO steadily. "That is what I hoped you would say," she said. "I want to keep working. The work helps. It gives the days a shape that is not about the illness." "Then keep working," said the CEO. "We will adjust as we need to." Nora stood. She did not thank the CEO effusively, which was not her way. She said, "Good," in the specific tone that meant the conversation had gone the way it should have gone, and went back to her desk. The CEO sat for a moment after she left. Then opened the contract on the screen and returned to page sixty-one. The CEO gave the signed contract to the company's legal team on a Friday afternoon. On the way back to the office the CEO stopped in the support area. Not for any specific reason. Out of the habit, still mostly maintained, of staying connected to the work by being physically present in the places where the work happened. The support area was quieter than usual. Several desks were empty, the desks of people who had already decided, which meant they had already started the process of leaving in the invisible way that departure begins before the formal notice, the slight pulling back of attention, the conversations that are slightly more careful than they used to be, the future being weighed against the present in a private calculation that nobody announces. Sandra was at her desk. She looked up when the CEO came in. "The contract is signed," said the CEO. "I know," said Sandra. "Jonathan's team called this morning to arrange the start of the discovery phase." "How is the team?" asked the CEO. "They are processing it," said Sandra. "Some of them have decided to go with the provider. Some of them have not decided yet. Some of them have decided to leave and have not told me formally. I can tell from the way they are sitting." "From the way they are sitting," said the CEO. "When people have decided to leave they sit differently," said Sandra. "It is hard to explain. They are still doing the work but they are not quite in it the same way. There is a small amount of distance that was not there before." The CEO looked at the room. At the people at their desks. At the slight variations in posture and engagement that Sandra was describing, visible now that the CEO was looking for them. Callum and Yusuf were both at their desks on opposite sides of the room. The quality of the silence between them had changed in recent weeks. Not new, but changed. Sandra had described it in one of their regular conversations in the careful and specific way that Sandra described things she was managing. They are not going to resolve it themselves, Sandra had said. I want you to know this one is going to take longer than the others. The CEO had left it with her. Now, looking at the two of them, the CEO thought about what the transition would do to the dynamic. Whether the disruption would resolve it or compound it. "Is Priya's desk going to stay empty?" asked the CEO. "For now," said Sandra. "We will see what the provider brings for the transition team." The CEO looked at Priya's desk. The headset was still there. A small plant that Priya had kept on the corner of the desk, the kind of small personalisation that people add to workspaces when they intend to be in them for a while, was still there too. The plant needed water. "Make sure someone waters that," said the CEO. "I will," said Sandra. The CEO said thank you and went back to the office and looked at the board presentation for the following week and thought about how to describe the signing of the contract and the beginning of the transition in a way that was accurate and appropriately positive and that captured the strategic rationale without getting into the things that could not be captured in a slide. Wrote three bullets. The first said: partnership with the provider formally established, transition commencing Q2. The second said: projected annual savings in line with Richard's model. The third said: knowledge transfer process initiated, full transition expected within six months. The CEO looked at the three bullets for a while. Then added a fourth. The fourth said: cultural alignment obligations included in contract. Looked at the four bullets. Then deleted the fourth one. It was the kind of thing that sounds like a reassurance and is actually an admission, and board presentations are not the place for admissions, which is one of the ways that board presentations become one of the gaps between what things say and what things are, the gap that runs, like a fault line, through every large organisation, visible to the people who know where to look and invisible to the people who do not. The CEO knew where to look. Saved the presentation and closed the laptop and went home. The plant on Priya's desk went unwatered for three days before anyone noticed.

End of Chapter 5

Writer's Thought:

The contract described what should happen. Nora described what was actually happening. I am not sure which document is harder to read.

Here is What is Broken. The CEO. The Contract.

MarvinPro | March 2026

marvinpro.com

Think Simple.