Nobody owns the shape of the system

Your CRM is a mess for one reason, and it is not the one on the audit. It did not rot because people were careless. It rotted because every single decision was reasonable, and nobody was ever accountable for the shape of the whole thing.

That is the part that is hard to say out loud. There is no villain. You cannot point at the person who did this, because everyone did, a little, correctly.

Five records for one company. The top rep's private pipeline. A required field added in 2019 for a campaign that ended in 2019. Each of those was someone doing their job properly on the day. Together they are a system nobody chose.

Every decision was reasonable. That is the problem.

A messy CRM looks like negligence from the outside. It almost never is. It is the opposite - a hundred careful, defensible choices that never had anyone looking at them together.

Sales needed a field. It took four seconds and saved a conversation. Reasonable. Marketing needed it structured, not free text, so the segmentation would hold. Also reasonable. The two never got reconciled, because reconciling them was nobody's actual job, so it got decided by whoever was more senior or more tired.

Run that meeting a few hundred times over three years. That is your data model. Nobody designed it. It accreted.

Accretion is not a scandal. It is just what any system does when growth is everyone's job and coherence is nobody's.

The field added in 2019

Every CRM has one. A required field that made sense for something that no longer happens.

Someone needed it for a launch, or a report a board member asked for once, or an integration that got switched off. The launch ended. The field stayed required. So now every deal carries a value someone typed to get past it - n/a, a dot, a space - and it quietly poisons every report that touches it.

One audit I ran found 722 custom properties on a single CRM. 203 of them were empty. Not misused. Empty. Created for a reason that made sense to someone, on a day, and then outlived the reason by years.

Nobody removed them, because removing a field is a decision with risk and no reward, and owning that decision was, again, nobody's job.

There is no architect in the room

The reason these choices never get reconciled is structural. The question underneath each one - what is this field for, and who has to live with it - is an architecture question. And there is rarely an architect in the meeting.

There is someone senior. Someone tired. Someone protecting this quarter's number. All of them arguing correctly for their own corner. None of them accountable for the thing all their corners add up to.

So the system grows a dialect. Two pipelines mean different things by the word "proposal." The forecast cannot roll up. And everyone blames the tool, or the reps, or the data - the three things that are only reporting the problem honestly.

Ownership is not administration

The distinction the whole thing turns on is this. Your CRM has an administrator. It does not have an owner.

The administrator owns the buttons - permissions, workflows, the field that broke this morning. Necessary work, usually done well. But administering the system is not the same as being accountable for its shape. One keeps the machine running. The other decides what the machine is supposed to be.

Almost nobody has the second job. It is not on an org chart. It has no ticket queue. It is the most consequential unowned responsibility in most revenue organisations, and it stays unowned precisely because it is everyone's problem - and a thing that is everyone's problem is no one's job.

You cannot clean your way out of a shape problem

This is why cleanups do not stick. You export the contacts, merge the duplicates, and two weeks later the duplicates are back, because the shape that produced them is untouched. I have written about that as bloat and the revenue it leaks - the fields, the records, the quiet cost of a system carrying weight nobody chose.

Cleaning is a task. Shape is a job. You can run the task forever and the job stays undone.

The confessions version of this is that I have caused some of it myself - granted the exception, added the field, taken the quick fix that became the architecture. Every one defensible. That is the whole point. Defensible parts, accidental whole.

Name it and it stops being invisible

If you have felt this and could not say it, that is the tell. The problem is not that your system is broken in one specific place you can point to. It is that the whole has a shape nobody is responsible for, and unowned shapes only drift one way.

So the system keeps the shape it was never designed to have. It keeps it until someone's actual job is the whole, not the parts. Until then, every fix is a well-meant edit to a document with no author.

Common questions