Start With the Decision, Not the Report

Before you replace the system that runs your business, change the question you are asking it.

When people get frustrated with the information coming out of their business, one of the first thoughts is often: maybe we need a different system.

Sometimes that is true. There are legitimate reasons to change a dealer management system, and an older DMS really can create limits you cannot work around.

But replacing the software that runs the business is not a purchase. It is a conversion, a retraining of every department, and six months from start to finish at the very best. Three months happens, but it is rare enough to be remarkable. A year is not unusual. Before you commit to that, there is a much cheaper question worth asking: are we getting everything we can out of the system we already have?

In a lot of businesses the answer is no — and not because the staff cannot use it, and not because the software is poor.

Your system already records more than you are asking it

Think about what passes through the system in a normal month: sales, purchase orders, inventory receipts, parts sales, work orders, customer records, labor, pricing, inventory adjustments, payments, credits, and accounting entries.

Most businesses have years of that history sitting in the same place. It tells a very detailed story about how the operation runs.

The difficulty is that almost all of it was recorded in order to complete a transaction. It was not organized around the next management decision. That is a real distinction, and it is where most of the frustration comes from.

What are we trying to decide?

The easiest way to get more out of an existing system is to stop asking “what reports do we have?” and start asking “what are we trying to decide?”

Those sound like the same question. They lead in completely different directions.

A parts manager may not need another inventory report. The real question may be: which items are tying up enough money that we should take a closer look? A service manager may not need another open-work-order report. The real question may be: which jobs have stopped progressing, and what are they waiting on? An owner may not need another margin report. The real question may be: where are we selling enough volume that small pricing problems have become meaningful? A controller may not need another month-end report. The real question may be: which recurring problems could we catch during the month instead of cleaning them up afterward?

Once the question is clear, you can work backward from it.

Recording a transaction and managing a business are different jobs

The system has to be dependable. It has to process the transaction correctly and preserve the record. That is its first responsibility, and a good one does it well.

Management has a different job: interpreting what those records are telling you.

The system can show you the current retail price, the cost, the units sold, the last sale date, and the quantity on hand. Those are facts. The management question is something else — are there products where the current price no longer makes sense, given cost, sales activity, and how we run this category?

That takes more than putting fields on a screen. It takes context. Sometimes a person supplies it. Sometimes a process does. Sometimes training helps the team recognize it, and sometimes a tool makes the review faster. But the underlying data is usually already there.

Things that look like a software problem

A surprising number of problems that seem to need new technology get better by using existing information differently.

What makes the information trustworthy

There is a practical limit here. You can only get value from information you can reasonably trust.

If manufacturer codes are entered six different ways, reporting gets harder. If work-order statuses do not mean the same thing from one employee to the next, you cannot tell where work is actually stalled. If customer records are duplicated constantly, follow-up stops being dependable. If costs or categories are not maintained, the analysis on top of them is worth less.

That does not mean the data has to be perfect. Nobody has perfect data. But consistency improves everything downstream of it, and cleaning up a few important habits often creates more value than adding another report.

The other half of trustworthy information is not in the database at all. The parts counter knows which oddball item the largest commercial customer always needs. The service writer knows which job is waiting because the customer is out of town. The salesperson knows a particular quote is not really lost. The controller knows why a balance looks strange this month.

Good management combines both — what the system knows, and what the people know. You need both, and neither one substitutes for the other.

Ask a better first question

If you are frustrated with your reports, or you cannot get the answers you need, resist the urge to jump straight to “what software are we missing?”

Look first at what your current system already knows.

You may find that the next improvement is not a replacement at all. It may be a better question, a clearer process, some training, or a better way of getting the right information in front of the right person.

Your existing system probably knows a great deal more about your business than you are asking it to tell you.