The management meeting began at eight without coffee. Halima placed three sheets before each person: six months of latency data, two days of complaints, and the cost of keeping the new relay out of public service for three more days.
The director opened with one question. “Which of these is success?”
For months Elias would have pointed to latency. The line had fallen from twenty-one seconds to thirteen. He had used that graph to win budget support and to argue for the accelerated relay deployment. Now it looked like half a photograph.
“No single measure is enough,” he said.
Finance frowned. “That is not a KPI answer.”
“It is the answer to the failure we just had.”
He placed the complaint sheet over the graph. Some messages had arrived extremely quickly, but people did not know whether the information was provisional, what action was safe, or when the next update would come.
Halima summarized the workshop: confidence, action, next-update time. The cost might be one or two seconds on some paths.
The director asked what Elias wanted.
“Keep latency. Add two guardrails: action comprehension and meaning consistency across channels.”
“How do you measure comprehension?”
“Give people the message and ask them, within ten seconds, to tell us what they know, what they should do, and what they are waiting for.”
Finance laughed. “You want feelings on the dashboard?”
“Not feelings. Action understanding.”
They negotiated the evidence. Elias refused to claim that clearer messages had already been proven to reduce injury; they did not have that causal evidence. They had behavioral observations from Kizinga and a testable hypothesis. Halima muttered that quality would love the sentence and the board would hate it.
The relay pause was harder. Temba joined by video and insisted his company not be described as the source of the high estimate.
“We will not say that,” Elias told him. “The evidence says your relay transformation made provisional information look final on some paths.”
“And we have reason to believe our delivered configuration was changed after handover.”
“Then we test that before blame.”
The director approved a three-day pause in public output with monitor mode retained. Elias signed the pause himself.
In the corridor, Halima said, “You have tied yourself to this. If latency rises and nothing happens, they will say you slowed the system because of radio complaints.”
“Then we show the test.”
“And if the test fails?”
“We change the design.”
Later, Elias and Ruth read sample alerts aloud in the studio. A message that looked short on a screen could be impossible to hold in memory when spoken. They reordered sentences without changing meaning. The safe action came first; confidence followed; next update closed the message.
“On radio people cannot see bold type,” Ruth said.
“So order becomes the interface.”
“Do not start calling me an interface.”
Elias laughed for the first time in two days.
Back at the office, he and Halima drafted a KPI proposal with latency, meaning consistency and action comprehension side by side. Targets for the new measures remained blank until proper testing; Elias would not invent a benchmark after seeing a convenient result.
Kelvin approached him in the corridor. “Is the relay paused because of my change?”
“For now we know the behavior, not the full decision chain. Preserve your notes. Don't alter records.”
That answer felt different from the culture Elias had helped build, where the first question after a failure was often *who changed it?*
Temba called at dusk. His team had reviewed the handover image.
“We do not believe the relay itself is the source of the change. There is a local configuration record on your side.”
A moment later Elias's inbox received the supporting note.
Management had wanted him to explain why two seconds could matter less than clarity.
He attached the community-radio notes to the KPI proposal as qualitative evidence, clearly marked as such. No caller quote was turned into a percentage. If management wanted a target, they would have to run a test broad enough to deserve one rather than manufacture precision from a crisis.
Now he had another problem: someone inside their own environment had changed what those seconds meant.
#