Tuesday, August 25, 2009
Co-Blog
Sunday, January 25, 2009
Alan Watts was a hard act to follow, but I did alright.
Each year I’m invited to lecture to our Organizational Psychology students on material from The Conscious Manager: Zen for Decision Makers. The lectures are well-received and I have fun with them.
Psychology has always big at our university; Carl Rogers, Victor Frankl, and Abraham Maslow have been faculty members here.
After my last lecture, a faculty old-timer remarked to me, “You know, long ago Alan Watts argued pretty much the same point you just did, and in this very room.”
Wow. What a rush to be a part of that tradition.
Just wanted to share the feeling with you.
Sunday, July 27, 2008
Cross-referencing my blogs
- The Conscious Manager. International perspectives on management, technology, media, and personal growth.
- Technopolis Times. Resources for technology-based regional economic development. Technopolis Times encourages networking and alliances that help grow new and established technopoleis. This blog is the new home of the Review of Technology and Economic Development newsletter.
- MsM Partners' Conference Blog. Annual research and business forum for Maastricht School of Management's outreach partners, representing more than 30 countries.
Wednesday, July 16, 2008
The Future of Management
In my classes, I (Fred) have been teaching that the most successful companies have made innovation systematic. Hamel goes further; he says innovation must be systemic, permeating the daily activities and attitudes of every employee – and not just in R&D or product development departments. Fear of change has been banished, the potential of every employee to contribute ideas and energy has been nurtured and realized, and organizational charts and structures change at the drop of a hat.
In this regard, Hamel likes Whirlpool, Toyota, Google, and a few others. Here are key passages from his book:
(p.31) While Whirlpool's innovation efforts have been widely reported, a competitor would find it hard to duplicate what is now a deeply engrained innovation system – for the same reasons it would be difficult to pick apart Toyota's multifaceted management advantage.
(p.34) Management innovation follows a power law: for every truly radical idea that forever changes the practice of management there are dozens of others that are less valuable and less influential. But that's no excuse not to innovate. Innovation is always a numbers game: the more of it you do, the better your chances of reaping a fat payoff.
(p.36) Many executives doubt that bold management innovation is actually possible. Strangely, managers are unsurprised when science advances by leaps and bounds, yet seem unperturbed when the practice of management fails to do the same.
(p.38) If management innovation has been mostly incremental in recent years, it may be due to a lack of daring in the choice of problems to tackle. Ask yourself, has your company ever taken on a management challenge that was truly unprecedented, where you couldn't rely on another company's experience as a guide? General Electric has. In 2006, chairman Jeff Immelt set his colleagues the goal of growing GE's top line at twice the rate of global GDP growth, net of acquisitions. No company of GE's size has ever managed this sort of growth, yet that didn't deter Immelt from taking on the challenge. If the problem is big enough, progress of any sort will be valuable, even if you never find a "solution." I once heard former U.S. Secretary of State George Shultz draw a distinction between "probems you can solve" and "problems you can only work at." As a seasoned diplomat, Shultz knows that some problems, like ethnic strife, global poverty, and terrorism, defy once-and-for-all solutions. Yet he also understands that when you're up against problems of this scale and significance, even modest advances can yield big dividends.
(p.102) What makes Google unique, though, is less its Web-centric business model than its brink-of-chaos management model. Key components include a wafer-thin hierarchy, a dense network of lateral communication, a policy of giving outsized rewards to people who come up with outsized ideas, a team-focused approach to product development, and a corporate credo that challenges every employee to put the user first.
(p.103) [Google top execs] Brin and Page understand that in a discontinuous world, what matters most is not a company's competitive advantage at a single point in time, but its evolutionary advantage over time. Hence their desire to build a company that is capable of evolving as fast as the Web itself.
Hamel’s oft-quoted aphorism: Organisations used to require intelligence, obedience and diligence from an employee – but they could get that from a cocker spaniel. Today’s organizations need employees to display passion, creativity and initiative.
I liked Hamel’s book, despite some bloopers:
- Hamel appeals to Francis Fukuyama’s largely discredited “end of history” notion.
- His reference to the “college student who spends less on an airline ticket to Fort Lauderdale than he'll spend on booze over spring break” is sadly out of date…
- His statement that “the law of diminishing returns kicks in and at some point the ratio of progress to effort starts to sag” doesn’t accord with learning theory as I understand it – and as Hamel notes, organizational learning is what it’s all about.
The main take-away for management educators is that we should be teaching how to create corporate culture. A good idea, but most new MBA grads are in no position to create culture. On the contrary, they tend to be overwhelmed by the prevailing corporate culture two weeks after starting their new jobs, or the second time their passionate, creative initiative is punished, whichever comes first. In this regard, Hamel’s advice is reminiscent of the Microsoft helicopter joke. (If you haven’t heard it, ask me.)
Still, it’s food for thought. And at least, business schools might seek out companies that are sympathetic to this new view, and point our grads in their directions. Or, we might emphasize Hamel’s ideas in executive ed courses. I look forward to discussing these ideas with you; enter your comments on this page.
Monday, December 31, 2007
Down with Lean, Flat Organizations
Compare, for example, Dell Corporation and Southwest Airlines. Dell deserves great credit for its successes, but basically the company has had one good idea: custom-assembled (but otherwise commodity) PCs coming out of a lean supply chain, made efficient by the World Wide Web. This idea and its offshoots are at the end of their life cycle. Dell has discovered it doesn’t want individuals to order computers from its web site after all, because customers are not as susceptible to up-sells when they are not speaking with a live salesperson. Dell has similarly discovered unexpected competition from Apple, which has churned out product innovations at a steady clip and has moved customers beyond the desktop and laptop.
In the process, Dell has become known as a pressure-cooker workplace. Smart, amiable young people go to work at Dell and emerge as nervous wrecks. Their sacrifices have not kept Dell’s stock price anywhere near its historic peak. This is not exclusively a Dell problem. Lean organizations, by virtue of eliminating layers of management and work-in-progress inventories, are more communications-intensive than any historic enterprises. Emails arrive at a pace that forces managers to be modern equivalents of Lucy and Ethel in the chocolate factory.
Southwest Airlines is only somewhat lean (it never embraced the efficient hub-and-spoke route system), but its employees are empowered. Any employee at any level may have an idea and run with it, even spend money on it. Was the employee’s idea a good idea? The company worries about that later, after the customer’s problem has been solved. Almost uniquely in the industry, Southwest is solvent, it attracts creative employees whose ideas ultimately save the company money, and its fares have remained reasonable. It is among the few airlines that customers actually enjoy flying.
Most companies, of course, debate ideas before they are implemented. Here’s a research project that would advance organizational science: One employee has an out-of-the-box idea. How many people should s/he “run it past” before the idea is spiked, or massaged into bland uselessness? What is the magical length of a communication chain, below which an idea can turn into a useful experiment, and above which initiative is (inadvertently or not) punished?
Many companies use the "skunkworks" strategy, but no one has investigated when, why, and at what scale skunkworks work. Management grad students, take this one up.