Just do it

Freshness Warning
This article is over 10 years old. It's possible that the information you read below isn't current.

Linux World points out how Google tests new ideas (via 37signals)...

Google is one of the few large companies that gets one fundamental rule of the Internet: Trying stuff is cheaper than deciding whether to try it. (Compare the cost of paying and feeding someone to do a few weeks of P* hacking to the full cost of the meetings that went into a big company decision.)

Don’t overplan something. Just do it half-assed to start with, then throw more people at it to fix it if it works. Worked for every successful Google project from AdWords to Google Maps.

Years ago I was consulting for a large technology company. They had an intranet measuring in the billions of pages and were looking to rein it in. One part of the effort was to create and maintain a global taxonomy to make things easier to find, but to do this, they needed a tool to manage that taxonomy. I was on a team of 8 people who were tasked with picking a product that would meet the client’s needs. These were all mid to senior level people, and I’d imagine the annual salary averaged over $100k each. In addition to this full time attention, we had the part time attention of dozens of others. Two project managers were assigned to keep the project on the rails. It wasn’t uncommon to have a meeting where 15 people attended. We also had two outside consultants who were experts in taxonomy management.

To choose the product, the eight of us worked full time for a year, analyzing requirements, interviewing stakeholders in various groups, documenting all the different pieces of software the taxonomy would be used in, and generally trying to figure out which software package best met the needs of the client.

Two weeks into the process we determined that there were four software packages that had any chance of being useful. Three of these packages cost around $20k and the other cost around $70k. Early on in the project planning process, a software engineer was tasked with eventually implementing a pilot project of whatever software we picked. His estimate of the task was that it would take 4 weeks to do.

We spent well over one million dollars to decide which $20k software package to buy so one person could spend a month creating a pilot project.

Jemaleddin
December 21, 2007 1:31 PM

Sounds like a great idea to me - if the 8 of you worked for an outside contractor that was billing the time you worked on this effort to the big tech company. Otherwise... not so much.

Your comments:

Text only, no HTML. URLs will automatically be converted to links. Your email address is required, but it will not be displayed on the site.

Name:

Not your company or your SEO link. Comments without a real name will be deleted as spam.

Email: (not displayed)

If you don't feel comfortable giving me your real email address, don't expect me to feel comfortable publishing your comment.

Website (optional):

Follow me on Twitter

Best Of

  • The best of 2006 I wrote a lot of drivel in 2006. Here's the things that are less crappy than the rest.
  • Let it go Netscape 4 is six years old.
  • Writing Realistic Job Descriptions Publish a job listing like this one and you are virtually guaranteeing that you won't get qualified applicants for the position.
  • Movie marketing on a budget Mark Cuban's looking for more cost effective ways to market movies.
  • Newly Digital Newly Digital is an experimental writing project. I've asked 11 people to write about their early experiences with computing technology and post their essays on their weblogs. So go read, enjoy, and then contribute. This collection is open to you. Write up your own story, and then let the world know about it.
  • More of the best »

Recently Read

Get More

Subscribe | Archives

10

Recently

Physical camera shutter for Cisco Spark Board (Jul 6)
A 3d printable design for a camera shutter for a Cisco Spark Board
My Travel Coffee Setup (Jan 20)
What my travel coffee brewing setup looks like, and how you can build your own for under $100.
Turkey Legs (May 30)
Product naming gone awry.
Speaking for Geeks: Your Slides (Dec 17)
Tips and tricks for creating great slides.
Speaking for Geeks: Writing Your Talk (Dec 14)
Don’t wait until the night before the talk to write it. Crazy, I know.
Speaking for Geeks: Tell a Story (Dec 13)
Telling a story keeps your presentation focused, keeps your audience interested, and makes it easier for you to remember your talk.
Speaking for Geeks: Where to speak (Dec 11)
You've got a great idea for a talk. How do you find conferences to submit it to?
Speaking for Geeks: Getting your session accepted (Dec 10)
Your conference speaking submissions are not getting accepted because they're bad. Here's how to make them better.

Subscribe to this site's feed.

Elsewhere

Tropo
Voice and communications platforms, including Tropo and Phono. Work.
SacStarts
The Sacramento technology startup community.
Pinewood Freak
Pinewood Derby tips and tricks

Contact

Adam Kalsey

Mobile: 916.600.2497

Email: adam AT kalsey.com

AIM or Skype: akalsey

Resume

PGP Key

©1999-2018 Adam Kalsey.
Content management by Movable Type.