How a Six-Month-Old Startup Got Bought by Google

Yes, this piece gives advice (based on an actual startup experience) about how to get bought by Google, but it's really just sound advice for any business:

Don't focus on getting acquired.
Instead, focus on the user.
Ignoring limitations lets you tackle problems from a different angle.
Don't be afraid to tackle the giants.
Pay attention to the details.
Have a really understanding spouse.

See the piece for details.

Comments

Brian Lawley said…

I think the main thing is to be incredibly passionate about building an INSANELY great product. Any startup can do that much faster and better than the bigger companies, and if you are lucky with timing and market conditions then you'll get snapped up. I've seen this happen time and again here in the valley.

Of course, the other part is that when Google or any other company makes you an offer don't get too greedy (easier said than done). :-)

Brian Lawley
www.280group.com

Fri Aug 03, 12:42:00 PM 2007

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Citizendium

You're probably familiar with Wikipedia , but have you checked out Citizendium ?

Cauvin

Search This Blog