Most people in Greece don't buy insurance because they believe in it. They buy it because the law requires motor insurance, because the bank requires it to release a mortgage, because the accountant told them it was tax-deductible. The transaction is compliance, not conviction.

I've spent three years designing the mobile experience for Anytime by Interamerican — Greece's largest insurance group. What that time has taught me: the UX problem in Greek insurance is not a design problem. It's a relationship problem. And design is the last mile of a broken trust contract that started decades before any screen existed.

Why Trust Is Structurally Low

Greek insurance penetration is among the lowest in the EU — roughly 2% of GDP versus the European average of 7–8%. This isn't explained by price. It's explained by history. The Greek public has a well-documented relationship of distrust with large institutions: banks, the state, and insurance companies occupy similar psychological territory. They are entities that take your money and are hard to reach when something goes wrong.

The claims experience historically reinforced this. Long wait times, opaque processes, disputes over what was covered. Word-of-mouth about bad claims experiences travels faster and further in a country where personal networks are the primary trust infrastructure. The product's promise — "we'll be there when it matters" — had a credibility problem that no homepage redesign could fix.

What This Means for Design

When I joined the Anytime team, the brief was ostensibly a mobile app redesign. V2.0, new design system, modern UI. What became clear quickly was that every design decision was downstream of a more fundamental question: how do you make a promise legible in a context where the promise isn't trusted?

This changes how you think about almost everything.

Clarity over cleverness. Insurance products are complex by nature — exclusions, coverage limits, policy conditions. The instinct in good UX is to simplify. But in a low-trust market, oversimplification reads as hiding something. Users who don't trust you are reading your interface for what you're not saying. The design response is radical transparency: surface the policy terms clearly, show coverage limits explicitly, don't bury exclusions. Let the product be honest, even when honest is uncomfortable.

The claims flow is the product. Every insurance app has a claims section. In most markets, it's a secondary feature — the purchase and policy management flows get the design investment. In Greece, the claims flow is the primary trust signal. Users aren't evaluating your app by how easy it is to buy a policy. They're evaluating it by how easy it would be to file a claim if something went wrong. I spent more time on the e-claims UX — the first automated claims flow in the Greek market — than on any other part of the product. Because that's where the promise lives or dies.

Human touchpoints matter more than digital ones. The Anytime app is mobile-first. But the highest-trust interactions still happen through the broker network and through customer service. Design can't replace those. What it can do is make the digital experience feel like it belongs to the same brand that the trusted broker represents. Visual consistency, tone of voice, the way the app handles error states — all of these either reinforce or undermine the human relationship.

The E-Claims Question

When we designed the first automated e-claims flow for Anytime, the question wasn't whether the technology could handle it. The question was whether users would trust it.

Our hypothesis was that the right UX could close that gap — that if the flow felt guided, human, and transparent about what was happening, users would follow it. We were right, mostly. The adoption curve was slower than a UK or German market would produce, but it moved. Users who completed one automated claim came back for the next one. The experience changed their mental model of what filing a claim could feel like.

That's a design win. But it required accepting that the first cohort of users would be skeptical and designing for their skepticism rather than against it. Every step of the chatbot flow was reviewed with the question: "What does a distrustful user read into this?" That framing produces different design decisions than "what's the fastest path to completion?"

What the Greek Market Taught Me About Insurance UX Everywhere

Greece is an accelerated case study in something that's true across most insurance markets: the product's UX is not the hardest problem. The hardest problem is the relationship the product inherits. Designing for low-trust environments requires accepting that the interface is not the thing doing the trust work — it's the evidence layer for trust work that happens everywhere else.

The designers who make a real difference in insurance UX are the ones who understand the full trust chain: the regulatory environment, the claims culture, the broker relationship, the customer service quality. Design that ignores these upstream factors produces beautiful apps that fail to convert because they're solving the wrong problem.

After three years in this market, I've become somewhat obsessed with the gap between what insurance interfaces promise and what the underlying product delivers. Closing that gap — through honest content, transparent claims UX, and mobile experiences that feel as reliable as the product they represent — is the actual work. The pixels are just how you show it.