When I started building Bespoke Analytics, I made a classic founder mistake. I assumed that if I built something genuinely useful, people would want to engage with it. The product was useful. They did not want to engage with it.
The people I was building for — small business owners, operators, sole traders — had a complicated relationship with data. Not because they were unsophisticated. Because every data tool they had ever used made them feel like they were doing it wrong.
Lesson one: the interface is the product
I spent the first three months building the analytics engine. Clean data pipelines, solid aggregation logic, accurate numbers. Then I showed it to ten potential users. Eight of them felt anxious looking at the dashboard. One told me it reminded her of her accounting software, which she also hated.
The numbers were right. The interface was wrong. For people who are not data natives, a dashboard full of charts is not a solution. It is a problem with more visual detail.
Lesson two: invisibility is the goal
The best UX for a reluctant user is an experience that does not feel like using software at all. We moved toward plain-English weekly summaries. "You had your best Tuesday since October. Repeat what you did on the morning shift." No charts. No drill-downs. Just the thing you need to know.
"If someone has to think about how to use your tool, they will stop using your tool."
Lesson three: the resistance is the insight
Every time a user resisted engaging with the product, there was a reason. Sometimes the data was intimidating. Sometimes the framing was wrong. Sometimes the number was accurate but the context was missing and without context, a number is just noise.
Building for reluctant users taught me to be ruthless about what the product is actually for. It is not for showing data. It is for reducing the anxiety of not knowing. Those are different products.