5 ms·
re: " These days we also have an NYC office, but we refer to it as "the Internet cafe", about 20 of our 70 people "so happen" to work out of there regularly..."
by chiefalchemist 8y ago
re: " These days we also have an NYC office, but we refer to it as "the Internet cafe", about 20 of our 70 people "so happen" to work out of there regularly..."
It would be interesting to know:
- How many other distributed companies have a similar arrangement (i.e., a non-distributed "HQ")?
- Does this make employees more productive and/or satisfied?
- When on the journey does it make sense to transition from centralized to distributed?
- Are distributed orgs more (or less) likely to outsource commodity-esque (e.g., bookkeeping) services?
- pixelmonkey 8y agoOur onboarding materials explicitly say, "NYC is not HQ". And it's not HQ. It is just an office we leased because we ended up with 10+ staff in NYC and they preferred an office to a co-working space, for security/privacy. (If you've ever lived in NYC, you know it can be challenging to have a home office at any reasonable cost, due to typical square footage of living spaces. That's part of the reason I left NYC.) We are a Delaware C-Corp. Yes, we have our mail sent to NYC, but that's for the lawyers/accountants. As for the NYC staff, they find that one "problem" with the office is that it has a "library atmosphere". I personally don't think that's problem, but I am the CTO and an engineer, so I prefer quiet & focus. Some people expect an office to have "energy" and ours is definitely lower on that scale. I try to remind people that "the web is our office and the front door to that office is your internet connection." Are people happier in our NYC office than on our remote team? Hard to tell, but the NYC folks complain about commuting a whole lot, and often take the occasional work from home day to spare themselves of it. I never hear those complaints from the other staff. I guess one benefit of the NYC staff is that they can have happy hours and dinner/drink outings, which inspires some jealousy on the non-NYC team. We make up for that by throwing annual and semi-annual team retreats. Our last two were in Upstate NY at a writer's retreat campsite (really fun getting to know everyone over campfires and s'mores) and the one before that was in Reykjavik, Iceland, where we rented out a whole hotel and got to know each other on city and countryside excursions during 23 hours of daylight! Where on the startup journey does transition to distributed make sense? Well, for us, day one worked! We reversed the typical evolution. We were 100% office-free for a few years. Then, in 2012-2013 or so, we got an NYC office, after a frustrating experience with a sub-leased co-working space for the NY staff. But we refer to it as the NYC internet cafe, not HQ. I think that is healthy for teams like ours. Are distributed teams more likely to outsource stuff? I dunno, probably. We outsource commodity accounting/legal/payroll/benefits services, but we have an in-house finance/collections team. We also outsource PR, cloud hosting (obviously), and we use a lot of SaaS services.
- chiefalchemist 8y agoThanks for the details. Just to clarify, "HQ" was in quotes, in an air quote sorta way :)
- shanghaiaway 8y agoWould be interested in seeing a write up on your services stack.
- briandear 8y agoBasecamp does it that way I think.
- ljm 8y agoOne such place I worked for had the non-distributed HQ and it housed the execs and some of the local team (being non-specific here on purpose). I switched from working remotely to working locally, which involved a change of country, and I realised that I couldn't justify my own position after that. As far as it goes with productivity and satisfaction, I thought the decision to go half-in on remote was a mistake. My take away was that a startup does not necessarily have the maturity to maintain the balance between local and remote while also focus on making things happen. It was totally a setup that was so advantageous to the staff that the business itself suffered, as I saw it. In those terms, you get a reprioritisation or a negligence and productivity suffers because you've just resigned to the reality that it's really hard to manage it all. Yet still, you feel entrenched so the best you feel you can do is to just... do nothing. I would say that a small startup depends on fluid interaction between founders and the various 'makers' on board who help fulfil the vision. If you're 50/50 on how you facilitate that then you get a lot of mediocre when you could have had one solid thing and your foundation is built upon a compromise. If I found myself in a leadership position in such a scenario again I would hope that I could stomach the firing act and invest in the culture that suited us best. But I don't think that's so easy to do with a small team.