Add some conference rooms of various sizes which can be taken over for weeks (the "war room" model), and some other meeting areas.
Plus some lounge open spaces which can be used for working, too (like, say, an actual library type space, where there are people but it is quiet, and also a video area)
Even spending $2500/mo/engineer on facilities doesn't seem unreasonable. That could get you quite a nice office. Even $1k/mo should do it (500 square feet per person in a place like Mountain View outside downtown)
Lots of shared space for meetings (with high resolution projectors!) and general chit-chat/hangout time, but any actual work-work is designed to happen in the offices. Not that you couldn't take your laptop into the "lounge", but it wouldn't be optimal.
I worked opposite a lady who would have various male admirers who would come over several times a day to chat her up. So these guys would either stand directly behind my chair and try and talk through me or go around to her side and whisper stuff to her and they would sit and giggle.
Of course nobody achieved any actual work there, so projects were always late. Their solution was to add more people to the project and more people = even more noise.
There were all kinds of rules and strict dress code, no dyed hair, no personal effects on desks, no mobile phones, no visible tattoos etc.
Not the most fun place to work, so after about a year I actually left for a job with longer hours and a worse salary.
I'm not sure what's up with the anxiety - are you constantly trying to hide that you're on the web all the time and getting nervous as a result?
I don't agree with this.
Bullpens/developer rooms are designed for collaboration and they have been for the last fifteen years. They are for developers to whiteboard or bounce ideas off of each other. If you are in a bullpen the expectation shouldn't be quiet.
With that said you cannot (or should not) have bullpens without open offices that developers can choose to walk in and shut the door. Offices should be some distance away from the bullpen and be unlabeled-first-come-first-serve (they should be designed for quiet focus). You should also be able to work from home whenever it best suits you.
Also, after reading some of the other comments, a bullpen is not a way to stuff the developers, call center team, and the sales team into one cheap room! If any company does this it's a sign of poor management.
I'm a headphones-focus person and I can't stand people talking around me when I focus. However, unless it is excessive (someone doing a conference call on speaker every day) then it's just how offices have been since... well forever. However, in every place that I've worked there has been offices that you can use to focus (or a liberal work from home policy). I typically spend most of my time in a closed door office getting all of the hard think-work done and then the remainder in the bullpen doing CRUD work.
A company that has a bullpen and enforces a quiet rule feels like a company that simply does not know how to build a proper development environment (Oh, developers are supposed to be in, like, big rooms or something, but our developers don't like noise... okay how about we make it a 'quiet only' big room... or something)
A civilised, open plan engineering office should indeed be quiet. Not silent, but fairly quiet.
We did exactly the opposite to your method by the sounds of things - meeting rooms for 4 to 5 people, and one or two much larger rooms, were available around the edges of the floor to go and bounce ideas around or discuss things. The rest of the floor was quiet space but informal conversation was fine. It worked very well for us.
I am somewhat of a misanthrope. I don't trust most people. I don't expect them to trust me. They shouldn't trust me if they don't know me, especially if the stakes are high. Much of the answer to the ubiquitous question, "Why Does Work Suck?" is that the stakes are just too high to trust anyone. The activity of work isn't so bad. The social bullshit and paranoia are intolerable.
I wouldn't let 20+ strangers in my house, 5 days per week. I resent that I have to let so many people-- even though there's nothing wrong with them as people, it's more that I don't know them and I have no choice-- into my career. It's not a problem with the people as people. The people themselves are fine. (They're in the same miserable, cramped boat that I am in.) I just resent being visible and the constant second-by-second impression management makes it hard to get anything done. I spend 90% of my emotional energy on appearing productive and that leaves little for actually being productive, and it sucks.
you use that word. I don't think it means what you think it means - or that it has the implications that you think it has; I am a misanthrope, but that does not influence my reaction to the floor plan of the office I work in. actually, I'd most likely go insane in a cubicle farm. there are ways around to signal that you don't want to be disturbed in an open space.
given that you write:
> I don't trust most people. I don't expect them to trust me.
followed by:
> The social bullshit and paranoia are intolerable.
I do assume that you're referring to your own paranoia, here...
> [snip the rest of the workplace description]
... which leads me to think your problem is not the office planning, or your social issues (with or without medications): I think it's your current job. my entirely serious suggestion is to either change it, or ask to work remotely, if you still think that you'd enjoy it more (and if they don't allow remote work, I'd seriously consider changing jobs anyway).
That said, open-plan signals to me that the company doesn't actually value productivity so much as image and availability. This is something that I have learned with age not to take personally, but I still dislike it.
I realize that 99% of white-collar work for the most talented is compensating for other peoples' fuckups, but I don't have to like it.
It may not be your perfect office environment, but that doesn't mean that other people (me) don't work much better when in an open space with some casual (quiet) impromptu collaboration possible. I would find being stuck away in individual or small offices quite isolating and stifling.
You ought to talk to your employer about making other working arrangements if you feel so strongly about it, assuming you haven't already and I'm not just being patronising here.
I don't let it get to me. It's not personal, and I know cognitively that no one's really watching me. (I spend more "web time" in open-plan offices because I can't get into flow.) It's just creepy. It probably reduces productivity by 80%, but surprisingly that doesn't seem to matter, because modern work environments seem to cripple everyone about equally.
What open plan says to me is that my employer cares more about my personal availability than productivity. Which is not worth taking personally, but it is a depressing statement.
No, it is perfectly fair and accurate. You can still collaborate just fine without an open office. Read peopleware, noisy open offices are detrimental to productivity, even for the people who claim to like them and "need" them.
Again, just because you don't like open doesn't mean nobody does, or that in non-US countries an open office necessarily means lots of noise.
That said, it does seem like the pendulum is moving back toward privacy in offices, though what that will look like is anybody's guess.
I for one am a fan of the office design concept known as Activity Based Working, where the work areas provided are the one's that are most conducive to your particular company's need. Not all companies, and not all tasks are best served by either having all open or all closed workspaces. Instead, offering a variety of places for employees to use seems most prudent - but again, only offering things your employees need. So if you don't need an executive boardroom, don't add one to you plan as it will just go unused.
quick question
There need to be library rules about this office behavior, too. The road to hell is paved with "quick questions".And in my experience educating them does not help, as long, as the managers are resistant. I had a lot experiences, were the managers came again and again with this sort of behavior and whatever I did to educate (or show) people, that I am in a "do not disturb"-moment was fruitless. Headphones == tap on shoulder. Hood of jacket == tap on shoulder + strange look.
If the culture, set by managers does not value makers, you are doomed. And educating managers, who live and breath a meeting, question work-style is really not easy. If a manger has never been a maker, you are lost. You won't change their minds.
Really, me? I have given up... as sad as it is.
A lot of corporate culture here is not so much result-focused, but sitting on your back, doing your time.
And in a lot of cases, this might work. If I were the typical product manager, this would work. But having found the bliss of automating things via scripting, I feel more and more like a maker and can more and more understand, not to disturb the makers and what it costs to be the disturber. But here most product managers are more managers, then makers - so the live and breath a manager-schedule, being able to cope with interruptions quite easily. So no problem for them, but a problem for our developers (and to some extent guys like me)...
... but as it is mostly my problem (and has been in previous gigs as well), it is something that I have to deal with obviously, as I am part of a minority here.
The situation is not so bad, that it kills me right now, but I will keep looking - and using my time, learning some new things while "doing my time in front of a monitor" ;-)
Being able to get a quick answer to a question is important. Being able to ask my question in a way that only distracts the person to whom it is addressed, and in a way that allows them to defer answering until they're at a natural stopping point makes us all more productive. As does being able to save the answer so I never have to bug anyone for that question again, or even share it when other people encounter the same issue.
Having an "open plan" for a smaller team - say under 10 - is probably a good way to go. That way each team can develop rules like this 'Library Rules' idea, or a more interruptive one if thats the way they feel they get more work done.
I can think of a few reasons why I disagree with this. - Your peak productivity can only be reached if you are not disturbed every five minutes from the work you are doing on your computer. We all know that focus is important, and indeed it is hard to focus in a noisy environment. I remember that the guys at GitHub have some kind of "no live talk" rule : if you need to speak to someone, do it on the internal chat room, even if he's litterally 1 meter away from you. It has several advantages : you can choose when you want to read messages and when you want to reply to them. If you're in the middle of a hardcore debugging session, you are free to continue. It also has the big advantage that chat can be recorded and reviewed and searched at a later date : live speech can't — or at least not easily. - On the other hand, if you're in the phase of a project where you need a lot of interaction with other people and where it would be to cumbersome to do it via chat, like when you're trying to design your architecture, or when trying to agree on rules, specs, etc... Then just set up a meeting : that's what they are for.
For me, it's open-back visibility. Noise I can shut out. Being visible gives me the creeps. If I am going to be in a place for the amount of time equal to a trans-Atlantic plane ride, then give me a goddamn decent space rather than treating my flight-or-fight response as your own personal toy. Asshole.