
Many AI initiatives begin with a model and a demo. The demo works because it was built on a clean, well-understood dataset. Then the project meets the organization's actual information — spread across file shares, SharePoint sites, line-of-business systems, spreadsheets, and a few databases nobody fully documents — and progress slows.
That is not a failure of the AI. It is a signal that the data foundations need attention first.
Know where the authoritative source is
For any question an AI system is expected to answer, there should be a clear source of truth. Which system holds the current customer record? Which document is the approved policy? Which spreadsheet is the real forecast, and which are copies? If people inside the organization cannot answer these questions consistently, an AI system will not answer them reliably either.
Connect before you generate
Useful AI often depends on combining information that currently lives in separate places. That may mean integrating systems, building a reporting layer, or simply agreeing on common definitions for terms like active customer or completed order. This work is less visible than a chatbot, but it is what makes the chatbot's answers worth trusting.
Permissions travel with the data
When AI systems retrieve information on behalf of users, they need to respect who is allowed to see what. Data brought together for AI should carry its access rules with it. Designing this in from the start is far easier than retrofitting it after sensitive information has been exposed through a new interface.
Sometimes the answer is a report
Not every information problem needs a model. If people need to see the same figures every week, a well-built report may serve them better than an assistant that generates the numbers on request. If a process needs data moved from one system to another, an integration may be the right fix. AI is most valuable where the information is varied, the questions are open-ended, or the work involves reading and summarizing content at scale.
The organizations that get practical value from AI tend to treat data as the first project and AI as the second. The order matters.



