I Was Just Coasting at Work

At 8:17 on Monday morning, I watched my boyfriend promise a room full of people that I would work every night this week. I was standing beside the conference-room screen with a paper cup of coffee in one hand and the launch schedule in the other. Grant Mercer stood at the head of the table, wearing the navy jacket I had once told him made him look like a man who owned a sailboat. He did not own a sailboat. He did own a talent for sounding calm while volunteering someone else's time. "The client needs the onboarding portal live by Friday," he said. "Mara can handle the revised data flow. She knows the account better than anyone." Across the table, Dana Holt, our department head, glanced at me. "Can you?" I set down my coffee. "I can review the change request. I can't promise a Friday launch until we know what changed." Grant smiled as if I had just made a charming joke. "That's what I mean. She'll review it, fix whatever needs fixing, and get us there." The meeting room went quiet in the particular way people went quiet when somebody had already answered for them. I had spent two years at Larkspur Systems building the small operational systems that kept our clients' software launches from becoming expensive public disasters. I wrote timelines, checked permissions, translated vague requests into actual tasks, and politely asked people to stop calling a missing requirement "a minor detail." It was work I liked. It was also work I was good at, which had become a problem. Grant was a senior client strategist. He handled the meetings where people wore jackets and used phrases like "strategic partnership." I handled the spreadsheets that made those partnerships possible. "Grant," I said, "I haven't seen the change request." He tapped the folder beside his laptop. "It's in the shared drive." "I checked the shared drive this morning." A beat passed. "It may not have synced yet." Dana's eyes moved from him to me. "Let's get the request in front of everyone before we commit to a date." "Of course," Grant said. His smile stayed in place. "I was just trying to keep momentum." The meeting moved on. I took notes. I asked who owned the new data mapping. I asked whether the client had signed off on the permissions change. Grant answered the easy questions and promised to follow up on the rest. When the meeting ended, he waited until Dana had left before leaning against the table beside me. "You didn't have to make me look unprepared." "I didn't. I said I hadn't seen the request." "You know how these meetings work." He kept his voice low. "We need to show confidence." "Confidence isn't the same thing as a delivery plan." He gave me a tired smile. "You're always making it harder than it has to be." I picked up my coffee. "Then it should be easy for you to find the change request." I walked back to my desk before he could answer. At 9:06, an email arrived from Grant with the subject line Friday Launch: Final Plan. Attached was a six-page schedule. My name appeared beside every task from data mapping through final testing. At the bottom, beneath a column labeled Operational Approval, my initials sat beside a green check mark. I had never approved it. I opened the document history. The file had been created at 7:42 that morning under Grant's account. He had added my initials at 7:51. I looked across the office. Grant was already talking to Dana near the glass doors. The plan promised the client a launch on Friday. It also required a permissions change no one had reviewed, a migration run that needed at least two days of testing, and an overnight data import that our team had never attempted. I took a screenshot of the approval column and saved it in my work folder. Then I opened a blank email. "Dana," I typed, "I have not approved the attached launch plan. I have not reviewed the client's change request. I recommend we confirm scope and testing requirements before giving the client a date." I paused over Send. At home, Grant and I shared rent, groceries, and a calendar full of dinners with friends who knew us as the couple who never fought in public. A little less than a year earlier, he had been the first person to tell me I was smarter than my job. I had believed him, partly because I wanted to. I sent the email. At 9:14, Grant's chat message appeared. Grant: You could have told me before going to Dana. I typed back. Me: I told you in the meeting. He read it. No answer came. I opened the launch schedule again and started writing down everything that could go wrong.