4 ms·

I agree mostly with the article, but early stage employees are also investing in themselves. Young product managers at Google or Microsoft don't get the opport

by ykumar6 12y ago

I agree mostly with the article, but early stage employees are also investing in themselves. Young product managers at Google or Microsoft don't get the opportunity to work on big problems. The few young people I've met tend to lack the macro thinking on what makes a product successful. Why talking to users is so important. Why defining a problem is so important. Why retention is more important than growth. Why cohorts are so important and why analytics can be misleading. With young engineers, they tend to lack the understanding on why striving for simplicity is important. Why thinking in iterations is important. Why writing tests are important. Why the best engineering in the world can't save a product that doesn't solve real problems. Big companies do teach you these things, but not at the pace of a real startup.

nostrademons 12y ago
My experience - having worked at both Google and in the startup scene - is that young PMs at Google/Microsoft actually get to work on much bigger problems and have a much better understanding of the macro scene than startup founders. At Google, it's not uncommon to hear "Can't we just buy [famous startup X]?" or "Figure out the benefit for users, and if it turns out to be useful for a large number of people, we'll see if the lawyers and lobbyists can get the law changed" or "We'll just throw 65,000 machines at the problem." As a result, there's a presumption that problems are solvable if we just think really hard and identify the incentives of everybody in the system. Few startups have this privilege. Where Google really falls down compared to a startup is in micro-level thinking. A PM at Google may understand how a hundred million users behave in the aggregate, but fail to understand how to change one user's behavior. When your sole work experience is at a powerful corporation, you start assuming that people will take your phone calls, and you don't develop the skills of how to cold-call an ambivalent prospect, or how to empathize with a minority user who is really frustrated, or how to focus and prioritize on only the tasks that you can make a real impact on. For engineers, I'd say Google (and presumably Microsoft) engineers understand far better than a startup why simplicity is important. The codebase, after all, is orders of magnitude bigger and harder to understand. And iterations and tests are common practice as well. What a Google engineer does not know is how to stare at a blank editor window and, in the next 3-4 hours, get something cool up on the screen. They don't know how to duct-tape open source components together into a working, if imperfect, system.

by ykumar6 12y ago

nostrademons 12y ago

My experience - having worked at both Google and in the startup scene - is that young PMs at Google/Microsoft actually get to work on much bigger problems and have a much better understanding of the macro scene than startup founders. At Google, it's not uncommon to hear "Can't we just buy [famous startup X]?" or "Figure out the benefit for users, and if it turns out to be useful for a large number of people, we'll see if the lawyers and lobbyists can get the law changed" or "We'll just throw 65,000 machines at the problem." As a result, there's a presumption that problems are solvable if we just think really hard and identify the incentives of everybody in the system. Few startups have this privilege. Where Google really falls down compared to a startup is in micro-level thinking. A PM at Google may understand how a hundred million users behave in the aggregate, but fail to understand how to change one user's behavior. When your sole work experience is at a powerful corporation, you start assuming that people will take your phone calls, and you don't develop the skills of how to cold-call an ambivalent prospect, or how to empathize with a minority user who is really frustrated, or how to focus and prioritize on only the tasks that you can make a real impact on. For engineers, I'd say Google (and presumably Microsoft) engineers understand far better than a startup why simplicity is important. The codebase, after all, is orders of magnitude bigger and harder to understand. And iterations and tests are common practice as well. What a Google engineer does not know is how to stare at a blank editor window and, in the next 3-4 hours, get something cool up on the screen. They don't know how to duct-tape open source components together into a working, if imperfect, system.