Andrew Waller
There's a particular moment that tends to happen early in a software selection project. Someone puts a feature list on the table, usually supplied by a vendor, and the room starts working through it item by item. Does the system do this? Tick. Can it handle that? Tick. It feels productive. It rarely is.
Remit Consulting has spent more than two decades avoiding that room entirely. Since the business was founded, the firm's approach to helping asset managers and fund managers choose IT systems has started somewhere else: not with what a piece of software claims to do, but with what the client's business does, day to day, workflow by workflow.
Finding out what you do
Process mapping sounds like a dry, back-office exercise, and in the wrong hands it can be. But the question at the heart of it is anything but administrative: what is the work the business needs to undertake, and how should that work be done in future? Not what a brochure says a system offers, nor a painstaking record of every inherited habit, but a clear, agreed view of the outcomes, decisions, responsibilities, data and controls needed to run a property, portfolio or fund well.
Reaching that view still means working with the people closest to the activity. Their experience reveals where work stalls, what is duplicated, which judgements matter and where poor data or unclear ownership causes friction. But Remit does not simply ask teams to describe today and then preserve it. We use our process library, sector experience and structured workshops to test assumptions, introduce leading practice and build agreement around a practical future state.
Since 2003, this approach has generated a substantial library of processes and a methodology that keeps evolving as client businesses and the technology available to them change. That library acts as an accelerator and a source of challenge: workshops do not begin with a blank page or assume that current practice is right. They begin with a tested view of what good can look like, which is then adapted to the client’s objectives, terminology and constraints. Over two decades on, Remit is running more process workshops than at any point in our history and finding more opportunities within them to identify where savings and better outcomes can be achieved.
Relevance
It would be easy to assume that process mapping is a legacy discipline, useful in an era of clunky software but less relevant now that AI may sweep away whole sequences of work. That challenge is fair, but it points to the need for better process design, not less of it. AI will remove some tasks, combine others and change where human judgement is required. Before any organisation can automate or redesign work responsibly, it must still agree on the outcome required, the information the process depends on, who remains accountable and where exceptions or controls sit.
That is why Remit’s maps are not intended as monuments to the present. They are working designs for the future: clear enough to support a current implementation, but capable of evolving as AI, automation and operating models develop. AI tools are only as good as the workflows, data and governance around them. Feed them confusion, and they will automate confusion faster than any human ever could.
Case study
Last year, Remit was approached to advise on the selection of a new software system, and the initial appetite for a full process mapping exercise was, to put it diplomatically, lukewarm. It was seen as an extra step, a delay before the real decision-making could start.
As the project progressed, that view shifted. The future-state process map that Remit developed with the client became the structure used to specify and shape the new system. The workshops did more than secure assent: they gave users a disciplined forum in which established habits could be questioned, alternatives tested and decisions made collectively. Rather than slowing the project down, the process work gave it something firm to build on, meaning fewer meetings circling the same undefined problem and a much clearer route from “we need new software” to a system designed around the business the client wanted to become.
Resist the urge!
For asset managers, property managers and fund managers weighing up a system or AI-enabled change, the lesson is not complicated, even if it runs against instinct. Resist the urge to start with vendors or tools. Start by agreeing the work, outcomes and controls the future business will need. That does not mean freezing today’s process, and it does not mean allowing the most change-resistant voice in the room to define tomorrow’s. It means using informed challenge and careful facilitation to create a future state that people understand, can scrutinise and are more likely to adopt. By the time a project reaches procurement or pilot, that shared design tends to be the thing that saves the most time and the most avoidable meetings.
The technology will keep changing, and some activities mapped today will disappear. The underlying question Remit keeps asking - “What is the work that actually needs doing?” - has not changed in twenty years. In an AI-enabled world, it is becoming more useful, not less.
If you're weighing up a system change and want to talk through where process mapping might fit into that, you can contact me directly.
