CHAPTER 18 — THE THING ABOUT TRUST
Monday arrived with the quality of Mondays that preceded important deadlines.
Su Wanqing had been tracking the Meridian response window since Friday — five working days from the deck submission, which placed the deadline at Thursday of this week. She had been tracking it the way she tracked all meaningful deadlines: not with anxiety, but with the specific attention of someone who understood that the period between action and result was not passive time. It was the time during which you prepared for all possible outcomes, including the ones you preferred not to think about.
She had prepared for a positive response. She had prepared for a request for revisions. She had prepared for a *no* — less likely, but possible, always possible when the work required the client to understand something they had not previously understood about themselves.
She had not prepared for what arrived at nine forty-seven.
The morning had been going well, which was perhaps why the email arrived with the specific quality of a thing that interrupted a trajectory rather than confirmed it. The rebranding work was progressing. The Meridian deck had been received. She had, for the first time in eleven weeks, started the day without the specific monitoring effort that the first weeks had required — the continuous management of distance, of register, of all the architectural scaffolding she had been maintaining. The morning had simply been work, and she had been doing it, and that had felt, for approximately two hours, like enough.
---
The email was from the lead contact at Meridian's brand strategy division — a name she had been in correspondence with since the deck went out, a professional who had communicated with the efficient warmth of someone who had seen many pitches and had specific views about what made them worth pursuing.
She read it twice before she understood what it was saying.
The language was careful, professional, the kind of language that communicated a problem while leaving all interpretations technically open. *Certain elements of the proposed direction have been discussed in wider circles than expected.* This meant: information from the deck had gotten out. *Temporarily pausing our review process pending clarification.* This meant: they were not rejecting the pitch, but they were not proceeding either, and the reason was not the work itself.
Someone had shared the pitch content outside the intended distribution.
She read it a third time.
Then she opened a new email, typed the address at the top, and forwarded it without subject line, without body text, without any comment at all. The email spoke for itself. He would understand what it was saying as quickly as she had.
She put her hands flat on the desk and sat for a moment with the specific quality of a problem she had not been expecting and that required immediate, considered attention.
She was not going to panic. Panic was a response to situations where the available actions were unclear or impossible. She could see the available actions from where she was sitting. They were not easy, but they were clear.
She waited.
---
Six minutes later, the reply came.
*Come up. Now.*
Not the standard professional address. Not a meeting request through the calendar system. Not *Miss Su, could you come to the forty-second floor at your earliest convenience.* Three words with the specific quality of someone who had also read the email, had also understood what it meant, and was not interested in the formalities of managing the situation through the normal channels.
She closed her laptop.
She picked up her bag.
Tang Xin, at the adjacent workstation, looked up. Wanqing said: "Meridian situation. I'll explain later." Tang Xin nodded with the particular economy of someone who understood that *later* was the honest answer and that pressing for more right now would not be useful.
She took the lift.
---
Room forty-two, or his office — she was not certain which it would be, and it was the office, door open, Zhou Cheng not present. He was standing at the window. Not looking at anything specific — the posture of someone who had read something and was standing with it before deciding what to do.
He did not turn immediately when she came in.
She sat down. She opened her laptop. She did not wait to be asked.
"The deck was sent directly to Meridian's team with a cc to the internal project record," she said. "No automated forwarding. No external copy permissions. If someone shared content from it outside the intended recipients, they did so manually — by forwarding, sharing the file directly, or communicating the direction verbally."
He turned.
"Who had access?"
She had already run the list. "You, me, Zhou Cheng, and two members of the digital team who were asked to review the technical integration specifications before the final submission. Five people."
"Not Zhou Cheng," he said. It was not a question.
She looked at him. "Not me," she said.
He looked at her.
"I know," he said.
Two words. Delivered in the specific register of someone stating something that had already been established in their own understanding, not as reassurance offered to the other person but as a fact that was simply true and did not need elaboration. He had not said *of course not* or *I didn't think so* — both of which would have been comfort language, the language of someone managing a situation. He had said *I know*, which was different. *I know* meant he had already made this determination before she spoke. It meant he had arrived at the conversation with the conclusion already formed.
She noted this without being able to immediately do anything with it.
She filed it in the specific location in her attention that she used for things that required processing at a later point — the same location that held the observation about his register with Bai Yueru, the same location that held the accumulating evidence about the narrative she had been carrying and the ways it was not holding up. The location was getting full. She was going to have to open it properly at some point.
Not now. Now there was a crisis that required her full operational attention, and she was going to give it that.
"That leaves two people," she said. "One of them attended an external meeting last week with a party that has competitive interests adjacent to Meridian's new sector positioning." She turned her laptop toward him. She had pulled the meeting log from the shared calendar. "Not a conflict per se — no formal relationship. But the overlap exists."
He looked at the screen.
"Forward this to compliance," he said. "Flag it as a potential information security issue, not an accusation. Get them started on an internal review."
"Already drafted," she said. She sent the compliance referral as she was speaking.
He sat down across from her. Not at the head of the table — at the table, same side, approximately two seats between them. The working distance rather than the formal one. She noted this too.
"You said two voices," he said. Not yet agreeing or disagreeing — asking her to develop the position.
"Meridian is making a decision about whether to trust a working relationship," she said. "If the response to a breach of trust comes only from the executive level, it reads as containment — corporate machinery managing a problem. If it comes from both the executive level and the person whose work was compromised, it reads as a team that handles problems together." She looked at him. "The second version is more honest. We both have accountability here. It makes more sense for us both to speak to it."
He was quiet for a moment.
"And if they decide the two-voice approach suggests the problem is larger than it is?"
"Then we'll have accurately communicated that we're taking it seriously," she said. "Which is true. The alternative — appearing to minimise it with a single corporate response — risks more if Meridian's team is paying attention, which I think they are."
He was looking at the window again. She had learned to read this — when he looked at the window, he was processing a position, not resisting it. The looking at the window was the thinking, not the not-thinking.
"How do you want to handle the call?" he asked.
She looked at him.
Not *I'll schedule a call.* Not *prepare briefing materials for a call.* How do *you* want to handle it. As if the answer was hers to determine.
She understood, in that moment, what he was doing — or rather, what he was not doing. He was not making the decision and informing her of it. He was asking what she thought the decision should be, with the specific quality of someone who intended to take the answer seriously. This was different from anything he had done in the previous eleven weeks of working together.
She answered him.
"Meridian," he said.
"We can't wait for the internal investigation to conclude before we respond," she said. "Five working days is their review window. If we go dark while compliance does its work, they'll interpret the silence as either guilt or incompetence, and neither will serve us." She had been thinking through this since the lift. "We need to reach out today. Proactively. Explain what we know, what we're doing about it, and what we're prepared to offer in terms of remediation."
"What are you prepared to offer?"
She considered. "A revised confidentiality protocol for the remainder of the engagement. A supplementary deck section — new material they haven't seen, which demonstrates the direction hasn't been compromised. And a direct call between you and their lead contact, which signals executive attention and accountability."
He was quiet for a moment.
"You want to write the communication," he said. Again — not a question, not an instruction. An observation about what she was describing.
"I think it should come from both of us," she said. "A joint communication — your cover letter as CEO establishing accountability at the executive level, followed by my letter as lead creative explaining the work and the protection process." She paused. "Meridian is deciding whether to trust us with a six-month engagement. What they need to see is that the people they would be working with are the people handling this problem, not delegating it."
He looked at the window for a moment. The city outside was doing its Monday thing — the traffic, the movement, the ordinary machinery of a week beginning.
"Write it," he said. "Both letters. Bring them to me when they're drafted."
She pulled up a document and began.
She had written crisis communications before. Not often — the kind of crisis that required this level of management was, in her experience, either prevented by good process or too large to recover from through communication alone. But she had been in the middle of a few situations in her years at smaller studios where a client problem had required immediate, careful language, and she had learned that the quality of the response in the first twenty-four hours determined almost everything about the trajectory of the recovery.
The principle was simple: be specific, be accountable, be forward-looking. Do not be defensive, do not over-explain, do not make the communication about your own distress when what the other party needed was information about what would happen next.
She applied the principle. The words came with the specific ease of someone who had done something difficult enough times that the difficulty had become technique.
What she had not done, in the previous situations, was have someone sitting across the table reading over her shoulder in real time — or rather, reading when the drafts were ready, with the specific quality of attention she had come to associate with the forty-second floor. She was aware of this as she wrote. Not as distraction — as orientation. The knowledge that what she was producing was going to be read carefully by someone who would catch everything she had not caught, which raised the quality of her own attention to a pitch she did not always achieve when working alone.
This was, she recognised, the function of good collaboration. Not just the combining of perspectives, but the elevation of your own thinking through the knowledge of who you were thinking alongside.
---
The letters took forty minutes.
She wrote the CEO's letter first — because the framing of it determined the framing of everything else, because the executive accountability language needed to be precise without being corporate, because the tone had to communicate seriousness without communicating crisis. She drafted it, read it back, made four changes, and put it in front of him.
He read it. He changed one word — *issue* to *matter*, which was the correct change. He handed it back.
She wrote her own letter.
This one was harder. It required her to explain, without making excuses, the process by which the deck had been created and distributed, the specific safeguards that had been in place, and why those safeguards were sufficient to contain the damage. It required her to make a case not for the work itself but for the integrity of the process around the work — which was, in some ways, more difficult, because process was less visible than output and required more trust to accept.
She wrote it in twenty-five minutes. She read it back. She changed the opening paragraph, which had been too defensive, to something that led with action rather than explanation. She handed it to him.
He read it slowly. She watched him reading — the quality of his attention to it, the specific kind of slowness that was not hesitation but comprehension, the way he read things he was taking seriously rather than things he was scanning.
He looked up.
"The process paragraph," he said. "Third section. You're explaining what you did right. Lead with what you're going to do going forward instead. The past is already past — what Meridian needs from this letter is confidence about what comes next."
She looked at the paragraph. He was right. She made the change in three minutes.
"Good," he said. "Send them."
She assembled both letters into a single email, attached them, wrote a four-sentence cover note, and sent it.
They both looked at the sent notification.
---
Meridian replied at two forty-eight.
*Thank you for your prompt and thorough communication. We appreciate the transparency and the proactive steps being taken. We will resume our review process once the internal matter has been concluded. We look forward to continuing our conversation with your team.*
She read it. Then she read it again.
Not a yes. Not a no. A door that had not closed — held open, explicitly, by a team that had decided the response was sufficient to justify continued engagement. In the context of what the morning had contained, this was as good as it was going to get right now.
She set her laptop down.
He was reading it on his own screen. When he had finished, he looked at her.
"Good call," he said. "On the two-voice approach."
It was not praise in the way praise was usually delivered — with warmth, with the expressiveness of genuine appreciation. It was the specific assessment of someone evaluating a strategic decision and finding it correct. The difference mattered to her, because she had learned, in this building over the weeks, to read the register of his communications accurately, and this was the register of professional respect rather than personal warmth, and professional respect from this specific person, based on this specific morning's events, was not a small thing.
"Meridian needed to know they were dealing with both of us," she said. "Not a company that routes everything through one point of contact."
"Yes," he said.
A pause.
"The compliance review will take a few days," he said. "I'll keep you informed of the progress."
"Thank you." She stood, collected her things. "I'll update the project documentation to reflect the communication protocol changes."
He nodded.
She walked out.
---
In the lift, she stood with her hands at her sides and thought about *I know.*
She had said: *Not me.* He had said: *I know.* Not *I trust you* — not the language of feeling, which could be revoked or conditional or a product of wanting to believe something rather than knowing it. Just *I know.* The language of someone who had arrived at a conclusion through observation and had sufficient evidence to hold it without qualification.
She had been building her professional reputation piece by piece for three years. She had been careful about the projects she took and the clients she worked with and the quality of the documentation she left behind. She had learned, through some expensive mistakes in the early years, that reputation was not about proclamation — it was about accumulated evidence, the record of small decisions made consistently over time.
He had read three years of that record before she walked through the door.
He had been watching it accumulate for three months since.
*I know* meant he had sufficient evidence. Not faith. Evidence. This was, she understood, the specific language of a person who did not grant trust easily and had therefore granted it specifically.
The lift opened.
She walked back to her workstation and sat down and opened the project documentation and began to write the protocol update, and in the background, at the level below active thought, she held the weight of *I know* and what it meant about what he had been paying attention to, and for how long, and with what quality of attention.
It was, she thought, a strange thing to find clarifying.
It was also, she was honest enough to admit, more clarifying than she had expected it to be.
You've reached the end of this chapter
CHAPTER 18 — THE THING ABOUT TRUST
Monday arrived with the quality of Mondays that preceded important deadlines.
Su Wanqing had been tracking the Meridian response window since Friday — five working days from the deck submission, which placed the deadline at Thursday of this week. She had been tracking it the way she tracked all meaningful deadlines: not with anxiety, but with the specific attention of someone who understood that the period between action and result was not passive time. It was the time during which you prepared for all possible outcomes, including the ones you preferred not to think about.
She had prepared for a positive response. She had prepared for a request for revisions. She had prepared for a *no* — less likely, but possible, always possible when the work required the client to understand something they had not previously understood about themselves.
She had not prepared for what arrived at nine forty-seven.
The morning had been going well, which was perhaps why the email arrived with the specific quality of a thing that interrupted a trajectory rather than confirmed it. The rebranding work was progressing. The Meridian deck had been received. She had, for the first time in eleven weeks, started the day without the specific monitoring effort that the first weeks had required — the continuous management of distance, of register, of all the architectural scaffolding she had been maintaining. The morning had simply been work, and she had been doing it, and that had felt, for approximately two hours, like enough.
---
The email was from the lead contact at Meridian's brand strategy division — a name she had been in correspondence with since the deck went out, a professional who had communicated with the efficient warmth of someone who had seen many pitches and had specific views about what made them worth pursuing.
She read it twice before she understood what it was saying.
The language was careful, professional, the kind of language that communicated a problem while leaving all interpretations technically open. *Certain elements of the proposed direction have been discussed in wider circles than expected.* This meant: information from the deck had gotten out. *Temporarily pausing our review process pending clarification.* This meant: they were not rejecting the pitch, but they were not proceeding either, and the reason was not the work itself.
Someone had shared the pitch content outside the intended distribution.
She read it a third time.
Then she opened a new email, typed the address at the top, and forwarded it without subject line, without body text, without any comment at all. The email spoke for itself. He would understand what it was saying as quickly as she had.
She put her hands flat on the desk and sat for a moment with the specific quality of a problem she had not been expecting and that required immediate, considered attention.
She was not going to panic. Panic was a response to situations where the available actions were unclear or impossible. She could see the available actions from where she was sitting. They were not easy, but they were clear.
She waited.
---
Six minutes later, the reply came.
*Come up. Now.*
Not the standard professional address. Not a meeting request through the calendar system. Not *Miss Su, could you come to the forty-second floor at your earliest convenience.* Three words with the specific quality of someone who had also read the email, had also understood what it meant, and was not interested in the formalities of managing the situation through the normal channels.
She closed her laptop.
She picked up her bag.
Tang Xin, at the adjacent workstation, looked up. Wanqing said: "Meridian situation. I'll explain later." Tang Xin nodded with the particular economy of someone who understood that *later* was the honest answer and that pressing for more right now would not be useful.
She took the lift.
---
Room forty-two, or his office — she was not certain which it would be, and it was the office, door open, Zhou Cheng not present. He was standing at the window. Not looking at anything specific — the posture of someone who had read something and was standing with it before deciding what to do.
He did not turn immediately when she came in.
She sat down. She opened her laptop. She did not wait to be asked.
"The deck was sent directly to Meridian's team with a cc to the internal project record," she said. "No automated forwarding. No external copy permissions. If someone shared content from it outside the intended recipients, they did so manually — by forwarding, sharing the file directly, or communicating the direction verbally."
He turned.
"Who had access?"
She had already run the list. "You, me, Zhou Cheng, and two members of the digital team who were asked to review the technical integration specifications before the final submission. Five people."
"Not Zhou Cheng," he said. It was not a question.
She looked at him. "Not me," she said.
He looked at her.
"I know," he said.
Two words. Delivered in the specific register of someone stating something that had already been established in their own understanding, not as reassurance offered to the other person but as a fact that was simply true and did not need elaboration. He had not said *of course not* or *I didn't think so* — both of which would have been comfort language, the language of someone managing a situation. He had said *I know*, which was different. *I know* meant he had already made this determination before she spoke. It meant he had arrived at the conversation with the conclusion already formed.
She noted this without being able to immediately do anything with it.
She filed it in the specific location in her attention that she used for things that required processing at a later point — the same location that held the observation about his register with Bai Yueru, the same location that held the accumulating evidence about the narrative she had been carrying and the ways it was not holding up. The location was getting full. She was going to have to open it properly at some point.
Not now. Now there was a crisis that required her full operational attention, and she was going to give it that.
"That leaves two people," she said. "One of them attended an external meeting last week with a party that has competitive interests adjacent to Meridian's new sector positioning." She turned her laptop toward him. She had pulled the meeting log from the shared calendar. "Not a conflict per se — no formal relationship. But the overlap exists."
He looked at the screen.
"Forward this to compliance," he said. "Flag it as a potential information security issue, not an accusation. Get them started on an internal review."
"Already drafted," she said. She sent the compliance referral as she was speaking.
He sat down across from her. Not at the head of the table — at the table, same side, approximately two seats between them. The working distance rather than the formal one. She noted this too.
"You said two voices," he said. Not yet agreeing or disagreeing — asking her to develop the position.
"Meridian is making a decision about whether to trust a working relationship," she said. "If the response to a breach of trust comes only from the executive level, it reads as containment — corporate machinery managing a problem. If it comes from both the executive level and the person whose work was compromised, it reads as a team that handles problems together." She looked at him. "The second version is more honest. We both have accountability here. It makes more sense for us both to speak to it."
He was quiet for a moment.
"And if they decide the two-voice approach suggests the problem is larger than it is?"
"Then we'll have accurately communicated that we're taking it seriously," she said. "Which is true. The alternative — appearing to minimise it with a single corporate response — risks more if Meridian's team is paying attention, which I think they are."
He was looking at the window again. She had learned to read this — when he looked at the window, he was processing a position, not resisting it. The looking at the window was the thinking, not the not-thinking.
"How do you want to handle the call?" he asked.
She looked at him.
Not *I'll schedule a call.* Not *prepare briefing materials for a call.* How do *you* want to handle it. As if the answer was hers to determine.
She understood, in that moment, what he was doing — or rather, what he was not doing. He was not making the decision and informing her of it. He was asking what she thought the decision should be, with the specific quality of someone who intended to take the answer seriously. This was different from anything he had done in the previous eleven weeks of working together.
She answered him.
"Meridian," he said.
"We can't wait for the internal investigation to conclude before we respond," she said. "Five working days is their review window. If we go dark while compliance does its work, they'll interpret the silence as either guilt or incompetence, and neither will serve us." She had been thinking through this since the lift. "We need to reach out today. Proactively. Explain what we know, what we're doing about it, and what we're prepared to offer in terms of remediation."
"What are you prepared to offer?"
She considered. "A revised confidentiality protocol for the remainder of the engagement. A supplementary deck section — new material they haven't seen, which demonstrates the direction hasn't been compromised. And a direct call between you and their lead contact, which signals executive attention and accountability."
He was quiet for a moment.
"You want to write the communication," he said. Again — not a question, not an instruction. An observation about what she was describing.
"I think it should come from both of us," she said. "A joint communication — your cover letter as CEO establishing accountability at the executive level, followed by my letter as lead creative explaining the work and the protection process." She paused. "Meridian is deciding whether to trust us with a six-month engagement. What they need to see is that the people they would be working with are the people handling this problem, not delegating it."
He looked at the window for a moment. The city outside was doing its Monday thing — the traffic, the movement, the ordinary machinery of a week beginning.
"Write it," he said. "Both letters. Bring them to me when they're drafted."
She pulled up a document and began.
She had written crisis communications before. Not often — the kind of crisis that required this level of management was, in her experience, either prevented by good process or too large to recover from through communication alone. But she had been in the middle of a few situations in her years at smaller studios where a client problem had required immediate, careful language, and she had learned that the quality of the response in the first twenty-four hours determined almost everything about the trajectory of the recovery.
The principle was simple: be specific, be accountable, be forward-looking. Do not be defensive, do not over-explain, do not make the communication about your own distress when what the other party needed was information about what would happen next.
She applied the principle. The words came with the specific ease of someone who had done something difficult enough times that the difficulty had become technique.
What she had not done, in the previous situations, was have someone sitting across the table reading over her shoulder in real time — or rather, reading when the drafts were ready, with the specific quality of attention she had come to associate with the forty-second floor. She was aware of this as she wrote. Not as distraction — as orientation. The knowledge that what she was producing was going to be read carefully by someone who would catch everything she had not caught, which raised the quality of her own attention to a pitch she did not always achieve when working alone.
This was, she recognised, the function of good collaboration. Not just the combining of perspectives, but the elevation of your own thinking through the knowledge of who you were thinking alongside.
---
The letters took forty minutes.
She wrote the CEO's letter first — because the framing of it determined the framing of everything else, because the executive accountability language needed to be precise without being corporate, because the tone had to communicate seriousness without communicating crisis. She drafted it, read it back, made four changes, and put it in front of him.
He read it. He changed one word — *issue* to *matter*, which was the correct change. He handed it back.
She wrote her own letter.
This one was harder. It required her to explain, without making excuses, the process by which the deck had been created and distributed, the specific safeguards that had been in place, and why those safeguards were sufficient to contain the damage. It required her to make a case not for the work itself but for the integrity of the process around the work — which was, in some ways, more difficult, because process was less visible than output and required more trust to accept.
She wrote it in twenty-five minutes. She read it back. She changed the opening paragraph, which had been too defensive, to something that led with action rather than explanation. She handed it to him.
He read it slowly. She watched him reading — the quality of his attention to it, the specific kind of slowness that was not hesitation but comprehension, the way he read things he was taking seriously rather than things he was scanning.
He looked up.
"The process paragraph," he said. "Third section. You're explaining what you did right. Lead with what you're going to do going forward instead. The past is already past — what Meridian needs from this letter is confidence about what comes next."
She looked at the paragraph. He was right. She made the change in three minutes.
"Good," he said. "Send them."
She assembled both letters into a single email, attached them, wrote a four-sentence cover note, and sent it.
They both looked at the sent notification.
---
Meridian replied at two forty-eight.
*Thank you for your prompt and thorough communication. We appreciate the transparency and the proactive steps being taken. We will resume our review process once the internal matter has been concluded. We look forward to continuing our conversation with your team.*
She read it. Then she read it again.
Not a yes. Not a no. A door that had not closed — held open, explicitly, by a team that had decided the response was sufficient to justify continued engagement. In the context of what the morning had contained, this was as good as it was going to get right now.
She set her laptop down.
He was reading it on his own screen. When he had finished, he looked at her.
"Good call," he said. "On the two-voice approach."
It was not praise in the way praise was usually delivered — with warmth, with the expressiveness of genuine appreciation. It was the specific assessment of someone evaluating a strategic decision and finding it correct. The difference mattered to her, because she had learned, in this building over the weeks, to read the register of his communications accurately, and this was the register of professional respect rather than personal warmth, and professional respect from this specific person, based on this specific morning's events, was not a small thing.
"Meridian needed to know they were dealing with both of us," she said. "Not a company that routes everything through one point of contact."
"Yes," he said.
A pause.
"The compliance review will take a few days," he said. "I'll keep you informed of the progress."
"Thank you." She stood, collected her things. "I'll update the project documentation to reflect the communication protocol changes."
He nodded.
She walked out.
---
In the lift, she stood with her hands at her sides and thought about *I know.*
She had said: *Not me.* He had said: *I know.* Not *I trust you* — not the language of feeling, which could be revoked or conditional or a product of wanting to believe something rather than knowing it. Just *I know.* The language of someone who had arrived at a conclusion through observation and had sufficient evidence to hold it without qualification.
She had been building her professional reputation piece by piece for three years. She had been careful about the projects she took and the clients she worked with and the quality of the documentation she left behind. She had learned, through some expensive mistakes in the early years, that reputation was not about proclamation — it was about accumulated evidence, the record of small decisions made consistently over time.
He had read three years of that record before she walked through the door.
He had been watching it accumulate for three months since.
*I know* meant he had sufficient evidence. Not faith. Evidence. This was, she understood, the specific language of a person who did not grant trust easily and had therefore granted it specifically.
The lift opened.
She walked back to her workstation and sat down and opened the project documentation and began to write the protocol update, and in the background, at the level below active thought, she held the weight of *I know* and what it meant about what he had been paying attention to, and for how long, and with what quality of attention.
It was, she thought, a strange thing to find clarifying.
It was also, she was honest enough to admit, more clarifying than she had expected it to be.
You've reached the end of this chapter