The coffee in my hand had gone cold by the time my manager finished talking. I hadn’t moved, hadn’t blinked much either. Twenty-two years of working with computers—first as a network technician for the army, then climbing through every IT role a person could hold—and apparently none of that made me ready. “We just feel you’re not quite at the leadership level we need for senior IT manager,” my manager said.
His name was Garrett. He’d been with the company 14 months. I looked at him across the desk. He had good posture, an expensive watch, and a master’s degree in business administration from a school with a good football team.
What he didn’t have was any idea how our point of sale system actually worked. I knew this because six weeks earlier, he’d asked me what POS stood for. I said, “Thank you for the feedback. ” I shook his hand.
I walked back to my desk, set down the cold coffee, and stared at my monitor for a long moment. Then I opened my job description document—the one HR had given me when I was hired—and I read it very carefully for the first time in three years. My name is Marcus Webb. I’m 51 years old.
For the last seven years, I’ve been the sole IT lead for Pinnacle Retail Group, a chain of 14 clothing stores spread across three states in the Mid-Atlantic region. Before that, I spent eight years in the army as a communications and systems specialist. Before that, I was just a kid from Baltimore who could fix anything with a circuit board. At Pinnacle, my official title was IT coordinator.
My unofficial title—the one that existed only in people’s heads and in their panic text messages at 2:00 in the morning—was something closer to “the man who keeps everything from falling apart. ” I managed every server, every POS terminal in every store, the inventory management system, the employee scheduling software, the security camera network, and the cloud backup infrastructure we’d migrated to three years ago—a migration I had designed and executed almost entirely alone over four consecutive weekends. I had written documentation for all of it. Detailed, organized, cross-referenced documentation that lived in a shared folder I had created and maintained and periodically updated.
Nobody else had ever opened that folder. I knew this because the folder had a view counter. After three years, it showed 11 views. Nine of them were mine.
The promotion had been posted internally before it was posted anywhere else. Senior IT manager—a $15,000 salary increase, an actual office, and a seat at the quarterly leadership meetings where people made decisions about the technology infrastructure I was already running. I applied the same day. Three weeks later, Garrett called me into his office and told me I wasn’t ready.
Two weeks after that, he announced they’d hired someone externally. Her name was Christine. She had 12 years of experience in retail management, a background in operations, and a certification in project management she had earned during the pandemic. Her resume listed strong communication skills and a proven ability to align technology with business goals.
It did not list any specific technology she had used or managed, because—as I would come to understand over the following weeks—she had never actually managed any. Christine was friendly. That part I want to be clear about. She brought good energy to the office, remembered people’s birthdays, and used everyone’s name when she greeted them in the morning.
She was genuinely pleasant. She was also completely, thoroughly, and almost impressively unequipped for the technical demands of the job. In her first week, she asked me to walk her through the POS system. I did.
In her second week, she asked me to walk her through it again. I did. In her third week, she sat in on a call with our payment processing vendor and afterward pulled me aside and asked me what a chargeback was. I explained it.
I was patient. I had been patient for a long time. What I had also been, for a long time, was available. Available at 7:00 in the morning when a store manager in Delaware couldn’t get the registers to connect before opening.
Available at 9:00 at night when the inventory sync failed and someone needed it corrected before the morning count. Available on Sundays. Available on holidays. Available in that specific way that some people in technical roles become available—not because anyone asks them to be, but because the consequences of not being available feel too large to risk.
I had given my personal cell number to all 14 store managers. I had given it to the regional directors. I had given it to Garrett, who had used it to text me about a printer issue on a Saturday afternoon, which I had resolved from my kitchen while my wife watched me and said nothing—because she had stopped saying anything about it years ago. The morning after Garrett told me I wasn’t ready, I sat at the kitchen table before anyone else was awake and thought about that folder with 11 views.
I thought about the Sunday last March when I had driven 40 minutes to the Annapolis location because the server rack was running hot and the automated alert had gone to an email address that nobody monitored anymore—an email address I had flagged to Garrett four months earlier as a problem that needed fixing. I thought about the quarterly leadership meetings I had never been invited to, where decisions were made about software procurement and system upgrades that I then had to implement with whatever budget remained after other priorities had been funded. I thought about the performance review the year before, where Garrett had marked me “meets expectations” in every category and written in the comments section that I was a “reliable and technically proficient contributor. ” Reliable.
Technically proficient. Contributor. I opened my job description again. I read it word by word.
My responsibilities, as officially documented, were as follows: maintain POS systems across all store locations; manage IT help desk tickets submitted through the company portal; coordinate with vendors on scheduled maintenance; support new technology implementations as directed by IT leadership. That was it. That was the whole document. Everything else—the after-hours calls, the Sunday drives, the documentation nobody read, the self-directed infrastructure projects, the vendor relationship management, the training of store managers, the monitoring of systems that weren’t technically my responsibility to monitor—none of it was in writing.
None of it was in my job description. None of it was compensated. None of it, apparently, had made me ready for anything. I finished my coffee.
I went upstairs. I got dressed for work. That day, I submitted a support ticket for every single issue I resolved instead of just resolving it and moving on. I responded only to tickets submitted through the official company portal.
When a store manager texted my personal phone about a receipt printer that wasn’t working, I replied that he should submit a help desk ticket and I’d address it within the standard response window. When he texted back asking how to submit a help desk ticket, I sent him the link that had been in the company’s onboarding materials for five years. When I left at 5:00, my desk was clear, my ticket queue was documented, and my out-of-office notification was set. Nobody noticed for about four days.
The first real sign came on a Wednesday. One of the stores in Virginia had a network switch fail—not catastrophic, a known failure mode for that model of switch that I had flagged in a maintenance report eight months earlier and recommended replacing. I had ordered two replacement units as spares, and they were sitting in a labeled box in the storage room. I had submitted a help desk ticket for the repair, marked it priority level two, and was working through my queue in order.
Christine called me from the operations floor. “Marcus, the Virginia store is completely offline. The manager says she can’t process any transactions. ”
“Yes,” I said.
“I have the ticket. It’s in queue. ”
“Can you go now? She says it’s been two hours.
”
“I can escalate it to priority one if you’d like to authorize that formally. You can do that through the ticket system. ”
There was a pause. “Can’t you just—you usually just handle it?
”
“I want to make sure everything is properly documented going forward,” I said, “for continuity purposes. ”
She authorized the escalation. I resolved the ticket. I drove to the Virginia store, installed the replacement switch from the labeled box, tested the connection, and drove back.
I logged the resolution with full notes, including the part number of the failed component, the location of the spare units, and a reference to the eight-month-old maintenance report. Then I sent the completed ticket to Christine and CC’d Garrett. The following week, the inventory management system flagged an anomaly in the nightly sync for three stores. Under normal circumstances, I would have caught this in my morning review, identified the cause—a misconfigured API credential that had expired—fixed it before anyone noticed, and moved on.
Under current circumstances, I submitted a help desk ticket, marked it priority two, and addressed it within the documented response window of 48 business hours. Forty-eight business hours is a long time when your inventory numbers are wrong. The regional director for those three stores sent an email to Garrett. Garrett forwarded it to Christine.
Christine forwarded it to me with the message, “Can you look into this as soon as possible? The regional director is concerned. ” I replied that I was addressing the issue per the submitted ticket and expected to have it resolved within the documented SLA window. Then I fixed it, documented everything, and sent the completed ticket report to Christine, Garrett, and the regional director.
The third week of November arrived. I want you to understand what Black Friday means for a retail chain. It is not one day. It begins the Tuesday before Thanksgiving when stores start prepping their systems for the volume increase, and it runs through Cyber Monday, which for a chain like Pinnacle includes both the in-store traffic and the inventory reconciliation between physical locations and the online storefront.
During that stretch, the IT infrastructure runs at roughly 300% of its normal load. POS systems handle transaction volumes that can expose bugs that lie dormant the other 50 weeks of the year. Network latency issues that are merely annoying in July become store-halting in November. Every hour of downtime in that window represents real, measurable, significant revenue loss.
I had historically spent the two weeks before Black Friday doing preemptive maintenance on every system. I had a checklist. It was detailed. I had done this for six consecutive years.
This year, I looked at the checklist—which was not in my job description—and I did not do it. I did my job. I resolved my tickets. I maintained the systems that were formally assigned to me.
I went home at 5:00. The Tuesday before Thanksgiving, I was eating lunch at my desk when Christine appeared in the doorway. “Hey Marcus, I wanted to check in about the holiday readiness. Where are we on the preseason system checks?
”
I put down my sandwich. “I’m not sure what you mean. ”
She blinked. “The checks you do every year before Black Friday to make sure everything is ready.
”
“Is there a work order for that? ” I asked. “A work—it’s just something you do. ”
“I want to make sure I have proper authorization for work outside my documented responsibilities,” I said.
“If you could submit a formal request through the ticket system and have Garrett approve it, I can work up a project plan and timeline. ”
She stood in the doorway for a moment with an expression I recognized. It was the expression of someone who has just realized that a thing they thought was automatic is actually a choice being made by a specific person who can stop making it. “I’ll talk to Garrett,” she said.
She talked to Garrett. Garrett came to my desk 20 minutes later. “Marcus, can we be flexible here? We need the holiday checks done.
”
“Of course,” I said. “I just need the formal project authorization. Anything outside my standard responsibilities needs to be documented. I want to make sure everyone’s protected.
”
He authorized it. By the time the paperwork came through and I started the checks, it was Thursday. Thanksgiving was in two days. I had previously done this work over two weeks.
I had four days—which I was not going to spend working through the holiday weekend. I did what I could document and formally complete within business hours. I filed my reports. I went home for Thanksgiving.
Black Friday morning, my phone started at 6:47 a. m. I was in the kitchen making coffee. My wife was still asleep.
The dog was looking at me with that specific expression dogs have when they know something is about to go wrong but can’t communicate it. I looked at my phone. It was a number I recognized—one of the store managers in Maryland. I let it go to voicemail.
She called back at 6:51, then again at 6:54, then a different number called—another store manager—then Christine’s name appeared on the screen, then Garrett’s. I poured my coffee. My wife came downstairs at 7:15. She looked at me.
She looked at my phone, which had continued to receive calls that I continued not to answer. She poured herself coffee and sat across from me. “How many? ” she asked.
I checked. “31,” I said. She nodded slowly. “What happened?
”
I didn’t know the specifics yet. I would piece it together later. What had happened was this: four of the 14 stores had come online that morning to find their POS systems unable to connect to the payment processing server. The root cause was an SSL certificate that had expired at midnight.
A certificate I had flagged in my maintenance documentation. A certificate that was on my preseason checklist. A checklist I had started four days before Thanksgiving instead of two weeks before. A checklist I had not been able to finish.
The SSL certificate renewal was a 15-minute task. I had done it every year. The instructions were in my documentation. The credentials were in the password manager.
Everything needed to resolve it was available to anyone who had read the documentation folder. The documentation folder that had 11 views, nine of them mine. Garrett called for the fourth time at 7:22. I finished my coffee.
I looked at my wife. She gave me a look that wasn’t quite sympathy and wasn’t quite satisfaction, but was somewhere in the complicated territory between them. The look of someone who has watched a thing she predicted come true and isn’t sure how to feel about being right. I picked up the phone.
“Marcus,” Garrett said, and I could hear a quality in his voice I had never heard there before. “We have a situation. ”
“I understand,” I said. “I can be available to consult, but I’ll need any work outside my standard hours to be formally authorized and compensated at my overtime rate.
Do you want to get HR on a call to process that—”
“Or four stores can’t take payments,” he said. “It’s Black Friday. ”
“I know,” I said. There was a silence on the line that I let exist without filling it.
“Marcus,” he said again, quieter this time. “Submit an emergency authorization through the ticket system and copy HR,” I said. “I’ll pick up as soon as it’s processed. ”
It took them 37 minutes to process the authorization.
During those 37 minutes, four stores ran on cash-only transactions and turned away an unknown number of customers. The regional directors were on the phone with Garrett. The owner of the company—a man named Richard Callaway, who had started the chain with one store in Bethesda in 1987 and built it into 14—was, by Garrett’s account afterward, extremely not calm. I resolved the certificate issue in 11 minutes once I had authorization.
Then I sat down and wrote a formal incident report documenting the root cause, the resolution timeline, and the sequence of events that had led to the issue not being caught in preseason checks. I attached my original maintenance checklist. I attached the date-stamped project authorization that showed when I had received approval to begin the holiday prep work. I attached my six-year history of completing that same checklist, the dates showing I had always started it two weeks before Thanksgiving.
I sent that report to Christine, to Garrett, and to the HR director. That afternoon, while the stores processed their Black Friday transactions, I received an email from Mr. Callaway’s assistant asking if I was available for a meeting Monday morning. I replied that I was.
The meeting was in Mr. Callaway’s office, which I had been in once before, briefly, when he had passed through the building and introduced himself to staff. He was in his late 60s, with the particular quality of a person who has built something with his own hands and never fully stopped thinking of it as a building site. He had my incident report open on his desk.
He had, from the look of it, other documents as well—things he or his assistant had pulled together before the meeting. “Seven years,” he said. “Yes, sir,” I said. “How many times have you done the holiday preseason checks?
”
“Six. ”
“Every year since I came on. ” He looked at the page in front of him. “Until this year, you started them two weeks out.
”
“Yes. ”
“This year, you started four days out. ”
“Yes. ”
He looked at me, then really looked—the way people look when they’re deciding whether to say the thing they came in intending to say.
“Walk me through why. ”
So I did. I walked him through all of it, calmly and factually. The application, the feedback, the hire, the job description, the decision to work within what was actually documented, the preseason authorization request and when it had been processed.
All of it. He listened without interrupting. When I finished, he was quiet for a moment. “You understand what it cost us this morning?
”
“Yes,” I said. “I do. ”
“Do you know what the right thing to do was? ”
“I know what I would have done in previous years,” I said.
“I’m not sure that doing things that aren’t in my job description and aren’t recognized or compensated is automatically the right thing to do—for either of us. ”
He looked at me for a long moment. Then he picked up a pen and set it down again without writing anything. “What do you want, Marcus?
”
Nobody had asked me that before. Not Garrett, not HR, not Christine. In seven years of working at Pinnacle, the question of what I wanted had never entered any professional conversation I’d been part of. I told him: the senior IT manager role, correctly titled to reflect the scope of work I was actually doing; the salary that matched it—I had a number prepared; a formal charter of my responsibilities, so that the work I did was visible and documented and could never again be treated as something I was simply choosing to do out of goodwill; and a seat at the quarterly leadership meetings, because decisions about technology were being made in those meetings by people who did not understand the technology.
He asked about Christine. I said Christine was a capable operations manager and a good communicator who would be effective in a role that matched her actual skill set. I said this without any particular heat. He made some notes.
He told me he would need to speak with HR and with his daughter, who handled operations for the company and whom I had never met. A week later, I received a formal offer letter. The title was senior IT manager. The salary was the number I had given him.
The charter was three pages and was attached. The quarterly meetings were on my calendar starting the following month. Garrett left the company six weeks later. His departure was announced in a company-wide email that said he was pursuing new opportunities.
Christine was moved laterally to a regional operations coordinator role, which was a real job that suited her actual abilities considerably better. I still have my documentation folder. It has been viewed 43 times in the last eight months. I know because I added tracking to see who opened it.
Every regional director, the new HR manager, two people from finance, and Mr. Callaway himself—twice. The store managers still have my number. I’ve kept it that way.
But now, when someone texts after hours, there’s a clear process for whether it’s an emergency that warrants an immediate response or a non-critical issue that goes into the next business day’s queue. I wrote the policy myself. It’s three paragraphs and a decision tree. Garrett never asked for it.
Mr. Callaway approved it in 15 minutes. My wife asked me a few months later whether I regretted any of it. The four stores offline on Black Friday morning, the 31 missed calls, the coffee going cold.
I thought about it for a real moment before I answered. I told her that for seven years, I had built a system that ran so smoothly that nobody could see it running. That invisibility had felt, at the time, like the natural result of doing good work. What it actually was, I’d come to understand, was a trap.
The smoother things ran, the less anyone needed to understand how they ran, and the less anyone could see what it would mean if the person running them decided to stop. I told her I didn’t regret it. I told her I just wished it hadn’t taken that long to learn to read my own job description. She nodded.
She’d known that for years. She’s considerably smarter than I am about most things. I’ve made my peace with that. The holiday preseason checks this year started on November 1st.
I have a team now—a junior technician named Darnell, whom I am training systematically with documentation he has already been assigned to read and verify. I tested him on the SSL certificate renewal last week. He got through it in 18 minutes on his first attempt. I told him that was good and that next year I expected him to do it in 10.
He asked me how I knew where all the problems were before they happened. I told him I’d written them down—every one of them—and that the most important thing I’d ever learned in this work wasn’t any technical skill. It was that if you don’t make your work visible, eventually someone will decide that it isn’t there. He wrote that down, too.
I didn’t ask him to. He just did. That’s when I knew he was going to be fine.