Because home might be an even worse place to concentrate in than open-space office. I know it is for me, it's the only reason I actually come to work instead of doing it remotely (which costs me additional 2h/day of commute time).
Well, if they hire me at local Google office, I could cut it down to ~40min / day ;).
Anyway, as my commute is walk+tram+bus+walk, I do offset this time by reading books and replying to e-mails while in transit. I'd be really, really angry if I had to spend this time driving a car.
The people who share my home do not respect my workspace. If you think interruptions for work-related questions are productivity killers, imagine being asked to empty the trash for the fourth time in one day. Oh yes, let me interrupt this work that requires some level of concentration and skill to do something menial and distracting. Again. Or be pestered about it incessantly until I do it.
I'd gladly work remotely, but not from home. No way. If there are no small-business-incubator businesses nearby, I'll be working public library hours, thank you very much.
I think the best arrangement is private offices / cubes surrounding a central team area where more interaction can occur. Pixar had a really cool idea where Steve Jobs put all of the bathrooms on one side of the building in a central area so people were forced to bump into each other spontaneously throughout the day but only when they were already interrupted.
This sounds like a great idea, but only ~25% of the 'bumping into each other' could lead to a conversation in this situation...
Only when A & B are both coming out of the bathroom can interaction occur. Otherwise, A is desperate and dashing in, B is wishing she'd not had that curry last night, or both A & B are desperate and not stopping for anyone ;)
Pixar had a really cool idea put all of the bathrooms on one side of the building
I'd be interested to know how much they saved on plumbing costs. That seems to me like an architectural decision driven by financial concerns and sold as a benefit. Not that it isn't a benefit, many of the most interesting designs are a consequence of some practical constraint.
Apparently you haven't seen the Pixar buildings; it's pretty clear that little of their design was guided by financial constraints. They are about as far as it's possible to get away from typical cheap office construction.
Really? Most people go to the bathroom once or twice a day. The chances of you timing that to coincide with someone else for whom it's beneficial that you start to spontaneously chat seems kind of low. To put it another way if Steve thought it was important to have that I suspect he would have found a different mechanism that the one above.
> To put it another way if Steve thought it was important to have that I suspect he would have found a different mechanism that the one above.
Maybe, but that particular mechanism was implemented. It actually received some negative feedback from a pregnant woman who felt she was forced to walk an undue amount to the bathroom.
The point of the parent was that the Pixar offices are designed around encouraging unplanned team member interaction. Their leadership believe this is crucial to encouraging creativity.
I'm not sure on the exact numbers, but in San Francisco a programmer probably costs you on average $100K a year in salary. With benefits the total cost is in the neighborhood of $120K. So a programmer is a $10K / month investment.
For what it's worth: assuming white-collar employees, the multiplier is typically 50% to 100% depending on your location and how generous you are with perks, rather than 20%. If you only have $120k available in the budget to hire someone, don't offer a salary higher than $80k, or you're going to have a very unfun meeting with your accountant saying "OK, would you prefer I took the money from somewhere else in the business, or do you want to go to prison for not paying our portion of the payroll taxes?"
There exist many folks who have more experience with San Francisco hiring than I have, but the word on the street for e.g. funded startups trying to pay market salaries is that you should be budgeting $15k~$20k a month to increase your team size by one.
Can you (or anyone) go into more detail on what the number "$100K yearly salary" includes and doesn't include, in the US? Helpful for those of us not in the US. I.e. what makes up that extra 50%-100%?
Our own multiplier (Israel) is usually 30% extra over the stated salary, although the salary here is usually stated as a monthly, not yearly, number.
I was always told that for "standard" jobs 2x or 3x was the OH rate I did work for one world leading RnD organization that was well over 5x and heading towards 7x.
When the cost of the a single piece of equipment for a single experiment cost in excess of $5 million you can see why - in the end we did not go down that route. A pity as the ML neural networks aspects of machine vision would have looked very cool on my CV
The universal understanding of salary numbers among employees in the United States is that it is gross cash pay before deductions. We typically quote them annually for professional positions, and they're typically paid out in approximately equal bi-weekly installments, with a bit of variation for cash bonuses (which are common in some industries/locales and not in others).
The biweekly paycheck for someone with a $100k salary would thus be approximately $4,000 gross. It would list a deduction for payroll taxes, a deduction for anticipated federal and state income tax, a deduction for the employee's portion of health insurance, and perhaps some miscellaneous deductions for unemployment insurance premiums, automatic contribution to their retirement account, and what have you. This leaves them with net pay (probably in the $2,700 region or so but it's heavily sensitive to their family situation because that makes a huge difference in how much anticipated income tax is withheld) which is actually transferred to their account.
So all of that is included "within" the $100k yearly salary. What isn't, such that business owners have to model it separately?
1) Payroll taxes are typically divided half between employees and half between employers. For example, there's a ~14% levy on the first ~$100k in salary, for Social Security (primarily a form of compulsory retirement savings which the vast majority of working Americans are legally required to contribute to). ~7% is deducted from each paycheck for this (so ~$280 out of $4,000). An equivalent sum is contributed by the employer, without ever appearing on a paycheck. So the employee's real salary is actually about $107,000 but $7,000 disappears to taxes prior to the point where they're told the salary that they are going to be taxed on.
2) For historical reasons, the United States does not tax many forms of health insurance if provided as a perk to employees. The United States also historically did not have a national health insurance scheme. (We've got Obamacare these days but it doesn't meaningfully interact with the math for Valley engineers.) The combination of these two facts means that virtually all white collar employees expect to have employers fund fairly generous health insurance plans as an employment perk. The pricing for these gets a little weird, but you're in the right ballpark at about $10k to $20k per employee per year.
3) In addition to our national retirement savings program, we have "individual" retirement savings. These programs have substantial tax advantages. These are not compulsory, and can be funded by either an employee, an employer, or both. It is the common practice of most employers of engineers to fund these retirement accounts on a matching basis. The offer is at the company's discretion (up to a legal cap). A common offer is "We will match $2 of your contributions with $1 of our own money, up to a maximum match of 3% of your salary."
4) American engineers are commonly offered perks. Many are comparatively inexpensive when bought at company size -- free gym memberships for all employees, for example. Some are not exactly inexpensive -- free lunches and dinners on the company's premises daily, prepared by gourmet chefs, for example. Americans do not customarily include the implicit cost of perks in salary figures.
5) There's a bunch of business overhead that I haven't accounted for above (desks, prorated rent, computers, etc), but they're substantially the same as in Israel, so I won't belabor the point.
Anyhow: health care, taxes, and perks is what gets you to 50 to 100%.
If anyone is interested, here in Israel we usually talk about the gross monthly salary, and we add around 25%-30% above that for the "true" employer cost.
Similar to the US system, but we usually don't include perks like gym membership when thinking of "employer costs". I think they're also less common, which might explain it. We do include the employer portion of the taxes, the employer portion of the pensions, potentially the employer portion of other savings accounts, and - unlike the US, I believe - one perk that is very common here is a company car, which is usually leased out to the employee.
For me, noise isn't the problem. Since moving from the SF bay area to North Carolina, I work at home a lot for my California job.
I like to get out for several hours almost every day, though. I head to either Krankies Coffee or Camino Bakery in Winston Salem, and both venues have: a lot of people talking about family, studies, work, business, gossip; the espresso machine; music; and at Krankies the coffee-roasting machine. * Undifferentiated noise actually helps a lot! * I find the background din soothing and conducive to designing and coding. The one thing that's annoying is the occasional person who insists on carrying on their half of a conference call very loudly, but I don't see that much.
I've had pretty good experiences with open floor plans in companies too. They've never been the row-upon-row of adjacent tables depicted in the post, but close enough see/hear everything that's going on. In the open environment, a lot of the noise will probably be discussions about coding/design matters on other projects, or general office hijinx. There are downsides to that, but there's a lot of benefit too. You don't need to wait till the water cooler to see some matter needs discussion.
I can see how both the open floor plan and coffee shop environment will be distracting for some. I always hated libraries as a student, and always did my best work in non-quiet environments.
(I miss having coworkers just five steps over -- they're now 2700 and 8000 miles away.)
I enjoy the chaos as well - I am not productive at home alone at all. But strangers don't interrupt my every 10 minutes (or ever.) Software development requires sometimes being collaborative and sometimes needing uninterrupted work time. An optimal environment would allow for both of these, as needed. Open floor plans and closed-door, isolated offices only allow for one.
I'm willing to bet noise isn't the problem for a fair chunk of developers who complain about open offices because they aren't annoyed by noise, they are annoyed by constant interruptions to work.
You too? I've got the blue pair. Some of my coworkers don't really get just how much sound they block, and get pissed that I'm not responding to them when they're standing behind me talking to me.
yeah, at an old job they were given out to every employee as standard workplace equipment. I found them really helpful so I bought a dozen of them and passed them around to other people that wanted them. They're pretty handy.
Open plan offices are only part of the problem. The other more serious issue is that we as a society have collectively ruined out ability to concentrate.
Email clients, chat clients, Social media, rapid fire short form articles, distraction wherever you look; these all contribute to a reduced attention span.
I do think it's possible to change the habit, but that requires mindfulness to engage in less context switching activities. That's really, really hard.
Suffers from the same flaw as most critiques of open plan: it focuses on individual productivity while failing to understand how it contributes to team productivity.
The misunderstanding here is that it's just about serendipitously "overhearing" other conversations.
1. Open plan makes it easier to ask questions. Those are "disruptions", yes, but what the Cornell study found is that in open plan it's actually easier to "read" a person and see if it's an ok time to ask a question, and to quickly reply or say ask me later, and so forth, to efficiently manage those disruptions. Compare that to offices where you are much less likely to ask questions, knock on a door, etc., and where when it does happen it may turn into a much longer disruption.
2. They found it also gives us more courage to ask potentially "silly" questions. Which can be the genesis of good ideas and help us get unstuck, contributing to team creativity and productivity.
3. They noted that developer reactions to office plans are often biased towards maximizing personal productivity in order to maximize (short-term) personal benefit, whereas the company benefits from a balance of personal and team productivity. That's a fancy way of saying we'd rather spend our time coding than helping others, so we may not instinctively appreciate the benefits of open plan as much. Which I think is the case here.
Interesting point. My concern about item #3 is that we're maximizing personal productivity because the company is still mainly rewarding personal productivity. I work at a company where only one person in each group can get an above-miserable raise every year.
This is one of those "beat the drum" issues on HN where we keep seeing article after article trying to drive the same one-sided point home. When I see this as the top article on HN, I just have to wonder if many of the people who come to HN are looking to disrupt the startup community.
I've worked in environments that run the gamut from individual offices, to cubes, to small working group rooms, to large open spaces. I've managed people in all of those environments as well, and I can tell you that openness leads to more synergy and more overall productivity. Maybe one or two in ten people have trouble working in that environment because they're too distracted. Sometimes you need to find hybrid arrangements to give people with trouble focusing a little more space -- but to just blanket claim that it's all about floorspace cost (as this article did) is akin to political advocacy.
I've managed people in all of those environments as well, and I can tell you that openness leads to more synergy and more overall productivity.
In my experience, synergy and productivity is far more closely tied to clarity of goals and effective leadership than floor plan. Open floor plan advocacy, when it involves dragging people out of the offices they are quite happy with, is often a sign of leadership with misplaced priorities.
"Maybe one or two in ten people have trouble working in that environment because they're too distracted."
How do you know? Did you actually ask everyone "Do you have trouble working in this environment because of the distractions?" People are afraid of being seen as "anti-team" and "anti-open plan", and they won't tell you the truth. And others fake it, even if they really hate working in such an environment (I'm one of them) because it seems like a necessary evil these days. So the reality is, maybe that number is higher than you think.
Yeah, I did communicate with people about the efficacy of the working environment. Plus, for the past 12 years or so, everyone I've worked with has had a laptop that they could always (and did at times) take to quiet places when they needed alone time. They self-identified as needing quiet. Most others self-identified as liking the more collaborative working spaces.
I'm one of them
If you're working in an environment that is unproductive for you (that you hate) and you're not able to say something, then you should consider departing from it or addressing your own inability to have frank conversations with the people for whom you work.
Having the ability to retreat to a quiet area is critical. Many people don't have the option of going to a 'quiet room'. It's just one big, chaotic workspace.
Personally I have discussed this with coworkers/managers, but the environment is not going to change. Wherever I go next, I'll be on the lookout for quiet&privacy.
I like that idea, but I can see an immediate trade off between the large screen of my desktop and the lack of distractions of taking my laptop somewhere.
Maybe I'm misreading, but that sounds like a questionable response to someone critiquing managerial blindspots. Shows blindness to corporate power structure. Also perhaps lack of understanding why people really take jobs. (One of the things bosses accept is that their subordinates lie to them. For instance, this is a driving force behind bad estimates.)
(I don't have a firm opinion on open vs. private offices, except I'd prefer to choose depending on what's best for the day).
In my experience, it's not accurate to say outright lying is a driving force behind bad estimates. Estimates are actually a difficult problem. "Padding" an estimate is not a lie, it's a tool to be more accurate in the aggregate, because it helps account for the 1 in X instances where a task is significantly more time-consuming than you ever could have reliably estimated.
"Take your laptop to a quiet space" is insane unless that "quiet space" is setup with a decent desk, external monitor, keyboard, and mouse. In fact, it's a great invitation for a lawsuit. I think I'd file it myself the moment I heard that, just to scare the HR and legal department into explicitly banning such an absurd excuse from ever being used again.
Suffers from the same flaw as most critiques of open plan: it focuses on individual productivity while failing to understand how it contributes to team productivity.
For what it's worth, most of the open plan proponents have a similarly frustrating tendency to completely ignore the individual productivity trade-offs.
At most organizations I've worked at that use an open floor plan for programmers, we pair-programmed aggressively. Subjectively, a good pair more than offsets the distractive drawbacks of an open floor plan. If instead you hand each programmer a pair of headphones as they walk in the door then yes, productivity's going to take a hit compared to closed offices. Working in isolation in an open floor plan is worse than working in isolation in offices.
Pairing is an inescapable all-day distraction, so I would expect it to trump other distractions. If I were to accept never ever getting into the Zone at work, I wouldn't be frustrated and less productive at being pushed out of it. But I'd rather flip burgers than spend my entire career talking instead of pondering.
This is really the best answer. Our office is open-plan as a rule, but there's plenty of "individually-sized" meeting rooms where you can work privately if you need to focus on something. It also serves as a good signal that you shouldn't be interrupted if you've taken one of those spots.
Obviously you need to have enough of these that there isn't competition for those rooms, but it can definitely work well.
Interesting, but I think that comfort speaks to a different issue. The office culture then is indirectly creating an environment that pressures you to act in a certain way and not acknowledging individual preference.
I agree that both is the way to go. You can find a study backing up either approach because they are important in different ways for different people.
I'm surprised no one has really brought up the introversion vs. extroversion angle. I just read Susan Cain's Quiet, and feel a wealth of clarity re: our general cultural stereotype that extroversion is better and therefore, so must be environments that are conducive to it (e.g., open floor plan. I don't have any illusions that corporations do that to save money, $ has never been a concern).
I work at a huge startup (300 people) that still has a very open floor plan and I basically work outside when it's not raining so that I can concentrate better. But the woman sitting next to me thrives in the activity and she can't work anywhere else.
I'm glad that the culture allows us to take freedom and ownership in how we channel our own productivity.
Speaking as a developer, I've worked for years both in open-plan spaces and in individual offices. My experience is that productivity is incomparably better in an individual office. There was no upside to open-plan; just constant interruption and frustration.
The point of the post you are replying to is that the "constant interruption and frustration" enables other developers to be more productive, raising the overall productivity of the team.
Also, you probably remember the times when you were interrupted and it was annoying strongly, but do you remember the times you interrupted someone else and saved valuable time?
It lowers the overall productivity, because the people who most need to be left alone are the people who do most of the work. Worse, it's a long-term detriment to each developer's individual capabilities, as it trains them not to use google or read documentation.
You can still interrupt someone without an open plan office, there's just a slightly higher bar that prevents most people from asking the knuckleheaded questions, and keeps constant non-conversational visual and auditory distractions to a minimum.
> do you remember the times you interrupted someone else and saved valuable time?
No, because I've never been so at a loss for things to do that I couldn't do something else productive while waiting for an email or IM question/answer response cycle to continue.
Interrupting is rude, full stop. Like other instances of rude behavior, it should not be undertaken lightly.
The data showed that younger workers liked these kinds of offices more than older
workers. The reason was instructive: they felt they could learn more from their
“officemates” in this kind of office. This makes sense, since in interviews a common
reason for wanting to join a company was the opportunity to work with “great” people.
Having great people around, whom you rarely see and even more rarely talk to, is not of
real value. Respondents talked about the much greater learning opportunities in a more
open environment. Older respondents, in contrast, found it harder to concentrate and
more disruptive. It also seemed the case that older respondents were simply comfortable
with how they had learned to do things over a number of years, and did well.
Hmm, that's one interpretation.
Here's a simpler interpretation.
Younger workers generally aren't going to know what they're doing and need to ask questions, so being able to ask questions is important to them. Older workers already know what they're doing and don't need to ask as many questions, so they don't really get anything out of it.
This BTW, squares exactly with my experience. All the benefit of open floor plans go to employees with the least expertise at the expense of the employees with the most expertise.
If you're the most talented, expert employee in an office, in general there's not going to be anyone in the office that can answer your questions, so an open office doesn't buy you anything.
If you're the most talented, expert employee in an office, then presumably you are being compensated proportionally. How much of that extra pay can you really earn by being the super-human solo coder, compared with how much can you earn by sharing your knowledge and raising the productivity of the entire team?
If you are not being compensated proportionately, that's a separate issue entirely...
Or, arguably worse, they are only interested in new, shiny things, whether they work or not. Let's run scalaz streams in production. It compiles, so it must not have any performance problems!
the question though is who needs does it make sense for the business to cater to?
also, from my experience, sometimes getting good answers to those early questions makes young workers exponential more productive going into the future
My initial thought is the best setup would really depend on the task.
For really complex tasks I would guess that you'd want a more closed environment. As a concrete example, if you're trying to make a theoretical breakthrough in cryptography, I'd guess you need an environment where you can seriously concentrate.
For maybe a less complex task, one where execution matters the most, like web development, a more open plan where its easier to coordinate might be better.
And obviously the quality of your co-workers matters a lot. High quality co-workers will have less questions and the value of training them up will be greater.
"If you're the most talented, expert employee in an office, in general there's not going to be anyone in the office that can answer your questions, so an open office doesn't buy you anything."
I've never worked at a place where I was the "most talented, expert employee" in an office, and as such there was nothing that I could learn from my co-workers. I consider myself to be a good developer, and believe that I benefit my coworkers with useful interactions. Similarly, I have co-workers who know things that I do not, and I can learn from them too.
I have been at my place for around 3 years, and it was pretty new when I started. I was in an office with one other girl, so when she was speaking, it was usually to me. Now there are 4 of us in the same office, team leads like to discuss stuff with the developers in the office(despite having their own larger offices with tables for that sort of thing). Plus we have more people using my database, so I am getting way more interruptions. I would give my productivity about a quarter of what it was.
Open plan may be better for team productivity, but I doubt it will be 300% more productive.
I personally prefer emails. That way you have something to refer to rather than having to remembered all of the tiny details. Plus we change our mind so often I often can't remember what the final choice was. And tehy don't interrupt what you are doing.
Wow. You think that time I spend coding features you asked for is not helping you?
Then at the end of the week, I am still giving an accounting of why a feature isn't finished on a schedule given by the same people who were interrupting the work I was doing to satisfy their stated priorities.
I'm amazed at how you totally ignore that this makes people miserable and contributes to bad management.
I don't think anyone is arguing that writing features isn't helping the company in general, and the individuals that asked for it - but that's not the only way developers can help other individuals within a company:
- Developers can ask other developers questions when they're stuck on a certain problem. In my experience, developers waste far more time when they're stuck on a problem then when they're interrupted.
- QA / PM / whoever is on your "team" can ask quick, simple questions, that are either too small for an e-mail, or would seriously slow them down if they had to write the e-mail, wait for a developer to check e-mail, write a response, etc. Again, in my experience, developers routinely underestimate how much inefficiency having QA / PM / whatever blocked while they wait for information from a developer generates.
E-mail has it's uses, and the fact that some questions are better suited to a quick face-to-face interruption doesn't mean that every question is, but there's definitely cases where it's not the right tool for the job.
> QA / PM / whoever is on your "team" can ask quick, simple questions, that are either too small for an e-mail, or would seriously slow them down if they had to write the e-mail, wait for a developer to check e-mail, write a response, etc. Again, in my experience, developers routinely underestimate how much inefficiency having QA / PM / whatever blocked while they wait for information from a developer generates.
It should slow them down. If they are blocked multiple times a day, it isn't the communication method that is the problem, it is the process. Interrupting developers multiple times a day is not the solution.
That link about the Cornell study is comically bad. Where are the raw data tables?
Doing a little background research it seems they were comparing open floor plans to cubicles. They didn't even consider the obvious alternatives to the panopticon, such as remote work or the tried-and-true office with a door.
That link about the Cornell study is comically bad. Where are the raw data tables?
It was a link to a summary of the actual study. With that said I went and skimmed the original study and that looked just as bad. Here's the original study.
Forget the fact that they didn't have the raw data. They don't clearly explain on what basis they reach their conclusions.
How are they measuring the 'success' of an open floor plan? For that matter, how can you even measure the 'success' of an open floor plan versus a close floor plan?
I don't think "office with a door" is an obvious alternative, because it's prohibitively expensive to build out a space with individual offices for every single employee.
It's like saying a study that compared air travel to high speed rail is comically bad because it didn't even consider teleportation. (Extreme hyperbole, but I think it conveys my point.)
Not that more expensive. Those cubicles cost nearly as much. I've built out spaces before, and offices are absolutely worth the expense, especially if you consider the improved work performance.
Its like saying light bulbs are comically bad because the sun is there for free. :)
I still have a hard time imagining that building individual offices, with the additional wiring, AC/heat, individual lighting etc. would be even close to a cubicle build out. Haven't built a space myself though and don't have hard data, so guess I'll take your word for it.
Cubicles are wicked expensive. Their price rose to almost that of building an office. Free market principle - charge what the market will support.
Now, you can re-use and re-configure cubicles, so that's often used as excuse to buy them. But moving them around is also expensive - rewiring, mechanical work, they're fragile to begin with.
So I call cubicles a dead loss to the bottom line. That's been my experience.
I'm going to agree. Until last year, I had worked exclusively in open office plans. Some were good, some were pretty horrible. Not all open office plans are created equal, and this is a critical distinction.
In my experience, open office plans scale poorly. The only successful ones I have worked in had less than 10 employees. Co-locating teams that don't need to collaborate (e.g. engineering & marketing) is typically a bad idea.
More to the point, I've now worked in a private office for a year. It has its perks, but I find myself wishing for a small open office plan again. The cons of isolation outweigh the pros of occasional distraction, IMO.
I think some of the best and most productive days I have had have been where I have been in the same cramped office as the rest of my team and we were all working on different chunks of the same problem - "Bob - are you using a list or a dictionary to pass the foobars in?"
That's great for a single team all working on one thing - but I do not see the open plan office as a series of nicely appointed open plan offices for 4-8 people with sound-proofing.
I have worked in open plan offices with hundreds of people in the same open-plan - hearing birthdays, laughter, horror, lunchtimes and socialising that have nothing to do with me personally or professionally.
Cornell may have found that it is useful to know what the rest if your physically co-located team is working on - yes - but not hundreds of others that I need to filter out too.
If serendipity is valuable to you as a company, throw a Wednesday afternoon mixer and expect groups to form and make something new to try out. But give them team rooms for that wednesday.
I am a big fan of "team rooms", and a big big fan of remote working and always on video. But living in the middle of hundreds of others just teaches us to ignore everyone.
I agree, team rooms is a suitable middle ground. You get the info and time-saving disrupting between members of the team, and get to ignore stuff from outside the team. If there's people running between all the rooms, a designated "contact person of the day" for each team is a good idea.
I think team rooms are a problem if, and only if, they are permanent. I've worked in cubicles, open floors and permanent team rooms and in the later all people did was to use the privacy to surf the web, talk about stupid stuff they would not dare to mention in a open floor. It made it very tricky to concentrate, but at least the problem was concentrate and a talk with the team leader / manager would usually quiet thing down for a while.
Ad-hoc team rooms sound like a very good idea though.
I agree, team rooms are really the best of both. I've worked in all sorts of environments.
When I started programming years ago I had to wear a tie to work, and shared an office with one other person. I've since worked in large open plans, at home, in cubes, and in what would be called team rooms with everyone from the intern to the boss sitting within earshot.
IHMO, team rooms really do work. They help facilitate communication while not bothering those working with undue noise. If the team is under a crunch then naturally non-work conversations are kept to a minimum because the whole team knows it is crunch time. When there is more free time then the team adjusts accordingly.
> But living in the middle of hundreds of others just teaches us to ignore everyone.
This is an important point. For many of us who have worked in startups, "open office plan" really just means "team room". I enjoyed working in open office plans in smaller companies since it basically just meant 5-10 engineers sitting in the same space.
Last year I worked for a mid-size company of about ~200 employees, most of whom were crammed into a gigantic factory like space with endless arrays of fluorescent lights lining the ceiling.
The experience was among the most distracting I can remember. This was in no small part due to having to overhear loud conversations between people in different departments, such as marketing and sales, which require much more verbal communication than engineering. if I can help it I will never work in a similar environment again.
That is probably the most important point - the reason startups go from a "team room" to massive open plan is because when it all began there were only 5 of them so open plan equaled sane. Add 20 more people and it's not sane anymore.
the reason startups do open plan offices is because no one is concentrating on managing the culture of the startup as it grows. Open plan is then I suspect both cause and symptom.
I don't really know, in any situation I've been in where people are watching me code anything I haven't been able to do it as well as when I'm alone. Even if I know they're not constantly looking.
Let me share some perspectives on the 'other side'.
1) I don't want people to be able to see me all the time. It's extremely nerve-racking and I feel like an animal in a zoo. And from my experience, people usually don't care whether I'm deep in some code or doing something less intense - they come over anyway. And people don't care whether their question is important enough to interrupt! As soon as someone taps my shoulder or calls my name, my concentration breaks completely and it takes me another half hour to get it back. Having offices makes people think harder and try to figure out the answer by themselves before going to someone else.
2) See above. The ratio of stupid questions that could have been resolved by Google or just another 2 minutes of thinking, to questions that ignited an interesting discussion is about 9 to 1.
3) How much work is going to get done by 'helping others'? 80-90% of a developer's work can be alone. Team productivity of course is important, but in development teams, this is really just the sum of individual developers' productivity.
Not only can the majority of a developers work can be done alone, but the majority of intra-team communication can be done over campfire/irc/im. You don't need to do meatspace communication to talk about code.
Unless there is an issue and things get heated, then it helps to sit people down in a room together. But this (should) happen rarely.
Number 2 is totally accurate. I can't tell you the number of stupid questions I have fielded by our Junior devs, just because I'm in their site line.
I have the unique experience of having been both in offices and an open floor plan (most recently) for the same company. I can unequivocally state that I was more productive with an office. Junior devs had to measure the opportunity cost of coming to my office before asking me a Googleable question, I'm fairly certain one of them doesn't even use Google anymore.
> I don't want people to be able to see me all the time. It's extremely nerve-[w]racking and I feel like an animal in a zoo.
I don't feel like this at all. In fact, that seems like an unhealthy reaction to me (so apologies for being judgmental). May i ask if you feel like this in other environments where there are other people around? Like, in a restaurant, or on public transport?
No, because in public places there is a degree of anonymity.
At work, people all know each other. Inevitably, you get nosy and annoying people who constantly check out what others are doing and peer into their screens.
But it's not just about personal productivity, it's also about enjoying your work.
Spending a day in the noise, getting distracted, and simply unable to get your head down and finish the one task you're assigned to gets highly annoying and draining. Which has negative effects on that person and the team as a whole; poor mood (and attitude by extension), bad work, and a higher inclination to simply pack up and leave.
I work in a ~20 people open floor plan; fridays feel the most productive, because it's the quietest. Some colleagues feel hugely relieved after spending a day working from home and, by their own words, getting some work done for the first time in forever.
tl;dr we're individual people, not team productivity numbers.
This raises an interesting point about design. I've worked for small (<8 person) startups where the open floor plan worked well. I now work for a large company (~50 people on my floor). We still use what I would call an "open floor plan" at the large company, but it has been carefully designed such that I only have 6 or so people in my immediate vicinity. Despite both being "open", they very different in layout from the each other.
At the large company, I can't generally here what's being discussed by folks in the next group over, except maybe as low background noise. I don't generally get distracted and I am easily able to grab my teammates' attention when I need it.
In the Cornell study cited, it specifically discusses that open plans should be fit for purpose. "There's no silver bullet."
I would love to be able to sit around my coworkers while I answer emails, catch up on the projects going on around me, bounce ideas off of people, etc. and then have a designated, quieter space to do "heads-down" work.
The trouble with this is that if you have a quiet space, then they have a quiet space, which means when you're sitting in the chatty space, most of your colleagues will be in quiet spaces, so you don't get the benefit the chatty space might offer.
This is pure hell for people who actually do work, and often repeated by managers who don't "get it." Silly questions are not the genesis of good ideas, they're a denial of service attack on good work.
Agreed. Also, trying not to listen to others conversations about the latest TV shows, etc. whilst trying to code negatively affects productivity and can generate some hostility towards the chattier folks in the office. Good, closed-ear headphones are a must.
know thyself. If proximity distractions are too much, go somewhere else where you can have privacy if you need heightened focus for some block of time - a couch, stay at home, the library, a conf room, etc.
Problem is, many of the places which have the worst types of open plan also seem to be the most allergic to things like working from home and quiet rooms. Also, many people who work in them don't have the luxury of going to a couch or quiet room.
Not mine. Everyone right up to Senior Director are embedded with the teams. The only exceptions that get an office and door is HR and Legal. When the CTO comes to our office, he also sits with us.
Ditto. Except our HR people don't have their own offices. We don't have lawyers in-house. If i draw a line from the window through my desk to the far wall, it passes through a developer on another team, me, the product guy for another team, the CTO, a co-founder/head of sales, and two salespeople.
I routinely gain great value from speaking to the developer and product guy on either side of me, both of whom are immensely expert. The salespeople are fortunately far enough away and quiet enough that they're not a distraction.
Stratification. Putting "regulars" into an open floor plan and leaving managers with offices is this concept on steroids (yes, I've actually seen that).
I believe that there is an unplanned unorchestrated ongoing attempt throughout the industry to prevent programmers from being seen as professionals. Reverse dress codes (you'll get odd looks and questions if you aren't dressed casually, but instead throw on a suit or even just a tie), cubicles, and open office space are all ways that this is done.
I had to wear a tie my first few years of working. It sucked. I see dressing how I want as a sign of power, but I do agree with your overall point. Because I can dress how I want, doesn't mean I should look like a slob or unprofessional. I still wear nice clothes to work, just not corporate drone clothes anymore.
Dressing however you like is a great perk. However in my experience, many companies who say that they let their engineers dress however they like are actually requiring (although not explicitly) that their engineers dress down. If you are the sort of person who enjoys wearing a tie, you may find that doing so as an engineer is untenable at many tech companies.
Most people don't bother trying to dress that way so they never encounter the pushback and therefore never even realize that there is an unspoken rule in place. I recommend that everybody try to go to work on a monday with at least a white button up shirt with long sleeves and a tie. I think many of you who work places "without" dress codes will find the experience to be illuminating.
When I tried it, somebody from HR had a nice "chat" with me, explaining that the corporate culture was for engineers to dress casually.
I haven't worn a tie to my current job, but routinely wear button up shirts and sport coats. The other engineers might joke if I have a job interview, but no one will tell you to not dress that way.
I'm not sure how I would respond if someone said I was not allowed to dress nice. It just seems like a completely foreign concept.
It is more than possible that you work at a company that actually has an no dress code / a permissive dress code. I think those workplaces exist and I appreciate and value the concept. What concerns me is reverse dress codes that sometimes hide in plain sight, disguised as "no dress codes".
Its the same chat that black people who didn't speak in dialect used to get, or who dared to learn to read, or get uppity in general. Its a pretty disturbing symptom of a sick workplace.
Seconded; it's a cost and politics issue to have open floor plans, and mostly to "put those uppity programmers in their place." Wouldn't want them asking for what they're worth, now would we? And hey, by having them constantly distracted and not able to concentrate, they won't be as productive and therefore not feel justified in asking for what they're worth! I mean, if open floor plans and cubicles were really that conducive to thinking work, you'd see it in many more places, such as research, doctors offices, law firms, etc, etc.
I don't think it's a "conspiracy theory" in the traditional sense (although I do admit that my post was slanted a bit that way). I'm fairly certain it is as Crito said, "unplanned [and] unorchestrated". And there's no need for conspiracy: simple human nature in the aspects of politics and pettiness can easily explain it - it doesn't matter if you can prove what is more productive or cost effective, management ("owners" or their representatives) will continually push for more leverage and control over their workers, until they experience pushback, profits be damned.
A company wouldn't. I posit that individual middle managers are the problem: whilst they do want the people working for them to be productive, they often subconsciously act to make sure they have the supposed "status" and that this comes (unknowingly, to them) at a cost.
Not where I'm at, nor at my last job. At Last Employer it was true in the old building, where the floor plan was laid out in the late 90s.
When we moved to our new building, interior spaces were meeting rooms. Next layer out were manager cubes. Final layer out were the worker cubes, everyone faced the big floor-ceiling windows.
This actually had a drawback. There were cunning metal shades over the windows to keep out the sun. These worked great to block the sun. They also collected snow. Which, thanks to wind, and sun, melted into in a slant, like a roof. Our first Thaw in that building and the ice/snow ...
BONNNGGGGG through the building frame as the snow slides off and the shade vibrates like a giant tuning fork.
A few minutes later BONNNGGGGG as the next in line sheds snow.
Great, except your performance evaluation is done individually. Try to explain to your manager that the QA asks you dumb questions incessantly, interrupting any attempt to remain or even begin to be "in the zone".
Non-programmers generally never know how to read whether it is a good time to interrupt or not, unless it's obvious you're just reading an article or something.
I complained about having too many meeting and other distractions to get any coding done recently. Result was a meeting about it (no joke). We discussed it asked people not to interrupt, but two weeks later is is back to the same.
> unless it's obvious you're just reading an article or something.
Generally agree with you, although just because I'm reading an article doesn't mean it's a good time to ask me a question. Right now, my brain is working on a weird problem while my tests run and I browse HN. I look like I'm goofing off, but I still wouldn't appreciate a context switch to another problem.
The polite question if you must interrupt a programmer is “Would now be a good time for a context switch?”
In 2011, the organizational psychologist Matthew Davis reviewed more than a hundred studies about office environments. He found that, though open offices often fostered a symbolic sense of organizational mission, making employees feel like part of a more laid-back, innovative enterprise, they were damaging to the workers’ attention spans, productivity, creative thinking, and satisfaction. Compared with standard offices, employees experienced more uncontrolled interactions, higher levels of stress, and lower levels of concentration and motivation. When David Craig surveyed some thirty-eight thousand workers, he found that interruptions by colleagues were detrimental to productivity, and that the more senior the employee, the worse she fared.
Edited to add: the study by Matthew Davis referenced above is behind a paywall; if anyone can actually access it, I'd be curious to know for sure if this summary is accurate/correct.
These studies are all great, but fall under what type of students and/or test subjects that already have been filtered in other ways before being tested. We all are different. Along your request to clarify, I would like to request any studies on a 7-9 man team.
I am one of those people who get distracted easily and am a new programmer. Working on a Scrum team of less than 10, I found this has grown into being very productive for the team and my growth, as I pick up the conversations, I am actually learning things and I throw my music on if the chatter is unproductive. I think the amount of dev's in the pit really can max out and that is what the writer of this article has probably experienced.
I spent a while trying to get it, went through the online library systems of two very different universities, which should theoretically cover almost every topic, and a lab. However, it seems that it's listed as an ebook in at least one of the systems, and it won't let me grab any specific article. I could request a physical or scanned copy I guess, but that would take longer than is probably worthwhile.
> he found that interruptions by colleagues were detrimental to productivity, and that the more senior the employee, the worse she fared.
My personal take. Learning a craft is a lifelong endeavor. Experience builds. The path is organic & fractal-like.
If someone is senior, they have a context of experience that a more junior person does not have. Their brains are literally wired differently.
It's less satisfying to be around ignorant (I don't mean judgement, just lack of context) people. Especially ignorant people who affect how you do your job.
Being a senior person means there is an aspect of leadership involved. You mentor & lead the more junior people in your craft. However, masters don't spend most of their time mentoring. They spend most of their time growing their own personal craft. They try to instill this process of continuous improvement onto their students.
One of the most fascinating observations by Cornell is how self-interested employees are biased towards maximum individual productivity to the detriment of team productivity. I wonder if the 100 other studies controlled for that. Cornell is a pretty reputable institution. You know what they say.. 1 great study is worth 100 good ones.
> but what the Cornell study found is that in open plan it's actually easier to "read" a person and see if it's an ok time to ask a question, and to quickly reply or say ask me later, and so forth, to efficiently manage those disruptions.
The Cornell study does not account for the fact that most people suck at "reading" a person. Yes, it's easier to do in an open space. Most people who don't work also ignore the result of that reading.
> They found it also gives us more courage to ask potentially "silly" questions.
Which can also non-intrusively be asked by e-mail, the communication medium that has carried more silly questions than air has done in generations.
> They noted that developer reactions to office plans are often biased towards maximizing personal productivity in order to maximize (short-term) personal benefit, whereas the company benefits from a balance of personal and team productivity.
This says nothing about the underlying mechanism. Yes, I am biased towards maximizing personal productivity, which means that I will gladly and reliably avoid obnoxious co-workers. Closed spaces help me do that.
It's not really the questions that disrupt me. It's the constant amount of movement. People getting up and sitting down. People walking across you or moving towards you, and also having to acknowledge them. It's constantly very visually distracting. This doesn't help the team or me.
Maybe there is a good middle ground? Shared cubes of 2-4 people or a single room for a single team?
Unless working is a constant stream of asking silly questions then no this is a stupid idea. You can irc someone, look through their office window to see if they are busy or not.
> Those are "disruptions", yes
But that is a huge deal. I would say disruptions many time outweigh the benefits of open spaces.
> the company benefits from a balance of personal and team productivity.
Without individual productivity there can be no company success. If someone is constantly interrupting others then they probably need more focused training or a class.
Imagine you are surgeon and while you perform surgery you doctor buddy from across the hall comes in and asks you some question about how to hold a scalpel or something like that.
I'm much more likely to ask questions on IM than face to face. The latter not only interrupts the person I am asking the question, but also interrupts my own flow.
If this were true, then why don't managers and Chief Officer types have their workspaces in open plans? Just think of the productivity increases that could be gained!
No, open plans are almost always for two reasons, ignoring any harm or benefit:
1) To reduce costs.
2) Politics/motivation - you have to work hard or be important to get an office.
And I'll see your one study and raise you a "Peopleware" by DeMarco and Lister; IMHO it should be required reading for everyone (especially those who decide on space layouts for knowledge workers).
This varies by the individual as well, however. There are some guys at work here who will ask the tech lead how to merge a source code change into the master branch every single time - one guy has done it three times in a row about a week apart each time and needed personal assistance every time. There are other people who just read the internal wiki and do it without needing hand holding every time. If you are one of the latter, you are penalized more and helped less for being in an open office. You are also penalized by being in a work situation that encourages the former bad behavior.
What if I told you I've experienced both and found your observations to be untrue. Is it possible that it depends on the context, nature of role and the team ?
> 1. Open plan makes it easier to ask questions. Those are "disruptions", yes, but what the Cornell study found is that in open plan it's actually easier to "read" a person and see if it's an OK time to ask a question, and to quickly reply or say ask me later, and so forth, to efficiently manage those disruptions.
So just for the off-chance that someone could ask me a question, I have force myself to wear headphones every day just to get any work done? What the fuck?
Maybe most people are not like me, and are not distracted by the moving, talking and noise making of other people around them -- but I am. I need as much silence as I can get.
What is absurd about this is that some companies make special "quiet zones" for people to go to and think, which means they implicitly admit that the actual work environment is not conductive to thinking.
This is interesting, actually. Why is being interrupted by IM not as bad? I agree with you, it doesn't seem to be as much of a problem. But why? Is it just that the interaction isn't quite real-time -- I can ignore you for a few minutes if I'm in the middle of something?
Maybe someone should try the combination of private offices and a local chat server, to see if that's the best of both worlds, concentration and collaboration.
In our company we combined the two, the developers sit in a large open floor plan which is a quiet zone, and to discuss something you go into a meeting room. The quiet zone is enforced through social pressure, a bit like a library reading room, except less perfectly quiet (people still periodically interrupt the silence). The result is a lack of team dynamics because people don't talk enough, AND a lack of personal productivity, because there are still enough distractions that you can't work for long uninterrupted stretches.
I've become convinced the best solution is the one from peopleware: 2 to 4 people offices, with a door.
People are generally a lot less likely to ask questions over IM. The Cornell study found a couple of things of note here:
1. Being able to "read" someone visually helps in determining whether it's an ok time to interrupt. "Unexpectedly.. more visual contact actually contributes to fewer unwanted interactions, not more, by changing not so much the frequency as the timing of conversations."
2. More frequent social interaction builds more trust. People felt more comfortable asking for help.
3. A lot of information is acquired through something called "tacit learning". That's info that's never written down that you pick up by observing others. You may not even know to ask about it or have an opportunity. Open plan greatly helps the spread of this.
4. Most damningly, it notes that self-interested developers are biased towards individual productivity more than team productivity. This often leads them to undervalue the benefits of "disruptions".
It is if it's at the detriment of overall team productivity.
Typically the more senior you get, the more important it is for you to allocate time to help others. A place I used to work at codified this. You had to have X percent helping-others time and X grew as you rose in the ranks. That's precisely because of the important of team vs. individual productivity.
> 1. Being able to "read" someone visually helps in determining whether it's an ok time to interrupt. "Unexpectedly.. more visual contact actually contributes to fewer unwanted interactions, not more, by changing not so much the frequency as the timing of conversations."
I don't mind being interrupted by someone who wants to ask me a question. The explicit interruptions are not what makes the open office a painful experience -- it's the background noise that comes with it.
This is why many people work with headphones on. You shouldn't be listening to music just because you need to concentrate on your work.
> 2. More frequent social interaction builds more trust. People felt more comfortable asking for help.
Surely you could think of better ways to build trust between team members other than sitting everyone in an open space?
> 3. A lot of information is acquired through something called "tacit learning". That's info that's never written down that you pick up by observing others. You may not even know to ask about it or have an opportunity. Open plan greatly helps the spread of this.
I don't want to be observed while working. I'm not a lab rat.
The point is, people may not know that you don't mind. Seeing someone's face makes it easier to "read" someone and manage the timing of their interrupt. Not the case with IMs, doors and cubes. This is one reason why the bar for "frequent communication" plummets in closed plan offices.
As for not wanting to be observed.. of course you don't. It's not in your self interest. But it is in the interest of team productivity to promote tacit learning. Let other people more readily learn how to do what you do, your tips & tricks, the little things not written down and formally taught.
Nailed it. A lot of "collaboration" is not derived from isolated silos of knowledge but when its "shared". People who can't operate in an open environment lack the focus required for such an activity in the first place. I'd rather blame a lack of "integration" into an environment like this on HR than the business owner / layout designer. There is a reason why start-up thought process is injection molded into an office "feel". So ... if you lack the ability to concentrate ... you lack the ability to function for a successful company.
So you think the needs of the [one] outweight the needs the of the [many]? That's the foundation of your sympathy card, right? Look, accomidations are made in any environment - but doesn't mean it's going to stop the idea that open-floor space is "bad" on the whole. Mihaly is in the minority, btw. The top things that motivate employees are not individualistic, silo achievement but rather derives from group/team building and worth of cultural acceptance into an environment. He's a nut - I took one of his lectures in my graduate program :) He's more interested in happiness than achievement in the end. I don't hire people to be "happy". I hire them to achieve things and become part of my culture.
So your saying that Steve McConnell and many other experienced developers are wrong.
Back in the 80's I was the core programmer on a map-reduce system that formed a part of one of the only 3 products British telecom sold internationally my CTO was one of Vint Cerfs reports.
I have no problem concentrating / focusing given there are no constant conversations / noise, people moving around, music, sales guy on the phone 8 hours a day, etc.
It's absurd to expect human beings, especially software engineers--who tend to be quieter, more introverted, and loner-types--to be herded like cattle into a crowded, noisy open-plan office and expect them to have the razor-sharp focus needed for high quality software development.
If you only hire people who thrive in noisy / distracting environments, I won't be surprised if you end up hiring the wrong people for actually getting the job done-because often times, the people who take on the most work, resolve the most difficult problems, and carry the most weight are those people who can't stand working in a place like that.
Why not use asynchronous communication? The askee can answer at their convenience instead of having someone with something "important" (a marketing person with an idea) interrupting something "unimportant" (the programmer working).
I worked in environments that optimize the team, rather than the individual, for years. It is a breath of fresh air to work from home & optimize my environment for me. I'm happier, healthier, more productive, can get my business taken care of, etc. It's pretty much a total win.
I also have some "eccentric" behavior. I happen to pace & otherwise move when I think. I cannot do that with other people around.
The architecture of the software I'm working on is more coherent. I'm able to collaborate with teammates. Things are progressing quite well. I've never been happier.
Sorry, I don't have a study. Just my anecdotal experience.
Team productivity? What is team productivity other than the aggregate of individual productiveness? You could argue that open floor plans help bring the weakest programmers up a bit, but at the cost of bringing down your strong programmers down. Presumably your stronger programmers are more productive, so even in this argument it brings "team productivity" down.
I have worked on a code base for the last 6 months in which I am the sole committer. A lot of my coworkers are the same. We have brief sprints where we are in each others' faces, the majority of the time we only need concrete pieces of high-context information from each other that have nothing to do with serendipity.
That Cornel study is pretty poor. Better studies have been done over longer periods of time and don't just rely on interviews that they decide to interpret the way they want.
Having worked in a company where engineers had individual offices, and now work in an open floor plan, I can assure you that sick days have gone up, the noise level is many times what it was and overall productivity is noticeably lower - guess what - if you lower everyone's productivity, then the team productivity goes down. Big surprise that NONE of the managers are in the open floor plan.
Open floor plans are simply a way for managers to feel better about themselves by hurting other people.
I used to work in a company which had "a culture that enforces a library-like environment on an open floor plan" as indicated (it wasn't a written rule, just the way the culture worked). I found it extremely stressful and depressing, so wasn't working well, and ended up quitting as soon as I could.
I'm now in an open-floor office in which people talk a lot and interrupt me when it's necessary, and I'm a lot happier and more productive.
"Now maybe you're different than me" is probably the most important phrase in there.
I think the issues arise partially on how "open" the open floor plan is. If it's just one big room, poorly designed, it seems like a disaster for productivity. If it's a series of pods or areas, with some effort made to provide space between them, and a healthy amount of huddle rooms or conference areas, I think it can work great.
The trick is to provide enough separation and space that people don't feel claustrophobic, and manage a culture that encourages people to take group conversations into a room if they're going to be loud/passionate.
My work has a relatively unique (I think) set up that in my opinion pulls the best of both worlds. Basically, it's a big semi circle of 6-8 half cubes around the manager. So if you are looking straight forward at your computer, there aren't too many distractions. But if you want to talk to a teammate/manager, you just need to pivot your chair 180 degrees. It's a good balance of collaboration/help and concentration.
How about having a developer area that is treated like a library? Silence enforced at all times, you have to whisper if you strike an impromptu conversation. And if that bubbles to a brainstorm, get up and grab a conference room to talk about it.
The trouble I have with these arguments by programmers against open floor plans is I directly correlate the dramatic increase in popularity to the rise of programmer rather than non programmer led startups. If in fact it was counter productive wouldn't the (presumably smart) developer/leaders of these startups switch as soon as they got their first Series A check? Or is there a sense they can't because a) they feel stuck due to the cost of rent or b) some herd mentality that means they can't attack talent unless they have the open floor plan?
As with most things, the truth is somewhere in the middle of two extremes. When you are developing a new product there are big changes being made all of the time, and you need good communication in the dev team so that everyone can stay abreast of what's happening - there is a good chance that the changes I am making will have a direct impact on your work. The size of the team also tends to be small, making the "openspace" much closer to a "team office" in a larger company.
This is pretty much the optimal situation for an openspace floor layout. Now compare that with the situation in a more mature company. The first thing any sane lead engineer wants to do once v1.0 is out the door and making money, is to pay down on the inherited technical debt. Organise code so that it is modularised, so that changes in one area don't have a major impact on other areas. As money is being made, the team starts to expand as well, so simultaneously you have less need for close interaction between team members (due to improved software structure) and greater opportunity to be distracted by irrelevant discussions, as the scope of the product has now grown so much that most of the engineers will never master all of it, but instead become experts in one particular aspect.
Let me give you a real-world example from my current job. At the moment, I'm deep in the source code of an OpenGL driver, identifying performance problems. The thing is, we already have a product, and it works well, but it uses a 2D graphics APIs, and the designers want iOS7-style blurring. So I've re-implemented the graphics APIs using OpenGL. This is completely independant work. No-one else knows OpenGL, and none of them even see the API, as it's hidden behind a facade that they already know. I had pretty much zero interaction with the team whilst implementing the OpenGL backend, as all I had to do was implement an existing API. I now still have zero interaction, because if the team don't know much about using OpenGL, they know even less about how it's implemented under the hood. I don't need to know about their problems with what happens when the user presses "back", and they don't need to know about my problems with the vsync callback.
Yet, we are still in an openspace. The designer with the ridiculously loud laugh is still distracting me every thirty minutes or so. The two guys having a discussion about the latest ministry shake up in the government, yup, they're doing that about 2m from my ears and not making it any easier for me to concentrate. They programmer talking about the first run sequence with a project manager one desk over? Absolutely of no interest to me.
OK, so much for why openspaces objectively suck once your past the project startup phase. Why do ex-developers / current-CEOs still stay with openspaces? You would have to ask them, but maybe it's because they remember how wonderfully productive it was at the start of the adventure and don't realise that the situation has changed. Or maybe their much more interested in raking in the cash,and are now just waiting to flip the company - future productivity is of no interest. Keeping the costs down to make the company more attractive to buyers though, that might be very interesting to them. Anyway, the fact that they persist with openspaces is not necessarily a ringing endorsement for openspaces.
“Another trait, it took me a while to notice. I noticed the following facts about people who work with the door open or the door closed. I notice that if you have the door to your office closed, you get more work done today and tomorrow, and you are more productive than most. But 10 years later somehow you don't know quite know what problems are worth working on; all the hard work you do is sort of tangential in importance. He who works with the door open gets all kinds of interruptions, but he also occasionally gets clues as to what the world is and what might be important. Now I cannot prove the cause and effect sequence because you might say, ``The closed door is symbolic of a closed mind.'' I don't know. But I can say there is a pretty good correlation between those who work with the doors open and those who ultimately do important things, although people who work with doors closed often work harder. Somehow they seem to work on slightly the wrong thing - not much, but enough that they miss fame.”
Notice that Hamming takes it for granted that everyone has an office; the only question is "office with closed door, or office with open door?".
This is a very different question from "offices or open plan?".
(My own preference is one I've seen others express here: rooms for groups of roughly 4-10 people, private rooms for intense concentration and private meetings, and some communal space.)
That was the rule in the Physics department I spent a little time in. 'Tea' involved about 40 researchers in a large room on couches and armchairs arranged (and rearranged) in small groups. You were expected to share problems, findings, ideas, and listen. Room had no blackboards but plenty of paper napkins.
Broke up around 4pm most days but sometimes went on much longer.
Leaders used to hear a problem and say things like "talk to Robin. He's been working on conditionally convergent series", so you did, and it helped.
I like open floor plans. I find I get more done in my open floor plan office then my closed off private office at my house. I hate how all these critiques are so absolute in that "Open Floor Plans are Bad". Open floor plans work, and they work well. Like Eric Schmidt if there was some secret benefit to having offices for everyone that could make workers so much more productive don't you think companies would jump at the productivity boost ?
There are totally trends in management, however the "shift" to open floor plans is not the new trend its a return to the trend we had _before_ we went on the quiet isolation kick in the late 60's. I think now that we have actual data point of isolation vs open businesses are seeing tangible benefits from the open floor plan. There is still experimentation going on with how to strike a balance, but to say open floor plans are all bad ignores the fact that in practice they work better then most everything else we have tried.
The real thing people are finally paying attention to is that not all human workers are the same. Some people thrive in an open noisy collaborative environment, while some can't operate at all in that environment. It is the real task of management to manage the work environment of all your employees.
1. For core teams, ditch the open floor plan and instead put teams into small (4-5 person max, with smaller options) private rooms that line the perimeter
2. Project rooms are not permanent. A team should expect to move around perhaps once every 3-4 months
3. Team leaders / managers would of course work in the same room as their team
4. In the center of the perimeter of team rooms could be a hacker workspace, shared areas, supplies, snacks, etc. With breakout meeting rooms around the space as well
5. executive leadership would work sitting with other specific staff (like finance, HR, office managers, etc) in an open floor plan-like area; most importantly, execs wouldn't have private offices because ideally they should be moving around meeting with the teams, jumping into conference rooms, jetting out of the office, etc.
6. this open area should be relatively quiet
7. people working in this open area should have ample access to private spaces for breakout meetings, private phone calls, reflection, relaxation, etc
Obviously these rules won't apply perfectly to every company and work type, but I'm just brainstorming
The problem is, and always will be, that the 9.2% cost difference is very visible whereas to non-technical people whereas the productivity differences aren't. And unfortunately more often than not it's the non-technical people making the decisions on office space...
Ye gods, another open floor plan rant. Never see enough of these any more.
Instead of point-by-point, I'm just going to offer one critique.
"...Programming is a very brain-intensive task..."
Sure thing, buddy. But guess what? You're not a machine for cranking out little bits and bytes. Instead, you're part of a team that's trying to provide value to a user. That means that most of your job, whether you like this or not, is human in nature. The computer part should just be a "gimme".
The physical space around a team should represent the mental space of the team. One hundred guys in a big cafeteria? Not so much. 40 guys in clusters of 3-6 with rolling whiteboards and allowances for breakout discussions? Much different.
There are things I would love in software development. I would love to sit on the beach fanning myself coding while money is deposited in my account. (Actually, I've done that.) I would love to work alone in my office in the wee hours of the morning in an awesome state of flow (did that many times too.)
But at some point you have to separate "things I want to do" from "things that optimize the value I provide". They aren't the same thing.
I'm all for private offices if it works for you and optimizes value. Same goes for distributed teams. Right now nobody has all the answers. On average, though, it looks like these things are counter-productive for projects that require creative new ways of thinking of things. I wish it weren't so, but it is.
I've noticed lots of programmers make unsupported assertions that a quiet workplace is better than a noisy one. But why? Have there been any studies demonstrating higher productivity if programmers have their own office? I don't think so.
We should be suspicious of such claims. Think of von Neumann:
At Princeton he received complaints for regularly playing extremely loud German marching music on his gramophone, which distracted those in neighbouring offices, including Einstein, from their work. Von Neumann did some of his best work blazingly fast in noisy, chaotic environments, and once admonished his wife for preparing a quiet study for him to work in. He never used it, preferring the couple's living room with its TV playing loudly.
It seems to me to be a personal preference only. Some people like noisy and some people don't, there's not necessarily any one correct answer. But folk like Joel and others (usually American where private offices are much more common) constantly push absolute silence and the myth of never being interrupted or distracted, seemingly without much to back it up.
I really prefer an active office close to others. If someone taps me on the shoulder I have no problem continuing my train of thought.
My Dad, when he was young, worked at the Institute for Advanced Study while von Neumann and Einstein were there. AFAIR, my Dad said that von Neumann tended to work late at night (I am visiting him this weekend and I'll ask about this).
Say it is purely personal preference: 50% of people can work well in open offices, and 50% of people cannot. Even if that were the case (which I highly doubt), that would still be a solid argument for closed offices. Why? Because while people who can work well in open offices can easily adjust their closed office to suit their temperament (e.g. by blaring loud German marching music), people who cannot work well in open offices have no recourse. Headphones are the recommended strategy, but in my experience they still lead to a decrease in productivity and are generally uncomfortable when worn for an entire day. Further, they do not block out the visual distractions of people walking back and forth, etc. They also do nothing for the feeling of lack of privacy, which for me personally is one of the most egregious aspects of an open plan office.
I think that among programmers especially, the proportion of people who cannot work at peak productivity in an open plan office is much higher than 50%, but even if it were only 30% that would still be a strong argument for closed offices.
Read Steve McConnell in "rapid development taming wild software schedules" he quotes an IBM study that found a 15% increase in productivity with private offices and that was for all levels of programmers even the less good ones.
At my first job, 6 of us (all programmers) sat around a large conference table. If I had a question about the code, I peaked over my laptop's screen, someone else noticed and asked "What's up?" It was great for that quick collaboration, but it also exposed us to every annoyance possible. There was a guy who burped a lot and liked to sing show tunes. The guy next to me bought me earbud-style headphones because the cheap ones I was using leaked out a lot of sound. We also needed an always-be-working atmosphere to prevent a conversation unrelated to work from taking more than 5 minutes.
I've had my own office for the last 3 years and enjoy the privacy, but occasionally miss the instant answers and social aspects of that open plan.
Has anyone studied open plan offices and choice of programming language?
Does an environment with a high chance of interruption lead to languages where you have to write a lot to do a small task, because you can write simple code between interruptions, and over time get enough code to do the task - and if you get interrupted well you only lose one minute's thinking.
Contrast with a powerful language where you need half an hour of thinking to build an intricate machine in your head, then you write it down in a little code, and need to hold its workings in mind while you test it. With no long spans of concentration you won't go slower or write half an intricate mechanism, you will write nothing.
Or to put it another way, is the problem of working in an open plan office: you aren't choosing the right tools and work pattern for your environment?
Or to put it another way: are enterprise languages 'blub' languages because they come from big offices and academic languages 'powerful and terse' because they come from people with time and quiet for deep thought.
Or another way: could we redesign our languages, tools and their UI to make us as effective, and feel as good, in open plan offices, like f.lux changes a screen for night use instead of complaining that it's not daytime.
Interesting question. Not sure we'll ever be able to determine an answer - I think there's too many variables at play, but it probably makes a difference for some people. I'm thinking here of something like "PHP is easier to work with in situations where there's more regular interruptions, because you can write smaller/simpler chunked code, whereas C# is easier to work with in situations with private/isolated offices with regularly scheduled collaboration". That's sort of where you're going, right? (Swap php/c# with whatever your theory is - those were random choices on my part).
Contrast with a powerful language where you need half an hour of thinking to build an intricate machine in your head, then you write it down in a little code, and need to hold its workings in mind while you test it.
That's not a powerful language, it's a bad language.
A powerful language isn't one that's overly concise to the point of crypticness, it's one that allows you to express yourself naturally. Meaning, there is a clean and strong conceptual mapping between the code and the problem domain. Meaning, it requires less mental effort to use.
> Not every programmer in the world wants to work in a private office. In fact quite a few would tell you unequivocally that they prefer the camaradarie and easy information sharing of an open space.
> Don't fall for it. They also want M&Ms for breakfast and a pony. Open space is fun but not productive.
It's not so much open plan vs offices. It's quiet vs. not-quiet.
One of the most effective office setups I have seen had two kinds of work areas:
1) Reconfigurable "team rooms" where most of the team can work together. These have a door that is kept closed to reduce conversation noise leaking into other areas, and a glass wall so you can see who is in the team room. The other two interior walls can be moved to adjust the size of the team room.
2) On a different floor, there is an open quiet area equipped with large monitors for individual coding, writing, and CAD work.
There are other workspaces, such as lab rooms for fabricating things. Their larger locations have large shops with all kinds of fabrication equipment.
Everything is hot-desked. Many people spend part of the week working at home. The company with this workspace is a major design firm, and I'd wager they put a lot of thought and objective measurement into the design of their workspaces.
In my experience, regular programming is doable in open floor plans. You can write stupid crud sites and winforms apps just fine. As long you have headphones on.
But when you have a system crash and need to dive through 100mb of log files to try and figure out what went wrong. Good luck doing that in a standard open office! You just have to schedule a few hours after everyone else has gone home so you can have some peace and quiet to do your log diving.
I honestly think the traits that make you able to hack the Linux kernel, optimize the linear algebra required for the internals of a 3d engine, write Haskell etc are incompatible with preferring open floor plans.
Edit: Btw, if you are able to do these "high level advanced" programming tasks while in a noisy open floor plan I would be very amazed. For me it's like trying to play chess against a highly rated opponent and that is impossible to do competently if you have to endure constant interruptions.
I have the exact same feelings, in an open office and are a developer who does braindead work then it's great as you can chat while working on repetitive tasks.
Anything that requires thinking, such as fixing a release-blocker bug that is very obvious once you get in the zone is pretty much lost.
This really says it all. If you're doing something which involves a great deal of concentration or careful thought (eg, software design) or learning something new, then interruptions are death.
Simpler work where you know exactly what you're doing, where there are no difficult choices to be made, can probably be accomplished in any environment. Sometimes that's the vast majority of the work you're doing, sometimes it's not. It really depends on the type of application.
I'd like to note that his self-assessment of likely open-floor-plan productivity appears to be an authentic QWANTZ moment. Personally, this is the first time I have seen one in the wild.
Most organizations are so inept at choosing leaders (they can't tell who's good at the job and who's not) that their only recourse is to set up pointless contests that grind people down, and then determine the last person remaining to be the leader. (Those who left weren't dedicated; those who broke were "weak".)
Open-plan offices (and, especially, open-back visibility) are just another shitty mechanism used to wear people down and make the attrition/sorting process happen faster.
258 comments
[ 2.8 ms ] story [ 317 ms ] threadIf your job can be done in a closed office without interacting with anyone, why do you need to be in an office at all?
Anyway, as my commute is walk+tram+bus+walk, I do offset this time by reading books and replying to e-mails while in transit. I'd be really, really angry if I had to spend this time driving a car.
I'd gladly work remotely, but not from home. No way. If there are no small-business-incubator businesses nearby, I'll be working public library hours, thank you very much.
Only when A & B are both coming out of the bathroom can interaction occur. Otherwise, A is desperate and dashing in, B is wishing she'd not had that curry last night, or both A & B are desperate and not stopping for anyone ;)
I'd be interested to know how much they saved on plumbing costs. That seems to me like an architectural decision driven by financial concerns and sold as a benefit. Not that it isn't a benefit, many of the most interesting designs are a consequence of some practical constraint.
Maybe, but that particular mechanism was implemented. It actually received some negative feedback from a pregnant woman who felt she was forced to walk an undue amount to the bathroom.
The point of the parent was that the Pixar offices are designed around encouraging unplanned team member interaction. Their leadership believe this is crucial to encouraging creativity.
For what it's worth: assuming white-collar employees, the multiplier is typically 50% to 100% depending on your location and how generous you are with perks, rather than 20%. If you only have $120k available in the budget to hire someone, don't offer a salary higher than $80k, or you're going to have a very unfun meeting with your accountant saying "OK, would you prefer I took the money from somewhere else in the business, or do you want to go to prison for not paying our portion of the payroll taxes?"
There exist many folks who have more experience with San Francisco hiring than I have, but the word on the street for e.g. funded startups trying to pay market salaries is that you should be budgeting $15k~$20k a month to increase your team size by one.
Our own multiplier (Israel) is usually 30% extra over the stated salary, although the salary here is usually stated as a monthly, not yearly, number.
When the cost of the a single piece of equipment for a single experiment cost in excess of $5 million you can see why - in the end we did not go down that route. A pity as the ML neural networks aspects of machine vision would have looked very cool on my CV
The biweekly paycheck for someone with a $100k salary would thus be approximately $4,000 gross. It would list a deduction for payroll taxes, a deduction for anticipated federal and state income tax, a deduction for the employee's portion of health insurance, and perhaps some miscellaneous deductions for unemployment insurance premiums, automatic contribution to their retirement account, and what have you. This leaves them with net pay (probably in the $2,700 region or so but it's heavily sensitive to their family situation because that makes a huge difference in how much anticipated income tax is withheld) which is actually transferred to their account.
So all of that is included "within" the $100k yearly salary. What isn't, such that business owners have to model it separately?
1) Payroll taxes are typically divided half between employees and half between employers. For example, there's a ~14% levy on the first ~$100k in salary, for Social Security (primarily a form of compulsory retirement savings which the vast majority of working Americans are legally required to contribute to). ~7% is deducted from each paycheck for this (so ~$280 out of $4,000). An equivalent sum is contributed by the employer, without ever appearing on a paycheck. So the employee's real salary is actually about $107,000 but $7,000 disappears to taxes prior to the point where they're told the salary that they are going to be taxed on.
2) For historical reasons, the United States does not tax many forms of health insurance if provided as a perk to employees. The United States also historically did not have a national health insurance scheme. (We've got Obamacare these days but it doesn't meaningfully interact with the math for Valley engineers.) The combination of these two facts means that virtually all white collar employees expect to have employers fund fairly generous health insurance plans as an employment perk. The pricing for these gets a little weird, but you're in the right ballpark at about $10k to $20k per employee per year.
3) In addition to our national retirement savings program, we have "individual" retirement savings. These programs have substantial tax advantages. These are not compulsory, and can be funded by either an employee, an employer, or both. It is the common practice of most employers of engineers to fund these retirement accounts on a matching basis. The offer is at the company's discretion (up to a legal cap). A common offer is "We will match $2 of your contributions with $1 of our own money, up to a maximum match of 3% of your salary."
4) American engineers are commonly offered perks. Many are comparatively inexpensive when bought at company size -- free gym memberships for all employees, for example. Some are not exactly inexpensive -- free lunches and dinners on the company's premises daily, prepared by gourmet chefs, for example. Americans do not customarily include the implicit cost of perks in salary figures.
5) There's a bunch of business overhead that I haven't accounted for above (desks, prorated rent, computers, etc), but they're substantially the same as in Israel, so I won't belabor the point.
Anyhow: health care, taxes, and perks is what gets you to 50 to 100%.
If anyone is interested, here in Israel we usually talk about the gross monthly salary, and we add around 25%-30% above that for the "true" employer cost.
Similar to the US system, but we usually don't include perks like gym membership when thinking of "employer costs". I think they're also less common, which might explain it. We do include the employer portion of the taxes, the employer portion of the pensions, potentially the employer portion of other savings accounts, and - unlike the US, I believe - one perk that is very common here is a company car, which is usually leased out to the employee.
I like to get out for several hours almost every day, though. I head to either Krankies Coffee or Camino Bakery in Winston Salem, and both venues have: a lot of people talking about family, studies, work, business, gossip; the espresso machine; music; and at Krankies the coffee-roasting machine. * Undifferentiated noise actually helps a lot! * I find the background din soothing and conducive to designing and coding. The one thing that's annoying is the occasional person who insists on carrying on their half of a conference call very loudly, but I don't see that much.
I've had pretty good experiences with open floor plans in companies too. They've never been the row-upon-row of adjacent tables depicted in the post, but close enough see/hear everything that's going on. In the open environment, a lot of the noise will probably be discussions about coding/design matters on other projects, or general office hijinx. There are downsides to that, but there's a lot of benefit too. You don't need to wait till the water cooler to see some matter needs discussion.
I can see how both the open floor plan and coffee shop environment will be distracting for some. I always hated libraries as a student, and always did my best work in non-quiet environments.
(I miss having coworkers just five steps over -- they're now 2700 and 8000 miles away.)
Trying to learn something new, with new concepts, and I really struggle.
And half the time, I actually can't hear them.
Email clients, chat clients, Social media, rapid fire short form articles, distraction wherever you look; these all contribute to a reduced attention span.
I do think it's possible to change the habit, but that requires mindfulness to engage in less context switching activities. That's really, really hard.
Cornell did a study of open plan awhile back that you should all read. I posted it here: https://news.ycombinator.com/item?id=7507404
The misunderstanding here is that it's just about serendipitously "overhearing" other conversations.
1. Open plan makes it easier to ask questions. Those are "disruptions", yes, but what the Cornell study found is that in open plan it's actually easier to "read" a person and see if it's an ok time to ask a question, and to quickly reply or say ask me later, and so forth, to efficiently manage those disruptions. Compare that to offices where you are much less likely to ask questions, knock on a door, etc., and where when it does happen it may turn into a much longer disruption.
2. They found it also gives us more courage to ask potentially "silly" questions. Which can be the genesis of good ideas and help us get unstuck, contributing to team creativity and productivity.
3. They noted that developer reactions to office plans are often biased towards maximizing personal productivity in order to maximize (short-term) personal benefit, whereas the company benefits from a balance of personal and team productivity. That's a fancy way of saying we'd rather spend our time coding than helping others, so we may not instinctively appreciate the benefits of open plan as much. Which I think is the case here.
This is one of those "beat the drum" issues on HN where we keep seeing article after article trying to drive the same one-sided point home. When I see this as the top article on HN, I just have to wonder if many of the people who come to HN are looking to disrupt the startup community.
I've worked in environments that run the gamut from individual offices, to cubes, to small working group rooms, to large open spaces. I've managed people in all of those environments as well, and I can tell you that openness leads to more synergy and more overall productivity. Maybe one or two in ten people have trouble working in that environment because they're too distracted. Sometimes you need to find hybrid arrangements to give people with trouble focusing a little more space -- but to just blanket claim that it's all about floorspace cost (as this article did) is akin to political advocacy.
In my experience, synergy and productivity is far more closely tied to clarity of goals and effective leadership than floor plan. Open floor plan advocacy, when it involves dragging people out of the offices they are quite happy with, is often a sign of leadership with misplaced priorities.
In my experience they are the one or two that do all the heavy lifting.
See what I just did there?
I was trying to illustrate anecdotal evidence.
http://en.wikipedia.org/wiki/Anecdotal_evidence
How do you know? Did you actually ask everyone "Do you have trouble working in this environment because of the distractions?" People are afraid of being seen as "anti-team" and "anti-open plan", and they won't tell you the truth. And others fake it, even if they really hate working in such an environment (I'm one of them) because it seems like a necessary evil these days. So the reality is, maybe that number is higher than you think.
Yeah, I did communicate with people about the efficacy of the working environment. Plus, for the past 12 years or so, everyone I've worked with has had a laptop that they could always (and did at times) take to quiet places when they needed alone time. They self-identified as needing quiet. Most others self-identified as liking the more collaborative working spaces.
I'm one of them
If you're working in an environment that is unproductive for you (that you hate) and you're not able to say something, then you should consider departing from it or addressing your own inability to have frank conversations with the people for whom you work.
Personally I have discussed this with coworkers/managers, but the environment is not going to change. Wherever I go next, I'll be on the lookout for quiet&privacy.
(I don't have a firm opinion on open vs. private offices, except I'd prefer to choose depending on what's best for the day).
For what it's worth, most of the open plan proponents have a similarly frustrating tendency to completely ignore the individual productivity trade-offs.
People should have private offices so they can be alone to think when they need, and also have bullpen areas where they can collaborate.
Obviously you need to have enough of these that there isn't competition for those rooms, but it can definitely work well.
Am I more productive in an isolated room? Absolutely. Do I feel comfortable doing it? No, not necessarily.
I agree that both is the way to go. You can find a study backing up either approach because they are important in different ways for different people.
I'm surprised no one has really brought up the introversion vs. extroversion angle. I just read Susan Cain's Quiet, and feel a wealth of clarity re: our general cultural stereotype that extroversion is better and therefore, so must be environments that are conducive to it (e.g., open floor plan. I don't have any illusions that corporations do that to save money, $ has never been a concern).
I work at a huge startup (300 people) that still has a very open floor plan and I basically work outside when it's not raining so that I can concentrate better. But the woman sitting next to me thrives in the activity and she can't work anywhere else.
I'm glad that the culture allows us to take freedom and ownership in how we channel our own productivity.
The point of the post you are replying to is that the "constant interruption and frustration" enables other developers to be more productive, raising the overall productivity of the team.
Also, you probably remember the times when you were interrupted and it was annoying strongly, but do you remember the times you interrupted someone else and saved valuable time?
You can still interrupt someone without an open plan office, there's just a slightly higher bar that prevents most people from asking the knuckleheaded questions, and keeps constant non-conversational visual and auditory distractions to a minimum.
No, because I've never been so at a loss for things to do that I couldn't do something else productive while waiting for an email or IM question/answer response cycle to continue.
Interrupting is rude, full stop. Like other instances of rude behavior, it should not be undertaken lightly.
http://iwsp.human.cornell.edu/file_uploads/offices1_12382569...
The data showed that younger workers liked these kinds of offices more than older workers. The reason was instructive: they felt they could learn more from their “officemates” in this kind of office. This makes sense, since in interviews a common reason for wanting to join a company was the opportunity to work with “great” people. Having great people around, whom you rarely see and even more rarely talk to, is not of real value. Respondents talked about the much greater learning opportunities in a more open environment. Older respondents, in contrast, found it harder to concentrate and more disruptive. It also seemed the case that older respondents were simply comfortable with how they had learned to do things over a number of years, and did well.
Hmm, that's one interpretation.
Here's a simpler interpretation.
Younger workers generally aren't going to know what they're doing and need to ask questions, so being able to ask questions is important to them. Older workers already know what they're doing and don't need to ask as many questions, so they don't really get anything out of it.
This BTW, squares exactly with my experience. All the benefit of open floor plans go to employees with the least expertise at the expense of the employees with the most expertise.
If you're the most talented, expert employee in an office, in general there's not going to be anyone in the office that can answer your questions, so an open office doesn't buy you anything.
If you are not being compensated proportionately, that's a separate issue entirely...
the question though is who needs does it make sense for the business to cater to?
also, from my experience, sometimes getting good answers to those early questions makes young workers exponential more productive going into the future
My initial thought is the best setup would really depend on the task.
For really complex tasks I would guess that you'd want a more closed environment. As a concrete example, if you're trying to make a theoretical breakthrough in cryptography, I'd guess you need an environment where you can seriously concentrate.
For maybe a less complex task, one where execution matters the most, like web development, a more open plan where its easier to coordinate might be better.
And obviously the quality of your co-workers matters a lot. High quality co-workers will have less questions and the value of training them up will be greater.
Open plan may be better for team productivity, but I doubt it will be 300% more productive.
I personally prefer emails. That way you have something to refer to rather than having to remembered all of the tiny details. Plus we change our mind so often I often can't remember what the final choice was. And tehy don't interrupt what you are doing.
Then at the end of the week, I am still giving an accounting of why a feature isn't finished on a schedule given by the same people who were interrupting the work I was doing to satisfy their stated priorities.
I'm amazed at how you totally ignore that this makes people miserable and contributes to bad management.
Why not learn to use email to ask a question?
- Developers can ask other developers questions when they're stuck on a certain problem. In my experience, developers waste far more time when they're stuck on a problem then when they're interrupted.
- QA / PM / whoever is on your "team" can ask quick, simple questions, that are either too small for an e-mail, or would seriously slow them down if they had to write the e-mail, wait for a developer to check e-mail, write a response, etc. Again, in my experience, developers routinely underestimate how much inefficiency having QA / PM / whatever blocked while they wait for information from a developer generates.
E-mail has it's uses, and the fact that some questions are better suited to a quick face-to-face interruption doesn't mean that every question is, but there's definitely cases where it's not the right tool for the job.
It should slow them down. If they are blocked multiple times a day, it isn't the communication method that is the problem, it is the process. Interrupting developers multiple times a day is not the solution.
Doing a little background research it seems they were comparing open floor plans to cubicles. They didn't even consider the obvious alternatives to the panopticon, such as remote work or the tried-and-true office with a door.
It was a link to a summary of the actual study. With that said I went and skimmed the original study and that looked just as bad. Here's the original study.
http://iwsp.human.cornell.edu/file_uploads/offices1_12382569...
Forget the fact that they didn't have the raw data. They don't clearly explain on what basis they reach their conclusions.
How are they measuring the 'success' of an open floor plan? For that matter, how can you even measure the 'success' of an open floor plan versus a close floor plan?
It's like saying a study that compared air travel to high speed rail is comically bad because it didn't even consider teleportation. (Extreme hyperbole, but I think it conveys my point.)
Its like saying light bulbs are comically bad because the sun is there for free. :)
I still have a hard time imagining that building individual offices, with the additional wiring, AC/heat, individual lighting etc. would be even close to a cubicle build out. Haven't built a space myself though and don't have hard data, so guess I'll take your word for it.
Now, you can re-use and re-configure cubicles, so that's often used as excuse to buy them. But moving them around is also expensive - rewiring, mechanical work, they're fragile to begin with.
So I call cubicles a dead loss to the bottom line. That's been my experience.
In my experience, open office plans scale poorly. The only successful ones I have worked in had less than 10 employees. Co-locating teams that don't need to collaborate (e.g. engineering & marketing) is typically a bad idea.
More to the point, I've now worked in a private office for a year. It has its perks, but I find myself wishing for a small open office plan again. The cons of isolation outweigh the pros of occasional distraction, IMO.
That's great for a single team all working on one thing - but I do not see the open plan office as a series of nicely appointed open plan offices for 4-8 people with sound-proofing.
I have worked in open plan offices with hundreds of people in the same open-plan - hearing birthdays, laughter, horror, lunchtimes and socialising that have nothing to do with me personally or professionally.
Cornell may have found that it is useful to know what the rest if your physically co-located team is working on - yes - but not hundreds of others that I need to filter out too.
If serendipity is valuable to you as a company, throw a Wednesday afternoon mixer and expect groups to form and make something new to try out. But give them team rooms for that wednesday.
I am a big fan of "team rooms", and a big big fan of remote working and always on video. But living in the middle of hundreds of others just teaches us to ignore everyone.
Ad-hoc team rooms sound like a very good idea though.
When I started programming years ago I had to wear a tie to work, and shared an office with one other person. I've since worked in large open plans, at home, in cubes, and in what would be called team rooms with everyone from the intern to the boss sitting within earshot.
IHMO, team rooms really do work. They help facilitate communication while not bothering those working with undue noise. If the team is under a crunch then naturally non-work conversations are kept to a minimum because the whole team knows it is crunch time. When there is more free time then the team adjusts accordingly.
This is an important point. For many of us who have worked in startups, "open office plan" really just means "team room". I enjoyed working in open office plans in smaller companies since it basically just meant 5-10 engineers sitting in the same space.
Last year I worked for a mid-size company of about ~200 employees, most of whom were crammed into a gigantic factory like space with endless arrays of fluorescent lights lining the ceiling.
The experience was among the most distracting I can remember. This was in no small part due to having to overhear loud conversations between people in different departments, such as marketing and sales, which require much more verbal communication than engineering. if I can help it I will never work in a similar environment again.
the reason startups do open plan offices is because no one is concentrating on managing the culture of the startup as it grows. Open plan is then I suspect both cause and symptom.
A campaign for team rooms is needed
1) I don't want people to be able to see me all the time. It's extremely nerve-racking and I feel like an animal in a zoo. And from my experience, people usually don't care whether I'm deep in some code or doing something less intense - they come over anyway. And people don't care whether their question is important enough to interrupt! As soon as someone taps my shoulder or calls my name, my concentration breaks completely and it takes me another half hour to get it back. Having offices makes people think harder and try to figure out the answer by themselves before going to someone else.
2) See above. The ratio of stupid questions that could have been resolved by Google or just another 2 minutes of thinking, to questions that ignited an interesting discussion is about 9 to 1.
3) How much work is going to get done by 'helping others'? 80-90% of a developer's work can be alone. Team productivity of course is important, but in development teams, this is really just the sum of individual developers' productivity.
Unless there is an issue and things get heated, then it helps to sit people down in a room together. But this (should) happen rarely.
I have the unique experience of having been both in offices and an open floor plan (most recently) for the same company. I can unequivocally state that I was more productive with an office. Junior devs had to measure the opportunity cost of coming to my office before asking me a Googleable question, I'm fairly certain one of them doesn't even use Google anymore.
I don't feel like this at all. In fact, that seems like an unhealthy reaction to me (so apologies for being judgmental). May i ask if you feel like this in other environments where there are other people around? Like, in a restaurant, or on public transport?
At work, people all know each other. Inevitably, you get nosy and annoying people who constantly check out what others are doing and peer into their screens.
Spending a day in the noise, getting distracted, and simply unable to get your head down and finish the one task you're assigned to gets highly annoying and draining. Which has negative effects on that person and the team as a whole; poor mood (and attitude by extension), bad work, and a higher inclination to simply pack up and leave.
I work in a ~20 people open floor plan; fridays feel the most productive, because it's the quietest. Some colleagues feel hugely relieved after spending a day working from home and, by their own words, getting some work done for the first time in forever.
tl;dr we're individual people, not team productivity numbers.
At the large company, I can't generally here what's being discussed by folks in the next group over, except maybe as low background noise. I don't generally get distracted and I am easily able to grab my teammates' attention when I need it.
I would love to be able to sit around my coworkers while I answer emails, catch up on the projects going on around me, bounce ideas off of people, etc. and then have a designated, quieter space to do "heads-down" work.
Why can't you have both?
Trying to get my company to make this happen...
Read Peopleware.
I routinely gain great value from speaking to the developer and product guy on either side of me, both of whom are immensely expert. The salespeople are fortunately far enough away and quiet enough that they're not a distraction.
I believe that there is an unplanned unorchestrated ongoing attempt throughout the industry to prevent programmers from being seen as professionals. Reverse dress codes (you'll get odd looks and questions if you aren't dressed casually, but instead throw on a suit or even just a tie), cubicles, and open office space are all ways that this is done.
Most people don't bother trying to dress that way so they never encounter the pushback and therefore never even realize that there is an unspoken rule in place. I recommend that everybody try to go to work on a monday with at least a white button up shirt with long sleeves and a tie. I think many of you who work places "without" dress codes will find the experience to be illuminating.
When I tried it, somebody from HR had a nice "chat" with me, explaining that the corporate culture was for engineers to dress casually.
I'm not sure how I would respond if someone said I was not allowed to dress nice. It just seems like a completely foreign concept.
I think it's more likely that open floor plans cost less per square foot or seem productive.
When we moved to our new building, interior spaces were meeting rooms. Next layer out were manager cubes. Final layer out were the worker cubes, everyone faced the big floor-ceiling windows.
This actually had a drawback. There were cunning metal shades over the windows to keep out the sun. These worked great to block the sun. They also collected snow. Which, thanks to wind, and sun, melted into in a slant, like a roof. Our first Thaw in that building and the ice/snow ...
BONNNGGGGG through the building frame as the snow slides off and the shade vibrates like a giant tuning fork.
A few minutes later BONNNGGGGG as the next in line sheds snow.
And so on. This went on all .. day ... long.
Non-programmers generally never know how to read whether it is a good time to interrupt or not, unless it's obvious you're just reading an article or something.
Generally agree with you, although just because I'm reading an article doesn't mean it's a good time to ask me a question. Right now, my brain is working on a weird problem while my tests run and I browse HN. I look like I'm goofing off, but I still wouldn't appreciate a context switch to another problem.
The polite question if you must interrupt a programmer is “Would now be a good time for a context switch?”
what would be the reaction if the internet was cut off because that was too distracting?
In 2011, the organizational psychologist Matthew Davis reviewed more than a hundred studies about office environments. He found that, though open offices often fostered a symbolic sense of organizational mission, making employees feel like part of a more laid-back, innovative enterprise, they were damaging to the workers’ attention spans, productivity, creative thinking, and satisfaction. Compared with standard offices, employees experienced more uncontrolled interactions, higher levels of stress, and lower levels of concentration and motivation. When David Craig surveyed some thirty-eight thousand workers, he found that interruptions by colleagues were detrimental to productivity, and that the more senior the employee, the worse she fared.
Source: http://www.newyorker.com/online/blogs/currency/2014/01/the-o...
Edited to add: the study by Matthew Davis referenced above is behind a paywall; if anyone can actually access it, I'd be curious to know for sure if this summary is accurate/correct.
I am one of those people who get distracted easily and am a new programmer. Working on a Scrum team of less than 10, I found this has grown into being very productive for the team and my growth, as I pick up the conversations, I am actually learning things and I throw my music on if the chatter is unproductive. I think the amount of dev's in the pit really can max out and that is what the writer of this article has probably experienced.
However, google search turned up that leeds link you probably came across in google scholar (or at least I did), and while the link appears to be dead, google has kept a cached version: http://webcache.googleusercontent.com/search?q=cache:Im7GHQR...
My personal take. Learning a craft is a lifelong endeavor. Experience builds. The path is organic & fractal-like.
If someone is senior, they have a context of experience that a more junior person does not have. Their brains are literally wired differently.
It's less satisfying to be around ignorant (I don't mean judgement, just lack of context) people. Especially ignorant people who affect how you do your job.
Being a senior person means there is an aspect of leadership involved. You mentor & lead the more junior people in your craft. However, masters don't spend most of their time mentoring. They spend most of their time growing their own personal craft. They try to instill this process of continuous improvement onto their students.
One of the most fascinating observations by Cornell is how self-interested employees are biased towards maximum individual productivity to the detriment of team productivity. I wonder if the 100 other studies controlled for that. Cornell is a pretty reputable institution. You know what they say.. 1 great study is worth 100 good ones.
The Cornell study does not account for the fact that most people suck at "reading" a person. Yes, it's easier to do in an open space. Most people who don't work also ignore the result of that reading.
> They found it also gives us more courage to ask potentially "silly" questions.
Which can also non-intrusively be asked by e-mail, the communication medium that has carried more silly questions than air has done in generations.
> They noted that developer reactions to office plans are often biased towards maximizing personal productivity in order to maximize (short-term) personal benefit, whereas the company benefits from a balance of personal and team productivity.
This says nothing about the underlying mechanism. Yes, I am biased towards maximizing personal productivity, which means that I will gladly and reliably avoid obnoxious co-workers. Closed spaces help me do that.
Maybe there is a good middle ground? Shared cubes of 2-4 people or a single room for a single team?
> Those are "disruptions", yes
But that is a huge deal. I would say disruptions many time outweigh the benefits of open spaces.
> the company benefits from a balance of personal and team productivity.
Without individual productivity there can be no company success. If someone is constantly interrupting others then they probably need more focused training or a class.
Imagine you are surgeon and while you perform surgery you doctor buddy from across the hall comes in and asks you some question about how to hold a scalpel or something like that.
I immensely dislike open work areas. I do not know many coders who like them either.
The people who benefit the most are the headphone makers. :)
May be just me.
No, open plans are almost always for two reasons, ignoring any harm or benefit:
1) To reduce costs.
2) Politics/motivation - you have to work hard or be important to get an office.
And I'll see your one study and raise you a "Peopleware" by DeMarco and Lister; IMHO it should be required reading for everyone (especially those who decide on space layouts for knowledge workers).
So just for the off-chance that someone could ask me a question, I have force myself to wear headphones every day just to get any work done? What the fuck? Maybe most people are not like me, and are not distracted by the moving, talking and noise making of other people around them -- but I am. I need as much silence as I can get.
What is absurd about this is that some companies make special "quiet zones" for people to go to and think, which means they implicitly admit that the actual work environment is not conductive to thinking.
You want to ask me a question? Send me an IM.
This is interesting, actually. Why is being interrupted by IM not as bad? I agree with you, it doesn't seem to be as much of a problem. But why? Is it just that the interaction isn't quite real-time -- I can ignore you for a few minutes if I'm in the middle of something?
Maybe someone should try the combination of private offices and a local chat server, to see if that's the best of both worlds, concentration and collaboration.
That is exactly why.
I've become convinced the best solution is the one from peopleware: 2 to 4 people offices, with a door.
1. Being able to "read" someone visually helps in determining whether it's an ok time to interrupt. "Unexpectedly.. more visual contact actually contributes to fewer unwanted interactions, not more, by changing not so much the frequency as the timing of conversations."
2. More frequent social interaction builds more trust. People felt more comfortable asking for help.
3. A lot of information is acquired through something called "tacit learning". That's info that's never written down that you pick up by observing others. You may not even know to ask about it or have an opportunity. Open plan greatly helps the spread of this.
4. Most damningly, it notes that self-interested developers are biased towards individual productivity more than team productivity. This often leads them to undervalue the benefits of "disruptions".
Typically the more senior you get, the more important it is for you to allocate time to help others. A place I used to work at codified this. You had to have X percent helping-others time and X grew as you rose in the ranks. That's precisely because of the important of team vs. individual productivity.
I don't mind being interrupted by someone who wants to ask me a question. The explicit interruptions are not what makes the open office a painful experience -- it's the background noise that comes with it. This is why many people work with headphones on. You shouldn't be listening to music just because you need to concentrate on your work.
> 2. More frequent social interaction builds more trust. People felt more comfortable asking for help.
Surely you could think of better ways to build trust between team members other than sitting everyone in an open space?
> 3. A lot of information is acquired through something called "tacit learning". That's info that's never written down that you pick up by observing others. You may not even know to ask about it or have an opportunity. Open plan greatly helps the spread of this.
I don't want to be observed while working. I'm not a lab rat.
As for not wanting to be observed.. of course you don't. It's not in your self interest. But it is in the interest of team productivity to promote tacit learning. Let other people more readily learn how to do what you do, your tips & tricks, the little things not written down and formally taught.
And you might want to Google "flow state" and how that applies to development work.
Back in the 80's I was the core programmer on a map-reduce system that formed a part of one of the only 3 products British telecom sold internationally my CTO was one of Vint Cerfs reports.
what have you shipped or done?
It's absurd to expect human beings, especially software engineers--who tend to be quieter, more introverted, and loner-types--to be herded like cattle into a crowded, noisy open-plan office and expect them to have the razor-sharp focus needed for high quality software development.
If you only hire people who thrive in noisy / distracting environments, I won't be surprised if you end up hiring the wrong people for actually getting the job done-because often times, the people who take on the most work, resolve the most difficult problems, and carry the most weight are those people who can't stand working in a place like that.
I worked in environments that optimize the team, rather than the individual, for years. It is a breath of fresh air to work from home & optimize my environment for me. I'm happier, healthier, more productive, can get my business taken care of, etc. It's pretty much a total win.
I also have some "eccentric" behavior. I happen to pace & otherwise move when I think. I cannot do that with other people around.
The architecture of the software I'm working on is more coherent. I'm able to collaborate with teammates. Things are progressing quite well. I've never been happier.
Sorry, I don't have a study. Just my anecdotal experience.
I have worked on a code base for the last 6 months in which I am the sole committer. A lot of my coworkers are the same. We have brief sprints where we are in each others' faces, the majority of the time we only need concrete pieces of high-context information from each other that have nothing to do with serendipity.
Even with nothing but white noise going through them I'm totally able to ignore 99% of all the open floor plan distractions.
Having worked in a company where engineers had individual offices, and now work in an open floor plan, I can assure you that sick days have gone up, the noise level is many times what it was and overall productivity is noticeably lower - guess what - if you lower everyone's productivity, then the team productivity goes down. Big surprise that NONE of the managers are in the open floor plan.
Open floor plans are simply a way for managers to feel better about themselves by hurting other people.
I'm now in an open-floor office in which people talk a lot and interrupt me when it's necessary, and I'm a lot happier and more productive.
"Now maybe you're different than me" is probably the most important phrase in there.
The trick is to provide enough separation and space that people don't feel claustrophobic, and manage a culture that encourages people to take group conversations into a room if they're going to be loud/passionate.
A practical concern might be that a library needs a librarian to shush people. And it needs people to obey the librarian when they do that.
This is pretty much the optimal situation for an openspace floor layout. Now compare that with the situation in a more mature company. The first thing any sane lead engineer wants to do once v1.0 is out the door and making money, is to pay down on the inherited technical debt. Organise code so that it is modularised, so that changes in one area don't have a major impact on other areas. As money is being made, the team starts to expand as well, so simultaneously you have less need for close interaction between team members (due to improved software structure) and greater opportunity to be distracted by irrelevant discussions, as the scope of the product has now grown so much that most of the engineers will never master all of it, but instead become experts in one particular aspect.
Let me give you a real-world example from my current job. At the moment, I'm deep in the source code of an OpenGL driver, identifying performance problems. The thing is, we already have a product, and it works well, but it uses a 2D graphics APIs, and the designers want iOS7-style blurring. So I've re-implemented the graphics APIs using OpenGL. This is completely independant work. No-one else knows OpenGL, and none of them even see the API, as it's hidden behind a facade that they already know. I had pretty much zero interaction with the team whilst implementing the OpenGL backend, as all I had to do was implement an existing API. I now still have zero interaction, because if the team don't know much about using OpenGL, they know even less about how it's implemented under the hood. I don't need to know about their problems with what happens when the user presses "back", and they don't need to know about my problems with the vsync callback.
Yet, we are still in an openspace. The designer with the ridiculously loud laugh is still distracting me every thirty minutes or so. The two guys having a discussion about the latest ministry shake up in the government, yup, they're doing that about 2m from my ears and not making it any easier for me to concentrate. They programmer talking about the first run sequence with a project manager one desk over? Absolutely of no interest to me.
OK, so much for why openspaces objectively suck once your past the project startup phase. Why do ex-developers / current-CEOs still stay with openspaces? You would have to ask them, but maybe it's because they remember how wonderfully productive it was at the start of the adventure and don't realise that the situation has changed. Or maybe their much more interested in raking in the cash,and are now just waiting to flip the company - future productivity is of no interest. Keeping the costs down to make the company more attractive to buyers though, that might be very interesting to them. Anyway, the fact that they persist with openspaces is not necessarily a ringing endorsement for openspaces.
– Richard Hamming, “You and Your Research” http://www.cs.virginia.edu/~robins/YouAndYourResearch.html
This is a very different question from "offices or open plan?".
(My own preference is one I've seen others express here: rooms for groups of roughly 4-10 people, private rooms for intense concentration and private meetings, and some communal space.)
That was the rule in the Physics department I spent a little time in. 'Tea' involved about 40 researchers in a large room on couches and armchairs arranged (and rearranged) in small groups. You were expected to share problems, findings, ideas, and listen. Room had no blackboards but plenty of paper napkins.
Broke up around 4pm most days but sometimes went on much longer.
Leaders used to hear a problem and say things like "talk to Robin. He's been working on conditionally convergent series", so you did, and it helped.
Or maybe there are fashions in management as there are in anything else.
The real thing people are finally paying attention to is that not all human workers are the same. Some people thrive in an open noisy collaborative environment, while some can't operate at all in that environment. It is the real task of management to manage the work environment of all your employees.
1. For core teams, ditch the open floor plan and instead put teams into small (4-5 person max, with smaller options) private rooms that line the perimeter
2. Project rooms are not permanent. A team should expect to move around perhaps once every 3-4 months
3. Team leaders / managers would of course work in the same room as their team
4. In the center of the perimeter of team rooms could be a hacker workspace, shared areas, supplies, snacks, etc. With breakout meeting rooms around the space as well
5. executive leadership would work sitting with other specific staff (like finance, HR, office managers, etc) in an open floor plan-like area; most importantly, execs wouldn't have private offices because ideally they should be moving around meeting with the teams, jumping into conference rooms, jetting out of the office, etc.
6. this open area should be relatively quiet
7. people working in this open area should have ample access to private spaces for breakout meetings, private phone calls, reflection, relaxation, etc
Obviously these rules won't apply perfectly to every company and work type, but I'm just brainstorming
Instead of point-by-point, I'm just going to offer one critique.
"...Programming is a very brain-intensive task..."
Sure thing, buddy. But guess what? You're not a machine for cranking out little bits and bytes. Instead, you're part of a team that's trying to provide value to a user. That means that most of your job, whether you like this or not, is human in nature. The computer part should just be a "gimme".
The physical space around a team should represent the mental space of the team. One hundred guys in a big cafeteria? Not so much. 40 guys in clusters of 3-6 with rolling whiteboards and allowances for breakout discussions? Much different.
There are things I would love in software development. I would love to sit on the beach fanning myself coding while money is deposited in my account. (Actually, I've done that.) I would love to work alone in my office in the wee hours of the morning in an awesome state of flow (did that many times too.)
But at some point you have to separate "things I want to do" from "things that optimize the value I provide". They aren't the same thing.
I'm all for private offices if it works for you and optimizes value. Same goes for distributed teams. Right now nobody has all the answers. On average, though, it looks like these things are counter-productive for projects that require creative new ways of thinking of things. I wish it weren't so, but it is.
We should be suspicious of such claims. Think of von Neumann:
At Princeton he received complaints for regularly playing extremely loud German marching music on his gramophone, which distracted those in neighbouring offices, including Einstein, from their work. Von Neumann did some of his best work blazingly fast in noisy, chaotic environments, and once admonished his wife for preparing a quiet study for him to work in. He never used it, preferring the couple's living room with its TV playing loudly.
It seems to me to be a personal preference only. Some people like noisy and some people don't, there's not necessarily any one correct answer. But folk like Joel and others (usually American where private offices are much more common) constantly push absolute silence and the myth of never being interrupted or distracted, seemingly without much to back it up.
I really prefer an active office close to others. If someone taps me on the shoulder I have no problem continuing my train of thought.
This is a huge gift. I, sadly, lack this ability.
I think that among programmers especially, the proportion of people who cannot work at peak productivity in an open plan office is much higher than 50%, but even if it were only 30% that would still be a strong argument for closed offices.
I've had my own office for the last 3 years and enjoy the privacy, but occasionally miss the instant answers and social aspects of that open plan.
Does an environment with a high chance of interruption lead to languages where you have to write a lot to do a small task, because you can write simple code between interruptions, and over time get enough code to do the task - and if you get interrupted well you only lose one minute's thinking.
Contrast with a powerful language where you need half an hour of thinking to build an intricate machine in your head, then you write it down in a little code, and need to hold its workings in mind while you test it. With no long spans of concentration you won't go slower or write half an intricate mechanism, you will write nothing.
Or to put it another way, is the problem of working in an open plan office: you aren't choosing the right tools and work pattern for your environment?
Or to put it another way: are enterprise languages 'blub' languages because they come from big offices and academic languages 'powerful and terse' because they come from people with time and quiet for deep thought.
Or another way: could we redesign our languages, tools and their UI to make us as effective, and feel as good, in open plan offices, like f.lux changes a screen for night use instead of complaining that it's not daytime.
That's not a powerful language, it's a bad language.
A powerful language isn't one that's overly concise to the point of crypticness, it's one that allows you to express yourself naturally. Meaning, there is a clean and strong conceptual mapping between the code and the problem domain. Meaning, it requires less mental effort to use.
> Not every programmer in the world wants to work in a private office. In fact quite a few would tell you unequivocally that they prefer the camaradarie and easy information sharing of an open space.
> Don't fall for it. They also want M&Ms for breakfast and a pony. Open space is fun but not productive.
http://www.joelonsoftware.com/items/2006/07/30.html
See also: http://www.joelonsoftware.com/articles/FieldGuidetoDeveloper...
One of the most effective office setups I have seen had two kinds of work areas:
1) Reconfigurable "team rooms" where most of the team can work together. These have a door that is kept closed to reduce conversation noise leaking into other areas, and a glass wall so you can see who is in the team room. The other two interior walls can be moved to adjust the size of the team room.
2) On a different floor, there is an open quiet area equipped with large monitors for individual coding, writing, and CAD work.
There are other workspaces, such as lab rooms for fabricating things. Their larger locations have large shops with all kinds of fabrication equipment.
Everything is hot-desked. Many people spend part of the week working at home. The company with this workspace is a major design firm, and I'd wager they put a lot of thought and objective measurement into the design of their workspaces.
But when you have a system crash and need to dive through 100mb of log files to try and figure out what went wrong. Good luck doing that in a standard open office! You just have to schedule a few hours after everyone else has gone home so you can have some peace and quiet to do your log diving.
I honestly think the traits that make you able to hack the Linux kernel, optimize the linear algebra required for the internals of a 3d engine, write Haskell etc are incompatible with preferring open floor plans.
Edit: Btw, if you are able to do these "high level advanced" programming tasks while in a noisy open floor plan I would be very amazed. For me it's like trying to play chess against a highly rated opponent and that is impossible to do competently if you have to endure constant interruptions.
Anything that requires thinking, such as fixing a release-blocker bug that is very obvious once you get in the zone is pretty much lost.
Simpler work where you know exactly what you're doing, where there are no difficult choices to be made, can probably be accomplished in any environment. Sometimes that's the vast majority of the work you're doing, sometimes it's not. It really depends on the type of application.
Would you care to explain what that means?
Most organizations are so inept at choosing leaders (they can't tell who's good at the job and who's not) that their only recourse is to set up pointless contests that grind people down, and then determine the last person remaining to be the leader. (Those who left weren't dedicated; those who broke were "weak".)
Open-plan offices (and, especially, open-back visibility) are just another shitty mechanism used to wear people down and make the attrition/sorting process happen faster.