[1] Source: http://books.google.pl/books?id=QZPpdB_yfqgC&printsec=frontc...
I called it "Cave and Campfire" -- blending collaborative team rooms connected by sound-isolating glass and half-glass walls to a common area with standup tables and info radiators.
http://blog.aelogica.com/business/cave-and-campfire-our-cust...
This is why I, and many others like working in coffee shops. There's usually an ambient background noise which makes it feel like you are involved in something, but it doesn't require your direct attention. I think there's also a subconscious element to having activity around you which keeps you focussed. I personally find it easy to look at cat videos on the internet when no one can see my screen, but when I know people might walk past me when at a coffee shop, or at work, it keeps me focussed.
I can do crap like respond to emails, make todo lists, read documentation, write specifications, and google for the solutions to known problems. I am however fortunate enough to have a job where all that makes up a minuscule fraction of the work I do, most of my work is in solving new problems by developing and implementing algorithms. And that requires thinking on my part which is something I am completely unable to do with new thoughts about my changing surroundings constantly entering my head. My work provides two person offices with enough space to be comfortable. As well as common areas where you can work if you so choose to be out in that type of noisy environment. Only a handful of people make use of the common areas for anything besides eating lunch or having scrum.
I believe it is because nearly everyone's work involves either thinking or being in meetings all day. And while I will not be supporting it I believe if you give someone who needs to think the choice between a nice quiet office where it is accepted that if their door is closed you don't bother them, or a nice common area with the noises of people walking by and milk being frothed, they will eventually realize they are more productive where there are fewer distractions. (Not that everyone wants to be more productive)
You seem to have a righteous indignation about people doing what you've described yourself as doing.
In fact, what really gets on my nerves is that we used to have our support people sitting three-to-an-office, and now they sit in a cube farm. It was much better isolating them with people of a similar function (both so that they aren't disturbing other people being on the phone all day, and so that there is less risk of some idiot saying something loudly that it would be impolitic for a customer to hear.)
We have a large-ish, well-lit open space, surrounded by several conference rooms. The open space is oriented in the overall space such that it's farthest from the door to minimize traffic. We're going to let each team (4-8 people) build out their own workspaces in the open area. They will organize the furniture, control how they physically interface with the rest of the space and other teams, etc. They'll have enough types of furniture to build walls, alcoves, desks, conference tables, social spaces, etc. As projects and teams change, adjustments can be made immediately.
I must say it's an exciting yet terrifying prospect, particularly because as with many existing spaces, it's not always possible to follow the prescriptive advice 100%. Additionally, almost no one has ever worked in an office space that is like the Alexander describes, which makes it somewhat of a leap of faith (in Peopleware we trust) that it will all work out.
If anyone else out there has already gone through this process, I'd love to hear how it's worked out for you.
This is the web page that got me into his work [http://zeta.math.utsa.edu/~yxk833/Chris.furniture.html].
It's one of my life's goals to build my own house using that book as a rough guide. I'm sure I'll write about it when it eventually happens.
edit: Sorry for bad English. I cannot slack in open spaces, that's why I like them.
When I'm tired and I have lots of dreadfully boring things to do, I end up reading HN. When I have a challenging task, and I'm well rested, I get into the zone and everything around me fades away and I'm really productive. The surrounding (people or no people) seems less important.
So I goof off. Perhaps I don't even work for an entire day. Am I meeting the schedule laid out for me? Am I producing as much as expected while being happy and carefully managing my output?
Forcing engineers to work nonstop is a good way to create buggy software.
There needs to be a shift in the industry to respecting what people get done rather than how many hours they spent working on it.
I personally find open space distracting. When I'm separated, I do browse a lot of HN and stuff - but at some point I eventually concentrate, gain speed, and start getting the work done. Not so in open-space; there I find it hard to do anything else than read HN or talk on IRC. Partly because I find the presence of other people unnerving and annoying when I'm working.
You're not trying hard enough.
In my last workplace I used to have the occasional unproductive day, spending more time than was reasonable on facebook and the internet. Toward the end of the day I would start to feel guilty about it. Then I looked around. There were some serious slackers in my previous workplace. I would occasionally finger a couple of peoples terminal sessions, and right enough they hadn't touched a terminal in 3 hours.
Mode 1: Preparing to program
Mode 2: Programming
Mode 3: Reviewing my code
The mix varies among projects and even days, but I usually spend more than half of my time in Mode 2: Programming.With a few exceptions, I can do Modes 1 and 3 almost anywhere, and sometimes they need to be done with others, so an open office/meeting room can be great for these.
But for Programming with any quality, I must have silence and no interruptions. I have never found this in an open office or cubicle. I can only do Mode 2 in a private office or at home.
Programmers want offices because they could need a safe haven for Mode 2 at almost any time.
If you're in an office, you can always find another place to be with others, but if you're not in an office, you constantly struggle to find a place to get into Mode 2.
Things that you are skipping in your modes: 1. Comprehending the business value and purpose of the project. 2. Interacting with end users 3. Testing ( unit testing, testing for feature completion, exploratory testing ) 4. Time management ( scrum meetings or various alteratives ) 5. Mentoring others 6. UI design and refinement 7. Bug tracking and resolution 8. Future planning/system maintenance 9. Disaster scenarios 10. System backups 11. System optimizations 12. Data structure/design
All of the things I have listed here should be understood by good engineers. They don't have to do them all, but they should dabble in all of them over time in order to be more effective.
There is no single setting that works best for all of these behaviors. It takes multiple areas and modes of interaction to accomplish everything that is needed for proper application development.
Anecdotally, at my current job I prefer working in a room where there are from three to five other engineers and lots of electronics around over working in the cube I'm assigned, but if I had a genuinely private office with a window, even overlooking a parking lot, I'd take it and work there 99% of the time, and be more productive if past experience is any indication.
I do agree that having private offices is way better, and the idea of having a building full of private offices seems great, but it is much more expensive than open floorplans with cubes. ( consider heating/cooling of many offices... having a maze of pathways to maximize the size of offices... )
Concentric rings of offices might work as a floorplan though??
Also, for some offices you do not want any windows.
I dont' know why, but your description makes the offices sound like the last place I would want to be. Small, cramped, dark, and soulsuckingly unalive.
The bullpen wasn't more productive, but it had character. It made people feel good. Made them feel welcome.
Lately, I've been doing two sorts of things: short turn-around bug-fixes and enhancements and longer-term major development. If I try to do the short turn-around work without being in the same room as the customer/tester/what-have-you non-developer, the latency of email/IM means less work gets done, which is frustrating for both sides. On the other hand, if I try to do major development while in the same room as the other people, my work simply won't get done due to the interruptions and general inability to concentrate.
To get a sense of where the OP is coming from, here's what he wrote recently on remote work:
"Some of the most blissfully productive days I’ve had are when my whole team is working remote because a winter storm has left us snowbound. There’s nothing quite like the glorious zone of productivity sans soul-crushing interruptions."
Cornell did a study awhile back that found that when you have a private office, the standard for "frequent" team interaction goes down. Way down. From several times a day ad hoc (open plan) to a couple times a week in scheduled meetings.
Want to have some time along? Move your desk away from the herd and grind away. Need to handle a sudden need that requires lots of team interactivity? Arrange your desks in a small circle for maximum interaction.
The problem with companies in general is that they are run by management who have been trained that fixed structure is the most effective way to get things done. Structures are good; but they don't have to be fixed. There are pluses and minuses to every single methodology.
Blend.
So... why insist on spending money on high end equipment and furniture while not giving people what they asked for?
I was at a place years ago that was happy to spend tens of thousands of high-end chairs, but giving developers private offices (those who wanted them) "cost too much". Bear in mind that they'd custom built a second office with private offices that were sitting empty (and devs were in the second office). The "it costs too much" doesn't carry much water when that sort of money is spent on things that people aren't asking for.
“All of humanity's problems stem from man's inability to sit quietly in a room alone.” - Blaise Pascal. It's true. I have never gotten in trouble sitting quietly in a room alone.
When we were planning some new office space for a move, some of the staff wanted open concept, while others wanted their own space with privacy. It was a tough conversation given that a moral air was added to it -- one where those who favored open concept were collaborative and selfless, while those who wanted a private space were selfish and insular.
Regardless, we designed a new office space that had both (it was designed for significant growth): An open area, similar to what was trending in the "startup world" (cargo culting), and private areas (not quite private offices, but tall private cubicle walls on all sides, strong sound abatement, no concern that someone is creeping behind you, etc).
We moved and let people pick their spots essentially anonymously. Every single one chose a private area, with the majority selecting the most private area which ended up being assigned by a random drawing. Indeed, it struck me that the person who was the most outspoken about open concept and all that jazz was the one who complained the most about others intruding in their quiet zone (they complained about music, loud conversations between peers, etc).
On a separate floor we had a bullpen with ops folks, people who were on the phone a lot, etc. One by one, each engineer gravitated towards the bullpen until no one spent more than perhaps 1 day per week in the dedicated office space. The part of the office that each engineer had claimed to want to work in became abandoned.
I think, in spite of the theoretical want for quiet space and isolation, there's a very human need at work to be in the middle of the action -- to hear what's going on, and to be connected to your colleagues. There were certain tasks and problems for which engineers would walk downstairs and make use of the dedicated space, but it was ultimately not where folks wanted to be on a daily basis.