Earlier in this series, organisations across Malaysia and Southeast Asia were invited to spend a working week noticing seven specific moments — the first spreadsheet on Monday, the WhatsApp decision on Tuesday, the custom transaction on Wednesday, and four more through the week. The follow-up, Not Every Shadow System Is a Problem, offered a sorting framework for what the observation produced — three categories of shadow system, each requiring a different response.
In the organisations that took the exercise seriously, a list exists. Sometimes in a notebook. Sometimes in a draft document on a senior leader's desktop. Sometimes only in the head of the person who did the observing. The list contains adaptations the business is glad to keep, symptoms the system is producing, and risks that warrant action regardless of any broader decision.
The list, by itself, does not change anything. This is the part that catches most organisations.
A sorted list is a starting point, not an action plan. It tells leadership what is happening. It does not tell them what to do, in what order, at what cost, with what trade-offs. More importantly, it does not survive the questions that will be asked of it the moment it becomes a serious item on a leadership agenda.
A finance director will ask which items have been costed and which are estimates. An audit committee will ask which risks are escalated, by whom, on what timeline. A board will ask what the cost of inaction is, and how confident the organisation is in its categorisation. The list, as it stands in most organisations, does not survive any of these questions cleanly.
This is not a failure of the observation work. The observation work was correct. The sorting work was correct. What's missing is the next layer — the layer that comes from someone who has run this pressure-test on comparable organisations and can quickly identify which items in the sort matter most, which are likely misfiled, and which are urgent regardless of broader decisions.
Why an outside view at this stage
Internal sorting tends to be biased in two predictable directions. The first is toward classifying symptoms as adaptations — because adaptations require less action and feel like progress signals rather than warnings. The second is toward classifying risks as symptoms — because risks demand immediate escalation, and most organisations prefer to bundle them into a longer-term system conversation that postpones the difficult decisions.
Both biases are understandable. Both are expensive. An outside view, applied at the right moment, validates the categorisation before the leadership team commits time and political capital to acting on it.
The view that helps most is not generic consulting commentary. It comes from someone who has worked specifically with organisations of comparable size, sector, and system maturity — who has seen what shadow systems typically look like in those environments, which categorisations usually drift in which directions, and what the cost of staying put has actually been for organisations that did stay put.
What the conversation produces
Wiz Asia's senior consultants run thirty-minute conversations specifically with organisations that have completed the observation and sorting work and want a pressure-test before deciding what to do next.
The conversation is not a demo. It is not a pitch for a system migration. The consultant brings pattern recognition from comparable engagements; the organisation brings its sorted list. In thirty minutes, the conversation produces three things.
First, an indication of whether the sort holds up — which items are likely correctly categorised, which are likely misfiled, and which require more information to assess.
Second, a prioritisation view — which items, if any, the consultant would treat as urgent regardless of broader system decisions, and why.
Third, a clear view of what an action plan would look like for that specific organisation — whether that involves reconfiguration within the current system, a structured migration evaluation, risk-response work that runs independently, or some combination.
The output is verbal. Nothing is committed to paper during the call. The organisation leaves with a sharper view of its own sort and a clearer sense of which next step makes sense for its specific situation.
Why this is worth thirty minutes
Most organisations that complete the observation and sorting work and then do nothing for a quarter find themselves at the start of the next quarter holding the same list, asking the same questions, having absorbed another three months of compounding cost from the symptoms and risks they identified. The cost of doing nothing is not zero. It is the cost of every workaround, every consultant hour, every reconciliation, every continuity risk, continuing to compound while the conversation is postponed.
A thirty-minute conversation with someone who has worked with comparable organisations is the lowest-cost way to convert sorting work into a credible internal recommendation. It is also the lowest-cost way to confirm that no further action is needed, in the cases where that turns out to be the right answer.
Where Odoo fits
Wiz Asia is an authorised Odoo Silver Partner, so the pressure-test does not stop at the sort. Where the list points to the system itself, the consultant maps each item against Odoo: which adaptations become configuration rather than custom development, which symptoms disappear when finance, operations and purchasing work from the same record, and which risks shrink when ordinary changes no longer need a developer.
Where the list points somewhere else — a process, an ownership gap, a continuity risk that documentation would fix — the consultant says so. The category-by-category view of how Odoo handles each type of shadow system is in Not Every Shadow System Is a Problem.
Who the conversation is with
The conversation is with a senior consultant from Wiz Asia, an authorised Odoo Silver Partner, who has worked with organisations across Malaysia and Southeast Asia on legacy ERP environments — including SAP and other major platforms. The consultant's job in the conversation is to apply pattern recognition, not to sell. If the conclusion is that the organisation is correctly categorised and on the right path internally, the consultant will say so.
For organisations whose observation and sorting work has produced a list — and whose leadership team has begun asking what to do next — this is the next useful step.