Skip to content

What years of work with Gjensidige taught me about customer communication

Published:
5 min read

Some customer relationships teach you more than any course or certification ever could.

For me, Gjensidige is one of those customers.

For readers outside Norway: Gjensidige is one of the large Nordic insurance companies, listed on the Oslo Stock Exchange, with operations in Norway, Sweden, and Denmark. General insurance is its core business, and in Norway it also offers pension and savings products.

XPER recently wrote about the cooperation with Gjensidige, and it made me think about what this kind of long-term work actually teaches you.

I have worked with Gjensidige on and off for many years, across document production, customer communication, integrations, batch processing, online document generation, print flows, email, SMS, archives, and the slow, careful modernization of systems that most people never see.

That last part matters.

Customer communication systems are usually invisible when they work. A customer receives the right letter, with the right data, in the right language, through the right channel, at the right time. Nobody celebrates it. Nobody says, “Great batch architecture today.”

But when it fails, everybody notices.

A wrong amount in a letter. A missing document. A PDF that cannot be read properly. An SMS that bounces. A template that behaves differently in Denmark than in Norway. A production run that creates thousands of documents before anyone realizes something is off.

That is the reality of CCM work. It looks boring from far away, but it sits very close to trust.

The real work is not just templates

A lot of people think document systems are mostly about designing templates.

Templates matter, of course. But in large organizations, the template is only the visible surface.

Underneath you have business rules, customer data, product logic, legal text, language variants, channel selection, archive requirements, delivery systems, monitoring, fallback handling, performance constraints, and operational routines.

At Gjensidige, I worked with many of those layers over the years. Some projects were about moving or modernizing document production. Some were about building infrastructure around HP/OpenText Exstream. Some were about high-volume batch output. Some were about online generation and local print. Some were about email and SMS communication, including bounce handling.

The common thread was always the same: make customer communication reliable enough that the business can trust it.

Not flashy.

Important.

Long-term customers are different

Short projects can be useful, but long-term customer relationships are where you really learn the domain.

You stop seeing only the task in front of you. You start understanding why the system looks the way it does. Which decisions were made ten years ago. Which integrations are fragile. Which documents are business-critical. Which manual routines are actually protecting production from chaos.

That kind of knowledge is hard to buy quickly.

It is also why I like the XPER model. We are not just dropping in with generic consultants. In the best cases, we become part of the customer’s technical memory. We know the systems, the people, the history, and the consequences of changing the wrong thing too casually.

Gjensidige has also been a good customer because they take the document domain seriously. The recent XPER article about the cooperation mentions trust, openness, and specialist competence. That sounds like normal company-language, but in this case I think it is accurate.

Good CCM work needs trust. The customer has to trust that you understand both the technology and the business risk. And you have to be honest when something is fragile, unclear, or more complicated than it looks.

Accessibility is the next serious chapter

One thing I respect about Gjensidige is that they are taking accessibility seriously.

The European Accessibility Act is easy to treat as a compliance deadline. But for customer communication, accessibility is more basic than that.

If a customer cannot read or navigate an important document, then the communication has failed. It does not matter that the batch ran successfully. It does not matter that the PDF opened visually. It does not matter that the archive received a file.

The message did not reach the person properly.

That is especially important in insurance, banking, healthcare, pensions, and public services. These documents are not marketing material. They explain rights, obligations, money, risk, decisions, and next steps.

Making them accessible is not cosmetic work. It is part of the communication system doing its job.

Why this still matters in the AI era

I keep coming back to this because AI is changing the surrounding work very quickly.

AI can help analyze templates, explain old logic, classify document types, simplify language, detect anomalies, generate tests, and support migration work. I am genuinely excited about that.

But AI does not remove the need for controlled communication systems.

If anything, it makes the boring foundations more important.

The output still has to be correct. The audit trail still matters. The business still owns the message. Legal text cannot be casually improvised. Customers still need consistent, accessible, and trustworthy communication.

So the future is probably not “AI replaces CCM”.

The useful future is AI around CCM: helping teams understand, improve, test, migrate, and operate these systems with more confidence.

That is why the Gjensidige work has stayed interesting for me. It combines old enterprise reality with new problems that are becoming more important: accessibility, modernization, automation, and now AI-assisted quality work.

Underneath all of it is a simple principle.

Customer communication is not just output.

It is part of the relationship between a company and its customers.

And that deserves proper engineering.


Edit on GitHub