4 ms·
My translation: labeling an engineer as 10x may be mis-attributing the discrepancy to individual people, when the causes are most often environmental. Sure, the
by dahart 11y ago
My translation: labeling an engineer as 10x may be mis-attributing the discrepancy to individual people, when the causes are most often environmental. Sure, there are outstanding performers and catastrophic duds every once in a while, they do exist. But more often than not your performance is less a reflection of innate skill and more a reflection of things like your managers, your situation and motivation, your momentum and familiarity with your tools, the mood in your office, your level of ownership, etc., etc..
I have been both subject and observer of situations where someone's performance was amazing in some cases and lacking at best in others. I have experienced being 10x when the situation was right, and 0.5x when it was wrong.
So how do you make a 10x environment on purpose? I've tried on teams I've led, and it is by no means easy. Can anyone with concrete experience share reliable tips?
- johansch 11y agoCulture/environment is a critical enabler, but alone it doesn't create 10x people.
- danharaj 11y agoIt doesn't matter if you're a 10x peanut butter sandwich maker; no one is 10x all the time. There are projects, and there are chores. Everyone wants to work on the projects all of the time, but that is wasteful. When one is productive, they should work on the projects, and when one isn't productive, they should do the chores. That's a habit that can be learned. The only person who knows what they should be working on is themself. So, autonomy is important. You can't have a person with a habit of using their time most effectively who also isn't in charge of when and how they spend their time. Self-management is a skill that can be taught.
- rm999 11y ago>So how do you make a 10x environment on purpose? I think there are two necessary parts: 1. A high level, well-known, agreed-upon plan. Everyone needs to know what they're working towards, why they're working on it, and how they'll do it. This lets people work largely autonomously but towards the same goal, reducing friction. I've been a 0.5x engineer because my manager told me what I needed to build but not why. So, I'd build something, and the feedback would be "no, that's not exactly right, just do it this way". What could have taken an hour would take days while I slowly figured out what he was imagining. 2. As few blockers as possible. Use tools and languages the whole team knows or can learn well. Create a collaborative environment where people can ask questions instead of spending hours working through tiny issues. The manager should make removing external blockers one of their highest priorities. This is what allows people to work at peak efficiency. I think when there's nothing holding them back, most good engineers are "10x" engineers.
- boomzilla 11y agoGreat points. One thing I would add is to pay a lot of attention to your team's dynamics. One bad (or just not as engaged) team member could derail the whole team's morale. Friction should be dealt with immediately, even if it's really minor.
- xyzzy4 11y agoWork with easy to understand frameworks, and don't try to link together tons of complex systems that are hard to configure and require outside support. Don't have nitpicking code reviews. Don't have complex and bureaucratic process rules for code check in. Don't have build and test environments that break all the time. Don't have too many meetings. Don't have deadlines or ETAs for engineers, this makes them stressed out. Allow for flexible work hours.
- bguthrie 11y agoI think that talking about a 10x engineer or 0.5x engineer misses the right optimization: good software is built in teams, so build a strong team. Cross-skilling, pairing, and blocker removal all help give people a collective sense of commitment and autonomy: you have the right to touch the systems you need to accomplish your job, and it's my job as servant-leader to remove whatever's stopping you. But you have less leverage and less resilience without that sense of collective ownership. I've likewise experienced both 10x and 0.5x situations. The latter invariably arose from sitting in a corner, divorced from context or support. The former is extremely rare and I've only achieved it on personal projects. But I'll settle for a motivated and healthy team of 5xers any day.
- maxxxxx 11y agoI think we should strive to avoid 0.1x environments. I work in a cube farm and there are plenty of days when my neighbors are so loud that my productivity goes to 0.1x or less. When I work at home on Fridays I often get more than than during the 4 preceding workdays. Add to this constant meaningless meetings where everybody is late and unprepared. I often hear "I will work tonight or on the weekend so I get things done". I don't understand why everybody seems to accept that the workplace environment is bad and nothing can be done. I have raised this to senior management quite a few times but they just shrug their shoulders.
- 50CNT 11y agoI think it's a autonomy thing. People that care about their work will care about their work environment, and they're the best stewards for getting that kind of work environment in place. They've got the tightest feedback loops after all. This seems to conflict with ease of management, which might be why this kind of autonomy is rarely granted. Cubicles are cheap and easy to manage, having 50 different environments in a 50 person office and resolving conflicts between them is not. There's some approaches that partially address this problem, for example "Work from home", which whilst allowing some workplace customization has a number of drawbacks. I guess the simplest way to go about it from a strictly physical (eg. excluding communication channels) work environment standpoint would be to give people a space and money budget, and treating them like responsible adults with it. "want to wall in and sound-proof your space? sure". "Need 2 different office chairs for your back problems? Put it on the list." Set a suitable budget cap per person, divvy up available space, and optionally set up a position that handles ordering of things and tracking of funds spent. Historically speaking, very senior employees get to do this with their own office to a degree. But the output and impact of good software engineers might warrant the same kind of autonomy. It may be a considerable leap of faith from a management standpoint, but there's some absurdity in managers trusting engineers with business critical systems, but at the same time being concerned about their ability to pick a desk and chair to seat their butts upon. Then there's the thing with open offices, but that's a cost of communication issue, signal-to-noise ratio kind of thing. Talking in an open office is broad-spectrum and cheap for some of the participants, but information conveyed is not necessarily valuable in the greater scheme of things, in addition to incurring attention costs for everyone else. It's like radio without the FCC or everyone communicating over the broadcast address in a network.
- dustingetz 11y agoPair programming, I think, can lead to a 10x environment, if the culture is built around pairing.
- vikiomega9 11y agoHow has pair programming worked in your experience?
- dustingetz 11y agoi am infinity better with a pair (can solve problems i cant solve alone) but you have to build the company culture around it. i am a founder, I pair with my partner, we think we can scale the company this way. You can't force it into an existing company. You hire different types of people when you're pairing full time, and that's just the tip of the culture iceberg.
- randallsquared 11y ago> You hire different types of people when you're pairing full time Yes, extroverts, specifically. :) Even if you've been close friends with someone for twenty-five years (as is the case with someone I pair with for some problems), there's still a fair percentage of your thinking that will have to be focused on social stuff: putting expressions on, conversational behavior, avoiding asides that take a second to think but would require a minute to explain, etc. These are things that tend to occupy the same mental space as where I am thinking about the context of the code I'm writing, and while pairing can bring back some of that contextual thinking in the form of the other person, the bandwidth is so much lower that pairing seems useful mostly for learning, or for sharing a problem that I've already struggled with (so that my deepest thinking about the problem happened while I didn't also have to run sociability at the same time).
- deleted 11y ago[deleted]
- deleted 11y ago