I always find it interesting to read how our information system (IS) textbook describe the success of IT implementation. These books are also compressed theoretical example of how other factors will affect IT deployment like system adoption and change management. In reality, there are other components that determine the real success of system deployment.

Culture and Relationship

Many of textbooks have been entrenched from the fundamentals of academic research. This is why the studies are less focused on the Asian context. You will find that culture and relationships are playing an important role in the deployment of new system initiatives in Asia. You will be surprise to know that the usage of system can be encouraged via relationships. In other cultures, these could be determined with hierarchy influences.

Resistance is Norm

As times passed, I come to realise that resistance to new system implementation is a norm. It is common to hear good feedback of the systems with the contradictions of data. Age do play a factor because it is really hard to accept change with it. A good cultural environment which embrace change and innovation will play a crucial antidote to resistance. Just as we accept resistance as norm, shouldn’t we create an acceptance environment?

The step beyond IT implementation is often missed out in reality. Cultures and relationships do play a key role in many of IT implementation on the field. Likewise, resistance to new system is norm. It is best that we create a favorable environment to accept resistance before we go for new system implementation.

Request for Proposal (RFP) is a good information gathering process. It is also one of the most annoying part in acquiring a new business. For the incumbent, RFP sounds like a formality because they have home advantage. Thus, RFP plays an important role in soliciting information and understanding of the vendors.

Setting Expectations

RFP is a good way of setting expectations. Sometimes, these expectations can translate to answers that you may not have thought of it. There are also instances where RFP is seeking answers to all available aspects. This will make you ponder the scope of RFP. Thus, you must always make use of this stage to align expectations. An experienced team in RFP will know how to clarify and balance expectations leading to a higher chance of success.

Template your RFP Responses

It is surprising to see many teams scramble to answer RFP at the last minute. RFP is a pretty standard process with minor variations across the board. If your team is constantly dealing with RFP, it is worth investing to template your RFP responses. There should be a cookbook for dealing with RFP. You should not approach each RFP as though it is new. There should also be a set of common clarification to review the RFP.

Creating and responding to RFP will get easier as you build up your templates and knowledge base. Unfortunately, not all teams are well adept to handling RFP. It pays to seek advice if you do not handle RFP often. With practice, RFP will be a breeze to win!

During software upgrades, it is common to encounter dependencies or showstopper that will cause havoc to your planned activities. Thus, one of the items that I always look in a plan is the catch-up plan. After all, you need to anticipate and mitigate risk like delayed dependencies. A well crafted catch-up plan can reduce the impact from delays or even meet the intended delivery date.

Ways to Catch-up

Many of standard catch-up plan requires flexibility and autonomy to your intended project plan. The first step is to obtain the authority to amend and modify the planned activities. You can also reallocate your idling resources to do tasks that have little dependencies. Another approach is to make use of the downtime to look into automating tasks. This helps to reduce and catch-up on the delivery dates. Do note that adding resources could run counterproductive due to tight timeline.

Catch-up Tips

There are no catch-up plans that will not work. These are some tips that you can consider for your catch-up plans.

• Build a collaborative catch-up plan to meet tight delivery date.
• Automate mundane and routine tasks.
• Allocate your best resources for catch-up plan.
• Do not turn your catch-up plan into the main plan.
• Commit to the success of catch-up plan for a realistic goal!

The catch-up must be triggered if the anticipated delays are affecting your project schedule. You need to commit to the success of your catch-up plan. There is no point to initiate a catch-up plan if it is impossible to meet the timeline. Finally, a well executed catch-up plan can make or break your project.

Software upgrade in mobile phone is a bliss with automated updates. You can even schedule the upgrades when you are asleep. All these are so ubiquitous that we take little note of it. The agony comes when your upgrade is stuck. This is where you are required to either not upgrade or change your existing mobile phone. Sounds familiar? These are common options faced in all applications.

Do Not Upgrade

Unfortunately, the option not to upgrade have an expiry duration. The period that you are not required for upgrade is likely last two years or so. After this duration, existing applications cannot support the older version. You may also realise your application cannot work for older version. In some case, the software upgrade is not supported in your older mobile phone. An example is Internet Explorer (IE) where you need to switch. Other risks are security patches and audit concerns for applications.

Fix the Root Cause

The root cause for stuck upgrade is a tough process. Standard support requested are logs from your mobile. You may find these root cause are mostly unresolved. Thus, typical resolution is to upgrade your hardware or mobile phone. Another form of resolution is the removal of customisation. The efforts to find the root cause for stuck upgrade will be a long waiting process. This stuck will end up as critical task.

Automatic software upgrade is envisioned for the future. However, it gets sticky if your upgrades are stuck. The options taken are standard for all applications. You can either forgo upgrade or find the root cause. The root cause is a time consuming process and you need to take account the wait time.

Project implementation have its ups and downs. For many, you will get your usual freeloaders and NATO (No Action Talk Only) members. In worst case, you may even get a self proclaimed project manager who is actually a project admin. The key is to ask yourself what you aim to achieve. This is also why you must stay positive in your project.

Why Stay Positive

If you are familiar with project implementation, you will realise that each ending provides better beginning. We tend to focus on negativity and grumble on how the project should be run. As you gained exposure, you will look back and realise staying positive is a better option. Being positive improves your oversight and gives you clear direction in the project.

Moving On

It is wise to stay positive and move on to the next project. There are some who cannot shake off negative energy from previous project. Some may even have PTSD (Post Traumatic Stress Disorder) from project. The right approach is learning to be positive and moving on with the correct learning. Of course, you may encounter good mentor who advocate positives. Steer clear of negative people and team members as they do not help in your project learning.

Project implementation can be fun and mentally challenging. I find it enriching to be positive in every project. Of course, I have also been to the dark side. You should also start to move on with positivity and leave your baggage behind.