Data Governance Matters

I’m having a pint right now at the Prince of Wales pub in London, halfway between Victoria Station and my hotel. And right now I’m thinking of my dad, Melville Thomas, who was born in Wales and came to the U.S. when he was five.

Dad was a good father and a good psychologist, who eschewed lucrative careers in Industrial Psychology and private practice to help thousands who came through the Florida Alcoholism Treatment Center in Florida, where we moved from Indiana when I was a kid. Dad was also an extraordinary teacher.

As anyone who knew him would attest, he was always ready to pull out a scrap of paper and pen, then diagram out the essence of a tricky problem, a  complicated concept, or an intricate idea. Dad told me on many occasions that “if you can’t describe something on the  back of a used envelope, you’re not ready to talk to others about it.”

If I’ve ever explained anything succinctly that has helped you or your program, you can thank my father and his back-of-the-envelope training. Here’s to you, Dad.

* * * * *

A postscript.

I wrote the above in a notebook, to transcribe into the blog software when I got back to my room. When I was done, I got involved in a discussion with a group gathered around the bar at the pub. One topic of conversation was what I’d been writing about, and of course someone wanted to know whether I’d written a book.

So wouldn’t you know it - we had a “small world”  moment. One man in the group runs very large SAP projects that rely on strong data governance. And, it turns out, he had a bone to pick with me about my book, Alpha Males and Data Disasters: the Case for Data Governance.  I was prepared to concede a few points right off the bat - yes, the book only addresses a few drivers for data governance. Yes, its provocative title was chosen to make a point. No, there’s no male bashing in it - it is simply using a recognizable term to talk about data-related risk and how to manage it. And yes, I do have newer thoughts than those from when it was first written, over three years ago.

But that wasn’t his point. And no, he didn’t take umbrage at the concept of Alphas. His point was that I hadn’t taken it far enough!

In his experience, there was a higher category - Uber Alphas - who were the key to successful data projects. An Uber Alpha, my new friend said, has the drive, focus, and skills of an Alpha. But the Uber Alpha has adopted Beta characteristics: the Uber Alpha is a system thinker, doesn’t let ego get in the way of reaching goals, is very willing to solicit advice from many sources, and values the support and contributions of less-aggressive Betas.

In our interconnected world, and with interconnected systems, this man said, a pure Alpha will self-destruct. But an Uber Alpha will come out on top.

It makes sense to me.