Rants
Questions
Soapbox
Best Practices
Apply today for a FREE subscription to CIO Magazine!
Wed, Jan 14, 2009 0:51 EST

|
Posted by: Michael Hugos in Best Practices Topic: Enterprise ManagementBlog: Doing Business in Real Time
Current Rating: |
Agility is no longer just an interesting idea to chat about while continuing to do business as usual. The days of the traditional pyramid shaped corporate hierarchy as a viable business model are coming to an end. The last twenty years have produced some winners and some losers and some of the biggest losers are companies that built themselves into huge conglomerates that were supposed to be too big to fail. Instead they are proving the truth of the saying, “The bigger they are the harder they fall.”
It’s not that companies can’t be big and grow revenue to many billions of dollars, it’s just that they have to swear off that fatal tendency to organize themselves as hierarchical pyramids where most people are powerless drones who just follow orders while the important decisions are made by a small group of powerful executives at the top of the pyramid. Given the pace of change, no small group of executives regardless of their smarts, hard work or fancy computer systems can make all those decisions in a timely or competent manner.
People at the top of corporate hierarchies are overwhelmed by the shear volume of decisions they have to make; they are too far away from the scene of the action to really understand what's happening; and by the time decisions are made they are usually too little and too late. Companies suffer the consequences of this performance by staggering from one bad decision to another like punch-drunk boxers who can't understand what's happening and can't understand why they keep getting hit.
Cisco got hit hard in the collapse of the last bubble - the dot com bubble - when their stock went from around $77 a share to around $11. But they took that opportunity to learn some lessons that lots of other companies are only now starting to consider. Because human nature is what it is, it often takes a smack-up-side-of-the-head event to send a wake up call and get us to consider new ideas and try out new ways of doing things.
Yet the good news is we really can learn from mistakes when we decide to do so. The cover story in the current issue of business magazine Fast Company chronicles what Cisco has learned, it’s titled “How Cisco’s CEO John Chambers is Turning the Tech Giant Socialist”. It’s not that they are really turning socialist. It’s that they are trying something new and before their smack-up-side-of-the-head wake up call, they would have dismissed it as unworkable and labeled it with an unkind word like socialist in order to justify not considering it.
Cisco used to be a traditional pyramid shaped corporate hierarchy where all the important decisions were made by 10 executives at the top of the organization chart. Then they fell on hard times. What has emerged in the last several years is an agile enterprise with a network organization structure (not a heirarchy) where decision making is decentralized out to some 500 managers and the whole operation is powered by Web 2.0 collaborative technology like blogs and wikis and social networking tools, some of which they’ve built themselves and are more powerful than the commercially available tools.
Now instead of a small group of executives telling everybody else what to do, people have authority to figure out for themselves what to do (hmmm... maybe Chambers read one of my posts from 2007 "Leadership for the Agile Organization"). People are motivated to coordinate and cooperate with each other by a financial incentive system that rewards
Good article, thanks.
Your question, "What kind of systems architecture would best support this type of business model?" - what level are you talking about; Network, OS, tool set, in-house, out-house, etc?
How about governance best practices or experiences: is anyone using anonymous participation, is there the need for a moderator, are there multiple social nets? Are contractors and business partners included?
What other organizations are facing these issues? I'm sure there's a blog around somewhere for this subject. If not, should I start one?
Jim
Agile software development practices recommend breaking up software development teams into "Scrums" (small teams of 5-7 people) who self-manage to deliver working software in rapid increments. The exact same thing can be done at the organizational level to break up massive efforts/companies into small, nimble groups who can react faster to customers and to the market than the big organization could ever do. This will absolutely be the way large companies organize themselves in the future. Ryan Martens, founder and CTO, Rally Software, www.rallydev.com
Ryan,
You are right that agile software development practices can be applied to the way businesses operate. This is something we practitioners of IT agility can teach to business people.
Regards,
Michael
Hi Jim,
The systems architecture I'm thinking of is the combination of Network, OS, tool set, in-house, out-house, etc. All these components combine to create a systems architecture that delivers the performance an agile business needs.
Systems architecture that made sense for supporting operations in traditional corporate hierarchies is not the architecture needed by a company employing an agile network organization structure like what is evolving at Cisco. Governance best practices, anonymous participation, the need for moderators, multiple social nets, and including contractors and business partners are all aspects of what this new systems architecture would encompass.
I like to think this blog covers some of those aspects but I don't cover them all and I believe there is definitely room for another blog on this topic. I think you should start one; you can do some posts right here at CIO.com. I'll be a reader.
Best regards,
Michael