Here are the slides from my TacoConf talk on “Anarchism for Fun and Profit”.
As is so often the case, a lot of great ideas and concepts were left out to make the story seem more straightforward, and to keep it in the time allotted. I attribute a lot of things to Drucker that were actually developed by a lot of people at the time, and cut out this whole section about Walt Disney, and several other anarchist thinkers. Max Stirner was just one of several relevant continental philosophers on the topic, etc.
Think of this work as a tease, and let it motivate you to go out and learn more.
I’m here today to talk to you all about Anarchism for fun and profit. Usually, the way we use these words, what we really mean is:
play and work. and as I’ll hopefully convince you by the end of this, what we typically think of as play or relaxation is just a brief recovery from what we call “work” which is actually bullshit.
This is what we ought to be doing.
So, I’m gonna give you a little bit of history, mostly to put these ideas into context. Then, I want to talk about how this applies to work, and some things I’ve observed in the world of software development.
Let’s start at the beginning.
"Anarchy" what does that actually mean? It’s not just a slogan for punk bands, but it’s also a pretty broad topic. The definition is right in the word:
"An" meaning "no" or "without"
"Archy" meaning ruler.
So, anarchy is the lack of rulers, hierarchies, and so on.
So, who runs things?
Basically, we all do
Of course, there are degrees of things. But typically, anarchy implies that associations are voluntary rather than forced, and that each person has control over themselves rather than being controlled by someone else.
A lot of this goes back to a guy named Max Stirner. Well, actually named Johan Schmidt. He wrote a book called “The Ego and Its Own”.
One thing that strikes me about Stirner was how similar his lifestyle is to some of ours. They had this philosophy discussion group back in the mid-19th century in a wine bar in Berlin.
Karl Marx sat in on a few of their sessions, Bruno Bauer, Friedrich Engels, and a bunch of other names you’ve heard of if you got a liberal arts education.
In this book, he said that the individual is consumed and overwhelmed by ghosts and illusions. In order to attain Right Action, these ghosts must be left behind.
Here’s a quote that I think sums up what is so interesting about knowledge workers when they’re really working at their best.
So, in other words, he wasn’t writing because it was his job, he was writing because it’s what he does. He is a writer, and he can’t find out the end of the story unless there’s someone to tell it to.
In this passage, he’s almost half-apologizing for inflicting the truth on society, because he fully expects it will incite revolutions; at the same time saying, “Well, I need to find out the end, so… deal with it.”
More in the modern age,
Bob Black is an American anarchist author, one of the most visible members of the “primativist” movement. He’s been criticized for being a “lifestyle anarchist” which is basically a fancy academic term for “crazy person”.
And, certainly, he’s a little bit kooky. But! He wrote a really interesting essay, in his spectacularly bombastic style, called The Abolition of Work. If you aren’t a fan of that style, there’s an essay called In Praise of Idleness by Bertrand Russell, which hits a lot of the same points, but is less confrontational.
He wrote this back in the 80s, and the central thesis of his whole ideology is that we work too much. Back in the hunter gatherer days, he says, people actually didn’t work nearly as much as they do today.
A lot of the work we do doesn’t actually have to be done. And a lot of the time we spend at work, we’re not even really working, we’re just sort of fucking around, hoping our boss doesn’t see us fucking around, because in reality, humans can’t be productive 100% of the time, and humans can basically never be productive doing something they hate.
A choice quote from his essay:
You should go read the essay.
So instead of being our best, and enjoying our time, and feeling happy, we get into this cycle of anxiety, guilt, and boredom. Our tasks are boring, so we have a hard time focusing on them, so we don’t get much done, and then we feel guilty, and are anxious that our bosses will find out and we’ll be punished somehow. This anxiety and boredom prevents us from ever achieving that glorious Csikszentmihalyi “flow” state where we have good ideas and feel great.
So, now that we’ve covered the 19th century philosopher anarchists, and the modern day hipster anarchists, I want to switch gears and get a bit more serious here.
How do we make work not sucky?
You really can’t talk about working and management in the modern era without mentioning this guy, Peter Drucker. It’s really rare to look back at someone from a few decades ago, who was writing about the future, and just go, “Yeah… he was right. Dude totally called it.”
He was born in Vienna, and grew up sort of just all over Europe in the years after WW1, eventually moving to the US in the 30s. He was influenced at a early age by Keynes and other economists of that time, but he wrote that he was more interested in the behavior of people rather than the movements of commodities, which is what economists usually focused on.
Viewed now, in light of the science of behavioral economics, it’s clear he was really on to something. Tversky and Kahneman really went on to define that field, but I don’t have time to talk about them. His career basically took off with the work he did at GM.
CONCEPT OF THE CORPORATION
GM, the car company. Drucker was fascinated with the concept of authority, and really believed that making the world a better place would have to be done by the managers running companies, since they held so much power over so many people.
GM hired Drucker to do an extensive analysis of their organization, and from 1943 to 1946, he did just that, resulting in a book called “Concept of the Corporation” which detailed the structure and politics of General Motors, and also delved into its effects on society at large, from the point of view of the political machinations and teams within the organization.
See, up until then, management literature usually focused on a very top-down model.
The idea is that you have a leader, and he has some subordinates. You tell your subordinates what to do, and they do it, possibly by delegating parts of their tasks to their subordinates, and so on. So, the question was, how do we draw this tree so that it is the most effective, and how do we deliver orders that will be followed effectively?
It’s a nice simple model, and it’s probably how most people would go about explaining “The Organization” to someone who wasn’t part of it.
But Drucker’s approach was completely different. He did investigate and explain how GM was organized, and praised them heavily for what was definitely a very scientific approach to developing management techniques and structures.
However, he also showed in this book that this hierarchy is only the tip of the ice berg of what actually happens. In actuality, those captains (or directors, or whatever) talk to one another, and also talk to the sergeants and privates in other departments, and so on.
He noticed that there was all this cross-department interaction, and that the political hierarchy actually got in the way. He suggested taking advantage of this, by structuring the company more like this:
A less hierarchical organization structure, where each business unit would be run more like a separate company with its own autonomy, and the ability to freely communicate with other business units.
Well, that was not taken well at GM, and his book was banned at the company. What’s super interesting is that the Japanese car companies did follow Drucker’s advice and restructure, and proceeded to take advantage of the benefits that Drucker predicted.
This was pretty early in his career. Again and again, the theme runs through Drucker’s work: Decentralize, push decisions to the edges of the organization, plan on changing direction when the environment changes (he called this “planned abandonment”)
What is most fascinating about Drucker, really his “crystal ball” moment, in 1959, in a book called “the landmarks of tomorrow”, he coined the term “Knowledge Worker”
THE LANDMARKS OF TOMORROW
Drucker predicted that the “Blue collar” worker would soon be a thing of the past. Increases in mechanization would eventually increase the productivity of a single manual laborer to the point where we just don’t need people doing that.
He also predicted that the manual labor that is still required would be outsourced to countries in the process of developing their infrastructures in the context of all this increased mechanization.
Society would increasingly rely on what he called “Knowledge Work”, or occupations where people think for a living. Whereas the 20th century is characterized by an increase in efficiency of manual work, the 21st century would be dominated by those who can properly understand and leverage Knowledge Work.
Managing knowledge worker productivity is hard.
The biggest problems is that it’s not even really clear what it is they’re doing. If you have a manual laborer, and his job is to make widgets, you can just count the widgets at the end of the day, and there you go.
But, somewhat by definition, a knowledge worker isn’t making the same thing over and over again, and the means of production is not a machine, but their brain, so we have to define the task, and often defining the task improperly can change perceptions and inadvertently reduce productivity
Once upon a time, you’d either go to school, or not, and then go to a company like GM or ALCOA, or whatever, that existed for as long as you could remember, and you’d climb a nice little ladder, or stay at the bottom, and after 50 years or so, you’d retire.
Well, with Knowledge Work, because it is unstable by its very nature, since the same knowledge doesn’t need to be created repeatedly, many of us — in fact, most of us — will have careers that long outlast the companies we work for. Or, if not, if it’s a google or apple, something with some staying power, by the time your career is over, it’ll be a whole different company, making different things in different ways, etc.
In fact, the industrial revolution had already started this wheel in motion. The information revolution has just accelerated it to the point where we can actually watch it happen in real time.
I’ve worked at a bunch of companies, even technology companies, that still seemed to be stuck in the last century, and didn’t quite “get” what makes knowledge workers work.
I’m sure there are a few people out there who just want to put in their 8 hours like Neitzsche’s Last Man, “earn a living and keep warm”. The rest of the knowledge workers are working to make their jobs obsolete.
Just as the 20th century was devoted to increasing the productivity of manual laborers to the point where a lot of manual labor simply didn’t need to be done, today’s technology is making a lot of inessential knowledge work go away. Already, many tasks have been replaced by software.
As Drucker repeated again and again in his work, if you take away the autonomy of knowledge workers, you take away everything that makes them valuable.
Huge fan of this guy. I think if I had to pick a favorite person I’ve never met but hope I someday do, it’d be Merlin Mann.
Merlin Mann’s history is somewhat interesting, and I think parallels the trajectory of a lot of reasonably successful modern-day knowledge workers. He did some web stuff, moved to california, worked at a few companies, pretty much hated it, and then ended up finding a niche where he can do what he’s really passionate about.
And that is basically to do podcasts and make dick jokes on the internet, but also he goes and talks to companies about how they’re literally murdering the souls of their employees.
In a lot of ways, Merlin Mann reminds me of Peter Drucker, but instead of spending 3 years writing a book to piss off one company, he goes around and talks at companies that never ever invite him back.
A lot of his work focuses on being a better knowledge worker, but also basically behaving like grownups in organizations.
This is one of those things that’s really easy to think you understand, but really hard to actually get, especially for managers.
Even in a lot of places where they’re are ostensibly trying to empower teams, at some level, priorities are still being handed down to them by people who are under the impression that writing a date on a spreadsheet is some sort of contract with the universe.
What this ultimately comes down to is that there are a lot of little unreasonable assumptions and expectations we place on one another without even realizing it.
Managers can say, “Yeah, check email less, reduce communication overhead, work at a sustainable pace, don’t be interrupt driven”, but then when you try to explain what this means: that your employees will only check their email once per day, meetings should have the minimum number of people in them, and so on, they laugh at you like you’re a crazy person.
In my own life, I’ve been unemployed a few times. I’ve been poor, though I was lucky enough to be educated and to have a great support network. I’ve worked for tech companies, and sold vacuum cleaners and other things, I’ve answered phones. Not having a job when I needed money was probably the most stressful time in my life.
But, for a few months in 2010, I didn’t have a job, but I didn’t actually need one. I’d worked at Yahoo for 4 years, and got sort of sick of it. So, I planned out how long my money would last, and decided to see what would happen if I just didn’t have an employer for a while.
I highly recommend knowledge workers do this, at least every few years. I didn’t even realize how burnt out I’d become, and those few months of idleness, well,
it just doesn’t really make much sense to call it “idleness”, since it was one of the most productive times of my life.
Why be productive when you don’t have a job?
Of course, I don’t want to make it seem like jobs are necessarily bad things.
A lot of times, a company gives you access and opportunity to do the things you’re passionate about, and that’s when it’s awesome.
But what really struck me about that time was how I felt so much more motivated to work on node than I ever had felt on any project before. And as I looked around the node community, it seemed really interesting to me in those early days that everyone was working their asses off, and loving it
I don’t know if who first coined this term, but I’ve sometimes referred to the Node.js ecosystem, and particularly the npm registry, as a “mostly anarchic dictatorship”.
That is, there’s definitely leadership, but the leader’s role is shrunken down to almost nothing. Because we built a decent module system, and node provided APIs that were easy to extend, little fiefdoms and satellite projects spun up.
So, it’s maybe not “anarchy” in the purest sense, but it’s about as close as we can get. Anyone has the opportunity to leave and do their own thing, and the leader’s role is mostly just to help everyone out, not to tell them what to do.
The awesome thing about working on an open source project like Node is that it is an anarchy with one dictator who is really answerable to the rest of the community. The leader doesn’t have any control over a person’s income, so if you want a person to work harder, well… you have to make it enticing.
This means that we have to plan for occasional outages, or for people losing interest randomly and disappearing.
The payoff, though, is that people actually have a sense of ownership of what they do, because they’re endowed with a sense of agency, and that attracts more people to come help, and when they’re done with whatever it was that was distracting them, they tend to come back.
Dan Pink has a great talk on this, where he goes through lots and lots of evidence and reproduced studies. The more people feel like they’re in control of what they do, the more than that they are connected via social ties, the more respect they are shown, the better and more creatively they can perform.
It’s not about how many hours you spend in an office. It’s about what you get done, and how good it is.
A lot of times, I think teams tend to forget what their mission is. Or, worse, they may not have ever had one.
It’s definitely helpful sometimes to have meetings or estimate when things will be done. Anarchy isn’t “everyone run in a different direction” (or at least, that’s not very useful or fun most of the time.)
But I’ve worked on a lot of projects where I would have sworn that my job was to pull bullshit estimates out of my ass about ill-defined product features just so some managers could massage the bullshit numbers into bigger bullshit numbers and hand it off to some other manager.
Which really highlights the point that we need “leaders, not managers”
It’s a pretty subtle distinction. But, the verb “lead” really implies a much more active role, and an assumption that we are actually going somewhere. “Managing” means we’re just kinda keeping everything in place.
The person who is ostensibly in charge of a team of knowledge workers needs to be a person who takes on a lot of group-helping tasks, but also is intimately involved in the project. Most of their job has to be to listen, not to tell. Because knowledge work happens best when it’s fun, and > fun cannot be forced
fun cannot be forced.
People work better when they’re having fun. So, this means that you have to let them work on things they care about, help them find good things to work on, and mostly stay out of their way.
So, I’m way over my time limit here I think, but if anyone wants to talk about any of this stuff, I’ll be around. Thanks!