Conflict and Contradiction
The past number of months I have on occasion mentioned that conflict and contradiction were analytical tools that were added to our user communities list of competitive advantages. To some these may seem counterintuitive to a team environment focused on productivity, profitability and prosperity in the greater oil and gas economy. I am not of the opinion that they’re that new to our primary target audience, those that we consider our customers, they being our user community members, not the oil and gas producers. People, Ideas & Objects exist to provide our user community with the software development capabilities they’ll need to satisfy the software needs of their customers, the oil and gas producers, in combination with the services they’ll provide through their service provider organizations.
Conflict and contradiction are most certainly unwanted attributes that people do not want in their lives. They’re avoided and ignored in order to make their lives easier. “Don’t rock the boat,” “he’s (insert your ad-hominem attack here).” If there is nothing to be argued from the other side then ad-hominem attacks, attacking the character of the one generating the conflict, is the method used to gain support. Very effective, i.e. “Trump is an ‘ad hominem attack’.” We need to look at those who are attacking others with comments about others personalities and character to understand that this shows they have no counter argument, policy or solution to provide and they’re only concerned with maintaining their self interest in the status quo. Bureaucrats use these tactics prolifically as we’ve seen in their excuses, blaming, lying and viable scapegoats as to why they’re such failures. What they should be doing is standing up and stating unequivocally the benefits they provide under their current business model. Benefits such as how they’ve kept the pulp and paper industry prosperous and profitable. My ad-hominem attacks of the bureaucrats are somewhat due to the fact that they are as bad as I state, and indeed are the issue of oil and gas’ destruction. Other than these facts, what would I write about?
Hugging things out in the Boardroom during the Directors meeting and C Suite has to be what’s been going on. Professor Jordan Peterson, of 12 Rules fame, states that “conflict delayed is conflict multiplied.” It’s clear that throughout the bureaucracy, but most importantly in the C Suite and Boards nothing but coffee, donuts and hugs have been taking place for a long time. The volume of producer issues reflects not so much a multiplication but an exponential extension of the original problem that could have been solved. If someone would have raised their hand and asked the pertinent questions at the right time, however unpopular it would have made them, everyone could have subsequently avoided so much destruction in the greater oil and gas economy.
Conflict is not a reflection of the individual that no one seems to be able to get along with. It is the one that has to ask the difficult questions at the right time before the issue manifests itself into the greater problems that can eventually take down an industry. It demands an understanding of the situation and a deeper knowledge of the issue than one would normally have acquired. It could and should come with a proposed solution or the consideration that it should be studied to determine what solution could be provided. Conflict is not a tool to disrupt the personal interactions of the team, only a means in which to disrupt the flow of another key human attribute and competitive advantage, that being our unique ability to make errors and mistakes. Something we’re quite good at and most familiar with. With the scope, scale and volume of work that each of us are managing within our domain. In an exponentially more complex environment that we’re building in the Preliminary Specification and we described in our previous blog post. Where people are using their thinking attributes more than their doing activities in the very near future. The implications and interactions of the work that will be done by an individual will be more involved and hence more important and impactful.
So where is the issue that needs to be addressed? How can these issues be identified and pointed out in a timely manner? Students of philosophy would know the answer comes about by identifying the contradiction of whatever it was they were looking at. That will be the source of the issue and the point that needs to be resolved, in most cases. The issue may go deeper than what it appears to be. The method necessary to analyze the contradiction is nothing more than the Socratic method that is the basis of all artistic and scientific progress since around 400 B.C. The Platonic Aristotelian philosophies are derivative of the Socratic method which means that you ask a lot of questions. The questions are pointed and have an agenda behind them in which those being questioned are informed and advised with an understanding of the issue, the perspective the questioner has and a probable solution that is consistent with the questioner's understanding. And in turn the questioner's understanding is broadened by the answers they recieve. Where contradictions and false assumptions are rooted out.
This is how People, Ideas & Objects, our user community and their service provider organizations will be able to seek and find the truth regarding the most efficient and effective method of proceeding with the development of the Preliminary Specification. “How, What and Why” it is that needs to be done and by whom at what point in time and where. Will need to be asked repeatedly by those in our user community in order to formulate solutions based on that understanding and knowledge. This, in a nutshell will be the method of how the Preliminary Specification is taken from its current form and prepare the details needed for our developers to develop the software in order that the user community is able to meet the producers needs.
Due to the fact that People, Ideas & Objects have been organizing our user community since the first quarter of 2014 we have been able to achieve something significant that I’m not aware that any other ERP software initiative has been able to do. Our user community will be able to do this work in the current configuration that we’ve determined. This consists of approximately 3,000 user community members. One for approximately each process in the application. To organize a community of this size isn’t the difficulty per se. It’s a challenge but certainly not the difficult challenge in putting together a user community. With eight years and the Internet it can be done. The difficulty is in expressing a usable vision, a viable business model that expresses a solution to those issues that are present in the marketplace. One that solves today's problems and sets the foundation for the future. A future where the means to make the necessary changes on an incremental and individual basis are available as needed on a timely basis where they are needed. Everyone in oil and gas has been able to view People, Ideas & Objects vision as spelt out in the Preliminary Specification since December 2013. These people have also been able to see how our user community vision has the ability and capability to provide them with the means to build the appropriate applications and services. Where by joining our user community they can affect change in the industry as change is required. Bring about the permanent, prosperous and profitable oil and gas producer and industry everywhere and always. And in turn, for each and every user community member.
None of this information regarding conflict and contradiction is new to the majority of the people we are attracting. I learned an important lesson that I don’t think many people know. When I published our first document in 1996, we then followed up with sales calls to discuss the work that we were doing. In almost all the meetings I was shocked at what I saw. The “white paper” I published was quite literally trashed. They were annotated, highlighted, dog eared, bent, rolled, used and abused to the point where they were almost unrecognizable. When people who were in the lower levels of the organization were in attendance they were cherishing the document. Looking at me as if to say we want this. This taught me something very important about my target audience. They were a) hungry, but that wasn’t the most important thing. Instead of consuming the bite sized marketing quotations, slogans and “nutshell it for me” type of summaries. They consumed the critical conflict and contradictions pointed out in the paper. They wanted analysis, they wanted to be challenged and they wanted to see the solutions that were being presented. I have used this understanding and the comprehensive response that people have to my writing on this topic as my personal competitive advantage throughout this adventure. To summarize this, I would say that people read voraciously. I am only willing to express this now as it would be too late for any of my competitors to learn from it and be competitive today. And I don’t think it is just my words but the words of anyone who conducts this type of analysis and determines this type of solution to real life problems. This is why I am listing conflict and contradiction in our user communities analytical tool kit for them to build out the Preliminary Specification at this critical time. This is how they’ll be making the product and their service provider organizations services polished and precise. By understanding that people read and they appreciate the hard work of others.
I’m not just identifying a competitive advantage of mine. This blog is not about me, never has and never will be about me. I only raise these points to make the following argument. I see the same competitive advantage in our user community today. It is inherent and present in their culture and reflective of the quality, highly educated and vastly experienced group of people they are. The bureaucrats ignore these cultural attributes and have their own means and methods of taking the organization in the direction that they’ve taken these firms. They perceive that their people have been along for the ride. And these people are as a result frustrated and disappointed as what has generally been expressed here on this blog. They also know they’re powerless to do anything about it. If they do say anything it will accomplish nothing. If they point out People, Ideas & Objects Preliminary Specification they’ll be dealt with negatively. If they’re found to be members of our user community, that would be the end of their careers. That is why we keep their information confidential. Only I know who they are. Only I know the full scope of the despicable tactics of these bureaucrats and how they will seek to destroy them. I wouldn't be surprised if there were a few who are only there to try to find the names of others to make examples of. Such are the ways of our good friends, the oil and gas bureaucrats.
The only solution as it stands today, from a creative destruction point of view, is People, Ideas & Objects, our user community and their service provider organizations implementation of the Preliminary Specification. The natural forces of disintermediation and creative destruction are being obstructed through the diversion of industries revenues away from the development of these initiatives. And therefore are unnecessarily directly supporting the status quo behaviors that have been proven to be disastrous. If the producers will not invest in their organizations profitability by implementing the Preliminary Specification, our user community and their service provider operation, why would anyone invest in them?
The Preliminary Specification, our user community and service providers provide for a dynamic, innovative, accountable and profitable oil and gas industry with the most profitable means of oil and gas operations, everywhere and always. Setting the foundation for profitable North American energy independence. People, Ideas & Objects have published a white paper “Profitable, North American Energy Independence -- Through the Commercialization of Shale.” that captures the vision of the Preliminary Specification and our actions. Users are welcome to join me here. Together we can begin to meet the future demands for energy. Anyone can contact me at 713-965-6720 in Houston or 587-735-2302 in Calgary, or email me here.