We have an interesting video of Professor Andrew McAfee talking about technologies under the label of Enterprise 2.0. This will be the fourth time that I have highlighted
McAfee's work and the sixty third
McKinsey article. All I can say is I'm glad this body of work is behind me. I still have many McKinsey articles that I want to write about, just not enough time in the day.
Professor Andrew McAfee coined the phrase and defined what "Enterprise 2.0" is and means. Particularly from the point of view of how organizations will be affected by these technologies. Like the recent discussion of Google CEO Eric Schmidt, McAfee is not talking about the technologies for the sake of the technologies but the massive impact that the Information Technology revolution is having on business.
Last time I highlighted the work of Professor McAfee and his Enterprise 2.0 concepts he was at Harvard. He seems to have escaped and moved closer to the river by joining MIT and is now the principal research scientist at the "Center for Digital Business" at the MIT Sloan School of Management. He also has a book coming out called "
Enterprise 2.0: New Collaborative Tools for your Organization’s Toughest Challenges". Lastly the McKinsey article has this video presentation of this paper. (Video is available
here.)
McKinsey ask a number of pertinent questions. McAfee's answers provide real value for this community in terms of what and how "Enterprise 2.0" and People, Ideas & Objects application modules will affect today's work place. The following is how I see it for oil and gas.
McKinsey: How is Enterprise 2.0 changing the way we work?
McAfee's answer to this question is in line with the collaborative developments of WikiPedia. How the initial start attempted to control the contributions of people, and only after scrapping the process and leaving it to self organized teams did the value, quality and quantity increase.
I see a much larger change. The 7 / 24 clock will be the time people are available to work. Asynchronous Process Management, a cornerstone of the People, Ideas & Objects
Technical Vision will permit people to work when and where they want. The office will not be used even half as much as they are today, and the quality of life will be substantially higher. When the computer screen looks the same at home or in the coffee shop as it does at the office, an office will become a place to go to concentrate. The rest of the day will be interspersed with personal and work related activities completed as required.
McKinsey: How do you get this started in an organization?
McAfee comments;
There’s a lot of debate about that question right now. And the debate is typically between people who advocate [a top-down approach and those who advocate] almost a purely bottom-up approach—in other words, deploy the tools, stop worrying about what’s going to happen, and get out of the way as the management of the company and let it percolate up from down below. Or, if you hear about a grassroots effort, encourage it, support it financially, but, again, get out of the way, let the bottom-up energy happen.
People, Ideas & Objects has chosen the bottom-up grassroots method of solving these problems and building the software based on the
Draft Specification. I like McAfee's comment that if you hear of a grassroots effort, encourage it, support it financially. Music to my ears so start spreading the news.
This software development can not be a sustained and quality effort unless the users are compensated financially for their time. This is a big part of our budget and defines why our approach is different from the rest of the marketplace. As McAfee states in this document, developing the community takes time and effort.
McKinsey: What else can undermine adoption?
McAfee notes the unreasonable time frames put on by management. People, Ideas & Object software developments, or any collaborative project, will not be zipping along before the end of the quarter. Such expectations are how the hierarchy greases the wheels with the consumption of human energy and spirit.
Another failure mode is to be too concerned about the possible risks and the downsides. If we get wrapped up in those, we’re not going to take the plunge and actually deploy any of these new tools and turn them on and encourage people to go ahead.
I don't see the downside here. Collaboration brings many risks to the bureaucracy. However their risks are the result of the collaboration out performing the bureaucracy. I can live with those risks, and I think that McAfeee's audience is different to those of this blog. He is preaching to the unconverted and as such has to hedge his comments while he moves the Trojan horse into place.
McKinsey: What is the CIO’s role in encouraging Enterprise 2.0 and managing the risk?
McAfee notes;
A lot of them see their roles as essentially conservative, though. In other words, “My job is to not increase the risk profile of this organization before everything else.” That’s a legitimate concern, it’s a legitimate job for the CIO, but all my experience so far tells me that Enterprise 2.0 doesn’t increase the risk profile of an organization.
This is probably why I get in so much difficulty with companies. I ask sarcastically what's a CIO? I don't see them surviving in the long run. Much like secretaries and draftsmen these positions may disappear rather quickly. These types of comments should be directed to the CEO or the CFO as they have the proper authority and responsibility to make the decision.
In my presentations to the industry I noticed something that I had never learned or considered before. When I talk to CEO's or CFO's I feel there desire to pick up People, Ideas & Objects software developments. Why they haven't is that they would do serious damage to their firms by changing direction to quickly, without the urgent need and support for the change. They therefore pass on the opportunity until such time as we proceed to a point where they can make the change.
McKinsey: What does this mean for middle managers?
McAfee notes;
If you’re a middle manager who essentially views your job as one of gate keeping or refereeing information flows, you should be pretty frightened by these technologies, because they’re going to greatly reduce your ability to do that. They’re going to reduce your ability to filter what goes up in the organization and what comes down in the organization. And they’re going to greatly reduce your ability to curtail who your people can interact with, talk with, and receive information from. So if you’re inherently a gatekeeper, this is a real problem for you.
In my presentations to the industry it is this group of people that feel challenged by these technologies and the People, Ideas & Objects application. The class of workers known as middle managers career and position are toast. I don't foresee many of these people continuing to be effective in the very near future. If this is news to anyone in middle management, good morning.
McKinsey: How should companies measure the success of Enterprise 2.0?
McAfee notes;
Again, you see a lot of energy, you see a lot of people very willing to take a few seconds to answer a colleague’s question—even if it’s a colleague they don’t know. So when I see successful companies tackling this tool kit, I see them doing a little bit of thinking upfront about what problem or opportunity they’re trying to address, then deploying an appropriate technology in response to that. They then measure progress: How much uptake are we getting? What’s the traffic look like on this? Which is very different than measuring ROI, I think.
In the
Preliminary Research Report I suggested that companies use the revenue per employee as a measure of an oil and gas firms performance. Revenue per employee can vary significantly from company to company based on the unique attributes of its asset base. It has direct application between producers and is an accurate measure of the firms current and future capabilities. This is particularly the case as those producers with low revenue per employee will have difficulty increasing the revenue factor without having to address a possible over staffing issue.
The purpose, or competitive advantage, for the
Community of Independent Service Providers and People, Ideas & Objects software applications. Is to provide the innovative producer with the most effective and profitable means of oil and gas operations. Revenue per employee will be a critical method of how the community advances the science of management and business for the oil and gas clients using this software and community. Please join us
here.
Technorati Tags:
People's McKinsey McAfee Video Technology