Commentary

How The Enterprise 2.0 Managerial Model Was Born

Venkatesh Rao

In this first of a three-part series, we explore the evolution of Management For Opportunity. How did "manager" become a dirty word?

New technological eras invariably create new managerial eras. Enterprise 2.0 is no different. In this three-part series, I will argue that E 2.0 organizational technology leads to a management model I will call "Management For Opportunity," a model that exposes managers to market risks in unprecedented ways. This model is contrary to the popular emerging idea that managers (especially the much hated middle managers) will become entirely obsolete.

But to get to this vision, we need to situate E 2.0 management and technology ideas within the evolutionary history of corporations.


More Social Business Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

I'll start the story around 1954 rather than go all the way back to 1600. If you're interested in earlier eras of management, check out my posts "A Brief History of the Corporation: 1600-2100" and "Hall's Law: The Nineteenth Century Prequel to Moore's Law".

Let's start by trying to characterize the job of the manager in the E 2.0 world. I assert that this job is to manage for opportunity (MFO), which is fundamentally a risk management role that requires E 2.0 tools to fulfill. It's the newest layer of the functional organization of the evolving managerial mind, which I visualize like so:

Evolution of the managerial mind

I've tried to capture higher- and lower-level functions in a dependency stack. You need the lower layers before you can install the higher layers. There's a chronological anomaly in that the second layer developed after the third one, but that was due to some historical peculiarities.

Let's start by tracing the evolution of the managerial mind.

The Evolution Of The Manager

Skipping lightly over a couple of centuries of early evolution, the story gets interesting with Peter Drucker, at a time when the default management culture was a layer of owner-executives on top of what you could call glorified shop-floor supervisors, whose job was to steward well-defined processes to meet objectives set by owner-managers. Call this Management By Process, or MBP.

In 1954, in a world where people management was still synonymous with MBP but operations were growing more complex, large-scale, and specialized by the year, Drucker offered an abstract principle for managing the emerging breed of information workers differently: Management By Objectives (MBO).

It was a revolutionary idea: Employees should participate in setting and monitoring their own performance goals. It was a natural consequence of selling complex products and services in a growing global market. In a way, it was a return to the high autonomy enjoyed by managers in the sprawling, flat-hierarchy railroad empires but had been slowly eroded in newer vertically integrated industries such as oil and steel.

Page 2:  Negotiated Goals
 1 | 2  | Next Page » 

Related Reading


Informationweek Discussions

Start the Discussion


InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS

Resource Links