Management...
Friday, August 26, 2011 at 1:40PM I wanted to blog about something that I've discussed with many people over the years: The management of a scientific group (specifically here, an academic lab). I have to admit that I was rather shocked the first time that I learned that professors generally don't need to go through any serious 'management' training1. I find this somewhat strange as companies routinely hire business and management majors directly out of college in order to oversee accounts that aren't exhorbitantly larger than some grants that PIs are working with. I've now worked under the supervision of 4 separate PIs, and I've observed that techniques vary wildely, as does success.
It seems obvious to me (though correct me if I'm wrong) that managing a scientific lab is qualitatively different than managing a company. Allow me to explain via a personal example: I worked as the night-shift manager at a Shopper's Drug Mart Pharmacy for 4 months between finishing my M.Sc. and beginning my Ph.D.2. When I came in for my shift, I looked at what people had to accomplish for the evening and delegated responsibility to my employees; that is, I told them precisely what to do. An academic lab may have a few people that fit the 'tell them what to do' bill - technicians and junior grad students, for instance - but senior grad students and postdocs are typically considered to be fairly independent.
Following on that topic of independence, a previous advisor of mine once described relationships within academic labs as 'partnerships', consisting of a senior partner (the PI) and various 'junior' partners with varying degrees of investment in the direction of their own work as well as the lab's. The job of the senior partner was therefore to steer the lab towards accomplishing its overall 'vision', for lack of a better term, by hiring interested people as well and 'consulting' on projects. I think that this consulting role plays a part in explaining why many lab websites say things like, 'we are broadly interested in...'. There are many ways to chip away at the myriad of current 'hot topics' in science.
I imagine that this ability to trust in the independent judgement of 'junior partners' is probably one of the most challenging tasks of being a PI. Unlike the 9-5 jobs at the office, people in labs tend to work in very different ways, and it's not always obvious that any particular person is being 'appropriately' productive. The obvious solution is to check in regularly with weekly lab meetings and/or round-tables. However, it's pretty common to hear of situations where supervisors want weekly written progress reports. A very controlling person may decide to take a completely top-down (a.k.a. 'hands-on') approach and simply come tell you what to do regularly.
There are pros and cons to the above scenarios. PIs who are too 'hands off' can leave more junior members floundering - it's not everyone who's able to walk into a new lab and design a project from the ground up without any guidance. Weekly progress reports force people to think about the overall picture of their work regularly, something that's easy to avoid in the tedium of long, ongoing experiments. However, such progress reports become less useful if they require a lot of work as well as polished figures (I have a friend who spends ~4 hours/wk preparing his progress reports, which seems excessive). The very 'hands-on' supervisor is arguably the worst in my experience, as they're rarely as 'up' on the details of techniques and background materials leading to many unreasonable requests based on misunderstanding.
For all of the differences between managing a business team and an academic lab, there are also a lot of parallels as well. Things like maintaining employee morale, how to deliver criticism, how to plan and manage long-term projects, and how to sell ideas in general, among other concepts, are certainly universal. Some people obviously have the knack for these types of things, but others clearly do not. Yet there's a certain hubris among academics in thinking that it is not a worthwhile exercise to have such skills taught. This is all the more odd given the general emphasis that academics place on education.
I don't think that it's a waste of time for me to ponder these issues given that I would like to have a lab of my own some day. Assuming that this comes to pass, where will I learn these techniques? There's a certain sad logic in the argument that one 'learns' to be a PI over the course of their grad-school and postdoc experiences. Though somewhat better than 'the blind leading the blind' (students of good PIs may learn good management skills) it's all too likely that poor skills will be passed on as well. I wonder if it would be practical to organize 'management seminars' or brief classes for new PIs (as well as refresher sessions for longer term employees)? Time and finances are likely stretched too thin as it is, but it's something to think about.
1Actually, I think that the first such shock that I received was when, during my undergrad, I found out that professors don't actually have to learn how to teach, either. I don't know which one worries me more now.
2Tangent here: The greatest benefit of this job is that it unequivocally established the value of my M.Sc. After I accepted the position, the big boss looked down at my resume and said 'Oh, I see you have a Masters degree. We can bump you up by $2/hr!' Thus, it would take me something like 4-5,000 hours of work to see a return on investment on my M.Sc. Ungh.




