Thinksum

Just sum thoughts on software and other stuff.

Bill Walsh's Legacy

Bill Walsh passed away today.  Many years ago I read his book on building the 49ers.  But to understand the quality of a man who became famous in a boys game played by men, you could refer to the answer he gave in an interview filmed by NFL Network last year.  When asked what he thought his legacy would be, Walsh didn't hesitate and didn't refer to any of his innovations or big games.  Instead, he said he though his legacy would be that he helped minorities advance as coaches.  Walsh hired Dennis Green and Ray Rhodes, and also had connections to Tony Dungy, Lovie Smith and Herm Edwards, all of whom became minority head coaches in the NFL.  Dungy and Smith became the first black coaches in the Super Bowl last year.

Congratulations Bill Walsh on a life well done.

July 30, 2007 in Leadership and Management | Permalink | Comments (0) | TrackBack (0)

Profit

A number of years ago I saw one episode (turned out to be the pilot) of an over-the-top TV show called Profit on Fox.  I couldn't tell if it was a mini-series or what, and I never heard anything about it again other than I read a quote from Rupert Murdoch saying that he loved it (not sure if that's a good thing or a bad thing).

Over the years I've sometimes looked for more info on the show without much luck, but lo-and-behold a few weeks ago in a Barnes and Noble I stumbled on the DVD of the complete series.  Turns out there were 7 episodes in addition to the 2-hour pilot, and only 4 episodes aired before public reaction caused the show to be pulled.

The story is about a sociopathic corporate climber, Jim Profit (played by Adrian Pasdar), and his attempts to gain power large multi-national corporation, taking out whoever he has to on the way.  With a nearly conscience-less anti-hero as the lead, and storylines filled with sex, greed and murder it's hard to see what caused the strong public reaction (hee hee) -- the DVD liner notes mention that Fox received an outcry of protest from stations in the South.  It's tame compared to HBO's Sopranos which launched three years later, but HBO is allowed to do that stuff.  Anyway, I watched all the episodes and totally enjoyed it, notwithstanding the hokey virtual reality computer program that Jim Profit uses every night to snoop for information while sitting naked in his penthouse apartment.  Of course, you might not want to take my recommendation because I sort of liked Melrose Place too.

It's interesting how some great (or potentially great) series miss their audiences.  Sportsnight is another favorite of mine that only lasted one season, written by Aaron Sorkin who then went on to create West Wing (so in a way I'm thankful that Sportsnight didn't live on).  Maybe they're just before their time, or maybe the network executives just didn't have the vision or commitment to see them through to success.

Some of the best software I've worked on missed its audience too, either because word never got out or because management gave up on it (the software guy will never admit it was the software's fault ... it wasn't, really).  It's interesting to think about all the elements that are necessary to make a software product successful, but over the years I've come to be a big believer in a great marketing team and passionate executives.  Put those together with good software, and you won't get axed after the first season (or halfway into the season as in Profit's case).

February 27, 2006 in Leadership and Management | Permalink | Comments (1) | TrackBack (0)

Hiring Outside Managers in a Startup

TNT is experiencing some growth, and in engineering this is creating the need for more management.  In any company, when you need more management, you either shift some folks from individual tasks to partial or full management, or you bring in someone new from the outside.  In a startup like TNT, this decision is particularly crucial.

In a startup, where in most cases you are strapped for people, every individual has crucial responsibilities.  If you shift someone to management, then you are reducing the time and energy they have for individual tasks.  While team members may want to gain management experience, the trade-off may not be acceptable for the overall product and company (unlike a bigger company where the results of individual changes can more easily be absorbed).  Also, appointing someone a manager over someone else who was previously a peer is always a bit risky, but can be really prickly in a small team in a small company (it usually means a raise, for instance, and in a startup the salaries and raises are necessarily limited).

But if you bring in someone from the outside, then you risk upsetting team chemistry and frustrating key team members who wanted to manage themselves.  Again, in a startup, team chemistry is particularly crucial.

When natural leaders have emerged within an existing team, they may be able to assume part of the management responsibilities without upsetting team chemistry or productivity.  We've done this successfully at TNT and I've seen this done quite successfully elsewhere in the past.  The natural leaders are not necessarily the most experienced people on the staff, but they're the ones with the best combination of experience and drive, and who in various situations have demonstrated leadership skills and who have come to be seen by the team itself as leaders.

But when no natural leaders emerge in areas that need more management, my experience is that it's better to look outside than to try to groom someone inside into the manager role (I'm saying this specifically for startups -- in a more mature company I would offer different advice).

Needless to say, this is a crucial hire and must be made extremely carefully.  The key, I believe, is that the team respect the individual.  In an engineering team, this means that the manager must be at least as intelligent as the team members, and must clearly have more experience in the specific area that would qualify them as a manager.  During interviews, if this is not clearly the case, and if questions remain about the candidate, then it's better to keep looking.  With individual contributors even in a startup you can take some risk, but with a manager (even the manager of a small team) you need to be sure.

January 08, 2006 in Leadership and Management, Software Companies, Software Start-Ups | Permalink | Comments (0) | TrackBack (0)

Labor vs. Creator

About a week ago on NPR I heard a report on overtime pay for software company employees, spurred by the class action lawsuit a group of employees brought against Electronic Arts.  This detailed report from one employee's significant other describes the policies and practices that led to the lawsuit (mandatory 12 hour days, mandatory six and then seven day weeks, no overtime pay).

Under legal pressure, EA has agreed to institute some overtime pay.  But on the NPR report, an unrepentant company spokesperson Jeff Brown indicated that the company does not take a positive view of complaining employees and the expectation of overtime pay, saying that EA is surprised they want to be treated as labor, instead of creators.

Overlooking the silliness of this statement -- since the employees are both labor and creators, and if anyone is treating them as labor it's EA management -- it also raises another interesting question.  What is the best way to get maximum productivity from a team over an extended period of time?

Here are the simple keys to productivity I've found over the years:

  • Hire good people who enjoy the job
  • Give them all the tools they need
  • Don't make anything mandatory
  • Provide individual financial rewards for exceeding expectations (in productivity, quality, creativity or teamwork)
  • Let the team share in the results (bonuses tied to product revenues, stock options and the like)

My theory is that motivated, happy teams will decide when it's appropriate to have extended hours and will work them accordingly, with much more allowance and tolerance for individual's personal schedules and family lives.

The most mystifying thing to me about the EA situation is that management would have ever thought the best way to get a new product out the door sooner would be to micro-manage people's work schedules (and thereby their lives) and to devise schedules that required extended overtime.  I wish we had a lab where we could run two identical projects in parallel:  one managed the EA way, and one with no mandatory work schedule but with the same deadline.  My guess is that the second team would deliver a much better product, probably sooner too, and definitely the team would be much happier at the end.

June 20, 2005 in Leadership and Management, Software Companies, Software Development | Permalink

A Leader Who Gets It

Apropos my previous entry, while many tech mogules understand vision and leadership, with Pixar and Apple's rejuvenation Steve Jobs has clearly separated himself from the pack.   I think he gets the fact that publicly stating bold goals can help you achieve them.  But his huge announcement this week was greeted with as much concern as confidence, with some folks questioning whether this flies in the face of the Apple "counterculture" or whether this might have some sort of Osborne effect that would cannibalize Apple's sales.

My belief, previously discussed here, is that coevolution is a powerful force in computing, and that Intel 64-bit chips represent the largest coming wave (and noted that current generation chips with 64-bit extensions may be a huge part of that).   By joining with Intel, Apple puts itself in position to capitalize, and I admire Jobs for big bets like this that could shake up the industry and deliver big results.

June 11, 2005 in Leadership and Management | Permalink

My Photo

About

Recent Posts

  • News Flash! Microsoft Invents Vacations
  • How Many Fronts?
  • Cultural Update
  • How do people answer questions like this?
  • New company blog
  • Better Than a Taco and Enchilada Combo
  • Introducing vmSight
  • What's the Deal with Oprah's Magazine?
  • The Sweet Morning After
  • Just Noticed that William Gibson is Blogging Again

Categories

  • Blogs
  • Enterprise Applications
  • Entertainment
  • Groupware
  • Hiring
  • Leadership and Management
  • Open Source
  • Predictions
  • Security
  • Semantic Web
  • Software Companies
  • Software Design
  • Software Development
  • Software Evolution
  • Software Quality
  • Software Start-Ups
  • Start-Ups
  • Usability

Archives

  • July 2008
  • February 2008
  • January 2008
  • December 2007
  • November 2007
  • October 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
Subscribe to this blog's feed
Blog powered by TypePad
View Jonathan Alexander's profile on LinkedIn
See how we're connected

Bloglines Blogroll