SQLServerCentral Editorial

Separation of Duty

,

In the Vietnam war we found people gathering data that had to support the analysis or decisions of the leaders. That's a fundamental problem. Arguably this led to the extension of the war, and more lives lost, without more decisive actions being taken. 

We should not have the people or systems designed to collect data that supports a particular position. We want data that is accurate and complete, which can then be used for analysis. We ought to have people gathering data separate, both in terms of hierarchy and process, from the people that analyze and make decisions. We know that keeping them in the same area leads to data that supports what the boss wants, or what the bonus warrants, rather than what the data can show.

Have you heard of the Franklin Gambit? I was reminded of that recently while reading Obliquity, a book that examines how we pursue goals and achieve success. Franklin's Gambit says that we often use data and explanations to justify a decision we've already reached, rather than actually prove that some choice is the best one. I'm sure most of you feel you don't live your live this way, but as I've thought about some of my decisions, I think this isn't necessarily true.

It's a natural tendency of humans to do justify their actions, regardless of the data, and I suspect many of us suffer from it. I think it also can extend to the data analysis and interpretation that many of us perform at work. We'd like to think that our reports and even data gathering are objective ways to examine a problem, but it can be easy to influence the data, especially in the way that data is gathered if we are not careful.

We want to separate the data gathering from the analysis. It might not ensure that the data analyzed is as complete and accurate as possible, but it helps prevent one side from influencing the other.

Rate

You rated this post out of 5. Change rating

Share

Share

Rate

You rated this post out of 5. Change rating