They need to either remove at least a major part of the overhead and constraints of these highly scalable systems, or create a well planned and organized transition path from something with low deployment and development overhead to something "google scale". This could be at least at first a completely non-technical thing, such as requiring teams to at least have a plan of how they will migrate their redis, solr or whatever data stores to whatever google is using at scale. But reading this makes me cringe, that sounds like a very frustrating environment to work at and sounds very ungoogle-like to me. It appears their public image diverges much farther from reality than I would have thought.
I assume things are similar in other large tech companies.
I'll posit that the real problem with big companies is the opposite: the price of failure is mild (you get reassigned to another team and get to do more cool stuff) and the benefits of success are also mild (you might get a promotion and an iPad or something). When your actions have little effect on the outcome, your actions tend to regress to the mean. In a startup, where failure means you starve and success means you never have to work again, you have a much bigger incentive to go the extra distance.
Startups given the market for engineers in particular actually only have a temporal starvation penalty. It's not like they can't get another job after they fail.
Doing this in a large company might lead to even more innovative products because startups are so under-resourced and governed by promises to investors that they risk becoming myopic and less agile.
(Serious question - what I have seen is that the team lead gets bumped up one notch and gets to try on a larger scale).
I know of at least one team that came up with something major that asked for their compensation to be tied to their product success having their idea moved to another team because "they should do it for IBM purely". Of course that product failed for lack of vision and focus.
The author started at Google post-IPO. That's hardly "startup" time. In a startup it's not like resources are given out like candy and there's massive amounts of free-time for working on 20% projects.
It's true that there are less meetings at startups, but there are other things that typical hackers find unsavory: developers also have to do sales, sysadmin, customer support and generally be much more aware of where the money comes from.
The thing that makes a startup interesting is that the company is the project. Frequent meetings aren't as necessary because the goals are usually easy to understand and fairly one dimensional, e.g. "We have one product and we need to increase the number people using it."
The way you'd make a big company more startup like would be to make teams far more autonomous and drastically increase the risk / reward gradients. Your product ships 6 months late? Your entire team is fired. You open up and sustain a new revenue channel that's paying big dividends? Everybody gets a $2 million bonus. Team leader disagrees with his boss? He can chose to do it his way, knowing he's risking his team's livelihoods.
I don't know if anybody's really crazy enough to try it in a large company.