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.
Read Peopleware.
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 think it's more likely that open floor plans cost less per square foot or seem productive.
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.
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.
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.
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.
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.
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.
Ad-hoc team rooms sound like a very good idea though.
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
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...
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.
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".
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.
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.
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.
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?
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.
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.
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.
For what it's worth, most of the open plan proponents have a similarly frustrating tendency to completely ignore the individual productivity trade-offs.
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 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.
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.
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).
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 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. :)
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?
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.
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).
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.
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.
> 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.
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.
May be just me.
Even with nothing but white noise going through them I'm totally able to ignore 99% of all the open floor plan distractions.
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.
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?
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.