The problem I've observed is also that (for performance / reward purposes), managers lie as hell when it comes to their team performance. The bigger the company, the less actual signal is received by upper managers because everyone doctors the hell out of this numbers. It might be impossible to even KNOW who the best team in your company is.
Re:Intel's disruption is now complete
by sanderjd on Saturday November 14, 2020 @04:19PM
(#25095730)
Yes. In fact, I would argue it should not be possible to have this "the best team" - if teams in different parts of the org are directly comparable, then they must be doing the same exact thing, and why do you have multiple teams scattered around doing identical things? That is, a well structured org will have teams working on Thing A and Thing B. If a brand new Thing C comes along, it isn't either Thing A or Thing B, and you have no real information on how good either team will be at Thing C, all you can know is how good they are at Thing A and Thing B respectively.
At one time IBM had the resources to assign the same major challenge to two internal organizations.
Fair point, and that sounds pretty awesome for getting data on things, but a luxury most don't have. I suspect nearly every organization where this is the case is doing it accidentally rather than conscientiously.
None of the options for dealing with this seem great. I've seen "internal incubator" type things which are designed to come up with new ideas, but honestly I'm not a fan of these. The structure incentivizes prototyping new "left field" ideas, but those ideas are likely not to gain any traction, and if they do, it is likely to be a mess to transition them into real projects within the more normal operations of the organization. And it does nothing for projects that are clearly important from inception, even if new; the "left field" incubator is not the right place to put something that isn't a crazy idea being tested but something known to be important.