The meeting is halfway through when it happens. The Real Estate department presents an overview of maintenance costs per unit. Immediately afterward, the Housing department shows a report on vacancy rates, with different totals for exactly the same neighborhoods. The discussion grinds to a halt. The conversation is no longer about the content, but about the numbers. “Why do our totals differ?” “Which data is correct?” Sound familiar? This scenario is a classic symptom of a deeper, non-technical problem. It stems from the fact that different departments, with the best of intentions, view the same reality from their own perspectives.

Two departments, one truth

For a housing authority, a “home” is not just a home. It is a concept with different meanings, depending on who is looking at it:

• To the Real Estate Department, a home is simply a collection of technical data: year of construction, energy efficiency rating, assessed property value, and the condition of the boiler.
• For the Housing Department, a single dwelling constitutes both a social and an administrative unit: is it rented out, who is the tenant, what is the rent, and are there any special social circumstances?

Both perspectives are correct and essential. The problem arises when these two truths coexist without an overarching, shared definition. For example, is each unit within an intramural property counted separately, or only the entire building? And are units that are not in use also included? Without that common language, reports will always differ from one another, and mutual distrust in the data will persist.

The technological reflex: a costly mistake

The initial reaction of many IT departments is to try to solve this problem with technology. “We need a better data warehouse,” or “The new BI platform will integrate this.” But this is a costly fallacy. A new, more expensive platform doesn’t solve the definition problem; it merely automates the chaos. The result is that you can see even more quickly—and on a nicer dashboard—that the numbers still don’t match up.

Technology is never the first step. Technology is the enabler of the solution, not the solution itself.

The solution isn't a technical fix, but an agreement

The only sustainable solution is to create a “single source of truth,” also known as a “golden record.” This is not a technical database, but an organizational agreement. It is the process by which the entire organization agrees on unambiguous definitions for its most important data.

What is the official definition of a “rentable unit”? What criteria do we use? And who owns that definition and the associated data?

The foundation of a successful data strategy for housing associations lies in establishing these definitions. This is not an IT project, but a business discussion facilitated by IT. It compels departments to look beyond their own boundaries and work together toward a single shared truth.

Only once those agreements have been reached can the technology do its job: building a platform that makes this single source of truth accessible to everyone in a reliable and consistent manner.

From a debate about numbers to a discussion about the substance

The result of this approach is transformative. The endless, energy-sapping debates about the reliability of the figures disappear. Confidence in the data grows. Meetings are no longer about defending one’s own reports, but about the content: what do these figures tell us, and what decisions do we need to make?

The most important step toward a data-driven culture is not a configuration in a server room, but a conversation in the conference room.