Launch issue

The customer sees one thing, you built it out of twelve

An organisation experiences itself as departments, budgets and systems. A customer experiences a single continuous thing that either worked or did not. Everything worth fixing lives in the gap between those two views.

Start with the mismatch, because almost every other problem grows out of it. Inside an organisation, work is divided so it can be managed. There is a team for sales, a team for onboarding, a team for billing, a team for complaints, and each has its own targets, its own systems and its own idea of where its job stops. From the inside this looks orderly. From the outside it is invisible. A customer does not know your structure and has no reason to learn it. They asked for one thing, and they are waiting to see whether they get it. The division of labour is your problem to manage, not theirs to navigate.

So the seams do not exist for the customer until they fail. Then they exist very loudly. The form that has to be filled in again because the second team cannot see the first team's record. The promise made at the point of sale that the delivery team never heard about. The account that is active in one system and pending in another, so the person on the phone insists the problem is not happening while it is plainly happening. None of these are caused by lazy or careless staff. They are caused by the fact that nobody was ever made responsible for the space between two teams, and space with no owner fills up with failure.

The Whole Journey

The seam is where the experience actually breaks

Most failures are not inside a team. They are in the space between two of them.

Nobody owns the middle of the journey

The start and the end attract attention. The long ambiguous middle attracts none.

Your structure is not a map anyone else can read

Asking customers to route themselves through your organisation is asking them to do your job.

Effort

Effort is the measure that tells you what to do

Satisfaction describes a mood. Effort describes a specific thing you can change.

Being asked for what you already hold

Nothing signals indifference faster than a question you should already know the answer to.

The transfer, and the second explanation

Every handoff asks the customer to tell the story again, and the story gets worse each time.

Recovery

Something will go wrong, so design for that

Failure is not the exception in your process. It is a permanent, predictable part of it.

The apology that is not an apology

Regret about someone's feelings is not the same as responsibility for your actions.

Let the front line fix the small things

Authority parked two levels above the customer turns a five minute fix into a fortnight.

Listening Properly

A score tells you the weather, not the cause

You cannot fix a number. You can only fix the thing the number is reacting to.

Complaints are cheap research, usually buried

Someone has done detailed unpaid analysis of your weakest process and handed it to you.

Close the loop or do not ask at all

The quiet majority never tells you. The few who do deserve to learn it mattered.

About CX and Co

CX and Co is a magazine about customer experience in the literal sense: what it is actually like to deal with an organisation, from the outside, as the person who needs something. Not the branding, not the promise, not the intention on a slide. The queue, the form, the transfer, the wait, the letter that answers a question nobody asked. We are interested in that gap because it is where most of the value quietly leaks out of otherwise competent organisations, and because it is generally fixable by people who already work there, using information they already have, without buying anything.

The editorial position is plain. Effort matters more than delight, because effort is what customers notice and what makes them leave. Structure explains most failures, because organisations experience themselves as departments while customers experience one continuous thing. Recovery is a design problem rather than an embarrassment, since failure is permanent and predictable. And listening means reading what people actually said and watching what they actually did, not collecting a number that moves for reasons nobody can name. We would rather describe one dull mechanism accurately than invent a memorable phrase for it.

We avoid the usual register of this subject. No coined terminology, no maturity ladders, no promise that a framework will resolve a problem that is really about who is allowed to decide things. We do not name organisations, good or bad, and we do not retell anecdotes about real incidents, because the point is the pattern rather than the villain. Where a tendency is well understood, we say so qualitatively instead of inventing a figure to make it sound rigorous. The subject is ordinary and the writing should be too. If an article does not suggest something you could change on Monday, it has failed.