I worked in an office like this onc- oh, no, what you're describing sounds more like 5th period English than an office. but seriously, it sounds like you're missing a lot of trust in the ability and autonomy of your reports. I feel bad for your reports, it sounds like you either need to let the axe swing and hire adults or learn to trust and delegate.
nobody gets to hidey-hole in their office, pretending to not be part of a team.
Seriously? That's what you think people are doing in their office: hiding from the team? I love being part of a good team. I love white-boarding broad design. I love sitting down and hammering out the nitty-gritty details. I even like pair programming and working one-on-one. But I am a classic introvert in that being around people is physically draining. I enjoy company and I'm good company, but it wears me out. Putting me in the same room with 5 other guys for 8 hours a day is a good way to get me burned out and exhausted with your project.
The whole business about having to waste an hour to get back into the zone after an interruption is, frankly, total BS.
This makes me seriously question the kind of work you've been doing. An hour may be on the long side, but there are lots of things I've worked on where an interruption will easily cost 15-30 minutes and have a much bigger impact on my willpower and focus. This is compounded by the fact that I'm mentally exhausted from constantly being in a room full of people.
Tracking a bug down through three layers of application, framework, and security code, for example. Writing that crypto implementation that has to be right the first time or customers get owned is another. Studying that new framework that you want the team to learn because it's the new shiny is another.
where they can go away into if they really need that occasional alone time
Look, I get that you're the boss and you get to tell me what to do. I want the team to succeed, so I'm not going to cause problems; I'll adapt to whatever you've decided we're going to do. But if you really want me at peak productivity you need to understand that alone time is my default mode, not something I need occasionally. I know I'm not the only one like this.
I'm curious if you've succeeded in finding an office environment that would let you work that way ?
Unless you're working from home most of the time, it seems like "the management" would generally not be too keen to this.
Looking back on my comment I was more harsh than I intended and a lot of that is because I am so frustrated with the current standard working environment. If I didn't have a family to take care of I would be extremely tempted to leave software as a profession entirely because of it.
When I was hired at my current job we had full-height cubes which are still not ideal, but workable. But now I've been shuffled into a new team working back in an open plan office. Many days after work I just want to go live in a cave and be left alone. It's not normal for me to be so socially drained and it's not a healthy dynamic for my family. I'm trying on the side to get my own company off the ground so that I can work the way I want to. We'll see.
I think one of the OPs points touches on this directly though. What is the ratio of questions asked to answers provided, or to put it another way, how many questions are you asking vs how many people come to you for help with their own question? I humbly submit that perhaps you are asking more questions than you are answering - and there's nothing wrong with that, but IMO it does explain a bit why we don't see eye to eye about this. Have you thought about asking one of your subordinates about their perspective on this?
With respect, I disagree about the cost of context switching being BS. I think it heavily depends on the complexity/sensitivity of the task being interrupted, but for any non-trivial task there is almost always a non-trivial cost as well.
> I've never been offended when someone stopped by to discuss a problem they're having...
I just wanted to clarify, I think it would be rather unreasonable to actually feel offended because someone asked your help or advice. I never feel offended in those situations. I do sometimes feel a bit frustrated or aggravated, but it's always about the fact that I was interrupted and never towards the colleague asking for help, and I take extra care to make sure that this frustration or aggravation never shines through to the person I'm helping because that would discourage them from asking for help and I would rather they asked for help than make an incorrect assumption (for example).
Their opinions matter too. Junior developers will probably suffer without easy access to those around them (yes, it's annoying for the senior devs, but that's part of the job). PM's, similarly, need to be effective; in a well-run company, they're there to help and if open-offices are important to that, well, there you go.
I'm a fan of slack etc, but I'm also an extravert. If I'm not talking to others as a part of my job, I'm going to be miserable and leave. I don't think I'm the only one.
It's important to point out though that if you make asking questions too easy for new employees, they can end up leaning on that as a crutch instead of developing the troubleshooting skills necessary to solve problems independently.
I've been on both sides of this fence. I've been that new colleague hunting for info that isn't clearly documented, and I've also been the senior colleague who was the go-to person whenever a problem came up that didn't have an immediately-clear answer. I was lucky in that shortly after I started my only senior resigned leaving me with nobody to ask, which forced me to get good at that kind of troubleshooting.
It makes me wonder if new colleagues should be given a time period for when they are allowed to ask any question no matter how stupid. After that time, they can of course still ask questions but it's expected that they try to find an answer before asking. Along the same lines of pair-programming for colleagues who have been here less than 1 year.
After 22 years in software development, I have to say I am tired of all the new tools that supposedly solve all the world problems only to be abandoned in the next quarter.
There is nothing wrong to talk to somebody when you want to tell them something. A lot of times it's more efficient then email, IMs or other more fancier tools.For you maybe, for them no. That's not to say you should not talk to them, but your interruption of their workflow has a cost you may not perceive.
there's your opinion and then there's science which actually goes out and sees how the real world works (http://en.wikipedia.org/wiki/Interruption_science)
I was in a pretty big company with super huge open floors, but globally everyone was quite, you would easily prefer to IM a person 10m away than to try to talk directly. Projects would have group IM sessions and it was the polite way to ask or share information.
If some difficult point arises, there was a meeting space at 10 or 20 meters away, or there's the coffee corner otherwise.
When discussion that atmosphere with people working in other fields, retail for instance, they would find it unhuman and creepy, but I think it really strikes the right balance. I moved to another company more 'startup' like in the athmosphere, with people cracking jokes Here and there, and it's just pure hell from a work POV.
I've worked as a developer for about 12+ years, then as a product/project manager for about 4 years. As a developer, I worked about half that time in soft-walled cubicles of various heights and another half in open office environments. I spent a year or so in a shared walled office. As a project guy, I spent about 3 years in an open office and 1 in a shared walled office (2people).
With my dev lead and project management hats on, open offices wins hands down. Whenever I want I can stand up and do a quick and dirty eyeball scan of the office and gauge who's deep in thought and shouldn't be disturbed, who maybe needs help with something, who's picking their nose on Facebook. Project goals, milestones, etc. can be on prominent display on the walls, so everyone can easily reference them--no more "oh, I didn't know we were releasing next Monday" excuses. Whiteboards all over the place so people can get up and do a quick informal collaboration, then visually reference it later from their desks. Everyone sees everyone all day, bringing an extra bit of team unity, nobody gets to hidey-hole in their office, pretending to not be part of a team. Daily stand-up meeting is quick to set up and painless, it takes a minute for everyone to just get up and walk over to the scrum corner, as opposed to having to lose 10 minutes every time waiting for everyone to decide to come out of their hiding holes. If I do have a quick question, I can tell if they're in the middle of something concentrating by just glancing over their way rather than having to knock on their office door (guaranteeing that I disturb them).
With my developer hat on, it's a bit of a toss up. I can appreciate the benefit of having a quiet, closed-in space to go deep on a problem. And open offices, while they can be quiet if you set basic etiquette rules, will never match the volume level in closed offices. But, in an open office, there's zero friction if someone needs to come chat about the code, collaborate, bounce ideas off me, and vice versa. I've never been offended when someone stopped by to discuss a problem they're having, or ask to review their approach or code. Sure, it gets you out of "the zone" a bit, but you just get back into it. The whole business about having to waste an hour to get back into the zone after an interruption is, frankly, total BS. One thing I'll say though, is the cubicles are the worst of both worlds: You have the noise level of an open office combined with the high-friction human interaction, collaboration that's limited to online tools, and hidey-hole mentality. I'd take either option over a cubicle any day.
I think my ideal office environment is open offices for everyone, but with small private workrooms here and there that people can reserve in 2hr blocks or so, where they can go away into if they really need that occasional alone time to get the job done.