Archive for October, 2007

Does Google 2008 = Microsoft 1998?

MSFT vs. GOOGThis is a question I’ve thought about often (See Google’s ten rules compared to Microsoft). Before I give my answer, if you’re in Seattle you should go listen to Lawrence Lessig give his talk on the subject Friday Nov 2nd at Kane Hall, at the University of Washington.

The short answer is No. In 1998 Microsoft was suffering from the shaky Windows 98 release, was facing a new DOJ lawsuit, and will still engaged in the browser-war with Netscape. I was in my 4th year at MSFT in ‘98, and it was the roughest year for the company I’d seen. The browser war was emotionally brutal, and on the Internet Explorer team we were trying to recover from IE4 (a release few of us were proud of). To outsiders, 1998 was a year of comeuppance for Microsoft.

Looking to next year I don’t see Google headed for seas quite so rocky. Yes, there are threats of major lawsuits with YouTube and search privacy, but those threaten future revenue sources more than current ones. However, like Microsoft in the 90s, the competitive landscape isn’t impressive. Yahoo and Microsoft have are still trailing players in tech-sector mind share.

Most important comparison: By 1998 Microsoft, the 23 year old company, had managed to piss off just about everyone at least once: at least it felt that way when I spoke at conferences. Google, only 8 years old, has a much higher standing in the industry, among competitors and partners, than Microsoft did. But then again, it’s 15 years younger :)

On culture and attitude: Life inside Google feels much like at Microsoft in the mid 1990s. I’ve been to Google several times (Chapter 1 of the Myths of Innovation recounts one visit) and know folks working there. The vibe feels incredibly familiar to my mid-90s MSFT memories: happy, smart, independent people who feel they are empowered to change the world, and who work in a special place, with special rules. And as best I can tell, it’s true. They deserve to feel that way. So in that respect, rock-on Googlers.

But the rub is that in the mid-1990s Microsofties felt the same way about their place in the industry, and their ability to change the world, as the folks at Google seem to today: We have the ball and we are running away with it. I suspect the folks at Atari in 1977 (year of the 2600), Apple in 1985 (and perhaps again now), Netscape in 1994 (year of Mosaic) and dozens of other companies that were once at the top of the world. And they were all prone to the same kinds of self-destructive hubris.

Common mistakes employees of dominant companies make:

  1. Believing no one has been at the center of the tech-universe before.
  2. Inability to take a non self-centric view of the world.
  3. Depending on power and intimidation, more than intelligence and wisdom.
  4. Failing to find ways to stay humble & hungry while being dominant.
  5. Focusing more on beating rivals than satisfying customers.
  6. Underestimating how decisions will be received by the rest of the world.

When I was at Microsoft (‘94-’03), I always felt the company made things so much harder for itself in how employees, executives included, presented themselves to the world. I can’t tell you how many times I saw Microsoft employees embarrassing themselves at conferences, e-mail lists or on newsgroups. And it wasn’t entirely their fault: they were expressing the internal culture to the outside world and the result was predictably disastrous.

The perception of Google today, and in 2008, is at a tipping point. They are quickly rounding out their positions of dominance and the Microsoft comparisons will only get sharper. If they can learn the best lessons from Microsoft’s 1998, it’s about handling pressure with grace, and the wisdom to pay more than token attention to the mistakes above.

World usability day: Free usability review

Next thursday Nov 8th is World usability day, and there are events all over the world.

For you folks online, just like year’s past I’m offering the first 10 people who leave a comment a free expert usability review of the website they post (it doesn’t have to be their own website).

How to get a free expert usability review:

  1. Leave a comment, include your e-mail address and a URL.
  2. If you’ve got a specific problem or user scenario you’re worried about, mention it.
  3. If you’re in the top 10, I’ll post your review online.
  4. If you’re after #10, be creative. If you make me laugh you might get yours too.

Bonus: If you work on stuff for cell phones or mobile devices, Sender11, a mobile design expert, is offering free usability reviews for you.

  • By Scott Berkun on October 30th, 2007
  • 4 Comments »
  • art of project management

Do you use / teach with the artofpm book?

Work is underway for the revision of the art of project management. One goal is to make the book more useful for teachers, professors, or even team leads who work through the book with their team.

If this is you, I want to chat and get your input – Either leave a comment, or contact me. Thanks.

Are you a leader or a tracker?

We have truly messed up our job titles.

Somehow, somewhere, the job title project manager became lame. I don’t know if it was born this way, or if it happened over time, but it’s a shame. Here’s what I think happened – we’ve confused project tracking with project leading.

If you take any interesting work in architecture, film, software, or any pursuit that involves millions of dollars or dozens of people, there is someone playing an executive role, overseeing decisions, budgets and schedules. They are a leadership force for the project, and are, in essence, a project leader. They might call themselves director, producer, architect, or VP of whatever, but if their authority is tied to a project, they are a Project Leader.

But somehow that job title never caught on. Not in software, not anywhere. Instead, the title project manager is used everywhere with all sorts of meanings. At NASA, the director of the entire space shuttle program is called a project manager. But more often the project manager is the guy with an ambiguous role and even less clear authority.

Many of these people are really Project Trackers. They write reports, make spreadsheets, and report back to people on what just happened. They aren’t expected to lead the entire project, as engineers or business analysts take most of the fun parts of the leadership role anyway. But no one ever gets that job title – it’d be too easy to figure things out.

Microsoft dodged this whole problem, and created new ones, by creating the role of Program Manager. This was a project manager who isn’t granted much leadership authority, but who is allowed to earn it and grow into a true project leader. But soon there were program managers whose sole job was to manage a single dialog box, and the power of the role was gone.

Worse, many places have Product managers, program managers, and project managers all on the same teams, further confusing who does what and why.

The solution: whenever I meet people with a P or an M in the title, I ask the following questions.

  • Does your team report to you?
  • Do you or your reports create / contribute to / follow requirements?
  • Do you or your reports create / contribute to / follow specifications?
  • Do you or your reports create / contribute to / follow schedules?
  • Is design a major / minor / negligible part of your role?
  • How much of your time is spent tracking the project vs. leading it?
  • Does your level of involvement, from project inception to completion, change?
  • Are you completely / partially / indirectly accountable for the project outcome?

Only then do I understand which dimensions of leadership/management the person is responsible for. I wish it was easier, but I find I’m always asking these questions every time I teach or consult in a different place, no matter what their job title says.

Anyone else have ideas for how to identify which kind of PM you’re dealing with?

It’s Novel writing month: join NaNoWriMo!

Novel writing month participant

This Thursday marks the beginning of national novel writing month – That’s right. A bunch of crazy people write an entire novel in 30 days (~1500 words per day, for 50,000 total). It’s a fun crazy thing, a chance to be bad, and I’m doing it this year.

You can sign up at their website, get moral support, tons of advice, a word count tracking tool, a FAQ, and other bits that help you start and keep going (Here’s my advice on the subject: Writing hacks part 1).

If you do join up, make me a buddy: my username is berkun.

Lessons from amazing projects: Russian Ark

We’ve all had tough projects, but this one might just top them all, and it hits on three of my favorite topics: design, management, and film making. Here’s the rundown:

  • It’s a feature length film shot on an independent film budget.
  • It’s one continuous 90 minute shot.
  • The film spans 33 rooms of the famed Hermitage museum in St. Petersburg.
  • It has over 800 actors and performers.
  • It has various plays, dances and orchestral performances, all performed live and in a scripted sequence.
  • It took years to plan, write and develop the custom steady-cam technology.
  • They only had budget/time for 4 tries, and got it on the 4th.

Russian arkI’ve both seen the film, and have visited the Hermitage (prompting a 2nd viewing of the film). Understanding Russian history helps make the film more than a stunt, as the story can be hard to follow (It’s an abstract and art-y film, both figuratively and literally as it’s shot in an art museum). But even without it, the film is a visual delight and a project management wonder. If you’re a designer or a manager you’ll be in awe even if you only make it through half the film. Moreso, the DVD includes a making-of featurette that entirely blew my mind: it will put whatever is stressing you out right now into deep relief.

Trailer, netflix listing, and reviews.

Scott's Bestselling Books
  • Confessions of a
    Public Speaker
  • Provocative and funny secrets from a veteran speaker, you'll laugh as you learn.
  • Buy now at Amazon Book Details
  • The Myths of Innovation
  • The classic bestseller on how amazing lessons from the past can help you innovate today.
  • Buy now at Amazon Book Details
  • Making Things Happen
  • The classic and bestselling handbook for any project leader, packed with tactics and stories.
  • Buy now at Amazon Book Details
Photos from Recent Events (view flickr stream)

You're reading Scott Berkun, All rights reserved unless noted. You can subscribe here Blog RSS Comments (RSS)