“I’m Spartacus!”

Who thinks they own the data?

In my last blog, I aimed to clarify the roles of “data owners” and “data stewards”. And on the face of it, establishing more explicit accountability for data seems like a good idea! What could possibly go wrong?

The reality may be somewhat different.

I was re-watching the classic Kirk Douglas film “Spartacus” the other week, and it put me in mind of the type of scenario that can occur in the Data Governance space. (If you’re not familiar with the story - which has also been the subject of a recent TV series - it tells of an ultimately unsuccessful slave uprising led by the Thracian gladiator Spartacus, which took place during the Roman Republic in the time of Crassus, Pompey and Julius Caesar.)

In the 1960 film version, at the end of a bloody pitched battle between the slaves and the Roman guard, the Romans are searching amongst the remaining survivors for our eponymous hero. All members of the revolt are offered clemency from crucifixion (the normal penalty for a rebellious slave), if only they give up their leader.

Roman Centurion: “…Identify the body or the living person of the slave called Spartacus.”

The first question in relation to data is “is there anyone who might claim to own the data?” Can someone be identified who is fits the mould of a “data owner”?

Slave #1: “I’m Spartacus!”

Slave #2: “I’m Spartacus!”

Slave #3: “I’m Spartacus!” etc.

Before the real Spartacus can make himself known, one by one each of the slaves stands and puts himself forward as being the leader of the uprising in show of defiance, and of solidarity with their leader (and effectively volunteering to be crucified). Brave? Courageous? Noble? Certainly. Effective? Clearly not.

In a Data Governance context, are there multiple owners of the data, or several candidates who would lay claim to being accountable? Which of these is most suitable, both in terms of organisational position and in terms of their ability to engage? Can you find ways of getting all of the protagonists to work together and operate in a collaborative manner, acting for the overall good of the organisation? Too many cooks spoil the broth, so the proverb goes. So too with too many Spartacuses (Spartaci?).

But what if the opposite were true? What if there’s no-one coming forward to take responsibility? Well, the Romans already had a robust plan in place to cater for such a scenario and an agonising death on the cross for all and sundry was the answer if Spartacus was not identified. But I’m not sure such drastic an approach would go down to well in these more liberal times (though you’d certainly get some attention!).

Clearly then, the “no Spartacus” solution isn’t workable.

Could we have a situation with a “conscripted Spartacus”? Someone who is pushed forward to make their sacrifice for the greater good of the group as a whole? Everyone else is saved in this scenario (at least in the short term), but I’m not sure that a co-opted approach where someone is unwillingly nominated can work very well either. The conscripted “volunteer” Spartacus gets crucified by the Romans, and the slaves are left with no leader, the rebellion I crushed, and everything goes back to the original status quo without any improvement in anyone’s lot. In our Data Governance context, a press-ganged Data Owner will usually mean no contribution, no commitment, and no success.

So, we’re left with trying to find the real Spartacus. Someone who will volunteer for the role of Data Owner, someone who is a willing and able leader who understands their responsibilities, someone who can execute against them, and someone who will be held to account for meeting their commitments. Even if we need to bide our time, we’ll have more success in the long run if that type of individual can eventually be found.

“Spartacus sum!”