Why the Best Fleet Conversations Begin With Questions, Not Products
Andy Dunne, Senior Solutions Consultant at Verilocation
When a fleet operator approaches a technology provider, it is usually because something needs to improve.
There may be too many incidents, rising fuel costs, underused vehicles, repeated compliance issues or an operational process that takes far longer than it should.
It can be tempting to respond by immediately recommending a product. However, the most valuable part of the conversation is not always having a quick answer.
Often, it is asking the right question.
Start With What Is Really Happening
The problem initially presented by a customer is not necessarily the underlying problem.
For example, a fleet experiencing repeated safety events might assume it needs more alerts. But what if the real issue is that managers do not have enough time to review and act on the alerts they already receive?
A business with poor vehicle utilisation might believe it needs additional vehicles. Further investigation could reveal that existing vehicles are being allocated unevenly or spending unnecessary time off the road.
An operator struggling with missing delivery paperwork may ask for better reporting. The real cause, however, could be an inconsistent process that begins with the driver and continues through several departments.
In each case, addressing the initial symptom without understanding its cause risks solving the wrong problem.
- What is happening today?
- Why is it happening?
- How frequently does it occur?
- Who is affected by it?
- What is the operational or financial impact?
- What has already been tried?
- What would a successful outcome look like?
These questions create a much clearer picture of the challenge before any solution is discussed.
Ask “Why?” More Than Once
Asking why something happened once may only reveal the most immediate explanation.
Suppose a vehicle was unavailable when it was needed.
Why? Because it was undergoing an unexpected repair.
Why was the repair unexpected? Because the defect was not identified early enough.
Why was it not identified? Perhaps the information was recorded manually, reported inconsistently or never reached the person responsible for acting on it.
The original problem appeared to be vehicle availability. The underlying issue may actually have been the way information moved through the business.
This does not mean every customer conversation needs to become an interrogation. It means being curious enough to look beyond the first answer.
The objective is to understand how the operation works in practice, not simply how a process is supposed to work on paper.
Separate the Symptom From the Cause
Fleet operations are interconnected. A problem in one area can easily appear as a symptom somewhere else.
A rise in fuel consumption could be connected to driving behaviour, route planning, idling, vehicle condition or the type of work being completed. Repeated harsh events could indicate an individual training need, but they might also be concentrated on a particular route or influenced by unrealistic schedules.
Late deliveries could be caused by traffic, yet they could equally begin with delays during loading, unclear instructions or poor communication between teams.
Technology can help identify patterns and support improvements, but it should not be used to jump to a conclusion.
Before recommending a solution, it is important to understand the people, processes and pressures surrounding the problem.
Challenge Assumptions Constructively
Customers understand their own businesses better than anybody else. However, when people work within the same operation every day, certain processes can become accepted simply because they have always been done that way.
An outside perspective can help test those assumptions.
Why does this task require several manual steps? Why is this report created if nobody acts on it? Why are vehicles allocated in this way? Why does the same issue continue to appear despite previous attempts to address it?
These are not questions designed to criticise the operation. They create an opportunity to look at familiar challenges differently.
Sometimes, the answer confirms that the existing approach is necessary. At other times, it uncovers duplication, avoidable delays or a straightforward improvement that had previously been overlooked.
Define Success Before Selecting the Solution
A solution cannot be judged properly unless everyone agrees on what it is expected to achieve.
“Improve efficiency” might sound like a sensible objective, but it could mean many different things. Does the customer want to reduce administration, use fewer vehicles, improve delivery performance, lower fuel consumption or give managers more time to focus on higher-value work?
A clearly defined outcome makes it easier to select the appropriate solution and evaluate its impact.
For example, success might mean:
- Reducing the time spent investigating incidents
- Identifying recurring risks before they result in a collision
- Improving the utilisation of existing vehicles
- Removing manual steps from the proof-of-delivery process
- Giving managers earlier warning of potential compliance issues
Specific outcomes keep the conversation focused on operational value rather than a list of features.
The Right Solution Follows the Right Diagnosis
Fleet technology can address a wide range of operational challenges, but it delivers the greatest value when it is applied to a problem that has been properly understood.
That requires providers to listen, investigate and occasionally challenge what appears obvious.
It also means recognising that the right recommendation may not be the largest or most complicated solution available. It should be the one that addresses the underlying cause and delivers the outcome the customer genuinely needs.
For me, that is one of the most rewarding parts of working as a Senior Solutions Consultant: understanding the bigger picture and helping customers find practical answers that work within their operation.
Sometimes, the right question is the first—and most important—step towards the right solution.
