Designing CX for Humans, Not Dashboards
Most companies will tell you they’re customer-focused. They roll out new CX platforms, build dashboards, and proudly show executives all the ways they can measure the customer journey. But here’s the uncomfortable truth: too many CX programs are designed to make reporting easier, not to make customers’ lives easier.
I’ve seen it first-hand. A sales rep forced to fill in ten extra fields in Sales Cloud, not because the customer benefits, but because someone in management wanted cleaner pipeline reports. A field technician in Field Service who spends more time clicking through checkboxes than actually helping the customer. A commerce checkout flow designed around marketing attribution tags, instead of making it easy for the buyer to pay and leave happy.
The dashboards look great. The experience doesn’t.
The trap of designing for metrics
The irony is that dashboards were meant to be a by-product of good CX design. When the customer journey works well, the data naturally flows into the system. Instead, we flipped it: we build the journey to match what the dashboard wants to see. That’s when empathy gets lost.
Get Satish Das’s stories in your inbox
Join Medium for free to get updates from this writer.
Customers don’t care if your SLA reporting is accurate. They care if their issue was fixed quickly. They don’t care about your lead conversion funnel. They care if your sales team actually understood their needs.
Putting humans back at the center
The shift is simple in theory, harder in practice: stop asking “What will this look like in a report?” and start asking “What will this feel like for the customer?”
- When designing a sales process in CPQ, don’t let approval flows drag on for days just to satisfy finance controls. Customers remember how long it took to get a quote, not how perfectly it matched a compliance checklist.
- In service interactions, reduce the number of steps agents need to log. If the system can capture context automatically — timestamps, call duration, even intent from AI — let it. The more natural the interaction, the more human it feels.
- In commerce, test your checkout as if you were the customer. Strip away the friction that was added for “marketing data capture.”
The payoff is bigger than the report
Here’s the funny thing: when you design for people, the dashboards usually get better anyway. Why? Because the data reflects reality. Sales stages actually match customer progress. Service cases tell the real story of customer sentiment. Field service reports show what actually happened, not what someone clicked under pressure.
And beyond data, the real win is trust. Customers who feel understood and respected come back. Employees who aren’t treated like “data entry clerks” actually use the system properly. That’s the flywheel of real CX.
Final thoughts
Dashboards are necessary. Leaders need them. But they’re not the reason customers choose you, stay loyal, or recommend you. The real scorecard is written in the customer’s memory of how easy — or painful — it was to do business with you.
So here’s my advice: design for the human moments first. If you do that, the dashboards will take care of themselves.
