Author Archives: Daniel Reidpath

Conflicts of interest in research leadership (Part II)

(The fond farewell. When enough is enough)

When I started my research career, a research leader’s retirement was a moment to celebrate. Their lives and their contributions were recalled through their research, their papers, their PhD graduates and Postdocs. The Festschrift was often published, literally celebrating their intellectual contribution to a field. Some of those researchers truly retired. Many took honorary appointments that gave them a desk or space in their old laboratory, and access to the library and email. They might mentor junior staff or be a part of a PhD student’s supervisory team. Many continued to do fabulous, original research. Others became the departmental raconteur, recalling embarrassing stories of now senior departmental researchers who were once their postdocs. The retired research leaders were appreciated but no longer had a formal role in the organisational structure.

My experience today with research leaders approaching an age that would, before, have been the time to retire — the time that I am beginning to see on my horizon — is somewhat different. The game now is one of holding back the younger researchers, and hanging on, limpet-like, to substantive position for as long as possible. It is cast as an age discrimination issue. If I am capable, and I am performing at a high level, then my age should not be a barrier to my continued leadership role.  Indeed, I have vastly more experience than junior colleagues, and it would be perverse to choose them over me.

While it is true, age need not be a barrier to the capable performance of one’s duties, it is also true that senior positions are rare, and if they are held by an increasingly ageing leadership, how will we train and develop younger cadres of leaders? Turning over leadership refreshes ideas and organisations.

I recall a radio interviewer with a well known Australian clinical researcher. He recounted how, as a junior researcher, his supervisor put him down as the first author on a significant scientific paper — a career launcher. He had not earned the spot, but the supervisor saw his potential and also recognised his capacity to influence the trajectory of a promising career. Without debating the ethics of that particular decision — it was a different time — there is little doubt that the paper launched one of Australia’s great scientific careers. Forty-plus years after those events, I have seen very capable, senior research leaders forsake their leadership role in favour of hanging on to power. They do not surround themselves with bright, eager, up-and-comers. They do not mentor and position their staff to take over. Instead, they retain non-threatening doers, many of whom will not even appear in the acknowledgements of their scientific papers.

In a post I wrote a little over a year ago I observed that in the interests of gender fairness, men had to be prepared to relinquish power. I have a similar view of intergenerational fairness. Those research leaders among us who were born in a twenty-year, golden age between about 1945 and 1965  have been extraordinarily lucky with the opportunities that we have had. In the interests of fairness and, frankly, in the interests of science, we need to know when to step away. We can still be a part of an exciting research agenda; maybe we do not need to be seen to lead it.

Perhaps the last act of truly great research leaders is to step back.

A literary bibelot

Within a minute I swung from apoplectic to flummoxed.  My erudition had been called into question with an unkind gibe. A friend — truth be told, an impious ragamuffin — started this small, mental kerfuffle by suggesting I would not be able to use a set of 21 words in a single blog post. Was this louse, this piebald swiller serious, or was it waggish humour? Apparently, he was serious. There was no playfulness here.

I confess the challenge did give me the collywobbles. Could I obfuscate? Could I substitute an alternative, thesaurus challenging vocabulary and get away with it? Perhaps there was a set of lexical dregs or suppositious words to hornswoggle the reader. I had it …. a story laden with sesquipedalian, polysyllabic nonsense.

“The mountains ached for the moon to rise and break the thick, tenebrous night. The canvas of a small ketch caught the zephyr wind to pull it across the ….”

Ugh! Jabber! I had macerated this nubbin long enough. If I wasn’t careful I would choke on the challenge, and no wine to quaff. On the other hand, there would be a simple joy in succeeding. With an exuberant ululation from the balcony, I would announce my victory to the world, and he (he who had created this casus belli) would withdraw — vamoose — tail between the moose’s legs.

There was one small problem. Yenta. As in, “she’s such a Yenta”;  a person, especially a woman, who is a busybody or gossip. It was a little too xenophobic for my taste, not to mention misogynistic. What to do? I could not meet the challenge. Hubris won. Who was the moose now?

Staff who want to leave

Learning from a member of staff that she wants to leave can feel surprisingly hurtful. It can be particularly upsetting when he wants to stay within the organisation, just not in your unit.

As bosses, we very often spend far more time with our staff than we do with our own family or friends. We invest time and resources in their development. They become a part of our lives and our plans. When they announce their intention to leave, it can feel like rejection.

I thought you liked it here. You can’t leave now, I’ve invested too much in you. Your the only person who can… And finally, “How ungrateful!!!!”

I have been that person who my boss cursed for leaving, and I have been that boss who cursed (silently) the person who wanted to leave. I have also seen colleagues abuse, belittle and try to destroy the careers of staff who want to leave. No surprise really, with a boss like that, that a person wouldn’t want to stay. Pathological behaviour by a boss in one quarter portends pathology in other quarters.

The most relevant advice I ever received about leaving was from Steve Schwartz, former vice-chancellor or Murdoch, Brunel, and Macquarie Universities. “You have to remember, Daniel”, he said, “the person most interested in advancing your career is you.”

And that is the heart of it. As bosses, we do not act solely with the best interests of our staff in mind. Sure, we are not indifferent to their welfare but that is not the raison d’être of the workplace. When we engage them, challenge them, mentor them, and develop them, it is at least in part because we hope to have smarter more engaged and more productive staff in return.

Inevitably, of your good staff, some will stay and some will leave. If your sensible, you were already a part of the discussions about long term career planning and you had plenty of warning– maybe not in detail, but at least in direction. When the time comes and they want to leave, do not curse them (outwardly). Congratulate them on their new opportunity and wish them well. If there is some outstanding work that desperately needs their skills to complete, you may be able to negotiate a better departure date. Do not try and bully them into staying.  When staff cannot leave, it is not employment, it is servitude.

Research Leaders

Over a 20 year career in global health research, I have worked with some great researchers and some inspiring leaders. They were not necessarily the same people. As the second piece in my reflections on leadership, I discuss the idea of the leader itself.

Two of the most thoughtful leaders I know are Rob Macredie and Richard Parish, both of whom I met while working in the UK. They are not the only impressive leaders I have ever met. Setting them apart, however, was the extent to which they thought about leadership itself: how to lead and how to lead better. Some people do seem to be “natural leaders”, but as far as I can tell, this is the exception rather than the rule, and there is a danger believing that leadership cannot be learned. Thoughtful leaders have a self-reflective, inquisitive edge in improving their skill. 

Of course, if you can learn to become a leader, does this mean that you have to wait until you are promoted to a leadership position before you can learn? And if you can learn to be a leader before you are in a leadership position, how do you practice? To my mind, the real value of these questions is that they reveal a problem with the ways we think about leaders and leadership.

Pick up almost any book or article on leadership, and it envisages a leader as a person who carries a “boss” position within an organisation: the CEO of a research organisation; the head of a department; a team leader. This view is too narrow to capture what it is to be a leader and limits an organisation’s opportunities to recognise and develop leaders.

My 3 am take on a leader is… “A person who acts strategically to move a collective towards its goals. Short, pithy, perhaps a little uninspired (3 am has delusional qualities), and with some nonetheless potentially provocative implications.

First, leaders can lie anywhere in an organisational structure. Second, in acting strategically, leaders may develop and evolve the strategy itself. Third, leaders may set and refine the goals of the collective. It is worth noting that, in the context of this definition, a collective may be (as I tend to think about it) a research group or research organisation, or it may be a commercial organisation or a team within a company, a school, a civil society organisation, or indeed society itself.

The key to being a leader lies in goal-directed, strategic action. That is, they think and act beyond the operational. Not all leaders will set strategy; not all leaders will set goals. Some leaders will hold positions in organisations that do not empower them to set strategy or goals. And some leaders will have both those authorities and would be well-advised not to wield them. Indeed one example of bad leadership is characterised by the need to be an agent-of-change in a collective that is already set on the right course and working effectively.

In the world of agile software development ( “Agile”), there is a refreshing approach to leadership. The software development team will have a head, but leadership roles evolve and shift according to the needs of the team at any time to ensure delivery of the product. One person may step into a leadership role now because of the skills and expertise she possesses, and another person will step up later; this is all done according to the flexible needs of the team to achieve its goals. Teams work this way because of Agile’s short cycles of incremental development and reflection as the software gets better and better.

Agile approaches may not work for the entirety of an organisation. They may, nonetheless, be ideal for smaller, fast-moving, evolving areas of research, a development unit in HR, or a commercialisation team working with a new scientific invention. The key idea, here, is that leaders should be encouraged to emerge according to need and circumstance, not according to rank and hierarchy. These agile leaders won’t be reworking the organisational strategic plan or resetting the organisational goals (unless that is the task). They can, nonetheless, evolve local strategy and local goals. Still, they can act strategically to advance the collective towards its goals — perhaps in something as simple as a small team writing a grant proposal. Interestingly, McKinsey & Co. has begun to embrace ideas of Agile in business transformation.

The management literature talks about “managing up“. If we are to develop research leaders, it is undoubtedly, at least as necessary to prepare staff for leading up. Some of the most successful leaders I have known, lead up. They work behind the scenes, they influence, they nudge, they target. Highly strategic, they are usually well-recognised within the organisation, but often unknown beyond it.

Reflecting on junior colleagues in my Division, some do their job, but some do their job and lead up. And they do this without stepping out of role or stepping on toes. A recent example was a colleague who suggested and then implemented process changes to the management of a large project. The changes will bring more reliable accountability mechanisms to bear for delivering research outputs on time.

Valuable organisational lessons emerge from all this. Invest in developing leadership skills at all levels. Take mentoring seriously. Embed the vision of the organisation, the department and the team to encourage strategic actors.