Dark Managers don't want to know the Problem

Logic states that if you know the problem its a good start for you to figure out the solution. Unfortunately, dark manager's want the solution immediately.

My personal pet peeve is when any attempts in explaining the root cause is often interrupted with a stern...

"I don't care, I want the solution!"

Which the subordinate will immediately reply,

"I'm sorry, but we don't have one"

In which the Dark Manager will ask, "Why..?"

and the routine rotates itself ad infinitum because he/she will just interrupt the engineer anyway... this chicken an egg solution is further exacerbated when the Dark Manager pops up behind the engineer every 5 mins, and yells...

"What's the problem? Is the server up yet!?"

Q&A: Have you met a Racist Bastard Dark Manager?

Asked Fred from San Francisco, well Fred; from where I've been, I haven't met any racist bastards, only bastard managers.

Race, is a tool for control, it allows the Dark Manager to create a "we" and "them" scenario. Its essentially like sports where we take sides. One minute we're friends, another, we're mauling at each other because we're on the other side of the field.

It also allows the creation of an "inner circle" for the Dark Manager

Short Term Dark Management

IMHO, short haul employment is pretty much 1-2 years. Within this period, the goal for success is in framing yourself for your next employer. With Dark Management principles deeply rooted, you need to succeed by all means possible, and time it such that you can leave the organization without too much collateral damage. Both to your reputation and the people that you interact with.

Sweep any unfinished tasks under the carpet
Someone else will inherit your problem anyway, so don’t fret.

Focus on the main goals, if your task is to deploy 10,000 users with SAP, then just focus on that. It does not matter that the users are screaming foul on the lack of training and change management. What you need to do is just concentrate on your key stakeholders as explained in “Managing Up while Shitting Down”.

Because the majority of managers are dark by nature, most of the peons will not have access let alone gripe to the CEO. What’s more, middle management has been forced fed to dilute all reports when addressing up anyway. For example:-

Truth: 9 out of 10 users, do not know how to use SAP upon deployment.
Report: We are 1 month away to complete user training (preferably a date where you’ve already left the company)

Truth: There’s 5,000 incidents and growing on system bugs.
Report: There are 5,000 “requests” due to enthusiastic users working on the new systems.

Truth: The Version Control system lies under the table of one developer and the power supply get’s dislodged periodically by his restless feet.
Report: we have a top notch version control system with Disaster Recovery built in.

Truth: We have a Sharepoint 2000 environment with 90% of all enterprise applications and another Sharepoint 2007.
Report: we have a Sharepoint 2007 farm and it'll be real easy for us to migrate to Sharepoint 2010

Here’s the kicker; nobody wants to report bad news because somehow, Dark Managers label bad news bearer as “whiners” (see Whiner Wanker), and your opponents won't be able to move the news upwards. True, your peers will bitch among themselves, but they won't have the gumption to do anything more than that.

Target one major project that allows you to work with a major Vendor.
In this example, SAP; ensure that the SAP Project Director is well managed. A lot of Dark Managers make the mistake of squeezing the vendors because they want to divert blame to another party; leaving the vendors to hang on most project blunders. But for the short term- that’s a huge foobar!

Your goal is to pucker up and smooch your way up the SAP hierarchy and make one heck of an impression to their brass. If you've done it right, you will be hired once the project ends.

With a short term employment approach, you need to shift all blame to “God” or the “User”.

Vet through & Re-word Risk Management documents.
To shift the blame to God, Risk Management documents have to be as vague as possible. Where the situation is something that cannot be mitigated unless management spends 3x more money compared to the project at hand. When the documents are endorsed by the Risk Committee, roughly verbalize the actual risks but never put it down in writing. That way, the Risk Management Community will be absolved of their duties when risks becomes issues. Everyone will exclaim ignorance but Governance would have captured that "due process" has been adhered to and no one needs to be blamed.

When magic hour happens, your risk document will be endorsed regardless.

Magic Hour
This item deserves a blog entry of its own. So I’ll summarize it as the act of ignoring all risks and in order for the project to kick off ASAP. This happens when the board of directors or Chairman requests for a USD100mil system with 20,000 man days worth of effort, developed by Q4 and today’s the first working day after Q2. Typically the commitment will be agreed upon by the CEO because they're born and bred wankers... especially CEO's that works for organization that they do not form and own)

You get to be cruel to your peers
Principally; through the act of back stabbing your peers via the Vendors to the CEO. You’ll gain even more brownie points when you slam your own peers for works that directly impact the status of the project in front of the vendor. This requires timing and orchestration of meetings.

____

So, here’s the best part about the Short haul approach to Dark Management success. The vendors will actually value you as a consummate executor. It’s one of the most devious ways to climb up the corporate ladder. Use it when you're in a small organization where losers abound with no hope of moving out. It works well when there's a ton of Dark Managers working for the long haul (more on this later)

Unfortunately, once you’re at the top, it’s hard to maintain that position because you won’t have many supporters that you can depend on.

That’s where you need to employ Advanced Dark Management skills… another lesson, another day.

Selecting Projects - Big and Bad Ass

There’s a number of ways to padding up your resume as a Dark Manager. The easiest is from the projects that you've ran; and strategic selection of these projects is an art in itself.

By strategic; your goal is to wring the most amount of money from upper management or your customer before you would even accept it. For example, if it’s a Document Management System, your first task is to justify several million dollars worth of hardware include Information Lifecycle Management tools from EMC and Hierarchical Storage Management add-ons.

It’s all about injecting fear into the stakeholders, and projecting "what if" scenarios that culminates into the birth of the Anti-Christ.

Anyway, here are several things that I stay away from with a 10 feet pole.

Do something for free.
Free means you, absorbing all the risks and the customer as well as management gaining all the benefits. It’s true that you’ll gain brownie points but it creates precedence, and more work will come your way.

Ask the team to research for freeware or Linux, Apache PHP based applications
This directly translates to a resume that says USD5,000.00 on a project sheet when instead it could have been worth USD5mil. Remember, it’s all about image and pretence. It does not matter that all the money is on hardware but the fact is, you ran it.

Tai Chi away easy big value Projects
There’s nothing like a sweet multimillion dollar projects that’ll make you look good – on paper. It doesn’t matter whether it becomes a white elephant; the fact is, you ran it. I know it’s the opposite of what I’ve been saying about ‘Tai Chi’ing away projects, the trick is, to take on projects if you’re in it for the short run, but to move away from it you’re on for the long haul.

In summary, you'd want to take on easy projects that could have been done over the weekend, and blow it up into a 7 or 8 digit figure assignment - cool huh! :)