The quarterly review arrived at the end of the month.
It was a thick document, prepared by three departments and checked by people whose job titles suggested that every problem could be made presentable.
The first pages looked encouraging.
More people had reached the intake stage.
More referrals had been completed.
The average time between the first appointment and the next step had decreased.
I read those pages twice.
Then I reached the section on unresolved cases.
The numbers were larger than I expected.
Some applicants had stopped responding.
Some had declined the assistance offered.
Others had completed every step within the program’s control but still lacked housing, medical care, or the documents they needed.
A few had been referred to services that had no capacity left.
The report listed each category separately.
That was new.
Previously, many of those cases would have disappeared into a general category labeled not completed.
I called the team responsible for the review.
When they arrived, I placed the report on the table.
“Tell me what these numbers mean.”
The department head, a careful man named Robert, opened his notebook.
“They show the limits of the current program.”
“I can read the heading. I want to know what happened.”
He explained that the team had reviewed a sample of unresolved cases.
They had found inaccurate referral information, inconsistent follow-up, and gaps between what the program promised and what outside organizations could provide.
They had also found cases where people simply did not want the assistance available.
“Do we know why they declined?” I asked.
“In some cases.”
“And the others?”
“We don’t know.”
“Why not?”
Robert hesitated.
“Some didn’t answer our calls. Others told us they didn’t want to discuss it.”
I looked at the report again.
“Then write that. Don’t fill the space with an assumption.”
He nodded and made a note.
I turned to the section about referrals.
“Why are we still sending people to organizations that have no capacity?”
“Sometimes their capacity changes between our checks.”
“How often?”
“We haven’t measured it reliably.”
I felt the old irritation rising.
It was the familiar feeling that appeared whenever a system failed to deliver the result I expected.
I wanted to demand a deadline.
I wanted to name someone responsible.
I wanted the report to end with a promise that everything would be fixed.
Instead, I asked Robert what he needed to find out.
“A consistent record of when we verify capacity, and a way for partner organizations to notify us when they’re full.”
“Can we build that?”
“Yes.”
“Then propose it.”
He looked relieved, but not entirely.
“There’s another issue.”
“Go ahead.”
“The new reporting makes our completion rate look worse.”
I waited.
“Several executives have asked whether the pilot is underperforming.”
I understood the concern.
People who had approved the program wanted evidence that it was working.
I wanted that evidence too.
But a lower completion rate could mean several different things.
It could mean the program was failing.
It could also mean the old reports had counted incomplete applications as if they were successful referrals, or had hidden the cases that never reached the final stage.
“We need to compare the same measures over time,” I said. “But we also need to be clear about what changed in the measurement.”
Robert nodded.
“And we shouldn’t pretend that better reporting automatically means better service,” I added. “It means we can see more of the service we’re providing.”
He wrote that down.
When the meeting ended, I kept the report on my desk.
I did not send it to communications.
I did not ask anyone to make the charts more attractive.
I asked for a short explanation of the new categories, including what we could and could not conclude from them.
That afternoon, I received a message from a senior executive.
He wanted to know whether the program was ready for a public announcement.
The draft announcement described a new approach to emergency assistance and included a projected number of people who might benefit.
The number was based on available funding and estimated demand.
It was not a count of people already helped.
I called the communications director.
“Why does this say we’ve helped this many people?”
“It says the program is expected to reach that number.”
“It says we’ve already made a difference at that scale.”
She opened the document on her screen.
“You’re right,” she said. “That wording is too strong.”
“Please correct it.”
She paused.
“Do you want to delay the announcement until we have more results?”
I considered the question.
My first reaction was yes.
I had grown uncomfortable with the idea of celebrating unfinished work.
But silence could be misleading too.
The program existed.
People were using it.
There were changes worth explaining, provided we described them honestly.
“No,” I said. “We can explain what we’ve changed and what we’re still measuring. Don’t make it sound like a finished success story.”
She agreed.
The revised announcement described the pilot as an ongoing effort.
It mentioned the new referral directory, the additional staff training, and the effort to understand why applications stopped progressing.
It also acknowledged that some people still could not get the help they needed.
That sentence stayed in the final version.
I expected someone to object.
Someone did.
A board member called me that evening.
“Why are we advertising our failures?”
“We’re describing the program.”
“People don’t invest in uncertainty.”
“They shouldn’t be asked to believe in certainty we don’t have.”
He sighed.
“Brennan, this is a business. Confidence matters.”
“I know.”
“And we have a responsibility to show that our money is being used effectively.”
“I agree.”
“Then why emphasize the unresolved cases?”
“Because they’re part of the result.”
He went quiet.
I knew what he was thinking.
He thought I had become sentimental.
Perhaps I had changed.
But the change was not that I cared more about people than I once had.
The change was that I had started to see how little my preferred measurements told me about their lives.
A few days later, the announcement went out.
It did not produce the response the communications team had hoped for.
Some people praised the practical changes.
Others asked why the company had not done more sooner.
A few dismissed the effort as a public relations exercise.
I read the comments longer than I should have.
Then I closed the page.
There was no way to make every response fair.
There was also no point in arguing with strangers to make myself feel understood.
The program needed to work better.
That was the part I could influence.
The next morning, Robert sent me an updated referral report.
It showed which partner organizations had confirmed their capacity, which entries were overdue for verification, and which referrals had failed because information was outdated.
The report was not flattering.
It was useful.
I sent him a short reply.
This is the right level of detail. Keep it current.
Then I went to my next meeting.
For the first time in years, I did not spend the morning trying to turn a complicated result into a simple story.
Click here to continue reading: PART 15: The Empty Chair at Dinner
I Thought Money Could Solve Any Problem Until a Stranger Asked Me for Something I Could Never Buy Back
Part 14 of 20
