Guide: Vendor Layer Memory Guide
Vendor Layer Memory Guide: A practical guide for checking what old systems, old data and old workarounds a shiny new AI or vendor layer is about to inherit.
Vendor Layer Memory Guide
A practical guide for checking what old systems, old data and old workarounds a shiny new AI or vendor layer is about to inherit.
Before buying the new layer, ask what old layer it has to stand on.
What this guide helps with
This guide helps teams avoid pretending that a new AI feature or vendor platform starts from zero. It is useful for buyers, operators, transformation teams and managers who want the new thing to work in the actual organisation, not the clean version from the demo.
Why now
AI features are being added to almost every platform. That makes it tempting to believe the new layer will solve what came before. Sometimes it helps. But if the old data, workflow, permissions and ownership are still messy, the new layer can inherit the mess quickly.
The pattern
The pattern is that old decisions become hidden infrastructure. A field, report, approval, spreadsheet or workaround may look ugly, but it may contain the memory of how the business actually survives.
The check
Before evaluating the new capability, name the older layers underneath it. Does it rely on ERP data, CRM records, SharePoint content, old reports, spreadsheets, APIs, manual approvals or local workarounds? A new vendor feature can look independent while quietly depending on years of unfinished operational history.
Ask which data sources, documents or workflow steps already cause problems today. If those inputs feed the AI layer, they will not become magically clean because the interface changed. For example, duplicate suppliers, stale policies and unclear ownership can all travel upward into the new tool.
Vendor demos usually avoid your weirdest Monday morning cases. Ask how the tool handles missing fields, exceptions, outdated documents, conflicting systems and users with different access. The gap between demo data and real data is where layer memory becomes visible.
Some workarounds are bad. Some are survival mechanisms. Before removing or hiding them, ask what they protect, fix or compensate for. An AI layer that deletes the workaround without understanding it may remove the only thing keeping a process usable.
If the new layer exposes an old problem, who owns fixing it? The vendor, IT, operations, data owners, process owners or local teams? Without an owner, the old mess becomes a new escalation thread with better branding.
Not every inherited issue must be fixed immediately. But the team should know what must be cleaned before wider rollout. Separate tolerable mess, risky mess and scale-blocking mess. That prevents “AI rollout” from becoming a tour of every unresolved system decision.
Quick examples
| Situation | Better question |
|---|---|
| AI search reads from old SharePoint pages | Which pages are current, which are local, and which are accidental fossils? |
| Vendor AI depends on ERP master data | Which fields are trusted enough to drive recommendations, and which should block output until cleaned? |
| A new workflow hides an old manual step | Is the manual step unnecessary, or is it handling exceptions the new tool does not understand? |
| A dashboard AI explains five different numbers | Which source is authoritative, and why do the other versions still exist? |
The Satire
The vendor sold the roof. Operations inherited the basement.
Related Vieews paths
Chaos scenes spot the contradiction. Signals name it. Guides give you the next simple move.
Chaos
The Blue Blob and the New Floor
The discovery scene that started this thread.
Signal
New Layers Inherit Old Mess
Use the signal when you want the pattern named clearly.
Playbook
Digital Work Portfolio
Use the heavier structure when you need the deeper lens.
Useful context
This guide supports the anti-cathedral layer: do not worship the new layer until you understand what it stands on.
These are Vieews, not bibles. Use them as simple lenses, not legal advice, investment advice, HR advice or a replacement for doing your own investigation. If a line makes the spreadsheet uncomfortable, excellent. Ask one more question and tug on that thread.
