<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Simon Dobson (Posts about leadership)</title><link>https://simondobson.org/</link><description></description><atom:link href="https://simondobson.org/categories/leadership.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2025 &lt;a href="mailto:simoninireland@gmail.com"&gt;Simon Dobson&lt;/a&gt; </copyright><lastBuildDate>Thu, 23 Jan 2025 17:16:08 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>The three academic stereotypes</title><link>https://simondobson.org/2010/10/29/academic-stereotypes/</link><dc:creator>Simon Dobson</dc:creator><description>&lt;p&gt;You encounter a lot of different personalities in academia, but when you get right down to it they all seem to fall under three basic stereotypes.

&lt;!--more--&gt;

OK, I admit it's a gross over-simplification, but here we go:
&lt;/p&gt;&lt;h3&gt;The young gun&lt;/h3&gt;
Young guns are the change-makers of academia: the people who want to change anything that doesn't work and replace it with something better -- or at least something different  that can be tried out and tested to see if it &lt;em&gt;is&lt;/em&gt; better. This often makes them talented researchers (although not necessarily more so than stalwarts, the next stereotype), but they're typically found in larger groups, taking on larger projects and collaborations.

Young guns can be of any age. They tend to be young, of course -- often junior staff who are keen and un-jaded, who want to move their discipline forward and teach it as well as it can be taught. They're often found pushing for new modules, new degrees, new ways of teaching and assessment -- and for promotion. But they don't have to be calendar-years young: the gun-iest young gun I've ever met  was in his late 40s when I first went to work for him, is now approaching retirement, and still has more ideas and energy than most people a third his age. These people &lt;em&gt;feel &lt;/em&gt;young even when they aren't.

As is probably apparent, young guns can be hell to work with, since for them everything is potentially up for grabs. They're often (but not always) better at idea-forming than at execution, and often (but not always) lack the long-term detail-orientation to make sure that their ideas work out. They are often (but not always) egotists, who may not recognise when a change they've become passionate about is wrong or not working. But without them there's no-one to drive change forward and make sure that schools and disciplines stay fresh and relevant.
&lt;h3&gt;The stalwart&lt;/h3&gt;
The majority of people in academia are stalwarts: people who have clear ideas about the things they want to do and how to do them, but are essentially positive about their activities. They might not lead change, but they'll row-in alongside if they like it and will accommodate to anything that's broadly agreed.

This applies equally to teaching and research. The typical stalwart will teach modules carefully, perhaps changing the content and delivery only slowly if left to their own devices but being perfectly open to updating to include new ideas. In research they will typically be found slightly off the mainstream with a small group of students (often only one at a time), not going for large grants or big collaborations but being solid supervisors and contributors at a small-to-medium scale. Often they come up with great ideas, because they pursue a line of research solidly over a long period and so become world experts. The ideas might not be widely circulated, and so it's easy to underestimate the  sophistication stalwarts bring to their work. They may need prodding to publish appropriately, but they'll then address tat problem as effectively as everything else they do.

Stalwarts are essentially positive people, working within a well-defined comfort zone. They are the backbone of any research project or school, and need to be appreciated and rewarded appropriately. They also need to be listened to carefully, since they provide a stability and a sanity that young guns often lack, and will make sure that changes are properly thought through and executed upon.
&lt;h3&gt;The twisted nay-sayer&lt;/h3&gt;
The first two stereotypes are basically positive, but it all goes down hill with the third: the twisted nay-sayer. (I can't claim credit for the great name, incidentally, which is due to &lt;a href="http://www.paddynixon.org/"&gt;Paddy Nixon&lt;/a&gt;.) Twisted nay-sayers oppose all change, no matter of what kind and no matter how motivated, and will to continue to oppose changes even long after the decision has been made and the time for action has passed.

On first acquaintance, a twisted nay-sayer often seems to be someone who's stuck-in-the-mud, after an easy life, and not wanting to have the hassle of changing -- a bit like a rather negative stalwart. But this is to overlook the &lt;em&gt;twisted&lt;/em&gt; part, which will not only avoid change but actively scheme against it, or to reverse it afterwards. It's this essential negativity that sets this type apart from others. They can, perhaps surprisingly, be excellent researchers, but they'll  also be constantly highlighting their successes to anyone who'll listen, even when those successes are long in the past. When faced with a new field or innovation they'll point out that it's really just a poor re-discovery of something that was current years ago, or just an instance of some pet area of theirs that the new innovators should really have found out more about.

The two things to remember about twisted nay-sayers are that they are egotists, and that they are &lt;em&gt;made&lt;/em&gt;, not born -- the young gun's dark shadow. You make them by thwarting the expectations they have for their careers. This can happen in two ways: either their expectations were unreasonable, and reality has intruded; or their expectations were completely reasonable but were thwarted by circumstance, malice or indifference. A particularly common case is someone who's been repeatedly passed over for a promotion they think (rightly or wrongly) that they deserve. The repeated denial of their aspirations eventually causes them to give up, turn their back on the future they can't have -- and then rail against fate and everything that comes afterwards.

How, then, are we to deal with the different kinds of academics? Most people fall into some compromise between categories (stalwart with young-gun moments, for example), but clearly one needs to understand an individual's primary motivations in order to know where they're coming from. I think the trick is to make sure a school keeps, listens to -- and occasionally reins-in -- its young guns; recognises and rewards its stalwarts; and tries hard not to grow any twisted nay-sayers.

All these activities are fraught with danger -- especially in academia, where we lack most of the levers of control that normal organisations have. A school can't typically promote on its own recognisance. Not promoting those who feel they deserve it risks overlooking a young gun and having them leave, or (worse) stay, but mutate into a twisted nay-sayer. On the other hand, many promotion boards over-value their young guns and ignore their stalwarts, who then feel under-recognised. Doing so can destroy the stability of a school and can lead fragmented research programmes, and to teaching being good at the edges but lacking a proper core. It's also worth remembering that some people in senior academic positions are extremely conflict-averse and so will cave-in to pressure from twisted nay-sayers in the interests of consensus -- not realising that consensus is neither possible nor desirable, and that acquiescing will only lead to more obstructionism, because it's &lt;em&gt;about&lt;/em&gt; the obstruction, not the particular issue at hand. It takes confidence to say &lt;em&gt;yes&lt;/em&gt; to experimental change -- but equally it takes confidence to say &lt;em&gt;no&lt;/em&gt; when necessary.</description><category>leadership</category><category>university</category><guid>https://simondobson.org/2010/10/29/academic-stereotypes/</guid><pubDate>Fri, 29 Oct 2010 07:00:09 GMT</pubDate></item><item><title>Computer scientists as university principals</title><link>https://simondobson.org/2010/10/25/cs-university-principals/</link><dc:creator>Simon Dobson</dc:creator><description>&lt;p&gt;I was surprised to discover a computer scientist as principal of a world-leading university the other day. I was even more surprised to discover that there have been several others.

&lt;!--more--&gt;Now I suppose I should first admit that I don't know &lt;em&gt;why&lt;/em&gt; I'm surprised by this -- but I am. In most institutions computer science very much takes a back seat compared to other, more established Schools: physics, mathematics, biology, history and the like. It's hard to see why this should be the case, especially given &lt;a href="https://simondobson.org/2010/04/computer-microscope/"&gt;computer science's central role in the new science&lt;/a&gt; and the fact that it's often one of the highest-earning Schools in terms of research and innovation income (although St Andrews is unusual if not unique in having a humanity -- &lt;a href="http://www.st-andrews.ac.uk/intrel/home/"&gt;international relations&lt;/a&gt; -- as it's highest-earning School, and from which we've drawn our current &lt;a href="http://www.st-andrews.ac.uk/principal/"&gt;Principal&lt;/a&gt;).

The person I came across was John Kemeny, who was &lt;a href="http://www.dartmouth.edu/~president/succession/kemeny.html"&gt;president of Dartmouth College in New Hampshire through the 1970s&lt;/a&gt;. Kemeny is one of the co-inventors of the &lt;a href="http://en.wikipedia.org/wiki/BASIC"&gt;BASIC&lt;/a&gt; programming language, which provided me (and many others) with their first introduction to computer programming. BASIC was invented at Dartmouth, of course, so it's perhaps unsurprising that he should have risen to such a position of influence. It's hard to over-estimate how important BASIC was, in a world then populated by low-level assembly code or compilers of dubious quality: the first Pascal compiler I used used to spit-out assembly code so you could go through it, optimise and correct it by hand. As an interpreted language, BASIC provided a far simpler and more accessible introduction to what computers were capable of, and even on early 8-bit microcomputers was fast enough to be used for both serious applications and games.

Having tweeted my surprise at this, I was then told about other computer scientists who've led -- or indeed lead -- universities:
&lt;/p&gt;&lt;ul&gt;
    &lt;li&gt;Maria Klawe (algorithm design, accessibility), President of Harvey Mudd College&lt;/li&gt;
    &lt;li&gt;Tim O'Shea (computer-assisted learning), Principal of the University of Edinburgh&lt;/li&gt;
    &lt;li&gt;Ewan Page (mainframe pioneer), Vice-Chancellor of the University of Reading&lt;/li&gt;
    &lt;li&gt;John Hennessy (processor design), Provost and then President of Stanford University&lt;/li&gt;
    &lt;li&gt;Jane Grimson (databases, health informatics), Vice-Provost of Trinity College Dublin&lt;/li&gt;
    &lt;li&gt;Jeff Vitter (algorithm design), President of the University of Kansas&lt;/li&gt;
&lt;/ul&gt;
And of course an honourary mention for:
&lt;ul&gt;
    &lt;li&gt;Paddy Nixon (pervasive computing), Vice-Principal for Research, University of Tasmania&lt;/li&gt;
&lt;/ul&gt;
Before anybody asks, this is &lt;em&gt;not&lt;/em&gt; a tradition I have the slightest interest or intention of following in -- or indeed the ability to do so. But it's great to see that techies can and do aspire to the top job.</description><category>leadership</category><category>university</category><guid>https://simondobson.org/2010/10/25/cs-university-principals/</guid><pubDate>Mon, 25 Oct 2010 07:00:46 GMT</pubDate></item></channel></rss>