The Referendum That Counted: What Australia's 1967 Vote Teaches Us About Inclusive Systems
On May 27, 1967, over 90% of Australian voters said yes to a constitutional referendum — one of the most successful in the country's history. The question on the ballot was striking in its simplicity: should the Australian government have the power to make laws for Indigenous Australians, and should they be counted in the national census? For decades prior, Indigenous Australians had literally been excluded from the population count. They weren't in the data. And if you're not in the data, you don't exist to the systems designed to serve you.
That's not just a historical injustice — it's a systems design problem. In tech, we talk constantly about edge cases, but the truth is that "edge cases" are often just people we didn't bother to design for in the first place. Whether you're building a user onboarding flow, a reporting dashboard, or an AI model, the question of who is included in your data determines everything downstream — what decisions get made, who gets served, and who gets left out. The 1967 referendum didn't just change a law; it changed what the system was capable of seeing. That's the kind of architectural decision that ripples forward for generations.
So here's the prompt for your week: look at what your systems are measuring — your analytics, your user personas, your testing groups. Who's missing? Not every gap is visible from the inside, and that's exactly why it's worth asking out loud. The Australians who campaigned for that yes vote spent years making the invisible visible. In software, in business, in leadership, that work never really stops — and it's always worth doing.