The Fallacy of Equivocation at the Economist

In a remarkably shoddy example of anti-market propaganda emanating from the Nottingham Business School, the Economist runs a screed that starts out with the debatable but reasonable premise that business leaders exaggerate their omniscience. It somehow ends up with the unsupported conclusion that business schools should abandon economics, finance, and the pursuit of profit for the cant trio of “sustainability,” “social responsibility,” and “leadership for all not for the few.”

The crude equivocating shifts from intellectual humility to moral humility to altruism would qualify for an F in any class on composition, much less philosophy. The vague assertions about “business excess” (entirely unsupported or even defined), the implicit attribution of these excesses to the teachings of business schools (ditto), and the wild leap at the end (replacing business school education with an agora-like setting in which sophists mingle with scientists and philosophers with philistines to figure out what are “social needs”), all conduce to a massive loss of reader brain cells per sentence. This article might be useful as a sort of mine detector–anyone who finds it congenial is best separated from responsibility for educating or commenting on business or economic issues.

 

Advertisements

David Stern and the Aging Emperor-CEO Syndrome

NBA Commissioner David Stern recently fined the San Antonio Spurs $250,000 and severely chastised them for the decision by Gregg Popovich, their near-legendary coach, to rest his aging stars at home rather than fly them to Miami for a meaningless (but nationally televised) tilt with the defending-champion Miami Heat. Is Stern losing his grip? Does he need an intervention and/or a forced retirement as he reaches his managerial dotage? While I haven’t heard of Commissioner Queeg–whoops, Stern–clicking steel balls in his hand or searching for the keys to the strawberries, a Caine Mutiny scenario may be approaching if he continues to deteriorate. Other firms with long-term, successful “emperor” CEOs have found their later years to be problematic. See Eisner, Michael (Disney) or Olson, Kenneth (Digital Equipment Corporation) or maybe Cizik, Robert (Cooper Industries).

Read the rest of this entry »


Geeenius!

How to Write a Malcolm Gladwell Book. Would most recently graduated MBAs get the joke?


Dark Knight strategy

(Note 1: Anyone who will be offended by light-hearted discussions of the Dark Knight Rises in light of the shootings at the Aurora premier should skip to another part of the Internet. I have no intention of giving murderous attention-seekers the power to hijack all media, but I am aware that not all will agree.)

(Note 2: MINOR SPOILER ALERT)

I’ve just seen the Dark Knight Rises, which was a pretty good movie–not as good as the previous film in the trilogy, unsurprisingly, but exciting and even moving at times, with lots of little moments for each minor character to reveal his true nature and seem like a unique individual.

One minor problem: Batman is supposed to be a master strategist and tactician. He’s chosen to go underground to pursue and confront his enemy, Bane, about whom he has considerable intelligence, including Bane’s background, training, experience, and physical prowess (including his main point of weakness–a mask over his mouth that keeps Bane from suffering intense pain). He can see Bane standing in front of him, a very large individual of obvious strength and questionable agility. Batman is wearing a utility belt filled with grenades, throwing blades, sleep darts, cable launchers, and bolas. He is standing in a large cavern and is capable of operating vertically by shooting lines up to the ceiling and using built-in powered winches. In short, he is in a perfect position to remain outside Bane’s striking distance while hitting him with a variety of entangling, injuring, and even killing weapons.

Out of this cornucopia of options, what does Batman choose? Of course, a head-on bull rush, followed by a slugfest and wrestling contest. That’s the combat equivalent of Neiman-Marcus starting a price war with Wal-Mart. Macho is one thing, unbelievably stupid is another. (It’s true that in the real world, people make stupid mistakes, but in fiction we want Aristotelian probability, not literalness. And if someone does go the literal route, the character’s stupidity should at least be noted by others in the story.)

The fundamental writing problem here was actually reflected way back in the Knightfall comic book series that introduced Bane–his supposed awesomeness as a combatant simply doesn’t match his capabilities. (At least in the comic book, they gave him a device that injected a super-steroid called Venom straight into his head when he needed to pump himself up for extra fighting fury. It still wasn’t enough to make him seem that tough for any foe with speed, agility, and distance weapons, but it made for a striking visual when his veins would bulge out in expansion mode.) So the Nolans gave themselves a tough writing challenge the moment they decided to use the Bane character–another example of a particular strategy causing tough execution problems.


Excessive government paperwork–meta edition

An earlier post described the sclerotic impact of excessive regulatory documentation requirements on real-estate development projects. it turns out that the private sector isn’t the only victim of this tendency:

I think we all know what the logical response to the GAO meta-meta-study is…

H/t Instapundit.


The History Tax

Try to guess the context for this piece of writing. Is it part of a scholarly study on the history of convention centers? A tourist guidebook? Is it the catalogue to a museum display on convention-center architecture?

In order to attract growing numbers of conventions in the
second half of the twentieth century, cities incorporated
convention center construction within urban renewal and
redevelopment schemes, usually at the edge of core urban
areas where space would be available for construction of
large buildings with contiguous, flat-floor space.

Read the rest of this entry »


How do you grow a capability?

The “dynamic capabilities” literature, I think, is a bit of a mess: lots of jargon, conflicting arguments (and levels of analysis) and little agreement even on a basic definition.  I don’t really like to get involved in definitional debates, though I think the idea of a capability, the ability to do/accomplish something (whether individual or collective), is fundamental for strategy scholars.

Last weekend I was involved in a “microfoundations of strategy” panel (with Jay Barney and Kathy Eisenhardt).  One of the questions that I raised, and find quite intriguing, is the question of how we might “grow” a capability.  The intuition for “growing” something, as a form of explanation, comes from simulation and agent-based modeling.   For example, Epstein has argued, “if you didn’t grow it, you didn’t explain it” (here’s the reference).   I like that intuition.  As I work with colleagues in engineering and computer science, this “growth” mentality seems to implicitly be there.  Things are not taken for granted, but explained by “growing” them.  Capabilities aren’t just the result of “history” or “experience” (a common explanation in strategy), but rather that history and experience needs to be unpacked and understood more specifically.  What were the choices that led to this history?  Who are the central actors?  What are the incentives and forms of governance?  Etc.

So, if we were to “grow” a capability, I think there are some very basic ingredients.  First, I think understanding the nature, capability and choices of the individuals involved is important.  Second, the nature of the interactions and aggregation matters.  The interaction of  individuals and actors can lead to emergent, non-linear and collective outcomes.  Third, I think the structural and design-related choices (e.g., markets versus hierarchy) and factors are important in the emergence (or not) of capabilities. Those are a few of the “ingredients.”

I’m not sure that the “how do you grow a capability”-intuition is helpful in all situations.  However, I do find that there is a tendency to use short-hand code words (routines, history, experience), and the growth notion requires us to open up these black boxes and to more carefully investigate the constituent parts, mechanisms and interactions that lead to the development or “growth” of capability.