3 ms·
It was at Microsoft that the change occurred: some management consultant at Microsoft issued the fatwa "beware the guy in a room". A person who isn't actively e
by bitwize 11y ago
It was at Microsoft that the change occurred: some management consultant at Microsoft issued the fatwa "beware the guy in a room". A person who isn't actively engaged with The Company at all times, who is off doing his own thing, is a huge productivity risk because he lengthens his manager's OODA loop.
- imgabe 11y agoIf the OODA loop seriously got dragged into this nonsense, that is ridiculous. That would almost be the exact opposite of Boyd's strategy.
- bitwize 11y agoIt wasn't described in OODA loop terms but rather in terms of "going dark". You don't want to have a developer "go dark" for too long. Of course that means that what management wants is exactly the opposite, for the developer to be continuously accountable and hence, always available. Jim McCarthy, the originator of the "guy in a room" quote, has indicated that it's not to be taken merely metaphorically, that offices encourage isolation and "going dark", and open plan is key to productivity, collaboration, and accountability.
- parasubvert 11y agoJim McCarthy made that observation while he was a manager at Microsoft (not a management consultant, though after he left MS he became one). He's absolutely right - dudes alone in a room all too often are doing the wrong thing very effectively. http://www.goodreads.com/book/show/1416996.Dynamics_of_Software_Development http://www.goodreads.com/book/show/1416996.Dynamics_of_Softw...
- jon-wood 11y agoThat feels pretty resolvable without forcing everyone to work in each other's lap wearing huge headphones. In my experience daily standups are often enough to keep everyone on the same page and make sure no one is dashing off in the wrong direction.