7 ms·
This sums up Google in a single paragraph: In 2015 Nest posted job listings for its "Nest Audio Team." The team would be responsible for "developing an audio r
by ChuckMcM 10y ago
This sums up Google in a single paragraph:
In 2015 Nest posted job listings for its "Nest Audio Team." The team would be responsible for "developing an audio roadmap for Nest products." Industry observers suspected the audio team was building a smart Bluetooth speaker, but Google beat Nest to the punch with Google Home, an Amazon Echo-style Bluetooth speaker and voice assistant appliance. According to a report from The Information, when Nest found out about Google Home, it asked to work on the project with Google. Nest's request was turned down. We can only guess why—maybe Nest's reputation inside Google had something to do with it?
Often times Google has multiple projects doing effectively the same "thing" going at the same time. They don't work together because the idea is to have the team that can get to the "finish line" first to win, not to co-operate. This, as it was explained to me by an engineering director there, was to encourage a 'natural selection mechanism that selected for the best teams and the best products.'
While I understood the idea, that you would pit your own resources against each other like that was kind of foreign to me. My own personal learning from that, having watched them for 15 years, four of which from the inside, is that as a way of managing a company it produces few viable products and no viable businesses.
- dexwiz 10y agoThe flipside of the argument is a Project Managers hiring 9 women to have a baby in 1 month. Collaboration between teams does incur a cost. Working closely with a single team is easier than coordinating across multiple teams in multiple business units. The additional headcount may not offset the cost.
- lostlogin 10y agoI'm slightly missing the point, but have to ask. Why 9?
- dexwiz 10y agoAverage pregnancy is 9 months long. "Limited divisibility of tasks. Adding more people to a highly divisible task such as reaping a field by hand decreases the overall task duration (up to the point where additional workers get in each others way). Some tasks are less divisible; Brooks points out that while it takes one woman nine months to make one baby, "nine women can't make a baby in one month"." https://en.wikipedia.org/wiki/Brooks%E2%80%99_law https://en.wikipedia.org/wiki/Brooks%E2%80%99_law
- SideburnsOfDoom 10y agoAverage pregnancy may be 9 months long, but that's not even the right metric: the cycle time from one successful birth to the next is longer than that.
- lostlogin 10y agoOut of every nine women, less than 9 are able to have children once age and various conditions, medical history, choices etc come into play. I think I was over thinking the scenario...
- deleted 10y ago[deleted]
- mmanfrin 10y ago1 woman can make 1 baby in 9 months, so 9 women can make 1 baby in 1 month.
- JshWright 10y agoMy wife recently made two babies in 33 weeks. That's less than half the average time per baby! Granted, they spent a combined total of 62 days in the NICU, but even accounting for that, we're still ahead, I think.
- stcredzero 10y agoCongrats! A premature baby in NICU might appear even cuter to many on the internet. The game and app reviewing public is less charitable to premature software, however.
- Normal_gaussian 10y ago62 days -> 9 weeks 42 weeks overall 4.33 weeks in a month 42 weeks -> just shy of 10 months I'm not so sure if you are ahead on weeks. But you are ahead on kids! Congratulations and good luck
- NLips 10y agoWell full-term is often given as actually being 37-42 weeks, with the due date estimate being 40 weeks (not 9 months), making 42 weeks a normal(ish) pregnancy duration. Not that I want to derail the well-wishing!
- JshWright 10y agoYou can only double count the babies' NICU time if you're looking at the average baby per week. We averaged 0.048 babies per week, as opposed to the baseline 0.025 babies per week.
- ChuckMcM 10y agoThat example from the mythical man month, however to really put it in context, it would be like hiring 9 pregnant women and giving a bonus to the first one to deliver a baby and aborting the other 8. And yes, that is an overreach because aborting a later term baby is a way more serious thing than canceling a project you've worked on for nearly a year. However, projects that were "late to deliver" were de-funded and it was really hard on the project leaders. When it happened I did not see it instilling in those engineers a desire to work harder and faster next time, rather it just made them cynical and bitter.
- bane 10y agoI think importantly, not all approaches requires equal time to achieve. Some approaches might have been more viable in the market if the PMs had simply been given more time to achieve the product rather than just tossing out the first thing to cross the finish line. It really explains the sloppy state lots of Google products ship in.
- fiatmoney 10y agoThe notion of internal competition is really tricky, since you're also competing externally. If you believe in the classic explanations of the theory of the firm, "companies" exist so they can be effectively communist on the inside in an attempt to lower transaction costs. If you have teams competing against each other directly for resources, time-to-market, etc. you don't really have a reason to be a single company anymore. OTOH, a little bit of internal competition to penalize complacency, if there's not too much wasting of resources, is probably a good thing. It's been fairly common IME for different teams to be working on very related concepts (eg, HPC platforms for different tasks), with a sort of implicit understanding that the team that does well will be able to do the logical extension of the project, and the team that doesn't will work on something else.
- jsprogrammer 10y agoWhere can I find more information about the theories that claim companies exist to be communist? I don't buy the "first to win argument", but it would seem useful to take multiple approaches to solving the same or similar problems.
- Avshalom 10y agoCoase's Theory of the Firm https://en.wikipedia.org/wiki/Theory_of_the_firm https://en.wikipedia.org/wiki/Theory_of_the_firm although I think fiatmoney is conflating a centrally planned command economy with communism.
- CamperBob2 10y agoalthough I think fiatmoney is conflating a centrally planned command economy with communism. Seems like a distinction without a difference, considering that every time a nation tries to implement the latter they end up with the former as an "intermediate stage" of the revolution that somehow never goes away. In a corporate body, there is no pretense that central planning is a transitional stage. There are a few exceptions like Valve and Zappos, but even fewer genuine success stories where a non-hierarchical structure has outperformed traditional ones in the long run.
- rcthompson 10y agoDid they actually refer explicitly to "natural selection"? Because while natural selection has indeed produced some impressive results, it did so over billions of years, and not terribly efficiently, so I wouldn't generally consider it a model to be emulated, unless Google is really optimistic about how long the company is going to be around.
- ChuckMcM 10y agoYes, they used that exact term, invoking Darwin at the same time. And I agree with you about the time frame. I've been reading "The Vital Question"[1] of late and it has been the first book in a while where I've had several "oh that makes so much sense!" moments. And one of the tenets is that Darwin was correct in the small, and wrong in the large understandings of evolution. Something that jumped out to me while reading it, is that information extraction drives our technology systems like energy drives biological systems. Read the book and then sit back and analyze Twitter as a multi-cellular organism with information as energy and individuals as cells. A sort of Datasaurus. Fun stuff. [1] "The Vital Question: Energy, Evolution, and the Origins of Complex Life" -- http://www.amazon.com/Vital-Question-Evolution-Origins-Complex/dp/0393088812 http://www.amazon.com/Vital-Question-Evolution-Origins-Compl... based on the recommendation tweeted by Gates and comments here, I read it through cover to cover while camping, and now going through a second reading to pick up what I overlooked the first time.
- walshemj 10y agoHmm this is how Hitler ran Germany and why they had multiple research programs competing with each other - not sure its a good model to follow
- sdenton4 10y agoMeh. The us military does this, too. It's pretty common.
- arethuza 10y agoIt's why the UK had 3 different types of strategic bombers - developed by different teams and with different levels of risk and performance: https://en.wikipedia.org/wiki/V_bomber https://en.wikipedia.org/wiki/V_bomber
- walshemj 10y agoAh like in ww2 where the Army and Navy intelligence refused to cooperate unlike BP did.
- walshemj 10y agoYour tax dollars at work :-)
- asdfologist 10y agoHitler also spoke German and ate 3 meals a day - not sure it's a good model to follow.
- walshemj 10y agoThe German competing fiefdoms method caused real problems when the allies got a good enough design and cranked it out like the T34, sten gun and arguably the Sherman tank
- crabasa 10y agoMicrosoft was famous for its internal competitions between engineering orgs: http://mobile.nytimes.com/2010/02/04/opinion/04brass.html?partner=rss&emc=rss&referer= http://mobile.nytimes.com/2010/02/04/opinion/04brass.html?pa...
- quanticle 10y agoEmphasis on was. It seems like these days Microsoft is moving towards more internal collaboration, with their "One Microsoft" initiative. They've found that greater focus on common, standard tools used across the entire company is better than having a bunch of teams, each rolling their own version of a given tool. More to the point, isn't this exactly what Steve Jobs advised Larry Page not to do? Steve Jobs said, famously, to put "more wood behind fewer arrows". And for a while, it seems like the advice was sticking - Google shuttered a bunch of products (for better or for worse) and seemed to be buckling down to focus on the search and YouTube division. But now it seems like Google is going right back to how it used to be - many teams, working on many products, with no guarantee of ongoing development or support. It seems to me that Google is turning into the next Cisco.
- stcredzero 10y agoToyota has formalized internal competitions. The Prius drivetrain was the best out of a field of 10. Designs for new iPhones apparently work in a similar fashion. I think such formal structures produce very good results and are necessary to prevent destructive internal competition.
- petra 10y agoCould you please explain the last sentence ?
- gnashville 10y agoI think he meant as opposed to informal (maybe petty, harmful) internal competition.
- stcredzero 10y agoSee ChuckMcM's cousin comments.
- ChuckMcM 10y agoFor me, there is an interesting difference. On the one hand you can say "everyone compete on the next iPhone antenna design". That is one component out of an over all strategy. But proposing incremental improvements at Google when I was there was death, you were accused of "not thinking big enough" and everything had to be a "moonshot". So you couldn't propose just a new antenna, you had to propose using an entirely different spectrum with entirely different rules and an entirely different platform architecture where voice service was one of many options rather than the main option. You don't get to propose re-inventing the phone, you have to re-invent telecommunications. One of those that got out of the door when I was there was the Google "wave" project. Its vision was so big it missed the fact that people just wanted Slack[1]. Bottom line is that competition within a structure is good, its something that lots of organizations have applied successfully. Google's style, when I was there, was never structured enough to head toward anything. It always went all directions at once, leaving the organization with a net zero momentum in any direction. [1] Yes they are nearly a decade different in time frame, but as a 'dogfood' wave user and then later outside of Google it was pretty clear the "win" was the IRC replacement, none of the vision stuff was getting much traction but it was the way to go if you're group wanted to figure out which cafe to go to lunch at that day.
- pkaye 10y agoMy own anecdotal experience I heard a much larger competitor in my line of work have 3 teams competing against each other for a product. All failed except one which tagged up with an external partner to build a solution for them. Apparently many large companies don't know what to do with all their employees. I spoke to some of them later after my company hired some and all some engineers hope for is to actually complete a project. Something similar happened to one of my previous employers. We were less than 100 people and cranking out many successful projects. Once we got acquired and nearly quadrupled in size, none of the projects succeeded. Many of the early contributors left one by one due to frustrations and pressure including me. The new management style had changed everything.
- OpenDrapery 10y agoThis is something I'm coming to grips with. Massive inefficiency is not just the domain of government agencies. There are plenty of firms in the private sector that have teams sitting idle, and the kicker is they are hiring! It is not uncommon for a software developer to be asked to keep a seat warm in an open office seating environment. It feels very unnatural to be expected to sit in front of a computer for 8 hours and be given nothing to do. Some people convince themselves that they are riding the gravy train, others go crazy and leave to find actual work.
- Nursie 10y agoThat sort of thing is supposed to have been a lot of what was going on at nokia towards the time it started to really founder.
- kristianc 10y agoIt's proven incredibly successful as an approach for Dentsu in Japan.
- CamperBob2 10y agoWhile I understood the idea, that you would pit your own resources against each other like that was kind of foreign to me. My own personal learning from that, having watched them for 15 years, four of which from the inside, is that as a way of managing a company it produces few viable products and no viable businesses. I can't find any good citations online, but Electronic Arts was reputed to do that as well. Supposedly they'd put several developers on the same title, and whoever finished first got to ship.
- pjmlp 10y agoWell if the reports are true, that is also what happened with Longhorn and later on with WinRT vs Desktop, meaning WinDev vs DevTools divisions at Microsoft.
- untog 10y agoI thought that really came through in I/O this year. The Allo team does not seem to be the same team as the one making Hangouts. Which is fine... except that has a Hangouts user I really wish they would dedicate themselves to a messaging app and actually make it good. The more confusing one was web vs. native - there were a dozen sessions on progressive webapps, yet they barely got a mention in the keynote, while Instant Apps got a full showcase. Internal competition is all very well, but it's frustrating as a developer to not be able to get a clear answer as to which platform we ought to be developing for.
- hkmurakami 10y agoMy understanding is that MSFT operates in similar fashion. The difference is that none of the implementations get green lighted until some C level exec asks years later, "Hey why don't we do X?" Some other guy in the room will reply, "Sure, we have 4 versions of X. Which one do you want."
- toyg 10y agoThat's what I thought while reading the post. Microsoft was infamous for internal divisions basically acting as separate companies, with divergent roadmaps, duplicated features and so on. In this case, however, given the prominence that was originally placed on the acquisition (at a time when Google had no direct presence in home automation), I suspect that the original vision was to actually merge the two worlds. The Google rank&file probably learnt very quickly how toxic Fadell was, and then proceeded to keep Nest at arms' length and do their own thing, basically writing off the acquisition and hoping it will eventually go away.
- greggman 10y agoPersonally I think it's great. Coordinating 57k people is very very hard. If you had to ask 57k people "Hey, I'm going to work on this, anyone else already doing something similar" the entire company would grind to a halt. Sure there are mistakes but I don't think it's top down "team x" compete with "team y". It's more like both teams don't know about each other until the projects are far along. At which point might as well see which one does better... Or at least that seems to be the attitude at google.
- yongjik 10y agoWhile that can be a problem, it's tough to address at Google's scale. Consider the possible solutions: (1) Top management tells everybody what to do. Result: No initiative from low-level employees. (2) In case of conflicting projects, top management decides which team should continue. Result: Rampant internal politics. (3) In case of conflicting projects, let all of them continue, and see which project wins the market. Result: Wasting resources; company looks disorganized to outsiders. Some other companies (Apple?) avoid the problem by sticking to (1). However, many Google employees joined in the first place thanks to the tale of "A company where you can work on the problem you want to": it will be very tough for them to ditch the model wholesale, and it may harm the company in the long run. I think Google does a bit of all three. While Google could certainly do better in some cases, it's not like Google's willfully ignoring an obvious solution.
- g9yuayon 10y agoThe problem with 3) is not just wasted resources or company looking bad to outsiders. It also leads to rampant internal politics as people simply do everything in their power to win, or worse, to survive. Just to name a few common tricks: developing features secretly, not sharing resources or technologies, poaching coworkers from other teams, lobbying to get more resources, developing moating features instead of focusing on what users really need, and trading long-term objectives for short-term gains just to get to the so-called "finish line".
- awesomepantsm 10y agoThis type of practice is common in government work. Hire a dozen teams to make a thing by some deadline, and award the best result with a contract. It seems wasteful, but as we can see here, clearly the Nest work style couldn't compete with Google, and so no need to waste further R&D. But until you didn't the contest, how could you know?
- bane 10y agoI think the fundamental problem with this type of approach is that the ugly, sausage making, competition ends up getting aired too much with the public which creates market confusion and drives potential customers to places with a better, simpler story. My understand is that great product companies, like Apple, also have a kind of Darwinian development practice, but only ever reveal the "winner" once it's clear that it's the winner. As an outsider, Apple looks like it has strategy and vision, while Google looks completely baffling, even releasing and pulling products from the market within weeks or releasing clearly incomplete, barely beta level products with no real vision and just expecting the public to sort it out. I mean, how many chat apps is google up to now?
- kinkora 10y ago> While I understood the idea, that you would pit your own resources against each other like that was kind of foreign to me. My own personal learning from that, having watched them for 15 years, four of which from the inside, is that as a way of managing a company it produces few viable products and no viable businesses. Interesting you say this as the first example that I can think of is Apple themselves when Steve Jobs was forced out of the Apple Lisa team and he joined the Macintosh team which then became in direct competition with the Apple Lisa team. I don't need to expunge on that but i found it to be a very famous case study on how 2 internal teams in direct competition affected the company.
- saalweachter 10y agoI'm not sure I believe that's an intentional strategy or just a side-effect of size and the philosophy of letting teams start projects on their own. So you have two teams somewhere in a company start a project at the same time. Your challenge is, what does the corporate structure need to look like such that these two teams learn about each other's project early enough to collaborate? If you rely on project information being passed up and down the corporate ladder, until one person learns that two subtrees of his reports are working on the same project, that's never going to work because bandwidth is reduced as you go up the tree, so less and less information is passed up, and early/experimental projects will frequently not make the cut and get filtered out. So your LCB will never hear about both projects. If you just rely on direct communication between teams, you've got an N-squared problem as you grow, so that will never work. If you try to give each team a carved out domain, new projects will frequently exist in the "chocolate & peanut butter" intersections, and both the "chocolate" and "peanut butter" teams will start the same project. It's a difficult problem, and I'm not sure there's an answer between "companies should be small".
- technofiend 10y agoRight before they went under Enron was doing the same thing: they felt having three teams compete for fastest to market was a competitive advantage and worth the wasted resources sunk into the two losing teams.
- anotherhacker 10y agoInternal competition destroy's companies. Deming said this over 40 years ago: "The present system includes competition between people, teams, departments, divisions, students, schools and universities. Although economists have taught that competition will solve our problems, we now know that competition is destructive." http://maaw.info/ArticleSummaries/ArtSumDeming93.htm http://maaw.info/ArticleSummaries/ArtSumDeming93.htm
- draw_down 10y agoAs I recall Apple did a similar thing with the original iPhone OS, one team took the iPod software as a starting point and another took OS X as a starting point. I think I have that right. If in the end it makes the best product it's probably worth the waste of having competing solutions. But that is kind of a big if. (I would say the iPhone passed that test, personally.)