« A Leap of Faith in Data-Driven Analytics | Main | Five Stages of Digital Transformation in the Oil and Gas Industry »

It's More Like a Diamond

For the past thirty or so years, we've heard time and again about every project having three components: people, process, and technology. And further, this trio is represented as an equilateral triangle. I would like to put forward that not only is this concept incomplete, its representation is just not right. First of all, all three of these pieces are not equal. People are the most challenging part of any project and the most likely reason for a project's failure. The "not invented here" syndrome, or the "I'll keep my head down for a couple of months and this change will blow over" thought is pervasive in every organization. Process is critical, and it is now getting the attention it deserves. We can't improve the way we work if we don't analyze our current processes and look for opportunities to improve. And finally, technology. With all due respect to hardware and software developers everywhere, of the three parts of the triangle, the technology component is the least challenging. That's not to say the developing technology is not a lot of work and not difficult, but compared to the people and process components, unless a poor solution is selected, the technology part of the trio is least likely to be the reason for a project's failure, but on its own, also the least likely to be the reason for success.

But what about the incomplete aspect I mentioned earlier. This triangle is really a diamond (I could go with a square, but a diamond looks cooler). In addition to people, process, and technology, there's data (or information). This is always overlooked, but I think mainly because most I.T. people focus on the "T" and not the "I" (I have other conspiracy theories, but I won't go into them here).

Now, my reason for bringing this up is not because as a Data Management professional I'm feeling left out. It's really because of numerous conversations I've been involved with where companies are looking for that silver bullet... that software solution that will solve their problems... when in reality, the answer lies in their business processes and the data and information that flows within and between those processes (many of the failures in processes occur at the hand-off points between processes).

Diamond-Kunzinger-Blog.jpg


I would like to put forward two premises on which I'm basing my thoughts:
First, "Every decision the business makes is based on the data and information at its disposal". In the Production/Operations world of E&P, there is a business process where wells are monitored to ensure that the wells are operating safely and productively. If something is wrong, an alert is issued. But what is an alert. Simply put, an alert is a piece of data or information that falls outside an acceptable range of values, thereby causing an action on the part of an engineer or technician. In this case, let's break it down into our diamond:

People: Engineer or Technician

Process:  Monitor the well to ensure normal activity and take steps to correct when that activity falls outside of the norm

Technology: Could be anything from manually reading meters at a well head to sensors feeding information back to a real-time data center and control room

Data: The value being read, analyzed or interpreted that causes the actions to take place and the agreed upon range of acceptable values

The second premise, "My job is to help find, produce and sell oil and gas". If I were a Data Manager in Aerospace, my job would be to help design, produce and maintain aircraft. As a Data Manager in the energy sector, what I do day-to-day is support the first premise by ensuring that those people making the business decisions have all of the data and information necessary to do their jobs: how they need it, when they need it and where they need it. In order to do this, I need to understand the business processes, what data and information is needed at each decision point, what tools they're using to make their decisions, and what next process is triggered by that decision. And this goes on throughout the E&P value chain. One process leads to another. Each process needs data as an input; each process creates a piece of data or information (that piece of information may be simply a yes/no decision, but it still needs to be captured); each process triggers another process that goes through the same cycle.

In every process, there is a parallel yet often overlooked data flow upon which the process is totally dependent. So, the next time somebody brings up the people/process/technology concept, remind them that they're missing something and that something that they're missing will make or break their ultimate success.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.