Chapter 7: Learning His World

1280 Words
POV: Cara Mills By the end of my first week, I had a system. Not one Damien had given me. Not one anyone had taught me or handed to me on my first day. One I had built entirely myself, quietly and methodically, through careful observation of everything around me. It started with a notebook. Not a digital one. A small physical notebook, dark blue cover, that I kept in my desk drawer and pulled out every time I noticed something worth writing down. A pattern. A preference. A trigger. A small piece of information that told me more about how Damien Cole actually operated than any job description or onboarding document ever could have. By Friday evening, three pages were already filled with small careful notes that were starting to form a picture. --- The first thing I learned was his schedule. Damien arrived at seven-fifty every morning without fail. Not seven-forty-five. Not eight. Seven-fifty. Which meant if anything needed to be on his desk before he started working, it had to be there by seven-forty at the latest. I started arriving at seven-thirty. He took his coffee black. No sugar, no milk, nothing. I had figured that out from the mystery cup that had appeared on my desk on Monday — the one made exactly how I took mine, which told me he had been paying close attention to something as small as how I made my coffee in the break room that morning. It was a strange thing to notice about someone. So I started paying equal attention to how he made his. He read emails in order of sender, not subject. I noticed this on Tuesday when I was in his office dropping off a document and caught a glimpse of his inbox on the second screen. The hierarchy of who he responded to first wasn't about urgency or subject line — it was entirely about relationship. Richard Hartwell's emails got answered within minutes regardless of what they contained. Legal got answered within the hour. Board members got same-day responses. Everything else got answered when he got to it, on his own timeline. I adjusted how I flagged things accordingly. Sender first, then urgency. --- The second thing I learned was his triggers. Damien did not like surprises. Not bad ones, not good ones. If something was going to land on his desk, he wanted to know it was coming. So I started sending brief one-line previews before anything arrived. Legal has a question about the Meridian contract — sending through now. Board pack updated, coming to your inbox in five minutes. Small things. Things his previous assistant had probably never thought to do. He never acknowledged them. But he stopped asking me why things were showing up unannounced. He also didn't like inefficiency. Not in meetings, not in emails, not in conversation. I learned early that when I needed to update him on something, I had exactly three sentences before his attention moved elsewhere. So I got ruthlessly efficient. Subject. Status. Next step. That was it. No padding. No context he didn't need. By Wednesday he had stopped cutting me off mid-update. I noted that in my notebook too. --- The third thing I learned was what nobody talked about. There was a rhythm to the office that only became visible once you stopped trying to find your feet and started watching instead. The way the senior team fell quiet when Damien walked into a room. The way his EA from two years ago — a quiet man named David who now worked in operations — would sometimes glance toward Damien's office with an expression I couldn't quite read. Not fear exactly. Something more complicated than that. I asked David about it once, casually, over coffee in the break room on Thursday. He was quiet for a moment. Then he said: "He wasn't always like this." I waited. "He used to be different. More — " He stopped. Shook his head. "Just do your job well and don't take it personally. That's the best advice I can give you." He picked up his coffee and walked out without looking back. I sat with that for a long time, turning it over in my head. He wasn't always like this. --- I saw both sides of that on Wednesday afternoon. Damien had called a last-minute team meeting — twenty minutes notice, everyone scrambling. I was in the corridor when it started and caught the tail end of it through the open door. A junior analyst named Priya was presenting numbers from a site acquisition report. She was nervous. I could see it from where I stood — the slight tremor in her hands as she held her tablet, the way she spoke a little too fast. She made an error. A calculation that didn't add up. Small, but Damien caught it immediately. "That figure is wrong," he said. Flat. No softening. Priya froze. "I — I think I may have used last quarter's—" "Don't guess," Damien said. "If you don't know, say you don't know. Don't stand in front of this team and speculate." The room went very still. Priya nodded. Her face was tight. "I'll correct it and resend." "Do that." He moved on without another word. The meeting continued. Priya sat down and stared at her tablet. I stepped away from the door. Twenty minutes later, as people filed out, I watched Damien stop beside Priya's chair. He didn't crouch down or soften his expression. He just said, quietly enough that I almost missed it: "The methodology was correct. Just the input data. Fix the source and the rest holds." Then he walked away. Priya looked up. Blinked. Like she wasn't sure what had just happened. I wasn't sure either. "He had made her mistake visible to the entire room and then privately reminded her the work itself wasn't bad." I added two lines to my notebook that evening. He will embarrass you publicly without hesitation. He will also quietly tell you you're not as wrong as he made you feel. I didn't know what to do with that yet. --- What I noticed most was the gap between what Damien asked for and what he actually needed. He would send a three-line email requesting a document. But the document was never really the point. Once I understood that, I stopped getting him what he asked for and started getting him what he needed. The first time I did it, he came out of his office holding a briefing pack I had prepared for a Thursday lunch meeting. Standard summary — plus a one-page background note on the client with two talking points I thought might be useful. He stood in my doorway. "I didn't ask for this," he said. "No," I said. He looked at it. Went back to his office without another word. That afternoon I heard him use one of the talking points through the partly open conference room door. The client laughed. The meeting shifted. I added a line to my notebook. He reads everything you give him, even when he pretends not to. --- The man the internet had spent a week declaring a monster was more complicated than any viral video could capture. I wasn't naive enough to excuse how he had treated Maya Chen. What she described was real and it was wrong. But Damien Cole was clearly not just one thing. I closed my notebook at five-thirty on Friday and put it back in my drawer. Something told me I had barely scratched the surface. That thought sat with me all the way home.
Free reading for new users
Scan code to download app
Facebookexpand_more
  • author-avatar
    Writer
  • chap_listContents
  • likeADD