𝗕𝗲𝘆𝗼𝗻𝗱 𝘁𝗵𝗲 𝗝𝗼𝗯 𝗗𝗲𝘀𝗰𝗿𝗶𝗽𝘁𝗶𝗼𝗻: 𝗪𝗵𝗮𝘁 𝗜𝘁 𝗠𝗲𝗮𝗻𝘀 𝘁𝗼 𝗕𝗲 𝗮 𝗟𝗶𝗻𝗰𝗵𝗽𝗶𝗻

After Mark, a co-founder of the entrepreneur and book club I attend, recommended Linchpin by Seth Godin to me, I started listening to it and could not stop because the book goes far beyond the idea of simply becoming good at your job. It talks about how we have been trained to work, why following instructions became such a big part of both education and employment, why we are afraid to stand out, and what it really means to bring something to our work that cannot be written into a job description.

Before going further, 𝗮 𝗹𝗶𝗻𝗰𝗵𝗽𝗶𝗻 𝗶𝘀 𝗹𝗶𝘁𝗲𝗿𝗮𝗹𝗹𝘆 𝗮 𝘀𝗺𝗮𝗹𝗹 𝗽𝗶𝗻 𝘁𝗵𝗮𝘁 𝗵𝗼𝗹𝗱𝘀 𝗮 𝘄𝗵𝗲𝗲𝗹 𝗼𝗿 𝗼𝘁𝗵𝗲𝗿 𝗽𝗮𝗿𝘁 𝗶𝗻 𝗽𝗹𝗮𝗰𝗲, and Godin uses that word as a metaphor for a person who brings value that goes beyond completing the basic requirements of a role. A linchpin is not someone who makes other people dependent on them or hides knowledge so they become impossible to replace; it is someone who can use judgment when there is no clear instruction, take initiative when something needs to happen, connect people, solve problems, create something useful, and handle the human parts of work that cannot always be reduced to a checklist.

Godin goes back to the industrial era to explain how we became so comfortable with the idea that good work means following instructions. As factories became more efficient, work was divided into smaller and more repeatable tasks, which meant a person no longer needed to understand the entire process of making something because they could learn one part, repeat it consistently, and produce the expected result. This made production faster and easier to scale, but it also created a system where individual workers could become easier to replace once their work could be clearly documented and taught to somebody else.

We usually picture this as a blue-collar story because factories, assembly lines, and machines are the easiest examples to imagine, but Godin argues that the same way of thinking eventually became part of white-collar work as well. The setting may be an office instead of a factory, but the work can still be structured around processing information, following procedures, getting approvals, completing assigned tasks, and staying inside clearly defined responsibilities, which means the tools and clothes may have changed while the expectation remained very similar: 𝗳𝗼𝗹𝗹𝗼𝘄 𝘁𝗵𝗲 𝘀𝘆𝘀𝘁𝗲𝗺 𝗮𝗻𝗱 𝗱𝗼 𝘄𝗵𝗮𝘁 𝘆𝗼𝘂 𝗮𝗿𝗲 𝘁𝗼𝗹𝗱.

Godin also connects this way of working to the education system because school has traditionally prepared us very well for structured environments. We learn to arrive on time, follow instructions, complete assignments, study what will be on the test, look for the correct answer, ask permission, and avoid mistakes, and then we enter the workplace where we receive another set of instructions in the form of policies, processes, managers, and job descriptions.

There is nothing wrong with structure because every school and workplace needs some level of it, but the question becomes 𝗪𝗵𝗮𝘁 𝗵𝗮𝗽𝗽𝗲𝗻𝘀 𝘄𝗵𝗲𝗻 𝘁𝗵𝗲 𝗶𝗻𝘀𝘁𝗿𝘂𝗰𝘁𝗶𝗼𝗻𝘀 𝗮𝗿𝗲 𝗻𝗼 𝗹𝗼𝗻𝗴𝗲𝗿 𝗲𝗻𝗼𝘂𝗴𝗵?

Godin uses the adoption of the washing machine as one example of how uncomfortable a major technological transition can be while people are still learning how to live with it. He writes that during the early adoption of washing machines, hundreds of people a year died while using them, which he uses to show that new technology can arrive before the knowledge, systems, standards, and behaviors around it have fully caught up.

Today, a washing machine feels so normal that most of us would never think of it as disruptive technology, but the people living through that transition did not know what the final system would look like because they were learning while the change was already happening. That part connects with many of the conversations happening around technology today because we often want a clear answer about which jobs will change, which skills will matter, and what work will look like several years from now, even though people living through previous technological changes did not have that kind of certainty either.

That uncertainty is one reason the idea of becoming a linchpin feels relevant now, because a linchpin is valuable not because they already know everything that is going to happen, but because they know how to respond when the old instructions are no longer enough.

One of the examples Godin uses early in the book is Albert Einstein, and he makes the point that 𝗻𝗼 𝗼𝗻𝗲 𝗶𝘀 𝗮 𝗴𝗲𝗻𝗶𝘂𝘀 𝗮𝗹𝗹 𝘁𝗵𝗲 𝘁𝗶𝗺𝗲. Even Einstein had ordinary moments, and Godin uses that idea to move the word genius away from being something reserved only for a few extraordinary people. All of us can have moments when we see a solution that somebody else does not see, explain something in a way that finally makes sense, make a connection between two ideas, solve a difficult problem, or create something useful.

Being a linchpin does not require being exceptional every second of the day.

Godin makes a similar argument when he talks about being an 𝗮𝗿𝘁𝗶𝘀𝘁, because he does not reserve that word for painters, musicians, or writers. In the book, art can happen in almost any profession when someone brings judgment, creativity, generosity, and something personal into what they do instead of simply following the instructions exactly as they were given.

A developer can be an artist when they understand the problem beyond the ticket and create a thoughtful solution rather than only writing code that technically works, a teacher can be an artist when they find another way to explain something a student is struggling to understand, and someone organizing a community can create art by building an environment where people who may never have met begin connecting and helping one another.

Godin's example of the cook and the chef explains this idea very well because a cook can follow a recipe exactly as it is written, while the chef understands the ingredients well enough to adjust, make decisions, experiment, and create something when the recipe no longer has the answer. Following the recipe is not a bad thing because there are many situations where we need instructions, but the linchpin becomes especially valuable when something happens that the recipe did not prepare us for.

The difficult part is that going beyond the instructions also means accepting more responsibility for the result. If I do exactly what somebody tells me to do and the outcome is not good, it is easy to say that I followed the process, but when I suggest a different approach, take initiative, create something of my own, or share an idea publicly, I also have to accept that someone may disagree with me, criticize it, or know more than I do.

Godin calls the part of us that wants to avoid that risk the 𝗹𝗶𝘇𝗮𝗿𝗱 𝗯𝗿𝗮𝗶𝗻.

He uses the lizard brain as a metaphor for the part of us that wants safety, acceptance, familiarity, and protection from embarrassment or rejection, and he connects that fear to our historical dependence on tribes, where belonging to the group once had consequences much bigger than simply whether people liked us. Being rejected by the tribe could have meant losing protection, resources, and support, so avoiding rejection became deeply connected to survival.

We are not living in that same environment today, but we can still feel a strong reaction when we are about to do something that puts attention on us, which is why the public-speaking example in the book makes so much sense.

You can know logically that standing in front of a group is not dangerous and still have your body react very differently once everyone turns around and starts looking at you, because suddenly there is the possibility of judgment, disagreement, embarrassment, or making a mistake where everybody can see it.

I am currently preparing for my first conference talk, so that example feels very real to me. I know standing on a stage is not a dangerous situation, but my brain can still come up with questions about forgetting something, something going wrong during the presentation, or someone in the audience knowing more about the topic than I do.

Godin describes that internal pushback as 𝗿𝗲𝘀𝗶𝘀𝘁𝗮𝗻𝗰𝗲, and what makes resistance interesting is that it does not always sound like fear. Sometimes it sounds responsible because it tells us we should prepare a little more, wait until we have more experience, earn another certification, revise something one more time, or wait until we finally feel completely ready.

Preparation is necessary, but there is also a point where preparation can become another way of avoiding the moment when we actually have to put the work in front of somebody else.

That is why Godin talks about 𝘀𝗵𝗶𝗽𝗽𝗶𝗻𝗴.

An idea can be great, but if it stays in your notebook forever, nobody benefits from it, and a presentation can be carefully prepared, but if you never deliver it, none of that preparation reaches the audience. At some point, the work has to leave our hands and enter a place where other people can use it, respond to it, disagree with it, or criticize it, and that willingness to ship is part of what separates creating from endlessly preparing to create.

Another major part of becoming a linchpin is what Godin calls 𝗲𝗺𝗼𝘁𝗶𝗼𝗻𝗮𝗹 𝗹𝗮𝗯𝗼𝗿, which goes beyond simply controlling our emotions at work. He describes it as doing the important human work even when that work is uncomfortable, and one of the lines from the book explains it clearly: 𝗘𝗺𝗼𝘁𝗶𝗼𝗻𝗮𝗹 𝗹𝗮𝗯𝗼𝗿 𝗶𝘀 𝘁𝗵𝗲 𝘁𝗮𝘀𝗸 𝗼𝗳 𝗱𝗼𝗶𝗻𝗴 𝗶𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝘄𝗼𝗿𝗸, 𝗲𝘃𝗲𝗻 𝘄𝗵𝗲𝗻 𝗶𝘁 𝗶𝘀𝗻'𝘁 𝗲𝗮𝘀𝘆.

Sometimes the technical part of a job is easier than the human part because it may be easier to fix the code than explain why an approach needs to change, easier to complete your own task than help someone who is struggling, and easier to stay quiet than give feedback that may create an uncomfortable conversation.

Emotional labor can mean staying patient when a conversation becomes frustrating, admitting when your first solution was wrong, helping someone even when it is not specifically written in your responsibilities, making someone feel welcome, speaking up when you notice a problem, or taking responsibility for a decision when there is no perfect answer.

Godin uses the example of a flight attendant who can rush through the required announcement and technically complete the task, while another flight attendant may bring energy, attention, and a real effort to connect with passengers. Both people may complete what the job description requires, but one of them chooses to bring something more human to the experience, and that difference is difficult to describe in a procedure.

That is why so much of linchpin behavior exists 𝗯𝗲𝘆𝗼𝗻𝗱 𝘁𝗵𝗲 𝗷𝗼𝗯 𝗱𝗲𝘀𝗰𝗿𝗶𝗽𝘁𝗶𝗼𝗻.

Godin also connects emotional labor with 𝗴𝗲𝗻𝗲𝗿𝗼𝘀𝗶𝘁𝘆 because creating art is not only about producing something impressive; it is about creating something that has value for another person. Sometimes that generosity is sharing what you know, taking extra time to explain something, introducing two people who should know each other, helping someone solve a problem, or bringing an idea into a room without immediately calculating what you are going to get back from it.

We are not going to be generous, creative, courageous, or brilliant every moment, just as Einstein was not a genius every moment, and I think that makes the idea of being a linchpin much more realistic. It is not about becoming a perfect person who always has the answer and always does extraordinary work; it is about recognizing that we have the ability to contribute something beyond the minimum and choosing to practice that behavior more often.

The more I listened to the book, the more I started connecting these ideas together because being an artist requires us to create something, generosity gives that creation value for somebody else, emotional labor asks us to do the uncomfortable human part of the work, and the lizard brain is often the part trying to convince us not to do any of it because following the instructions and staying unnoticed feels much safer.

That is also where the uncertainty around AI fits into this reflection for me, not because I think the book gives a prediction about exactly what technology will do, but because it gives a way of thinking about how to behave when the way we work is changing.

If more routine and repeatable work becomes easier to automate, then trying to make ourselves valuable only by becoming better at following instructions may not be enough. The ability to understand a problem, question an answer, communicate with people, use judgment, take initiative, build relationships, create something useful, and handle situations where there is no clear map becomes even more important.

A job description can tell us what our responsibilities are, but it cannot completely tell us how to handle every person, every unexpected problem, every difficult conversation, or every situation where the answer is unclear.

For me, that is the biggest lesson in Linchpin.

Being a linchpin is not about knowing exactly what the future will look like, becoming impossible to replace, or trying to be extraordinary every day. It is about continuing to build our skills while also developing the judgment to know when following instructions is not enough, being willing to create and share our work, doing the uncomfortable emotional labor, helping other people with what we know, and recognizing when resistance is trying to make the safer decision for us.

The rules around work will continue to change, just as they have changed before, but we do not have to wait for someone to hand us a perfect new instruction manual before we decide how we want to contribute.

𝗚𝗼𝗶𝗻𝗴 𝗯𝗲𝘆𝗼𝗻𝗱 𝘁𝗵𝗲 𝗷𝗼𝗯 𝗱𝗲𝘀𝗰𝗿𝗶𝗽𝘁𝗶𝗼𝗻 𝗺𝗲𝗮𝗻𝘀 𝗯𝗿𝗶𝗻𝗴𝗶𝗻𝗴 𝘁𝗵𝗲 𝗽𝗮𝗿𝘁 𝗼𝗳 𝗼𝘂𝗿 𝘄𝗼𝗿𝗸 𝘁𝗵𝗮𝘁 𝗰𝗮𝗻𝗻𝗼𝘁 𝗯𝗲 𝗿𝗲𝗱𝘂𝗰𝗲𝗱 𝘁𝗼 𝗮 𝗰𝗵𝗲𝗰𝗸𝗹𝗶𝘀𝘁, 𝗮𝗻𝗱 𝘁𝗵𝗮𝘁 𝗶𝘀 𝘄𝗵𝗮𝘁 𝗜 𝗻𝗼𝘄 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝗶𝘁 𝗺𝗲𝗮𝗻𝘀 𝘁𝗼 𝗯𝗲 𝗮 𝗹𝗶𝗻𝗰𝗵𝗽𝗶𝗻.