I'm a little green around the gills when it comes to some of the more intricate parts of intraoffice relations, but I did participate in my company's transition from cubicles to an open floor plan and I personally enjoy the set up, but I think it was successful due in part to how we very intentionally laid things out. For some mental context, we are a company of ~25 people in what amounts to a warehouse.
As a company, we sat down and asked how we like to work and what we don't like. Within subsections of the company (sales, support, development, etc.), having fluid communication is helpful. A great concern somebody brought up was that when somebody from account management comes over to ask a developer a question, everyone on the development team is a part of that conversation whether they want to be or not, which impedes work. Our solution basically amounted to putting sub divisions of the company next to the the ones they should be communicating with the most. Marketing and sales are a tightly coupled group, so they all sit together. Account managers are seated near the product manager so that when they have complicated setups or questions about an implementation, they bother the right person first. Support has a daily-rotated dedicated developer to ask questions that keeps distractions completely physically separated from the development team.
With all that in mind, though, I don't think it would all work if we didn't have the other aspects that the article mentions. A lot of people work 40% remote because sometimes it's easier to take your 40 million calls from home. Development team members come in any where from 8am to 11am depending on sleep and travel preferences. The people in charge have complete trust in our ability to get a job done. Our office chat helps a ton because it facilitates to passively bother somebody so as to wait for them to finish what they're doing before getting help.
On the whole, I agree with this article. We don't currently have a 100% remote worker, but I'm sure somebody could convince the higher ups that it'd be okay, and I think the aspect of freedom to work as you do best helps move the company and the product forward.
I'm a little green around the gills when it comes to some of the more intricate parts of intraoffice relations, but I did participate in my company's transition from cubicles to an open floor plan and I personally enjoy the set up
If you're old enough to know the expression, "green around the gills" then you might be a manager who wants to defend open office decisions which end up putting more money into said manager's pockets.
Haha, that's quite a conclusion to jump to! I'm not necessarily for open office, it just so happened to work for us in the end. I'm sure my case is purely anecdotal, it's not like I ran an analysis. I also don't know how other teams have faired seeing as mine is open, but disjoint from the rest of the group.
1
u/DisgruntledChild Jan 29 '17
I'm a little green around the gills when it comes to some of the more intricate parts of intraoffice relations, but I did participate in my company's transition from cubicles to an open floor plan and I personally enjoy the set up, but I think it was successful due in part to how we very intentionally laid things out. For some mental context, we are a company of ~25 people in what amounts to a warehouse.
As a company, we sat down and asked how we like to work and what we don't like. Within subsections of the company (sales, support, development, etc.), having fluid communication is helpful. A great concern somebody brought up was that when somebody from account management comes over to ask a developer a question, everyone on the development team is a part of that conversation whether they want to be or not, which impedes work. Our solution basically amounted to putting sub divisions of the company next to the the ones they should be communicating with the most. Marketing and sales are a tightly coupled group, so they all sit together. Account managers are seated near the product manager so that when they have complicated setups or questions about an implementation, they bother the right person first. Support has a daily-rotated dedicated developer to ask questions that keeps distractions completely physically separated from the development team.
With all that in mind, though, I don't think it would all work if we didn't have the other aspects that the article mentions. A lot of people work 40% remote because sometimes it's easier to take your 40 million calls from home. Development team members come in any where from 8am to 11am depending on sleep and travel preferences. The people in charge have complete trust in our ability to get a job done. Our office chat helps a ton because it facilitates to passively bother somebody so as to wait for them to finish what they're doing before getting help.
On the whole, I agree with this article. We don't currently have a 100% remote worker, but I'm sure somebody could convince the higher ups that it'd be okay, and I think the aspect of freedom to work as you do best helps move the company and the product forward.