Tag: management

Org Structures

People seem to be happier with a little bit of middle management. Not middle management that’s going to overrule the decisions they make on their own. Not symbolic middle management that only makes people feel important. But middle management that creates useful channels of communication. If my job is getting obstacles out of the way so my employees can get their work done, these managers exist so that, when an employee has a local problem, there’s someone there, in the office next door, whom they can talk to.

As a design firm Pentagram’s structure is unique; it is essentially a group of small businesses linked together financially through necessary services and through mutual interests. Each partner maintains a design team, usually consisting of a senior designer, a couple of junior designers, and a project coordinator. The partners share accounting services, secretarial and reception services, and maintain a shared archive. Pentagram partners are responsible for attracting and developing their own business, but they pool their billings, draw the same salary, and share profit in the form of an annual bonus. It’s a cooperative.

From a historic perspective, I like to think that it’s one of the few truly bohemian places left in New York City, just based on the way we run it, like a commune. The management system here is that everybody manages. In order to work here you have 2 tries to show you can manage the place and if you can’t, you’re fired. Everybody manages about one shift a week and everybody’s equal. People work hard for each other. I don’t want to let you down because tomorrow it will be me. And I think they enjoy the responsibility of running a New York City restaurant. They get to pick the music, set the vibe, the lighting, everything. And they’re all pretty laid back, so it’s got a bohemian nature.

various schemes to avoid typical middle management problems

Jeff Bezos vs Bill Gates

I’ve given presentations on “creating passionate users” at both Amazon and Microsoft. 2 big companies, 2 CEOs. Guess which CEO has been to the talk? And he didn’t just sit there, he participated. His hand shot up when I asked a question. He quit fondling his Blackberry. But far more importantly–he asked an amazing question. then he asked, “How can I do more for our reviewers? These people do so much, and work so hard–especially the ones who do a lot of reviews — and the ‘Top Reviewer’ badges are not enough.” I was speechless. Not because I couldn’t think of an answer, but because I couldn’t believe someone this far up the food chain would even think–let alone care about this.

Wikipedia HBS Case

Andrew McAfee and Karim Lakhani created the first Harvard Business School case on Wikipedia which is available for free online and published under the GFDL. The case explains Wikipedia mechanics and the story of the Enterprise 2.0 article for deletion debate. I guess we now have peer reviewed evidence that not only does Enterprise 2.0 exist, but Wikipedia exists.

oy. the “wiki consultants” can’t be far now.

151% productivity

Big Consulting Company calls up Big Oil Company. “Hey, do you guys need help being more productive developing software?”

Big Oil Company says, “Yeah, sure, whatever, we’ll buy anything,” and they buy a $1M software productivity consulting deal.

The consulting company comes on site, measures a bunch of bogus things like Lines of Code Per Developer, or, if they’re really fancy shmancy, Number of Function Points Per Programmer Per Day. Then they tell the oil company, “Gosh, you’re only getting 73.844% productivity. Pay us another $2M and we’ll double your productivity.”

Oil company pays the $2m.

Consulting company comes in, gets all the programmers in a room, tells them all about Function Points and stuff, and how productivity is REALLY IMPORTANT.

Programmers remember that scene from Office Space where Bob and Bob, the consultants, recommended all the people to get fired.

Programmers start writing a heck of a lot more function points. For example you can triple the number of function points in your code simply by round tripping everything through an XML file. Big waste of time, prone to bugs, does nothing, but each file you touch adds a function point. W00t!

Consulting company comes back, measures again, and lo and behold, with all the round trips through XML the function point count is up drastically. Consultant announces that Oil Company is now at 151.29% productivity. MISSION ACCOMPLISHED.

Google growing pains

As the size grows, I see colleagues, particularly those who join Google from other companies, tempted to carve out fiefdoms and mandate SWOT analyses and extensive Excel spreadsheets littered with 3 letter acronyms. I have seen a few mid-level bosses evoke the traditions of Japanese management and schedule “pre-meetings” to plan, discuss, and approve what will be planned, discussed and approved at the actual meeting itself. MBA-speak creeps into the parlance and these new managers require the filing of more and more TPS reports.

google in need of a reeducation of middle management?