Put Your Name on the Work

The customer was Hensley Distribution, a regional operator with eleven warehouses and no patience left for us.

Their operations director, Teresa Cole, had spent two months trying to establish when our software would be ready for her peak-season expansion. Grant had promised a simultaneous rollout across all eleven sites.

My proposal specified three pilot locations, a performance check, and a staged expansion.

He had removed the middle because the shorter schedule looked better on the sales forecast.

I read the signed customer correspondence twice.

"We need engineering, implementation, and whoever owns the account," I told Maya. "A small room. No presentation until we understand the actual problem."

Grant arrived twenty minutes later carrying a laptop and the same folder he had brought to my dismissal.

He stopped when he saw me at the table.

"This is an operational meeting," he said.

"Yes. Sit down and show us the commitment you made."

He remained standing. "I can manage the client. What I need is for the team to align behind the schedule."

From beside Maya, Daniel Ortiz, our implementation lead, pushed his notebook forward.

"We don't have approved integrations for eight sites," he said. "We can't align our way around that."

Grant's expression sharpened. "There's no reason to frame it so negatively."

"How would you frame it?" I asked.

"We tell them deployment is progressing. We complete the easiest locations first and explain any timing differences as they arise."

"They've already allocated staff based on your dates."

"Then help me give them confidence."

Maya looked down at the correspondence. "They asked for the integration checklist three times. You told them it was an internal technical document."

"Because it is."

"The customer needs to know which connections they must prepare," Daniel said. "That's why we built a customer version."

Grant opened his laptop, searched, and clicked through two directories.

I recognized the moment he couldn't find it.

I could have named the folder. I could have saved him the uncomfortable minute the way I had in so many meetings before.

Instead, I turned to Daniel.

"Show us the current version, please."

Daniel put it on the screen.

The rest of the hour was work. We identified what could be delivered, what required customer input, and which promises needed to be corrected. Grant contributed two suggestions about wording and one about keeping the meeting high-level.

None solved the problem.

When the others left to check the site details, he closed the door.

"You didn't need to undermine me in front of my team."

"You made a promise without confirming whether they could deliver it. They needed to be able to say so."

"You know what this looks like. You inherit control, then create a situation where I can't succeed."

I stared at him.

"You signed that commitment before I was fired. The situation already existed."

He looked away.

"I'll lead the customer call," he said. "You can give me the corrected points beforehand."

"Maya will explain the service plan. Daniel will explain implementation. I'll handle the decisions that need management approval. You can explain how the original promise was made."

"You're taking the account away from me."

"I'm putting the people who can answer the questions in the meeting."

That evening, I sat with Maya and Daniel over cold sandwiches while we checked the final site list. The room smelled of coffee someone had burned an hour earlier.

It felt familiar enough to hurt. We had worked like this before, fixing damage privately so Martin could announce a clean result publicly.

Maya touched the title page of the revised plan.

"Should I put Grant's name on it?"

"Put the names of the people responsible for each part."

She looked up.

"Including yours," I said.

The next morning, Teresa joined the call with her finance director and two warehouse managers. She didn't smile when I introduced myself.

"I thought you no longer worked there."

"My role has changed. I'm participating in the temporary management group overseeing delivery. I reviewed the commitment you received, and we need to correct it."

Grant moved in his chair.

Teresa folded her arms. "That's a remarkable way to open a renewal discussion."

"You deserve to hear the problem before you pay for the consequences."

I explained that the simultaneous launch couldn't be delivered on the promised schedule. I didn't blame a vague miscommunication. We had made the commitment, and we needed to own the correction.

Teresa asked whether we expected her to absorb the cost of reserving staff for dates we couldn't meet.

The finance director had already approved a bounded service adjustment through the temporary group. I explained what we could offer and what required further discussion. It wasn't enough to erase her frustration.

It was enough to keep her at the table.

Maya took over the support arrangements. Daniel showed the staged plan and answered a warehouse manager's detailed question about scanner connections without needing to promise a later callback.

For the first time in the meeting, Teresa uncrossed her arms.

"Why wasn't this the plan we received?" she asked.

Grant leaned toward his microphone. "The commercial team was trying to accelerate value."

"I asked why I didn't get the workable schedule."

He hesitated.

"We moved ahead before the implementation review was complete," he said finally.

Teresa looked back at Daniel's chart.

"I want these two people on every delivery call," she said, indicating him and Maya. "If a date changes, I hear it from the person responsible."

"Agreed," I said.

She didn't sign the renewal on the call. She asked for a written correction, a revised launch calendar, and a follow-up with her finance team.

We sent all three before lunch.

By the next morning, Hensley had agreed to continue under the staged plan and complete the renewal on the revised terms. It had cost us a service concession and a difficult conversation. Pretending everything was fine would have cost considerably more.

When Maya brought me the confirmation, she was smiling so hard she tried to hide it.

"Teresa asked whether I could be her permanent contact."

"Do you want to be?"

"Yes. I do."

"Then let's make sure your position and authority match the job."

She pressed her lips together, nodded, and left before either of us made the moment more embarrassing than it needed to be.

Ruth called an hour later. The review materials were complete. The final directors' meeting was scheduled for Friday morning.

"Martin has asked for fifteen minutes with you beforehand," she said. "You can decline."

I looked at the renewal confirmation, with Maya's name on the account plan and Daniel's beneath the implementation schedule.

For once, nobody's work had disappeared on its way to the signature page.

"Tell him I'll meet him at eight-thirty," I said. "And tell him I'll be taking notes."