A new direction

Having heard more from Foxxx of the ins and outs of software developement in senior management, and from my own experience, it seems clear to me there is a role for a person to step in on a contract basis.

1 : The Father Dougal type

The fuckwit, all the managers can blame stuff on and come out looking squeaky clean.
"Dougal, you said it had to be done that way, this was the scope, that was the timescale, these were the resources needed, that was the budget, it had to be this colour, those were the new requirements"
I'll provide a checklist they can use pre-meeting for me to look stupid and carry the can for.
"What!, on your arse I did" just to give that manager a bit of credibility.
"Yes you did, you had on a Blue cardigan".
"Ah yes, that sounds familiar now".

OR

2: Vague Guru

"As a team bringing this project in is like we are trying to land a helicopter". Waft hand at the open mouthed suits.
"One of you controls the collective (up and down), another the cyclic (left and right), you the throttle(how fast up and down) , and finally someone the anti torque pedals (which way you point). If you don't do it in a co-ordinated fashion, you'll crash together, land somewhere else and get taken prsioner together and be sodomised, or just run out of fuel and crash together.
At the same time as running your own bit of control to make a landing you must also complete a particularly tricky Soduko puzzle which you personally will be rewarded on, regardless of your helicopter".

Hmm this is actually quite good.

I can't get bogged down in specifics, so it's questions.
"Why are we going up when everyone else was set up for us to descend"?
"The airfields over there, who has us pointed at those mountains? Can the up and down or left and right people bring us back around?
Maybe I should throw in, the windows are blacked out, and the landing pad is specified on a sheet in the cabinwritten by a dyslexic seaman".

Gettin late, I have to sign on tomorrow, so I'll sign off here