|
|
|
|
|
by andrew93101
5143 days ago
|
|
I think the successfulness of open space plans depends greatly on the work you're doing. If you're working primarily alone on difficult engineering problems, with well-defined specifications and a clear division of who owns what part of the code, then (from my experience) solitary offices are more productive. Communication doesn't need to be as high-bandwidth, and concentration needs to be deep. On the other hand, there are many environments that are different. If your organization intentionally has low-fidelity product requirements, the cost of communicating with business stakeholders needs to be low. If you intentionally eschew code ownership, engineers will frequently be working in areas of the codebase they haven't worked in before and need to talk to colleagues who know it better. Open plans make concentration harder and communication easier. Closed office plans are the reverse. I think no office plan is "better" than the other, but rather our office plan should fit the work style of your organization. |
|
The real reason for cubicles and open floor plans is that it makes the bean counters happier. Everything else is rationalization, IMHO.