The best scientist in the lab gets made head of the lab. The engineer who solved the hardest problems is put in charge of the people who solve them. This is how it works in technical fields. We are promoted for being excellent at the work, and then handed a job that is not the work. Almost no one warns us that it is a different job, or that we will have to learn it from the beginning.
I have watched this go wrong many times, and I got it wrong myself. I came to leadership the way most of us do, from a technical training. I started in science, in physics and genetics, then trained in law, earned a doctorate, and spent years working in conflict zones. A few years in, I was hired to run a six-person team that was already in disarray. The previous team lead had been demoted to make room for me, and another member had applied for my job and not got it. No one had warned me that the culture in Sweden was strongly anti-hierarchical. Every attempt I made to change how we worked met the same answer: we can't do it like that, that won't work. One day, out of patience, I said, "This is not a democracy." It did not help. When my new boss arrived, several of the team went around me and took their grievances straight to him. I left.
It took me years to figure out how to lead a complex team well, and then how to lead a company. In the process I took a fourth degree, a master's in public administration, during which I attended all the classes I could find on leadership, including those at MIT on systems and at Harvard Business School on influence, as well as those at my own school, the Kennedy School.
This is the move from technical expert to leader, and it happens to the subject matter expert in every field: lawyers, doctors, scientists, engineers, professors. We spend years mastering a craft, and the mastery becomes who we are. Then someone gives us authority over other people, and we find that the craft does not transfer.
Here is why it is so hard. It looks deceptively easy from the outside, which is why we walk in underestimating it. And it is a genuinely different kind of problem than the one we trained on. However hard our old problems were, they yielded to the expertise we had already built. Leadership does not. It requires people to change how they think and work, to bear the discomfort of not yet knowing, and to accept that they are part of the problem as well as the solution. The expertise that got us here does not shortcut that. Leading well is a skill of its own, and we have to learn it.
There is a logic underneath it. People are held in place by the group around them, and the group runs on forces you can learn to read. That is the part we tend to miss, and it is what makes leadership a problem we can actually get better at. A team is one of these systems, with forces running through it that are invisible until we learn to see them. Groups behave in patterned ways. They form a relationship to whoever holds authority, and they respond in fairly predictable ways when they are pushed into disequilibrium. That team in Sweden was doing all of this, and I could not read any of it. None of this is random, and none of it is simple.
That is why the way we teach leadership fits analytically trained minds so well. We give people a way to read that system, with frameworks built to be learned, applied, and tested against the real world, which is exactly how we were trained to think. The approach is a learning model of practice and iteration. We read the situation, we make a move, we watch what happens, and we adjust, the same loop that runs any experiment. It takes the nuance of context seriously, because leading well is difficult and worth the effort it asks.
Here is some of what comes into view once we start to look.
What we have to learn to see
Start with the group itself, because we have to re-train our eyes to see it. We miss what is going on when the argument in the room is not the argument people are actually having. Silence needs reading too. Sometimes a quiet room means people have settled and are ready to move. Sometimes it means they have decided it is not safe to say what they actually think. The two look identical and call for opposite responses: the first you can build on, the second you have to open up. The person everyone has written off as resistant is often protecting a risk nobody else has looked at. A conflict between two senior people is usually a conflict between the parts of the organization they sit in, which is why replacing either of them changes nothing.
Seeing a group this way is one kind of leadership work, and it helps to know where it sits. The skills sort along two axes. One runs from the self to the system, because some of the work is inside us and some is out in the group. The other runs from insight to action, because some of it is seeing clearly and some is doing something about it. Reading the room is insight into the system, and it is the quadrant we underestimate most, because a system is frequently nonlinear.
Then there is what we do once we have read the situation: holding a conversation someone does not want to have and staying in it when they push back, or managing the pressure in a room so it stays high enough to keep people working and low enough that they can still think. There are more of these than one article can cover. I have written separately about the capacities I train first, and about the services a group needs from whoever holds authority and when to withhold them. What matters here is that knowing the theory is only the first step. The theory is knowledge. The skill is a practice, and practice is the only way to build it.
Our own defaults under pressure
Reading the group and acting on it are only half the map. The other half is the self. Leadership exposes us. Pressure removes our intentions and reveals our defaults. It narrows us, driving us to the one move that always worked before, and we reach for it hardest at the moment it is least useful. For the expert, that move is often to take the work back. We rewrite the junior researcher's analysis, we solve the thing ourselves, and for a moment it feels like relief, even as it teaches the team that their work will be redone and their judgment is not trusted. Someone else's default runs the opposite way: they go quiet and wait for the problem to pass, or they try to keep everyone comfortable and decide nothing. The particular default matters less than the fact that it runs us before we notice it, and that it is usually plain to everyone but us. Until we know our own, what we reach for when we are uncertain and what pressure does to the way we hold authority, we cannot build anything steadier on top of it. Otherwise we just repeat the pattern, faster, under more pressure.
Early in my career I thought leadership was a distraction from the important work we were doing, rebuilding nations after war. Over the years, as the question began to interest me, I realized I had it wrong. Leading people well is an area of real importance, as complicated as the work of rebuilding a nation, and hard in the same way. Once we can see the forces at work in a group, figuring out how to lead well starts feeling like the most interesting problem in the room. That is the real shift we are after. Techniques help, but the thing that changes us is learning to see what is actually happening in front of us, and that is something we can spend a whole career getting better at.