Sometimes the most valuable thing a consultant can do is listen.
Not arrive with a ready-made answer. Not assume the process map tells the whole story. And not confuse a technically sound solution with one that will actually work in practice.
Just listen.
But in the rush to solve problems, meet deadlines and deliver results, it's surprisingly easy to overlook one of the most valuable sources of information available to us.
The people who do the work every day.
The person who uses the system eight hours a day and knows exactly where it falls short. The manager juggling competing priorities, trying to meet targets while keeping their team motivated. The employee who has quietly developed a workaround because the official process doesn't quite reflect the reality of their job. And the person who has raised the same concern several times but has gradually stopped mentioning it because nothing ever seems to change.
These are the people who understand how an organisation really operates.
And their experiences don't always make it into the process maps, project plans, or management reports.
There's often a difference between how a process is designed to work, and how it actually works.
A process might look perfectly logical on paper. Every step accounted for, every responsibility assigned, every approval neatly mapped out. But sit down with the people carrying it out, and a different picture can emerge.
Perhaps a particular step creates unnecessary delays. Perhaps two teams are unknowingly duplicating the same work. Or perhaps an important task depends entirely on one person's knowledge, with no documented process to support it.
These aren't always problems that can be identified by looking at systems and documentation alone.
Sometimes, the most revealing question is simply:
"Can you talk me through how you actually do this?"
Of course, listening doesn't mean accepting every existing practice as the best approach, or assuming that every frustration requires a new solution. It means being curious enough to understand the reasons behind things before deciding what needs to change. It also means recognising that different people can experience the same process very differently.
Without those different perspectives, even the most carefully designed improvements can miss the mark.
And listening is about more than gathering information. It's also about building trust.
Change can be unsettling, particularly when people feel that decisions are being made without understanding the realities of their work.
Being heard doesn't necessarily mean getting everything you want. But knowing that your experience has been considered, and understanding why decisions have been made, can make a real difference to how change is received.
At Antares, we believe meaningful transformation starts with understanding.
Understanding the processes, the challenges, the competing priorities and, most importantly, the people behind them.
Because successful change isn't simply about finding a solution that works on paper. It's about finding one that works for the people who will use it long after the project team has moved on.
Sometimes, the best way to move a project forward is to stop talking and start listening.
We're curious: What's the most valuable thing you've learned simply by stopping and asking someone how they do things?
Our insights are provided for general information only and reflect the position at the date of publication. They do not constitute legal, financial, regulatory, cybersecurity or other advice tailored to your circumstances and should not be relied upon as a substitute for appropriate professional advice.
While we take reasonable care over our content, we do not guarantee that it is complete, accurate or current. Reading our insights does not create a client relationship with Antares Consultancy. To the fullest extent permitted by law, we accept no liability for decisions made or losses arising from reliance on this content. External links are provided for convenience and do not imply endorsement.