TRAP-PROOF your Technology Enablement Program

IT enablement program, although well intended and management supported, fails to deliver as it falls prey to traps during the journey.  Here are a few “Traps” that spread across six dimensions; System, People, Infrastructure, Data, Execution and Resources (S.P.I.D.E.R) that can play havoc—being cognizant of these upfront help.

SYSTEM:

Trap 1:  New system will automate everything

System in its original or morphed form should cater to all users’ wishes, including complete elimination of paper documents; excel sheets and other manual ways of working. 

Trap 2:  All systems should be able to talk to each other…… seamlessly. 

In the professed new “open, networked, connected world”, there should be no barriers with regard to data flow, access rights and application usage between new and existing legacy systems.

PEOPLE:

Trap 3:  People care for new IT system, as much as IT team does. 
IT enablement once completed will help business gain better control on planning, operations and customer acquisition levers, resulting in real business benefits.  So business should be readily sparing team members for system testing, getting trained and conducting trainings as asked by IT team. 

Trap 4:  People adopt well designed IT systems on their own.

The new system offers multiple benefits and all it expects is people to enter data into system instead of on paper or Excel! On top of that, we have offered training programs, designated super users to help and made management reinforce the benefits of new system.  Human beings are rational beings, at-least in office, all of them, all the time……. fair assumption? 

INFRASTRUCTURE:

Trap 5:  Infrastructure availability is only a cost issue

You can get any infrastructure you need, provided you are willing to pay for.  Issues like existing infrastructure status, network security and risk vulnerabilities, buy vs rent decisions, vendor delivery timelines are too trivial aspects to bother about.   

Trap 6:  New system is modern only if it works on my tablet. 

My personal applications work across channels, so should my office applications.

DATA:

Trap 7:  All type of recordable data should be available in the system. Lets’ have it, just in case!    
It takes hardly any effort to configure another template/KPI in the system.  And business will religiously maintain correct and up-to-date data in the system. 

Trap 8:  Data preparedness can be managed easily

The challenges associated with data preparedness, i.e. collection, validation or migration from existing formats, need no special attention.  

EXECUTION:

Trap 9:  Assigning Accountabilities and Responsibilities will ensure delivery
RACI is more used when things go wrong for finding scapegoats, than for driving effective collaboration.

Trap 10:  Getting stakeholders meetings on calendar is Governance

All stakeholders when invited to the weekly meetings and risks and issues openly sought, should leave no scope for surprises at the last moment.

RESOURCES:

Trap 11:  Two partially competent resources can substitute for one competent one
Is It?

Trap 12:  Resource replacement is BaU (business as usual)

We have robust documentation of changes and requirements.  Moreover everyone is expected to collaborate, jell well with team members and adapt to the operating context, fast.  Isn’t it?

The above list is by all measures illustrative. 

Have you also encountered traps that have potential to derail the program?  Help validate and add to the above list.