There are a million ways of killing any new initiative in the corporate world but none more powerful than the invocation of dependencies, the dreaded weapon that can immediately start a vicious spiral of death.
No man is an island. And no corporate initiative is independent. You want to change a HR policy – you need to depend on the applicable laws. You want to hire a new employee – you should get budgetary clearance from Finance. You want a promotion – you need to work hard (just kidding!).
However, the masters of corporate affairs can create real and imaginary dependencies in such a way that nothing can ever get started. As an added bonus, if something does get off the ground against all odds, you, the master, are already armed with the ammunition to absolve yourself of blame for any subsequent failures.
Let us watch the practice of this art in simple and complex situations.
Let us say that a particular manager wants to rearrange the time for a weekly projects status meeting that falls on a Friday at 9 AM, as she has a conflict with another recurring meeting at 9:30 on Fridays. You, the ‘status quo’ master, do not want to change anything and so start drawing upon your repertoire of dependencies. You start explaining, “Oh…I wish I could consider a new timing but the Board room is not available between 9:30 and 2:30. Reordering coffee and snacks served during the meeting, currently scheduled for 9:30 AM, to a different time requires prior approval from the VP as coffee trolleys are shared with other meetings. And, Liz calls to check on her children during her walk between meetings at 10 AM. Additionally, some people have early lunch at 11 AM on Fridays…….. So, you see, it may be rather difficult to change the timing of our weekly meeting; it has a lot of dependencies”. The manager concerned returns to her desk crestfallen.
Fast forward to a more complex scenario – the dream of every IT professional – system dependencies. Poor Joan, the store manager in a Retail chain, wants to ask her IT Gods for extension of time to submit her daily cash balances till 6:30 PM instead of the current 6 PM, in order to have reasonable time to balance her cash registers after store closing. But, of course, the IT powers would have none of that and confront Joan with, “….you have no idea of how inter-dependent things are; your cash balances have to be placed on the FTP server at 6:10 for the batch job to transport them to the interim holding area by 6:18; this will be followed by a purge of yesterday’s totals at 6:24 at which time our monitoring staff will initiate a manual upload before leaving office at 6:30 (if the staff has to stay back, that costs us 73.99 dollars per hour extra); building in redundancies for failures, we are expected to be complete with our ledger processing by 9 PM and then wait for the daily maintenance cycle to kick in at 4 AM (yes, a good 7 hours of ‘holding time’)….. it is all very complicated and inter-dependent. So, your request for an extra half hour to balance your registers will likely cost us an extra $ 2 million per month”. Needless to say, Joan goes away feeling that she might single-handedly have been responsible for the company going into the red.