And here's the problem - some people just cannot be respectful of other people's time or flow and also you can find a lot of variation between communication styles (e.g. synchronous vs asynchronous) or noise tolerance of people.
For example, some people only want to work from home, whereas I cannot work from home, but on the other hand I need a very distractions free environment. I have really good and respectful colleagues and yet I find myself saying no to requests and interruptions several times per day even, actively declining attempts at synchronous communications between us, just so I could get anything done. This happens to the point of becoming nauseating, not only because "Alex, can you talk?" is distracting enough, but also because I have to say NO a lot. And I'm probably labeled as being a jerk, yet I cannot help being one, because contrary to other people, I really, really need to be left alone when focusing on something.
On your experience, I'm not arguing that the open office in question wasn't productive for you or for your close peers, but have you asked the others about it?
Open floor plans would probably work great for people like that. I prefer to not be pre-empted from my current task, and to have a written record of the things you wanted to tell me, so I can refer to it later. Face-to-face conversations are fine if I'm not already doing something else, but don't force me into one just because you're doing your "manager walk" or can't be arsed to have a specific agenda for the conversation.
If I have a door, I can hang a "do not disturb" sign on it, and lo, I am not disturbed. Otherwise, it may just be closed because the compressor from the fridge in the break area bothers me. I don't mind interruptions, provided they are more important than what I am currently doing, but it seems like open plans lower the threshold for interruption. Some people see that as also lowering the threshold for collaboration. But there are ways to design a space to encourage one without also encouraging the other.
Amen. My voicemail greeting for my work phone is "Hi, you've reached the voicemail box of Jack Maney. Instead of leaving me a voicemail, please leave me an email. Thank you."
It's faster and easier to get an email, click it, and read/skim it, and let it sit in your inbox until you're ready to decide what to do with it.
The thing I like most about async is that there must necessarily be a record of everything that was said. When appropriate, the record may be retransmitted.
Things like internal wiki entries, message boards, e-mail chains, instant message groups, and issue-tracker tickets are all asynchronous. If you conduct most of your business with ephemeral synchronous conversations, you're going to end up repeating yourself a lot, and there's going to be a larger "hit by a bus" risk. I consider it to be irresponsible business practice.
There's good reason why human development was very slow during oral tradition, and experienced exponential growth after writing.
Some use of synchronous is always appropriate. But using it instead of asynchronous rather than in addition to it is, in my opinion, pure folly. At best, the synchronous communication is what you use to make your asynchronous communication more efficient.
My unsolicited advice on this is to just let yourself be distracted. As much as we may not like it, it's much more important to be liked among your peers than to have high raw productivity. Employment is a popularity contest (at least for popularity among the powerful segment of the corporate structure) and there's really no way around that. If we accept that, our future as employees becomes brighter.
We also communicated our preferences directly. If someone was interrupting us, we would let them know that it was better to send an email or grab us before or after a known distraction (arriving at work, lunch, coffee break, end of day). We tried to schedule meetings on Mondays and Fridays to give us largely uninterrupted time during the week. People respected our preferences and tried to accommodate the "Maker's Schedule."
I'm not sure every company could or should work this way, but I worry that backlash around poor implementations of the open layout will cause us to throw the baby out with the bathwater. It's up to each company to evaluate the compromises necessary to create a productive workspace, open or otherwise. I worked with great people and the open office concept worked for us.
OK, so I believe that this is a good strategy - the ones that prefer more privacy, should get it, the ones that prefer the open space should get an open space.
Could it be that a solution or mitigation here is to directly address this problem? I think the idea that people are only capable of communicating in a certain way is probably too strict. Maybe it's just my experience but it seems to me that most people (with exceptions of course) don't give or get direct feedback about what type of communication works best for them, more typically they use some passive-aggressive move like brightly colored headphones or just acting annoyed and expect people to get the hint. This probably works to some degree but in a large open space it seems like you need everyone on the same page.
The privacy issue also needs to be addressed on a cultural level as well. My first job was open layout but I had one of those nosey managers that wants to know what you're doing every 15 minutes. I got talked to for being on Facebook during my lunch break. In order to really have a successful open office layout you need to have everyone on board and prepared to "let go" a little. Yeah people goof off during the day. We aren't robots that can sit down at 8:30 and constantly type for the next 8 to 9 hours. At my current job no one really cares if they walk up to you to ask a question and you happen to be taking a couple minutes to clear your head and look at cat gifs. I think that's the way it should be.
As someone who's had to run programming groups and do the programming work, I will say open floor plans are the worst idea ever.
If you need/want to get into the zone on a project and actually make progress, the open floor plan will keep you from doing that as much as possible. For breaks, the last thing I would be doing is going on facebook or checking email or doing other useless crap like that.
Your job sounds horrible if people can just walk up any time for any reason. And if you're spending time looking at cat gif's then I think you or your manager needs to revisit how you're spending your time. Doesn't sound like work to me. Sorry...
I think this speaks more to what you think about your coworkers than actually weighing in on open floor plans.
I would prefer to choose when to have my interruptions.
"A factory pattern, you say? Well.. Oh, look, a squirrel!"
For collaboration nothing beats an open office layout. But collaborative periods make up a very small amount of our [developers] time.
If we spent most of our time collaborating then maybe open office layouts would make some sense (though maybe not, since there's still downsides to consider). It is illogical to choose an office layout based on what you spend a small fraction of your time doing.
https://news.ycombinator.com/item?id=117171
> pg 2455 days ago | link | parent | flag
> I think it's ok to use the up and down arrows to express agreement. Obviously the uparrows aren't only for applauding politeness, so it seems reasonable that the downarrows aren't only for booing rudeness.
> It only becomes abuse when people resort to karma bombing: downvoting a lot of comments by one user without reading them in order to subtract maximum karma. Fortunately we now have several levels of software to protect against that.
The fact that upvotes and downvotes are not treated symmetrically seems to imply that they really aren't suitable for merely conveying agreement or disagreement. Somebody's comment shouldn't literally be greyed out, sometimes to the point of being illegible, because a few people disagreed with it. This combination -- using downvotes freely to express disagreement, and hiding or fading out downvoted comments -- is a recipe for groupthink. It's very nearly a form of censoring comments that are maybe contentious but in no way inflammatory or off-topic or poorly written.
I can look round and see exactly whether it's OK to approach people....
[NB I wouldn't mind one on a hat I could wear at home!].
If you work with a bunch of thoughtful people, of course they are going to respect flow. And they're going to realize when their personal habits affect the people around them. Even gregarious extroverts will be quiet in a library like atmosphere, and move their conversations to a kitchen or break out room
The open office allows people to split into sub teams and to work together on projects more fluidly than an arrangement where people have strong physical barriers to moving.
But it's a sort of environment that comes together as the sum of its parts. Forcing an open environment into a shitty company with shitty employees will likely make it worse.
>>> Maybe the reason is because you're doing it wrong.
That can be said of any failed ideology.
Viewing your office layout as an ideology is part of the problem. It's not about us-versus-them. It's about identifying your team's work styles and building a space to support them as best as you can.
Open offices can work well, but it requires a little bit of effort and adherence to the rules. We have plenty of breakout areas for impromptu meetings, ample numbers of meeting rooms for more extended ones. There's plenty of space to cloister oneself for a while if needed. Our development team is together, and a few desks away from more customer-facing staff, which keeps noise down.
Yeah, there are occasional distractions. But so long as everybody is respectful, there are benefits too. It's great for quick pairing sessions, which we do a lot; overhearing conversations and being able to chip in with relevant information is really often useful; even just being able to see who's physically in the office helps.
I suspect a lot of this is going to be dependent on size and culture. So maybe there's an argument that on the whole, open-plan is not worth it. But I'm unconvinced.
Your entire post is about how you can minimise the negatives, but anyone who has been to a library before already knows you can make an open plan almost noise free.
I'll just give a +1 for small pods and breakout spaces, since those were a big part of what worked for us.
Here's what I would add to what you're saying:
1. Being respectful of flow has never worked for a team I was on. Instead, what we did is that at all times we had a pair (or the odd person out) whose job it was to field questions. If you needed to know something from a team, you went to the assigned person or pair. A corollary of this is that everyone on a given team was expected to be able to answer questions as a representative of the team. 2. Pair programming: I definitely am prone to distraction, but it's much easier to stay focused when you're working with someone on something. This also contributes to information sharing, which contributes to everyone on the team being able to answer questions.
Many people mention that introverts have a hard time working in an open office layout. But what I haven't seen mentioned on this thread is that extroverts might have an equally hard time working in isolation. I'm an extrovert and I've definitely been in situations where isolation hurt my productivity. And I think that points to the core of the problem: your office space needs to meet the needs of your team, not some romanticized ideal of an Agile™ team. It's unlikely that any processes or procedures are going to make an open office work for an office full of introverts. If an open office doesn't work for your team, that doesn't mean open offices don't work, it just means that your team needs something different.
This points back to the agile manifesto[1]: "Individuals and interactions over processes and tools." An office is just a tool. If you're still looking for a one-size-fits-all office layout, you're prioritizing that tool over the individuals who are using it. That's not agile.
edit: a clarification. It is ridiculous to put backend/Linux developers on Macs with 8Gb of memory on which it is nearly impossible to run a virtual machine. And glossy monitors are very good for designers in light-controlled rooms, not so for developers, who can see every ceilings light in theirs.
* Separate clusters by function / noise level -- We didn't put sales people and developers next to one another. People who spent all day on the phone were near other people who spent all day on the phone.
* Keep clusters small -- We had 4 person "pods" of desks for most of our early lifecycle. You weren't constantly interrupted by a dozen people from every direction, but you had a few people you could bounce ideas off of when you needed to.
* Lots of breakout spaces -- If you need to have a conversation that lasts more than a minute or so, find a private space. It was nice to hear a snippet of a conversation and decide "I care about this topic, let's break out and discuss further" or "This is not relevant right now, I'm going to disregard."
* Be respectful of flow -- If someone is deep in focus, just leave a post-it on their desk or send a message via chat. (This was a good form of one-bit communication for us.)
I don't think it's impossible to create a great open office layout. People just copied the ceremony without the essence. It's no different than "Agile is broken! We have 20 minute standups 3 times a day and nothing gets done!" Maybe the reason is because you're doing it wrong.