Users, the focus and the key
The visions that are part and parcel of People, Ideas & Objects Draft Specification provide the "User" with an interesting "mainstream" business opportunity. User based development is the critical link in making this or any software development successful. I may now start stating this project is "mainstream" based on the ideas of Professor Oliver Williamson and his winning the Nobel in economics.
We have seen in the past few weeks the discussion turn to the hundreds of thousands of jobs that make up Exxon, and by assumption there are hundreds of thousands of different jobs in the industry. This knowledge is held tacitly in the minds of those that work in the industry. To hold the understanding of a handful of the roles is available to many who have an abundance of experience in the business. But that's about it. The collective knowledge of how this industry operates and runs on is unknowable, and that's the point. The only way we are going to be able to understand this tacit knowledge is by having the community of Users detail what it is they know.
Ask SAP how it processes the delivery of propane to a new customer and they will provide you with their understanding of how to bill for a product. What the User knows is how to use the SAP module to achieve the results that are desired. The User has the tacit knowledge of how the industry works and retrofits that understanding into SAP's version of best practice. What is the best or optimal way of doing the job is never asked, until now.
Users have to be the individuals that work with the developers to build the applications that they know can be better. Until such time as the User is the focus of the development, we will not see the optimal or most effective solution. We will continue to be presented with applications that the developer or a single producer needed. Not what is known to be possible. People, Ideas & Objects is the Users opportunity to have the applications they need, built.
It's also an area where the User can build a business. By bringing their ideas of how best to do a job in the industry, they are paid by People, Ideas & Object's. This is not just a one time event, or something they can be involved in for a few years. I see the applications changing constantly as the underlying industry and business changes. These Users will be involved with the developers on a somewhat permanent part time basis. But that's not all. The User has to have hands on understanding of what is happening at the producer firms.
As members of the Community of Independent Service Providers they also have free use of the People, Ideas & Objects applications at their producer clients. Ensuring that the needs of the producer are met by the applications they have had a significant hand in defining and developing. Being intimately involved in bringing the applications to their producer clients. Where their role with the producer being the defining part of their work with People, Ideas & Objects.
This is not a small undertaking and the amount of work being done by the Users is a large multiple of the volume of time that the developers spend in writing the code. To expect that these people would not be compensated for doing this work doesn't pass the laugh test. They need to be compensated for the advanced skills they bring to this project.
User driven developments are proven to be the only successful method of building quality software. With this project we are taking on the entire scope of the administration and management of the Joint Operating Committee and producer operations. Including compliance and governance. This is not a small task, and although the costs have not been tallied, our focus on the User communities development is the only means of software development that is considered. Please join me here.
Technorati Tags: People's User Development Community Change