Some people avoid doing things using what I heard referred to by a colleague of mine as the rabbit hole technique.  This practice has many names, like “road block, ” passive avoidance” and so on.

The rabbit hole resonates for me because as an analogy it provides insights about things to do and things to aviod.  Lets explore the rabbit hole model for accepting accountability while trying to avoid actually doing any work.

The set up

This starts with a request; in this example let’s say a service request to an IT group to take on accountability for support and maintenance of a new application.

The group knows this is their accountability but are not ready to take on the work so they go into avoidance presenting you with the first “rabbit hole”.

“We don’t have enough trained staff, can you help us out by sharing some resources. ” This is a very clever gambit , because if you accept and enter the hole it’s unlikely you will get out in the near term. if ever.

The advice here is be polite but firm, refuse to go down the hole.  For example; “No we are understaffed at the moment which is why we made sure your resources had the training needed for support, before starting the project”

This leads to rabbit hole number two.  “We cannot do this without documentation”. This is an IT favourite blocker.  Again, don’t go down the hole “We have been sending you the documents for review since the project started, here is where they are located.”

The rabbit holes will probably continue. (Who is paying for this, what are the roles and responsibilities) all the while refusing to get involved or start anywork till the hole is filled.

Exercise Caution

The most important advice I can share at this point is never go down the holes, you will regret it.  Always fill them up and force them to move on.  Ultimately the blockers run out , just hang in there.