4 ms·
>Corporate culture isn’t your company’s ping-pong table. It’s not your catered lunch. It’s not the posters you tape onto the office walls. A real culture is
by hkmurakami 14y ago
>Corporate culture isn’t your company’s ping-pong table. It’s not your catered lunch. It’s not the posters you tape onto the office walls. A real culture is the cumulative effect of productive relationships among employees. Those relationships can take years to develop. And they don’t always work out.
Probably the best statement on culture I've read recently.
- cuppy 14y agoI actually wonder if this means that SF-based startups (or those who are blindly following this 'culture hacks' mentality) are actually worse places to work overall? I wonder if focusing on the quick fixes like free lunch, company trips & ping pong tables ends up outweighing REAL company culture in terms of ROI.
- encoderer 14y agoHave you worked at many non-sf-startup companies? Just because you don't have foosball and catered lunch doesn't mean you're doing squat to build a "culture."
- jmspring 14y agoThere are a number of people out there who have a very rigid view of what "startup culture" means. I've seen it in first time as well as repeat entrepreneurs. Often they thing hard work, spending free time together, need the perks, everyone will always have the same rah-rah approach. People have lives, hobbies, different interests. The best companies are those that have a management team that embrace peoples differences, nurture where needed, give space where appropriate, and cultivate a culture where people feel like they are contributing in the way they best can and allowing them paths to grow.
- rhizome 14y agoMy sense is that non-SF startups can be inclined to ape these "features." Not all of them, of course, but I've certainly seen it in at least a couple of cases. I mean, here we all are reading about them, right? Lots here don't live in SF, but do take their culture cues from whatever information sources they have. "This is the way they do it in the old country."
- jonnathanson 14y agoPerhaps, but I think we're missing a crucial point of the article, which is that the culture needs to match the employees. For a startup that wants to hire a bunch of college grads, company trips + ping pong tables + Call of Duty + Friday keg sessions may actually increase productivity. Conversely, for a company trying to hire older, more experienced employees, such perks are considerably less appealing. I think the general takeaway here is not that X is inherently bad, or Y is inherently good. Rather, it's that you need to know yourself, know the culture you're trying to create, and know the people you're trying to hire, rather than trying to imitate whatever perks happen to be trendy at the moment.
- pm90 14y agoAbsolutely. I hope more companies take note of this and stop trying to blindly ape what Google/Facebook are doing. Not only does it result in a better environment, but -and arguably this is more important- its what makes you unique
- hkmurakami 14y agoOf course it is much easier to demonstrate and sell free food, ping pong tables, couches, posters, etc. It's much more difficult to communicate and sell your culture to the people you are wooing. Perhaps we as applicants really need to take the initiative in calibrating ourselves to look for such culture fit. (Having worked at two places now, I now see this as my top priority that I'm willing to trade in 10~20% of compensation for. Hopefully I can act on these words!)
- samstave 14y agoExactly, and honestly, this is something that more experienced people will see immediately. The "culture icons" of the first bubble are actually red-flags in some situations. There is a balance of providing real perks, while being on a startup budget, and using fake incentives to lure in talent. The fact is that you will have both long-houred positions and people who will work 8-5 only. Both are valuable employees, and their commitment should be based on their productivity and value - not in how much free/extra time you can get out of them. As people get older, they have kids and they have out-of-work priorities. This does not make them less of a person/employee/resource. If you require your employees to work ~12 hour days - then maybe you should be able to actually pay them for each hour of work.
- Swizec 14y ago> If you require your employees to work ~12 hour days - then maybe you should be able to actually pay them for each hour of work. You are also very likely doing something terribly wrong and your employees aren't being very productive.
- thisisrobv 14y agoI don't have any data to back up this theory, but I believe that the trend towards less recreational benefits is due to an aging engineering talent pool. But until we make this jump as an industry we'll continue to see ping pong tables and ddr machines. It won't happen quickly but I believe that the median age of engineers will dramatically increase in the next decade. We won't be looking for ping pong tables, we'll be looking for day cares.
- greghinch 14y agoIt seems like you are implying that current and soon after generations of young folks aren't going to be entering the engineering/software trade in droves. Considering that's where a lot of the well paying, available jobs are currently, it seems like everyone and their sister will be vying to become developers
- InclinedPlane 14y agoOne thing a lot of employers and managers don't realize is that humans aren't cogs. The general model of employment is that you replace a given human in a specific role with another human in the same role, just like replacing cogs. The real world doesn't work that way though. In reality everyone brings a different set of skills and passions to the table. And the way person X does job Y is going to be very much different than the way person Z does job Y. And sometimes this can be significant enough to where you can't actually replace person X with person Z directly. What you're doing is building a machine with parts that are all different, and if you have to replace a key part often times you will need to completely restructure the machine to make it work well again. Meaning, sometimes you might replace one person with several people who do different parts of the job. Or you might replace one person with a new person who now also does the job of current employee person W, who's know redundant. Teams are complex beasts, and they get more complex the more talented people are in them. Managers need to be very mindful of those complexities when they form or change teams.
- hobs 14y agoThis is why managers are so obsessed with process and documentation, because they have a vain hope that they can replace people by just having someone following a process.
- yardie 14y agoNo, they want documentation because humans are mortal and selfish. Whether you leave the company by your own free will or in a body bag someone has to pick up the pieces and resume where you left off. Documentation means I can take a vacation and know things at the office will be fine. If this also means I'm replaceable, so be it.
- benjamincburns 14y agoIt's both. No documentation is irresponsible. An over emphasis on 'repeatability' through exhaustive process and product documentation (and strict adherence to said process) is a red flag in my book (in most situations). To me it either means that the employer is worried about its employees walking (as you suggested), or that the employer wants to minimize the effects of discarding the employee. In the first case, it's a self-fulfilling prophecy. In the latter case you'll achieve what you're after, but not how you planned. Instead you're minimizing the current value and productivity of the employee, meaning that when you fire him/her, the impact will be minimal. The moral of the story? Limit the scope of your documentation, and place high emphasis on that limited scope. Instead of worrying about how you'll replace someone when they're gone, worry about whether or not you're putting them in an environment where they can perform to the potential of their unique abilities as an individual. (And don't even get me started on the whole "No documentation is better than bad documentation" thing.)