Designing for human connection
A customer in a research interview said the same sentence twice. Her order was fine, but nobody could tell her why the delivery date moved. She did not want a refund. She wanted somebody to explain.
Every process is built around the customer who fits it. Connection gets decided at the edge, in the cases the flowchart has no box for, where somebody needs what the system was never asked to do.
Where the rules run out
Loyalty is decided by the exceptions, not the rules.
The support agent she spoke to had followed the script correctly. Three replies apologized for the inconvenience and repeated the new date. None of them said who had changed it or whether it could change again. By the fourth reply she stopped writing and the account went quiet.
One sentence changed the form
Verbatim complaints are easier to act on than themes.
Her line about nobody being able to tell her why went into the notes word for word. It named a missing fact, not a feeling. The delivery status page carried a date and a progress bar and no reason field.
That change was one line under the date, giving the reason and the team that set it. Work like that gets priority when the alternative is a customer having to ask.
The authority to break rules
An exception only happens if somebody is allowed to make it. Most teams put that permission two levels up, so the person actually talking to the customer has to say they will check and come back. That wait is what the customer feels. Giving the front line a small standing allowance, and a written limit on it, removes the wait without removing the control.
Exceptions cost the people handling them
Generosity has a price, and staff usually pay it.
Each exception made by hand costs handling time, and handling time is what support staff are measured on. If the same person is rewarded for closing tickets quickly and asked to slow down for the odd case, the metric wins.
Logging each exception in one place turns goodwill into information. When one kind of exception shows up every week, the rule is wrong and the product needs the fix, not the agent.
Writing the exceptions down
Behavior lists outlast visual identities. Two entries from one of them read like this. Anyone answering a customer can waive a late fee without asking. Nobody sends an automated apology for a delay a person has already explained. The support lead and the design lead reread the list quarterly, and the next version gets written by the customers who did not fit this one.
The strongest approach is to combine technology with human thinking. Use AI to explore ideas, accelerate workflows, analyze information, and create new possibilities while keeping strategy.
