Skip to main content

Layoffs, Banks and the Blond: A radical approach to reacting to bad results

The scene: A college bar. A group of young men are sitting around a table when a group of young women, led by an especially attractive (blond) young lady enters the room. The men, all budding economists, start planning their strategies to win the attention of the blond - 'remember Adam Smith! Every man for himself and every actor acting in his own best interests (and the losers drink with their friends)!'

One of the young men, John Forbes Nash, realized that every-man-for-himself is suboptimal. The best strategy, the strategy in which each of the young men has the best outcome, is achieved when the group members work both in their own and in their collective best interests. His strategy: "Ignore the Blond!"

Governing Dynamics - "Ignore the Blonde"

Long bicycle races, like the Tour de France, may look like an individual sport, but actually cycling is a team sport. Even though there is a single winner, an individual without a team has no chance. A corporate career is treated like a individual sport, but actually it's a team sport as well.

Last month, both UBS (NYSE: UBS) and Credit Suisse (NYSE: CS) announced layoffs. Together, they only made 1.6 Billion CHF last quarter, so they need to lay off up to 7'000 employees -- between 4 and 7% of the total staff worldwide.

What's happening now as a result of the layoffs?

Everybody is scrambling to maintain their position. People are worried about their own careers, not about the issues of the bank, are certainly not the wishes of the customers. Some people will get laid off, taking their know-how with them. Management is moving people around, teams are getting split up, and Know-how is getting lost.

Even those who stay are afraid of making mistakes, so raising issues is dangerous, decisions get postponed, and innovation has no chance. (Bonus question: How is this different from the situation before the latest round of layoffs?) Result: stagnation at best.

What does stagnation mean? You can see it in the stock price. Except for the bad profits generated by investment banking leading up to the financial meltdown and which were destroyed in 2008-2009 meltdown, these stocks have gone nowhere for the last 10 years (even ignoring the tremors of the last few days).

UBS and CS New York relative Share Prices, 2001-2010

This latest move is nothing they haven't already done before. It will provide short term benefit (maybe), but does not really solve their problems.

What should UBS and CS be doing? Radically managed companies have an open flow of information with quick feedback loops. They have a climate of trust, not fear, so that problems can be identified and rapidly addressed. And mostly, they are focused on the their customers, not on themselves. (People experienced with Agile, Scrum or genuine Lean will recognize these characteristics!)

What do UBS and CS need to do to get back on track? A partial answer is people in these banks need to think like a team, not just a collection of individuals. They need to transform their organization into a team sport so people can work to a common goal with pleasure,  enthusiasm and confidence in the future. They need to eliminate the climate of fear.

How can they do this? Here are a couple of places to start:
  1. Commit to keeping their staff on board and create an atmosphere of confidence.
  2. Change their bonus to systems to reward not personal success (and infighting) but rather team success (and customer delight), especially at the top. More than anyone else, top management needs to work as a team.
  3. Update their concept of management by the numbers to focus not on financial success but rather on customer delight.

P.S. Does this situation resemble your company? What to make it better?  Join us for the Zurich Gathering For C-Suite Leaders with Steve Denning and myself: Zurich, Sep 12, 2011


Paulo said…
Sweet! The best systemic analysis I read in a long time. Congrats!!!

Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…