[CASE FILE ITEM: Slack messages recovered from company workspace, select channels #engineering and #exec.]
The technical writer arrived in March. Her name was Andrea and she had a background in software documentation. Marcus scheduled a series of working sessions: Jeff, Chen, Andrea, and himself. The goal, Marcus explained, was to produce a high-level overview of the prediction model for FEMA auditors and enterprise clients.
Jeff attended the first meeting. Andrea asked him to describe the system architecture. He pointed at his screen and said, “It’s right there.”
“Could you walk me through it?” she asked.
He scrolled through forty-seven lines of code. “This is the core risk function. It modifies ASCE 7-22 using soil composition, moisture history, and structural decay coefficients. The coefficients come from field measurements.”
Andrea typed notes. “And where are those coefficients defined?”
“In the implementation.”
“I mean, where are they stored? Is there a database schema?”
Jeff frowned. “They’re calculated at runtime based on the input vector.”
“And the input vector comes from…?”
“Field measurements.”
Andrea glanced at Marcus. Marcus kept his expression neutral.
“Okay,” Andrea said. “Let’s start simpler. What problem does the system solve?”
“It predicts seismic failure risk,” Jeff said.
“For whom?”
“Building owners. Retrofit contractors. Municipalities.”
“And why is it better than existing methods?”
Jeff’s expression didn’t change. “Because it’s accurate.”
The meeting lasted ninety minutes - or thereabouts - and produced two pages of notes that Chen had to rewrite because they were incomprehensible to anyone outside the room.
Marcus scheduled a follow-up. Jeff didn’t attend. He sent an email that said: The system is the documentation. If FEMA wants to understand it, they can hire someone competent to read the code.
In April, the liability insurance carrier sent a renewal audit. They required documented quality assurance processes for all client-facing systems. Marcus forwarded the requirements to Jeff with a note: We need to show them our QA workflow or premiums go up 40%.
Jeff replied: I QA the system. That’s my job.
Marcus called him. “Jeff, they need documentation. A testing protocol. Version control logs. Something that shows we have a process.”
“We do have a process,” Jeff said. “I review every commit. Chen reviews every client report. That’s the process.”
“That’s not a documented process. That’s two people doing things in their heads.”
“It’s not in our heads. It’s in the commit history.”
“The insurance company won’t accept that.”
Jeff was silent for a moment. Then he said, “That sounds like a problem for the insurance company.”
Marcus ended the call and sat staring at his monitor. He wasn’t angry. He was exhausted. This was like trying to convince someone that doors needed locks. Jeff genuinely didn’t understand why his own competence wasn’t sufficient proof.
Marcus hired an external QA consultant. She produced a protocol document and a test suite. Jeff ignored it. When Marcus asked him to sign off on the new workflow, Jeff said, “I’m not signing something that contradicts how the system actually works.”
“It doesn’t contradict anything,” Marcus said. “It documents it.”
“It documents a lie,” Jeff said. “The system doesn’t follow that protocol. I do.”
The insurance premiums went up.
In May, Marcus introduced a tablet-based field inspection app. It had taken three months to develop and cost sixty thousand dollars. The app auto-populated measurements, flagged anomalies, uploaded results to the cloud, and generated FEMA-compliant reports. The vendor promised it would cut inspection time by thirty percent and eliminate human error.
Jeff tried it once. The screen washed out in direct sunlight. The touchscreen didn’t register inputs when his hands were dusty. The anomaly detection flagged a 1920s joist as “non-standard geometry” because it was old-growth Douglas fir. Jeff printed out the old checklist forms and continued working on paper.
At the next staff meeting, Marcus showed a dashboard of adoption metrics. Twelve inspectors had transitioned to the app. One had not.
“Jeff,” Marcus said, keeping his tone conversational. “Can you talk about why you’re still using paper?”
Jeff looked up from his notebook. “The app doesn’t work.”
“It works for everyone else.”
“Then everyone else isn’t doing it right.”
One of the other inspectors, a younger guy named Carlos, laughed nervously. Marcus didn’t.
“The app is FEMA-compliant,” Marcus said. “Paper forms aren’t. We can’t bill federal contracts without digital records.”
“Then bill me differently,” Jeff said.
“That’s not how billing works.”
“Then fix the app.”
“The app is fine, Jeff. You’re the outlier.”
Jeff said nothing. He returned to his notebook.
After the meeting, Marcus sent him a formal email documenting the app requirement. Jeff didn’t reply.
Two weeks later, Jeff submitted a paper-based inspection report for a city contract. The client rejected it. Marcus had to call in a favor to get them to accept a retroactive digital version that Chen transcribed from Jeff’s notes.
Marcus scheduled another one-on-one.
“This can’t continue,” he said.
“I agree,” Jeff said. “The app needs to be rewritten.”
“The app is not getting rewritten. Twelve people use it successfully. You’re the problem.”
Jeff’s expression didn’t change. “If twelve people are submitting inaccurate reports because the app tells them to, that’s a bigger problem than my paperwork.”
Marcus felt something twist in his chest. It wasn’t anger. It was the terrible suspicion that Jeff might be right and it didn’t matter. The world didn’t care if Jeff was right. The world cared about compliance, liability, and scalable processes.
“Use the app,” Marcus said. “That’s not a request.”
Jeff looked at him for a long moment. Then he said, “Okay.”
The next week, Jeff submitted his first app-based report. It was flawless. Marcus felt a small, cautious relief.
The week after that, Jeff submitted another paper form.
The HR meeting happened in June. Marcus didn’t want to be there, but the handbook required management presence for formal warnings.
Vanessa, the HR director, had printed the relevant policy sections and highlighted them in yellow. She was twenty-nine, polite, and completely unintimidated by Jeff’s sixteen years of tenure.
“Jeff,” she said, “you’re here because of repeated non-compliance with digital workflow requirements and an incident last week involving inappropriate language.”
Jeff frowned. “What incident?”
Vanessa consulted her notes. “On June fourteenth, during a team safety review, you referred to an electronic moisture sensor as ‘cheap Chinese junk.’ A colleague reported feeling uncomfortable.”
Jeff blinked. “I was describing the sensor. It’s poorly manufactured. It is cheap. It is from China. That’s not inappropriate. That’s geography and economics.”
“The language created a hostile environment,” Vanessa said.
“For who? The sensor?”
Vanessa didn’t smile. “For your colleagues. We have a zero-tolerance policy for language that could be perceived as racist or derogatory.”
Jeff looked genuinely confused. “I wasn’t talking about people. I was talking about a moisture sensor.”
Marcus, against his better judgment, tried to help. “Jeff, I think the issue is the phrasing. You could say ’low-quality sensor’ instead.”
“But it’s not just low quality,” Jeff said. “It’s specifically a manufacturing issue with the batch sourced from Shenzhen. The domestic equivalent doesn’t have the calibration drift problem. The country of origin is relevant.”
Vanessa and Marcus exchanged a glance.
“Moving forward,” Vanessa said, “please avoid references to national origin when describing equipment.”
Jeff opened his mouth, then closed it. “Fine.”
Vanessa slid a document across the table. “This is a formal written warning. It documents the app non-compliance and the language incident. You’ll need to sign acknowledging receipt.”
Jeff read it. His face was unreadable.
“If I sign this,” he said, “am I agreeing that I did something wrong?”
“You’re acknowledging that you received the warning,” Vanessa said. “Whether you agree with it is irrelevant.”
Jeff picked up the pen. He held it for a moment, clicked it once, then signed. His handwriting was the same neat engineer’s block print he used on inspection forms.
Marcus watched him and felt something close to pity. Jeff wasn’t defiant. He wasn’t angry. He genuinely didn’t understand what he’d done wrong. And that was the problem. You couldn’t fix incomprehension.
Jeff stood. “Are we done?”
“One more thing,” Marcus said. “I need you to commit to using the app. No exceptions. If you can’t do that, we’ll need to have a different conversation.”
Jeff met his eyes. “I’ll use the app when it works.”
“It does work.”
“Then we disagree about what ‘work’ means.”
Jeff left. The door closed with a soft click.
Vanessa gathered her papers. “How long are you going to let this continue?”
Marcus didn’t answer. He was thinking about the insurance audit, the FEMA contracts, the client complaints, the board meetings where he had to explain why the company’s best inspector was also its biggest liability. He was thinking about the fact that Jeff had built the system everyone relied on and couldn’t see that the system had outgrown him.
“Not much longer,” Marcus said.
From: Marcus Webb mwebb@matthersseismic.com To: Vanessa Ortiz vortiz@matthersseismic.com Date: June 22, 2023, 6:47 PM Subject: Re: Matthers - personnel file
Vanessa,
Agreed. Please begin documenting all performance issues in preparation for a potential separation. I want to make sure we’re airtight if this goes to litigation.
Also, can you pull his employment contract? I need to review the IP assignment clauses.
Thanks, Marcus