This the first in a sequence of posts about “operations”.
Acknowledgements to Malo Bourgon, Ray Arnold, Michelle Hutchinson, and Ruby for their feedback on this post.
Several years ago, I decided to focus on operations work for my career. From 2017 to 2019 I was one of the operations staff at the Center for Effective Altruism, initially as the operations manager and later as the the Finance Lead. Prior to that, I was a volunteer logistics lead at approximately 10 CFAR workshops; I also ran ops for SPARC twice, and for a five day AI-safety retreat. I also attribute some of my ops skill to my previous work as an ICU nurse.
I have spent a lot of time thinking about hiring and training for operations roles. In the course of hiring I have had numerous conversations about what exactly “operations work” refers to, and found it surprisingly hard to explain. This post, and the rest of my operations sequence, will be an attempt to lay out my current thinking on what these roles are, what they have in common, and what skills they lean on most heavily.
Operations work, or “ops”, is a term used by organizations like 80,000 Hours to refer to a particular category of roles within organizations.
I don’t think that “operations” as used in this sense is a single coherent thing; my sense is that 80,000 Hours is gesturing at a vague cluster that doesn’t completely carve reality at the joints. There isn’t a set of defining characteristics shared between all operations-type roles, and many of the attributes described are also found in other roles. However, I do think this is a useful shorthand that points both at a set of functions that need to be filled within organizations, and the skills that are necessary to carry out these duties.
It’s worth noting that this use of the word “operations” does not seem to be standard outside the EA community. In large companies, it can sometimes refer to e.g. the production side of manufacturing, or to supply chain logistics, whereas the internal admin roles are called by their individual job titles (Finance Manager, HR Manager, etc). I do think it makes more sense to carve out the “operations” cluster for small organizations, where the internal support work is more likely to be done by a single person or team rather than a multi-part bureaucracy. In smaller orgs, operations/admin staff often wear multiple hats since there often isn't a full-time work for a role in just finance/HR/etc.
80,000 Hours: “Operations staff enable everyone else in the organisation to focus on their core tasks and maximise their productivity.”
My sense is that roles in the ops cluster usually fill the following functions:
Ops roles can vary widely on both seniority (responsibility and autonomy, skill and experience required), and specialization. In my thinking, the most central ops role is the “operations generalist” or “operations manager” at a small organization (10-20 people).
My knowledge about this area is limited, but my sense from talking to others is that some software jobs (devops, sysadmin, internal tech support, etc) perform similar functions, in terms of helping to support and enable other staff and maximise their productivity. However, in this sequence, I’m not including these roles in the “ops” cluster I’m trying to point at, since they require specific technical skills.
80,000 Hours: “operations staff are especially good at optimising systems, anticipating problems, making plans, having attention to detail, staying calm in the face of urgent tasks, prioritising among a large number of tasks, and communicating with the rest of the team.”
Of course, the skills described here are useful in almost any job, not just operations roles, and can tend to sound like “just being generally competent.” I do think that jobs vary widely in terms of what skills are most load-bearing, though, and “ops” is a cluster that relies especially heavily on these skills as opposed to others such as technical ability, writing talent, aptitude for deep work, etc.
My sense is that many of the skills being gestured at when describing someone as “good at ops” fall out of a certain type of attention pattern, which I describe below. I am particularly trying to contrast this style of thinking with the “deep work” attention pattern that is most useful for, e.g., research.
There are some other skills that might or might not fall into the same cluster, but that I think are also particularly key.
The rest of the sequence will go into various aspects of this summary in more detail. Future posts will cover the following topics:
Before working in operations, I was a nanny for many years. Before that I was doing research while in grad school. I've always been bemused by the differences between the way people perceive and treat me in my various roles over the years.
Particularly, operations jobs (and childcare jobs) are possibly not a great idea for people whose identity is strongly centered around being (perceived as) intelligent:
Most of your work isn't the sort of work that proves how smart you are. Coworkers expectations of your intelligence will be much lower. The skills you need run towards conscientiousness and agreeableness, which are traits that people stereotype as correlated with lower intelligence. Because your tasks are so wide ranging, there will always be things you are brand new at, therefore less competent at.
I've pushed my identity over the years more into being "a responsible hard worker", so that people's opinions of my intelligence don't feel meaningful at all. Given that I feel the need to have SOME sort of identity, this seems like a more useful one. Identifying as "smart" can't do anything to change my underlying g factor. But identifying as responsible and hard working is likely to actually make me behave in those ways.
I'm mostly bringing this up because LW readers often highly value being regarded as intelligent, and it might be a thing to take stock of before aiming for a new career in operations.
This is, unfortunately, kind of true in practice. (Although, ideally, is and will become a bit less true at major EA orgs - CEA was pretty good on this dimension and I never felt like people saw me as less intelligent, although that could be because it's less a part of my identity so I didn't notice).
I do think that ops work, especially the finance & accounting aspects, is pretty G-loaded, and that people wrongly perceive this as not the case. Anyway, I hope to discuss all of this more in a later post about the personal fit aspect.
(1) This post is awesome. I agree. I'll dive in later to apply guidance. Ops are awesomely powerful and underrated by a lot of abstract thinkers ("blah, those are just details" effect).
(2) Ready to have your mind totally blown?
Here you go —
That is a pretty interesting article, thank you!
I asked for posts like this not 24 hours ago, and here one is. It's a Petrov Day improbable!
This post was an excellent introduction into what an operations job or role looks like and feels like from the inside plus touches on what other people think (especially if they aren't in operations) think of operations roles and the people working such jobs (hint: they tend to look down on such roles and individuals, especially if they hold a "socially higher status" and/or intellectual type of job). Reading it helped me realize that my previous job was in fact a very high autonomy operations role and that's been helpful in emotionally processing what that job was to me, what I experienced doing it, and whether or not I want another operations job in the future.
I'm nominating it for the above reasons mostly, but also because I think LessWrong could really use more content about operations type jobs / roles. You can have as many people talking very intelligently about something as you'd like, but until someone gets their hands dirty and does the operations work to spread those ideas, book a venue, publish a book, organize a community, manufacture something novel and innovative, and much much more, then those ideas are nice, but they stay fairly locked up where they originated and don't get broadly dispersed, thus making them much less helpful / useful than they could have been.
It's one thing to have a small niche community with unique and new ideas, but it's quite an entirely other beast of a challenge and accomplishment to spread said ideas more broadly, to "go viral", and have an outsized impact on the world beyond small local improvements. The aforementioned small niche community is nice, I like it, feels good to be a part of, but if that community or individuals within it want to globally instead of hyper locally "decrease worldsuck", "do good better", "raise the sanity waterline", "create dath'ilan", etc. etc. etc. then they had better get good at operations and start organizing.
Ideas run the world but operations keep them running and help them grow :) I'd love to see a full sequence on operations such as what Swimmer963 mentioned at the end of their post.
P.S. I think these yearly reviews are good examples of smart operations at work and they help us as a community become more organized with our ideas, reflect more, open more space for improvement, etc. My paragraph about the niche community vs imagined larger robust good at operations and organizing community was not meant to be any sort of attack nor a critique. Its purpose was only to point things out that seemed good to point out :) (I think many here at LW are already cognizant of such things, anyways.)
I imagine it's like how it's not at all obvious from the outside what a "producer" does in a play or movie - but after you are part of a production, it becomes clear why one needs a producer.
(Or, if there's enough money involved that the producer is mainly a financial job, substitute the appropriate name for the person who makes sure things are working.)
I think operations and associated problems are kind of understudied on LessWrong, and I would really like to see more posts like this. Sadly, this sequence was never completed, but I do think it's outline itself is valuable, and maybe this being included in the review increases the probability of the rest of it being written.
Good reminder! It's been...quite a year for me, and I was unclear at the time on how much people were engaged with and getting out of this post, but I still have my planning notes for further content.