by Robert<\/p>\n\n\n\n
<\/p>\n\n\n\n
Last week, one of our programs wrapped up again. And as always, the participants and I looked back together on what had been achieved and what had gone well. One sentence in particular stuck with me, and that is what gave me the idea for this blog post.<\/p>\n\n\n\n
One of the participants, let\u2019s call him Dr. V., said that he could now see how you can be the boss in your team or in a project without being bossy. And I really think that is something worth talking about. Because this is exactly where a lot of researchers get stuck internally. They want to lead, but they do not want to come across as authoritarian. They want to take responsibility, but not seem like they are constantly checking up on people or telling everyone what to do.<\/p>\n\n\n\n
Dr. V. said this question is especially important in the social sciences, because there are a lot of free spirits and independent thinkers there. And yes, I can see that. But I think this is true across research in general. Of course, not for every single person. But who among us actually wants team members who just mechanically do whatever is put in front of them? We want people who think along, think further, think outside the box a little, and who do not immediately get boxed in by a \u201cthat\u2019s how we\u2019ve always done it.\u201d And that is exactly why leadership, a.k.a. \u201cbeing the boss,\u201d is not less important in these settings, but more.<\/p>\n\n\n\n
The alternative to leadership is not freedom. It is confusion. And over time, that gets pretty draining for teams. That is why I liked Dr. V.\u2019s sentence so much. Being the boss and being bossy are just not the same thing.<\/p>\n\n\n\n
Let\u2019s look at the role of research team lead itself for a moment. Whoever leads a research team is accountable for a research program that runs well and for a team that makes good work possible and multiplies the research output. That responsibility does not just disappear because you are more friendly, reserved, or cooperative by nature. And it does not disappear just because you do not enjoy hierarchy games. The role is still the role. And part of that role is making decisions when it matters, especially when something is unclear or when others have reached a point where they cannot make the decision.<\/p>\n\n\n\n
But that is only one part of it. It is not just about making the final call from time to time. It is also about making expectations clear, setting priorities, following up on things, and paying attention to the team climate. And I really do mean climate, not weather. I do not mean whether everyone happens to be in a good mood today, but whether the way people work together is sustainable over time, whether there is clarity, whether there is reliability, whether things get addressed or not.<\/p>\n\n\n\n
And this is often where it starts to feel uncomfortable. Because a lot of people think they are being bossy the moment they ask for things, check in, or come back to something that had been agreed on. But honestly, regular check-ins, real follow-through, and performance discussions are not bossy. They are part of the job. There is no other way to actually fulfill your responsibility.<\/p>\n\n\n\n
A lot of people put necessary conversations off because they are uncomfortable. Understandably. Really. If someone is not working at the level that is needed, if behavior becomes difficult, or if expectations are not being met over a longer period of time, then you have to talk about it. That part is not optional. But how you have that conversation matters a lot. The goal is not to prove a point or show authority. The goal is to understand what is going on well enough that something can actually change.<\/p>\n\n\n\n
In our latest webinar, we talked about how you can shift from \u201cWhy don\u2019t they care?\u201d to \u201cWhat is actually getting in the way here?\u201d Is the task unclear? Are the expectations fuzzy? Is it beyond their current skills, or just so big and messy that they do not even know where to start? Do they need more support or more resources? That does not mean you lower the bar or let things slide. It means you are trying to address the real problem instead of just reacting to the symptom.<\/p>\n\n\n\n
And to me, that is one of the clearest examples of the difference between being bossy and being the boss. Staying on things, following up, and addressing issues even when it is uncomfortable, that is part of the role. Doing it with curiosity, clarity, and a real intention to solve the problem is part of doing that role well. You do not have to become authoritarian, but the accountabilities of your leadership role are not optional.<\/p>\n\n\n\n
And maybe that is the really useful distinction. The role of \u201cboss\u201d is not optional. The way you fill it is. You need to find your own style. You can be clear, consistent, and still be human and kind.<\/p>\n\n\n\n
There is no need to copy people whose style never fit you in the first place. But there is also no way around the parts of leadership that feel uncomfortable. If you lead a team, then part of your job is to address things, make decisions, and stay on them long enough that they actually happen. That is not bossy. That is the job.<\/p>\n\n\n\n
Being bossy is a question of tone and method. Being the boss is a question of role. And there is no getting out of that role<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
by Robert Last week, one of our programs wrapped up again. And as always, the participants and I looked back together on what had been achieved and what had gone well. One sentence in particular stuck with me, and that is what gave me the idea for this blog post. One of the participants, let\u2019s…<\/p>\n","protected":false},"author":1,"featured_media":4177,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-4741","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","category-1","description-off"],"_links":{"self":[{"href":"https:\/\/www.glia-leadership.com\/index.php?rest_route=\/wp\/v2\/posts\/4741","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.glia-leadership.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.glia-leadership.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.glia-leadership.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.glia-leadership.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4741"}],"version-history":[{"count":1,"href":"https:\/\/www.glia-leadership.com\/index.php?rest_route=\/wp\/v2\/posts\/4741\/revisions"}],"predecessor-version":[{"id":4742,"href":"https:\/\/www.glia-leadership.com\/index.php?rest_route=\/wp\/v2\/posts\/4741\/revisions\/4742"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.glia-leadership.com\/index.php?rest_route=\/wp\/v2\/media\/4177"}],"wp:attachment":[{"href":"https:\/\/www.glia-leadership.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4741"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.glia-leadership.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4741"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.glia-leadership.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4741"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}