Why Diakon?
The story behind the name — and why data governance is, above all, service.
Diakon comes from the Greek diákonos (διάκονος), which literally means "one who serves" — someone who runs through the dust to bring something to someone.
The word first appears in an administrative context in Acts of the Apostles, chapter 6. The early Christian community in Jerusalem had grown quickly. There were two cultural groups — the Hebrews (Aramaic-speaking Jews) and the Hellenists (Greek-speaking Jews). The widows from the Hellenist group were being overlooked in the daily food distribution — no one was recording them. They were invisible in the records.
So the apostles called the community together and said: "It would not be right for us to neglect the ministry of the word of God in order to wait on tables. Choose seven men from among you who are known to be full of the Spirit and wisdom. We will turn this responsibility over to them." The community chose seven — including Stephen and Philip. They were the first deacons.
The original problem was, at its core, a data governance problem: there were people who needed care, but they weren't in the records. The deacons were instituted to solve that problem — to ensure that no one would remain invisible.
That's what data governance is. Not bureaucracy. Not control for control's sake. It's about making sure the right data reaches the right people, that nothing gets lost, that everyone who depends on that information is seen and served. To serve, not to rule by power.
"Diakon (from the Greek diákonos, 'one who serves'): the first deacons were appointed so that no one would remain invisible in the records. That's what data governance is — service."
Pronunciation
DEE-uh-kon
EN: DEE-uh-kon | PT: di-Á-kon
The Diakon Canon — our normative baseline — carries this principle: serve governance, not impose bureaucracy.
Explore the Diakon Engine