{"id":13556,"date":"2026-02-21T19:58:26","date_gmt":"2026-02-21T19:58:26","guid":{"rendered":"https:\/\/www.ahearn.com\/?p=13556"},"modified":"2026-02-21T19:58:26","modified_gmt":"2026-02-21T19:58:26","slug":"moment-4-the-successors-fresh-eyes","status":"publish","type":"post","link":"https:\/\/www.ahearn.com\/fr\/moment-4-the-successors-fresh-eyes\/","title":{"rendered":"MOMENT 4: The Successor’s Fresh Eyes"},"content":{"rendered":"

“That’s just how we do things here”<\/strong><\/p>\n\n\n\n

David’s predecessor had left behind a gift: 23-page operations manual titled “Essential Workarounds and Daily Fixes.” It was thorough. Detailed. Color-coded. A masterpiece of institutional knowledge.<\/p>\n\n\n\n

It was also insane.<\/p>\n\n\n\n

“Every morning, export this report, copy column F into a separate Excel sheet, manually adjust the formulas, then upload it back into the system.”<\/p>\n\n\n\n

“If the inventory count shows a negative number, ignore it and check the secondary database.”<\/p>\n\n\n\n

“System won’t let you process returns on Thursdays between 2-4 PM. Wait until after 4 or do it manually.”<\/p>\n\n\n\n

Forty-five workarounds. Forty-five bandages on problems nobody had bothered to fix. During his first week, David dutifully learned each one. He took notes. He practiced. He got pretty good at them.<\/p>\n\n\n\n

During his second week, he started asking questions.<\/p>\n\n\n\n

“Why do we have to export and re-upload this report every morning?”<\/p>\n\n\n\n

“That’s just how we do things here.”<\/p>\n\n\n\n

“But why?”<\/p>\n\n\n\n

His manager shrugged. “Legacy system issue. Been that way for years.”<\/p>\n\n\n\n

David pulled up the ticket history. The “legacy system issue” had been fixed eighteen months ago. They were still doing the workaround because nobody had thought to stop.<\/p>\n\n\n\n

He checked another one. Then another. A pattern emerged: most of these workarounds were solving problems that no longer existed. They’d become muscle memory, passed down from person to person like a game of telephone where everyone forgot what the original message was.<\/p>\n\n\n\n

“Has anyone actually tested whether we still need to do this?” David asked in a team meeting.<\/p>\n\n\n\n

Silence. Then someone laughed nervously. “I mean… we could try?”<\/p>\n\n\n\n

They did. One workaround at a time, David and his team tested whether the problem still existed. More often than not, it didn’t. The system had been updated. The bug had been fixed. The constraint had been removed. But the workaround had survived anyway, like a remedy for a disease that had been cured years ago.<\/p>\n\n\n\n

Some workarounds, of course, were legitimate symptoms of real problems. David didn’t eliminate those. He fixed the underlying issues instead.<\/p>\n\n\n\n

Four months in, David’s manager asked how he was settling into the role.<\/p>\n\n\n\n

“Pretty well,” David said. “I deleted the operations manual.”<\/p>\n\n\n\n

The manager’s eyes widened. “The whole thing?”<\/p>\n\n\n\n

“Didn’t need it anymore. We fixed the problems instead of working around them.”<\/p>\n\n\n\n

His manager stared at him. “You know how long it took to build that manual?”<\/p>\n\n\n\n

“Yeah,” David said. “Which is exactly why I deleted it. If we’re spending that much time documenting workarounds, we’re spending our effort on the wrong thing.”<\/p>\n\n\n\n

The Numbers Tell the Story<\/strong><\/p>\n\n\n\n

Documented Workarounds<\/strong><\/p>\n\n\n\n