Welcome to a new series in which I apply the methodologies of my day job to classic Doctor Who stories. Project management is a subtle profession requiring people skills and precise organisational abilities. Let’s find out if the Master’s got what it takes.
1. SET A CLEAR GOAL
In Castrovalva, the Master’s goal is to humiliate and kill the Doctor. It’s the vagueness of the ‘humiliation’ aspect that will eventually cause the project to fail. With the powers available to him in this story, killing the Doctor would be a precise and quickly achievable aim. But by over-complicating his win-conditions – namely that the Doctor must know before dying that he’s been trapped and defeated – the Master allows too many random variables to affect his plan. “These facile victories only leave me hungry for more conquest!” he declares at one point. And this obsession with setting himself convoluted challenges will be his undoing.
2. ESTIMATING AND PLANNING
This is however a very well planned project. Castrovalva clearly doesn’t follow on as immediately from Logopolis for the Master as it does for the Doctor and his friends. He’s taken some time out in the vortex to consider how much more powerful block transfer computation is than he realised and decided to recruit Adric to his project team, noting that the boy can a) add up and b) fill a pair of pyjama bottoms to his liking. Then he’s made a quick trip to the planet Hadron, whose inhabitants will face some delayed trains the next morning as they find the overhead power lines missing. Only at this point does his Pillar of Doom pop up (in front of some pylons appropriately enough), his Web fully constructed and waiting within. Collating and readying all necessary resources before the project’s start date is an admirable achievement and ought to help towards success.
The Master’s risk management record here is exemplary. He confides to Adric at one point that should his plan for the Doctor to perish in the hydrogen in-rush fail, he’s prepared a trap behind the trap. And when he learns that it’ll be necessary for him to use up this contingency, you’ll note that it then takes only seconds for him to cause all the associated information (about neutral interfaces in real locations, ‘Classic Plainness’ and ‘Dwellings of Simplicity’) to pop up unprompted on the TARDIS’s databank screen. It’s a clear sign that these project assets have been prepared well before they should be needed, and another good mark for the Master.
We can assume too that at this point the Master uses the other main tool available to him – time travel – to set up the dwellings of Castrovalva well before the Doctor arrives. It’s impossible to guess how long the citadel has existed for, as all its inhabitants are created with pre-loaded memories. But from the looks of it Adric hasn’t aged much, so it can’t have taken more than say a few months to set up. Although at one point the Master does threaten to keep him in the Web for eternity so who knows, maybe it keeps life in some sort of stasis and they’ve been hanging around for years. Either way, bodily functions aren’t impaired in the Web AS WE HAVE REGRETTABLY SEEN AND CAN NEVER UNSEE, so those pyjamas must stink.
4. THE PROJECT GOES LIVE: MANAGING THE TEAM
In choosing Adric as the only member of his team, the Master is putting a high project dependency on the lad’s computational powers. Happily they really are impressive. Seconds after the real teenager has been kidnapped and flung into the Web, telebiogenesis Adric appears and spends a remarkably short time at one panel of the TARDIS console, during which he not only dematerialises the ship but also, apparently, sets and locks the co-ordinates for Event One and pre-programmes both co-ordinates and landing for the contingency plan.
The depletion of Tegan's make-up supplies was NOT budgeted for
But the Master has made a sloppy assumption: that he will be able to restrict Adric’s activities to prevent him from aiding his friends and Tegan, or else command his absolute loyalty. So Adric manages to undermine the project goals by giving the inhabitants of Castrovalva enough intelligence and free will to assist the Doctor.
Is the Master’s management style at fault? It’s certainly inconsistent, roving from apparent sympathy with Adric’s viewpoint ( “If escape were that easy, we could all be free of this nasty world”) to an emphasis on detachment (“You must control these dangerous emotions!”) and an authoritarian slant (“You can’t escape, you’re mine, Adric! Mine! Until we have completed our final task”) which at its worst leads to his dismissively referring to his employee as “a mere utility”.
5. TRACKING, STATUS REPORTING AND CHANGE MANAGEMENT
“The Master leaves nothing to chance,” admits the Doctor at one point. And his enemy certainly loves a regular status check – he monitors the TARDIS up until the last moment as it hurtles towards Event One, and in Castrovalva he gets hands-on to keep an eye on the Doctor in person. He has a good feel too for the day-to-day timeflow and resource management that a big project requires – “Now save your energies. There’s so much yet to be done!”
Fashion design with Adric
One thing we never see is the design briefing meeting the Master must have held with Adric at the project’s critical point: the creation of Castrovalva and its denizens. They end up with such a sumptuous, ridiculous looking town that I can only imagine the Master flinging countless contradictory instructions at the boy and expecting them all to be met at once. This is not uncommon in the real world either, to be fair. “Let’s have alpaca robes and a sort of hockey mask for the hunting party! With a Mardi Gras feel! And hats! Lots of hats! The biggest one for me! And some cobweb gloves! And bindis! Oh and can you base the city’s shape on these old mathematically-inspired paradoxical etchings so that we can fold time and space in on each other at the end
cheers nyah hah hah.”
- An overcomplicated set of subsidiary goals contributed to the project’s failure
- Project planning, asset collation and contingency allowances were all excellent
- The team was chosen well with regards to its skill-set, however its lack of buy-in to the stakeholder’s win-conditions also contributed to the project’s failure
- Time spent micro-managing the team might have been better spent motivating it
- That cock-up with the library books was sloppy. A proofreader/quality-checker should have been employed
- Overall the project manager was competent, but would work better as part of a team