My career has crossed government, enterprise software, artificial intelligence, process improvement, analytics, marketing, and education. On paper, those fields don't have a lot in common. In practice, they kept teaching me the same lesson from different directions.
In each one, I watched a reasonable question turn into a complicated project. Someone wanted to know what was actually happening on a block, inside an organization, across a process, or within a public institution. The answer existed. It just wasn't anywhere a person could get to it without time, technical skill, institutional memory, or all three.
Working inside operational systems taught me that isolated records rarely tell the complete story on their own. A permit is not only a permit. A property record is not only a property record. An inspection is not only an inspection. A vote is not only a vote. Each one is a fragment of a larger system, and the meaning only shows up once the fragments are connected — across time, across place, across the entities and processes involved.
Years spent in enterprise technology and artificial intelligence added a second lesson on top of the first: better tools don't automatically produce better decisions. I saw plenty of dashboards that could display activity without ever answering the question someone actually had. I saw AI systems that could generate confident-sounding language without producing anything a person should actually trust.
None of this was a single bad job or a single broken system. It was the same shape, over and over, in institutions that otherwise had very little to do with each other. That repetition is what eventually made the pattern impossible to ignore — and what sent me looking for an explanation on my own, outside of any job title or org chart.
That search is where this story actually starts.