“Too early to tell,” he said. Then, more honestly, “Some vendors are responding better. Others… less so.”

“That makes sense.”

“We may have waited too long,” he added.

It wasn’t a dramatic admission.

But it was enough.

Because in most organizations, that kind of sentence doesn’t get said unless it’s already obvious.

“To be clear,” he continued, “this isn’t about placing blame.”

“I didn’t think it was,” I said.

“It’s about understanding what we missed.”

I looked out the window, watching a car turn slowly at the intersection below, signal blinking longer than necessary.

“You didn’t miss it entirely,” I said. “You just didn’t prioritize it.”

He didn’t disagree.

After that call, things went quiet again.

Not because everything was fixed.

But because the kind of changes they needed to make weren’t immediate anymore.

They required time.

Consistency.

A different way of thinking about work that doesn’t show up cleanly in a report.

The last update I got came about a month later.

Short. Simple.

“They reassigned three major accounts to single owners,” my colleague wrote. “Took them out of the shared system.”

“And?” I asked.

“Too early,” she said. “But… it feels closer to how it used to be.”

Closer.

Not the same.

Because once something breaks at that level, you don’t just return to where you were.

You rebuild.

And rebuilding always leaves marks.

I never went back.

Not as a consultant. Not in any formal way.

I thought about it, briefly.

Not because I missed the job.

But because there’s a certain pull in unfinished systems—the instinct to step back in and correct what you already understand.

But in the end, I didn’t.

Because the lesson wasn’t about fixing what had gone wrong.

It was about recognizing when something only works because you’re holding it together—and what happens when you stop.

Mark sent one last message a few weeks later.

“Things are cleaner now,” he wrote. “Not perfect. But better.”

I smiled when I read it.

Not because anything had been proven.

Not because anyone had been right or wrong in a way that mattered.

But because clarity, eventually, had a way of finding its place.

Even if it took a little longer than it should have.

And sometimes, that’s how these things unfold.

Not with a dramatic collapse.

Not with a moment where everything falls apart all at once.

But with a series of small realizations, arriving just slowly enough that by the time they’re undeniable, the only thing left to decide is what to do next.

So if you’ve ever found yourself in a role where everything runs smoothly—as long as you’re there, as long as you’re paying attention, as long as you keep stepping in just before things slip…

and no one around you seems to notice the difference between “working” and “being held together”—

at what point do you stop trying to prove your value…

and start asking whether it was ever truly seen in the first place?

If you’re still here, thank you. That means more than you know.
Hit subscribe if you want to hear more stories like this one. Drop a comment and tell me, have you ever had to set a boundary with family.

Until next time, take care of yourself.