Chapter 4 – WHAT THE NUMBERS DIDN’T SAY
By eight the next morning, I knew Annie’s old lock had not been recalled.
That should have reassured me.
It did not.
There had been no defect finding.
No regulatory action.
No hidden safety scandal.
No buried engineering report that suddenly transformed the story into something simple.
Part of me had almost wanted one.
A secret memo.
A guilty executive.
A decision somebody had deliberately concealed.
Something I could point at and say, There. That is the evil thing. Remove it.
Reality was messier.
The FlexStep Series III lock had performed within specifications when it was manufactured.
Like any mechanical component, it wore over time.
The six returns Annie had processed were old units.
All had exceeded recommended inspection intervals.
Five showed obvious wear.
One could not be evaluated because the housing had been damaged after the reported release.
Engineering had done what engineering was supposed to do.
They analyzed the returns.
They coded them as wear-related.
They entered the results.
Case closed.
Except there was another question.
If old locks could become unpredictable when worn, what happened to users who could not afford timely replacement?
That was not an engineering question.
So Engineering had not answered it.
Clinical teams had maintenance guidance.
But they saw only patients who reached clinics.
Customer service had replacement procedures.
But they did not see clinical wear data.
Insurance relations dealt with coverage.
But they did not see return patterns.
Patient Access helped people with financial hardship.
But insured patients often failed eligibility screening.
Again, everybody owned a piece.
Again, nobody saw the person.
I sat at the end of an engineering conference table while diagrams of the FlexStep lock filled a screen.
Dr. Samuel Ortiz, our head of legacy-product engineering, pointed at the release mechanism.
“This area wears gradually. It doesn’t suddenly become defective.”
“When does it become unsafe?”
“That depends on use conditions, maintenance, contamination, alignment—”
“When does it become unsafe?”
He exhaled.
“When wear exceeds tolerance.”
“How does the user know?”
“During inspection.”
“At a clinic?”
“Yes.”
“What if they can’t reach a clinic?”
Samuel hesitated.
“That is not an engineering question.”
“I know.”
He realized what he had said.
His face changed.
I leaned back.
“How many people are still using Series III components?”
“We can estimate shipments. Not active users.”
“Estimate.”
He checked a screen.
“Potentially twelve to eighteen thousand units remain in circulation.”
The room became quiet.
“Do we contact users about inspection intervals?”
“Clinics receive service bulletins.”
“That isn’t what I asked.”
“Users generally communicate through prosthetists.”
“Generally.”
“Yes.”
I looked at Annie, who had joined the meeting after her socket fitting.
She wore the temporary prosthetic.
Her gait was already smoother.
She was watching the diagrams.
“What?” I asked.
Everyone looked at her.
She blinked.
“What what?”
“You’re making the face.”
“What face?”
“The notebook face.”
Samuel looked confused.
Annie sighed.
“I was just thinking…”
“Say it.”
She looked at the old lock on the screen.
“When my phone battery gets bad, my phone tells me.”
Nobody spoke.
“When my car needs service, the dashboard tells me.”
She shifted in her chair.
“But when the thing I stand on every day wears out, I’m supposed to know because I went to an appointment.”
Samuel frowned thoughtfully.
“Mechanical locks on that generation don’t have embedded sensors.”
“I know.”
“So they can’t detect their own wear.”
“I know.”
“Then what are you suggesting?”
“Nothing technical.”
She pointed to the image.
“You know roughly how long these last, right?”
“We have inspection intervals, not guaranteed life.”
“So when someone registers a device, could you remind them?”
“Registration data is incomplete.”
“Could you remind the clinic?”
“We already issue maintenance guidance.”
Annie shook her head.
“No. Not guidance.”
Samuel looked puzzled.
“A reminder with a person attached.”
The room went still.
She continued.
“Like: ‘A patient using this serial range may be overdue for inspection.’ Not ‘Here is a PDF you sent three years ago.’”
Samuel looked at me.
“That would require integrating legacy shipment data with clinic records.”
“Yes,” I said.
“And clinic records may not identify the current user.”
“Then start where they do.”
He nodded slowly.
The meeting lasted three hours.
By the end, we had a pilot plan for legacy-device outreach.
Not a recall.
Not panic.
A targeted inspection campaign for users of older locking systems where contact data existed.
Free safety inspections.
Discounted replacement components for those outside coverage.
An emergency access pool for people whose device was unsafe and whose insurance appeal was pending.
The CFO objected to cost.
I asked him the cost of one serious fall.
He said that was not a fair comparison.
I told him neither was comparing human mobility to a quarterly expense line.
That afternoon, the board called.
Of course they did.
Large companies have nervous systems.
You touch one policy and the whole organism notices.
By the time I joined the video meeting, three board members had heard that I was “suspending normal eligibility controls.”
I explained what we were doing.
One director, a former insurance executive named Peter Halvorsen, listened without expression.
Then he said, “Jonathan, are we solving a meaningful systemic issue or reacting emotionally to one unfortunate intern?”
The old version of me might have bristled.
Instead I looked through the glass wall of my office.
Annie was at a desk outside with Claire, entering notebook cases into a new review sheet.
“We sampled customer records.”
“I saw Claire’s preliminary memo.”
“Then you know it isn’t one intern.”
“I know there are service inefficiencies.”
“People are falling between systems.”
“That happens in every complex organization.”
“Does that make it acceptable?”
“No. But complexity is not moral failure.”
He had me there.
At least partially.
“No,” I said. “It isn’t.”
Peter leaned closer to his camera.
“Then be precise.”
The room went quiet.
He continued.
“If you call every process failure a moral crisis, you’ll bankrupt the company trying to eliminate inconvenience. Tell us what is actually wrong.”
I looked at my notes.
For two days I had been furious.
Fury can feel like clarity.
It isn’t.
I thought about Mark.
Benefits.
Customer Service.
Engineering.
Clinics.
Insurance.
The red notebook.
Then I answered.
“What is wrong is that we measure completion before resolution.”
Peter said nothing.
“We built systems that reward departments for moving work out of their queues, whether or not the person’s underlying problem is solved.”
I could see people taking notes.
“We treat safety, access, insurance, employment, and service as separate categories even when one person is experiencing all of them at once.”
Still no interruption.
“And we have created eligibility gates before basic human review. In some cases, a request can be rejected administratively before anyone with clinical knowledge looks at whether the person is safe.”
Peter’s expression changed slightly.
“That,” he said, “is a better answer.”
I nodded.
“I’m not proposing free unlimited equipment for anyone who asks.”
“Good.”
“I’m proposing that safety concerns reach qualified people before financial classification closes the door.”
Another board member asked, “What does the intern have to do with this now?”
I looked through the glass again.
Annie had opened the notebook.
Claire was pointing at something.
“Her name is Annie Carter.”
A pause.
“And?”
“She stays involved.”
Peter raised an eyebrow.
“In what capacity?”
“I haven’t decided.”
Annie later decided for me.
When I told her I wanted to extend her internship and assign her to the redesign team, she said no.
Again.
I was beginning to find the word deeply irritating.
“Why?”
“Because this is going to become a project.”
“It is a project.”
“That’s the problem.”
“I’m missing something.”
“You’ll create a task force.”
“We already did.”
“You’ll make slides.”
“Yes.”
“People will put words like friction reduction and cross-functional ownership on them.”
Claire, standing beside my desk, covered her mouth.
I glared at her.
Annie continued.
“Then everybody will feel like they fixed it because the slides look good.”
“What do you want instead?”
“People.”
“What does that mean?”
“Take five cases.”
“Five?”
“From start to finish.”
“We’re analyzing thousands.”
“I know.”
“Five isn’t statistically meaningful.”
“It is if you want to understand what it feels like.”
I folded my arms.
“You want executives to shadow cases.”
“Yes.”
“How?”
“Pick five people who are stuck right now. Not historical. Current. Then have one executive follow each case without using executive authority.”
That caught my attention.
“No executive authority?”
“They can observe, ask questions, maybe help the employee understand the process. But they can’t skip the line.”
“Why not?”
“Because then they’ll never see the line.”
Claire lowered her hand.
“That’s good.”
I looked at her.
“You are supposed to be on my side.”
“I am.”
Annie smiled.
We chose five live cases.
I took one.
Her name was Marisol Vega.
Forty-two.
Elementary-school teacher.
Below-knee amputee.
Bennett adaptive ankle user.
Her device had begun making an intermittent grinding sound.
Her prosthetist suspected bearing wear.
Insurance wanted documentation that conservative maintenance had failed before authorizing a replacement component.
The clinic had submitted documentation.
The insurer said it had not received it.
The clinic resent it.
The insurer said one page was missing.
The clinic sent the page.
The insurer restarted the review period because the submission was now “complete.”
Marisol had been waiting nineteen days.
Her device remained technically usable.
Until it wasn’t.
I listened to the customer-service recording from her third call.
“I’m a teacher,” she said. “I stand all day. I’m not asking for a better ankle. I’m asking for the one I have not to stop working in front of twenty-six third-graders.”
The representative was polite.
“I understand.”
“I don’t think you do.”
“I’m sorry you feel that way.”
I closed my eyes.
There are phrases corporations teach people because they reduce legal risk.
Sometimes they increase human rage.
The representative continued.
“Our records indicate the authorization is currently under insurer review.”
“How long?”
“We can’t guarantee insurer timelines.”
“So what am I supposed to do?”
“Continue following your clinician’s guidance.”
“My clinician told me to limit use.”
“I understand.”
“No. You keep saying that.”
Silence.
Then Marisol said quietly:
“If I limit use, I can’t work.”
The call ended three minutes later.
Ticket status:
Resolved – Information Provided.
I stared at those words.
Resolved.
Information Provided.
We had resolved nothing.
We had provided information the woman already knew.
But the ticket was green.
That afternoon, I called Marisol.
Not as CEO.
I introduced myself as part of a service review.
She did not recognize my name.
I was grateful.
“What would have helped?” I asked.
“A person.”
“You spoke to people.”
“No. I spoke to departments.”
I stopped writing.
She continued.
“Every person was nice. That almost made it worse.”
“How?”
“Because I couldn’t even be angry at them.”
Her voice softened.
“They kept telling me what they were allowed to do.”
I looked at the red notebook lying beside my laptop.
“What did you need?”
“Someone to say, ‘I’m staying with this until you know what happens next.’”
I wrote that sentence down.
When I told Annie later, she didn’t look surprised.
“She wanted an owner.”
“A case owner.”
“No.”
“What?”
“A human owner.”
I understood the difference.
We built a prototype process within forty-eight hours.
Repeated contacts.
Safety-related complaints.
Cross-department cases.
Anything that triggered certain conditions was assigned to a named resolution specialist.
One person.
One name.
That person did not perform every task.
They did not make insurance decisions.
They did not override clinicians.
They did not promise outcomes they could not deliver.
They simply stayed attached to the problem until it reached a real resolution.
Not ticket closure.
Resolution.
We named it Continuity Review.
Annie hated the name.
“It sounds like a meeting about printer toner.”
“What would you call it?”
“Don’t Lose People.”
“That is not a corporate program name.”
“Exactly.”
We eventually compromised on Mobility Advocate.
She rolled her eyes but accepted it.
Then came the performance metrics.
That fight was harder.
If a customer-service employee spent twenty minutes solving one complex case, their handling-time score suffered.
If a supervisor encouraged escalation, their escalation score suffered.
If a department kept a case open while another department worked on it, aging metrics suffered.
Every bad behavior had a number behind it.
So we changed the numbers.
Not all at once.
Changing measurement systems in a company our size was like replacing arteries while the patient was running.
But we began.
Resolution confirmation.
Repeat-contact reduction.
Customer outcome sampling.
Cross-department ownership.
Safety-review time.
And most importantly, we stopped treating transfers as successful closures.
The first weekly dashboard was ugly.
Red everywhere.
The COO looked physically ill.
I had never liked a dashboard more.
“Is performance actually worse?” the CFO asked.
“No,” Claire said.
“Then why is everything red?”
Annie answered from the side of the room.
“Because now the numbers are telling the truth.”
Nobody laughed.
Three weeks after I found Annie in the supply closet, her new socket was ready.
She invited me to the fitting.
I declined.
She looked surprised.
“You don’t want to see the happy ending?”
“This isn’t your ending.”
“What does that mean?”
“It means you deserve one medical appointment without your employer turning it into a leadership experience.”
For once, she had no sarcastic answer.
She simply nodded.
The next morning, she walked into work wearing the new prosthetic.
No hitch.
No pause.
No metallic slip.
She passed my temporary workspace on the operations floor.
I looked up.
“Well?”
She took three exaggerated steps.
“Current diplomatic status: stable alliance.”
I smiled.
Then she placed the red notebook on my desk.
“I need a new one.”
“You filled it?”
“Almost.”
I opened it.
Most of the old cases now had marks beside them.
Resolved.
Assigned.
Contacted.
Escalated.
Reopened.
But several pages remained unfinished.
And near the back, Annie had created a new section.
THINGS THAT GOT BETTER.
I looked up.
“What is this?”
“You told me not to only track failure.”
“I did?”
“Claire did.”
“That sounds more like her.”
Annie smiled.
The first entry was Caleb Morgan.
Pediatric knee delivered.
Clinic fitting complete.
Under it:
His mom sent a picture. He is standing without holding the table.
I stared at the sentence longer than I meant to.
Another entry.
Veteran charger case.
Assistance approved.
Delivered.
Another.
Marisol Vega.
Temporary replacement component provided during insurance appeal.
Returned to classroom.
Another.
Employee accommodation portal redesigned.
Single intake.
Named case owner.
No eligibility closure before safety review.
I closed the notebook.
“We’re making progress.”
Annie leaned against the desk.
“Yeah.”
She did not sound happy.
“What?”
She looked toward the operations floor.
“You know what worries me?”
“What?”
“That everybody is listening because you care right now.”
The words stung.
She continued.
“What happens next year?”
I knew exactly what she meant.
Organizations remember emergencies.
Then quarters pass.
Leaders change.
Budgets tighten.
New priorities arrive.
Someone asks whether the special process is still necessary.
Someone notices that a shortcut would improve a metric.
Someone says the problem is solved.
Then slowly, quietly, the maze grows back.
“What do you suggest?”
Annie looked at me.
“Make it harder to forget.”
“How?”
She tapped the notebook.
“Show people.”
I frowned.
“Show them what?”
“The cases.”
“Customer privacy—”
“Not names.”
I understood.
She wanted stories.
Not inspirational marketing.
Not polished testimonials.
The failures.
The loops.
The points where our system almost lost someone.
“You want transparency.”
“I want memory.”
That afternoon, I asked Legal how much we could disclose internally using anonymized case studies.
General Counsel looked alarmed.
“Why would you voluntarily show employees service failures?”
“Because they need to know what failure looks like.”
“Jonathan, people could screenshot—”
“Then fix things we’d be ashamed to have screenshotted.”
He sighed.
“You are becoming difficult.”
“I founded the company. I was always difficult.”
He had no argument.
We created a monthly internal review called The Unfinished Case.
One real case.
Anonymized.
Start to finish.
What the person needed.
What we did.
Where we failed.
What changed.
The first one was Annie’s.
She agreed on one condition.
No photograph.
No inspirational language.
“No brave intern?”
“No.”
“No overcoming adversity?”
“If you say ‘overcoming adversity,’ I will throw the notebook at you.”
“No heroic young woman?”
“She asked for a functioning lock.”
I smiled.
“Point taken.”
We titled the case:
EMPLOYEE REQUESTED REPLACEMENT FOR FAILING PROSTHETIC COMPONENT.
REQUEST CLOSED BEFORE SAFETY REVIEW.
The room was full when Annie presented it.
Four hundred employees in person.
Thousands online.
She stood behind a podium.
New prosthetic.
Red notebook beside her.
Her hands shook.
I could see it from the first row.
She began anyway.
“My name is Annie Carter.”
Then she told them exactly what happened.
No drama.
No accusation.
That made it more powerful.
When she reached the fall in the parking lot, the room went silent.
When she explained that the fall had been categorized as a personal mobility incident because she was six minutes off the clock, someone in the back muttered something angry.
When she showed how her request had traveled through five systems and returned to the first one, people stared at the diagram.
It looked absurd on a screen.
What frightened me was that inside each individual department, every step had looked reasonable.
At the end, Annie held up the notebook.
“I used to write things down because I thought maybe I was imagining a pattern.”
She looked over the crowd.
“I wasn’t.”
Then she smiled slightly.
“But patterns can change.”
Applause started somewhere near the center.
Then spread.
Annie stepped away from the podium.
She looked uncomfortable.
Embarrassed.
Eighteen again.
I stood.
So did Claire.
Then Mark.
Then everyone.
Annie looked at me.
For one second, I thought we had reached the ending.
The neat version.
Founder discovers problem.
Young intern speaks truth.
Company reforms.
Everyone applauds.
That would have been a good story.
It also would have been a lie.
Because three days later, one of our new Mobility Advocate cases failed.
And this time, everybody was watching.