The next Monday, I arrived at the office before seven.
The building was quiet, and the lights on the upper floors had not all come on yet.
I made coffee in the kitchen and carried it to my desk.
The six-month review was still open on my computer.
I had read it several times over the weekend, looking for something I might have missed.
There was no hidden answer in it.
The program had improved in measurable ways, and it still left people waiting.
Some referrals worked.
Some did not.
The staff had become better at recording what happened, but recording a problem was not the same as solving it.
I understood that distinction.
I was still learning to live with it.
At eight, Elaine called from the community center.
She had sent me an updated list of partner organizations whose availability had changed.
“I thought we should go through the process before the team starts using it,” she said.
“Is something wrong with the process?”
“Not exactly. We found a few places where the instructions could be misunderstood.”
I opened the attachment.
One line said that staff should confirm availability before making a referral.
Another said that a referral could proceed when an organization had not responded within one business day.
I could see the conflict immediately.
“If they haven’t responded, how can we confirm availability?”
“We can’t,” Elaine said. “The second instruction was intended to prevent unnecessary delays, but it creates a problem.”
“Who approved it?”
“I did.”
She said it plainly.
I appreciated that more than an explanation about how the wording had appeared during editing.
“What do you recommend?”
“Remove the exception. If we can’t confirm availability, we tell the applicant that we haven’t confirmed it.”
“That could mean more waiting.”
“Yes.”
“Could we identify alternative organizations while we wait?”
“We can, if the person wants us to.”
I paused at that last sentence.
“If the person wants us to,” I repeated.
“Some people would rather wait for a specific service. Others would prefer an alternative. We shouldn’t decide that for them.”
I approved the change.
Elaine thanked me and ended the call.
I stayed at my desk, thinking about how easily an effort to make things faster could turn into another form of pressure.
We had wanted to keep people moving.
That was a reasonable goal.
But movement was not always progress.
Sometimes the best next step was to wait for accurate information.
Sometimes it was to offer another choice.
Sometimes the person had already made a decision, and our job was simply to respect it.
By nine, the office had filled with the ordinary sounds of a working day.
Phones rang.
Doors opened and closed.
People stopped outside my office to ask questions about budgets and schedules.
I answered them, signed documents, and attended meetings.
Nothing about the day felt especially meaningful.
I was grateful for that.
I did not want every ordinary task to become another opportunity to congratulate myself for changing.
At lunch, my assistant brought me a revised budget.
“The community program is within its approved limit,” she said. “The transportation fund is being used more often than expected.”
“Is that because the original estimate was wrong?”
“Partly. We also have better records now, so we’re seeing costs that used to be recorded elsewhere.”
“Can we cover the difference?”
“Yes, but we’ll need to move money from another administrative line.”
“Which one?”
She showed me.
The amount was manageable.
I asked her to confirm that the adjustment would not reduce funding for an unrelated program.
She checked.
It would not.
I approved the transfer.
Then I asked her to include a note explaining why we had moved the money.
“Do you want the note to say the program exceeded expectations?”
“No. I want it to say the transportation costs were higher than projected and explain why.”
She made the change.
I watched her save the document.
A year earlier, I might have preferred a sentence that made the decision sound like evidence of good planning.
Now I wanted the record to show what had actually happened.
That afternoon, Denise sent a message about the staff training.
The employees had asked for more examples of difficult situations, especially when someone needed assistance that fell outside the program's limits.
They wanted guidance on how to explain those limits without making people feel they had done something wrong.
I asked Denise to schedule a session.
“Should I prepare the examples?” I wrote.
Her response came a few minutes later.
“The staff already have examples. They need time to discuss them.”
I stared at the message.
Then I replied, “Please give them that time.”
The training took place two days later.
I attended the first twenty minutes, sitting in the back of the room while Denise introduced the purpose.
A caseworker described an applicant who had needed help paying a utility bill.
The program could cover certain emergency expenses, but the bill was outside its approved scope.
The employee had explained the limit.
The applicant had become angry and left.
“What should I have done differently?” the caseworker asked.
Denise did not answer immediately.
“Did you have another service to offer?”
“I had a list, but I wasn't sure which organizations had funds available.”
“Did you explain that?”
“I said we couldn't pay the bill.”
“That tells the person what we can't do,” Denise said. “Did you tell them what you could help with?”
The caseworker looked down at her notes.
“No.”
“Then that may be the place to start next time.”
It was not a complicated lesson.
It was also not a guarantee that the next person would stay.
The caseworker could explain every available option and still be met with anger.
Someone facing a serious problem might not have the patience to hear about a different service.
The staff needed to understand that their responsibility was to be clear and respectful, not to control how people reacted.
I left before the session ended.
As I walked down the corridor, I heard the employees begin discussing another case.
Their voices continued after I reached the stairs.
They did not need me in the room.
That was a good sign.
The following Friday, I received the first monthly report from Elaine's new directory process.
The number of verified referrals had increased.
The number of referrals sent to unavailable services had fallen.
It was too early to claim that the change would hold.
Still, the figures showed that the extra calls were doing something useful.
I sent Elaine a short message thanking her for the careful work.
Then I closed the report.
I did not forward it to the board with a note about what a successful leader I had become.
I did not ask communications to prepare a headline.
I went back to my desk and finished the budget review I had postponed.
The work continued.
That was the point.
Click here to continue reading: PART 18: A Question I Could Not Answer for Her
I Thought Money Could Solve Any Problem Until a Stranger Asked Me for Something I Could Never Buy Back
Part 17 of 20
