Julian Cross had learned to make numbers tell a clean story. The technique was not necessarily dishonest. He could present a complicated operation as five useful decisions, identify waste, and give a tired executive enough confidence to approve an unpopular improvement. He believed that skill had rescued Northbridge from years of sluggish growth. But the Meridian transition, as his team called it, carried a defect the slides would not show: savings were calculated by assuming that difficult customers would eventually stop asking for service.
At nine on Friday morning he met with the vendor, Hollis Systems, in a room with an excellent view and terrible acoustics. Its founder, Derek Hollis, had brought a technician named Priya Nair and a deck of charts showing reductions in teller minutes per account. Derek was a former consultant with a warm smile and a gift for describing denial as behavioral redirection. Priya had built parts of the decision engine and sat silently while the others congratulated themselves.
“We classify requests by channel compatibility,” Derek explained. “A customer with high support needs should migrate to guided digital service.”
“Who determines high support needs?” asked Corinne Shaw, the finance director.
“A weighted matrix. Age of platform, frequency of manual interaction, absence of digital authentication, transaction patterns.”
“Does the matrix use the customer's age?”
“Not directly.”
Priya looked up. She had warned Derek that several variables acted as near-perfect proxies for age, and that customers with older accounts often had no realistic way to satisfy the new verification prompt. He had told her the bank wanted operational segmentation, not a philosophical debate. She watched Corinne make a note that read AGE NOT USED and felt the familiar discomfort of seeing something technically defensible become misleading through omission.
Julian clicked to a chart that predicted three million dollars in annual savings. “We have board resistance because of a highly publicized branch incident. I need the compliance position settled today.”
Derek leaned forward. “The system doesn't refuse anyone. It places them in a referral queue.”
“What happens if the queue isn't staffed?” Priya asked.
The room became quiet. Derek turned toward her with a smile intended to erase the question. “Our deployment assumes proper staffing.”
“Then the outcomes depend on a service the savings model recommends eliminating,” she said.
Julian stared at the graph. He understood at once. He also knew the contract had been signed under a procurement exemption granted to a company whose owner was the brother of a Northbridge regional vice president. The relationship had been disclosed in a footnote that legal had accepted, but no independent review had challenged the vendor's claims about access. He told himself that every large implementation involved mismatches between policy and practice. They could fix this before anyone noticed. That had been his answer to inconvenient facts for longer than he liked to admit.
After the meeting, Priya found an email in her inbox instructing the vendor's analysts to remove demographic comments from the quarterly methodology note. She saved the message in the project repository as required by her team's document-retention rules. Later she drafted a longer note explaining how the model had been tested only against users who already had smartphones and recent transactions. The excluded population included precisely the people the bank claimed it could serve through referrals.
At lunch she sat outside on a concrete bench overlooking the traffic. An older man nearby held a paper map against the breeze, trying to find a hospital. Priya gave him directions, then watched him fold the map carefully. It struck her that maps were useful only if the roads on them were still open. A digital banking route with no person at the end was not a route at all.
She sent her methodology note to the vendor's internal compliance officer and copied herself through the approved system. She did not call it a whistleblower report yet. She believed there was still time to correct the assumptions through engineering channels. In the afternoon, however, the project manager responded that the scope of her inquiry exceeded the current release. She was instructed to focus on performance validation and avoid customer-impact commentary. Priya printed the instruction, dated it, and placed it inside her work notebook. The margin already held a question she had written months earlier: What happens to the people who cannot follow the path we've designed?
- · ·
Lillian Park invited Evelyn to the bank's archives on Monday morning, away from the public branch. The archive occupied part of a converted warehouse near the river, where the air smelled of cardboard, dust, and the machine oil from the freight elevator. Northbridge had moved its historical records there during the last renovation. Its public website celebrated a century of service, yet the people running the business rarely visited the room where that history was stored.