Motivation, Productivity, and Change Management

Motivation, Productivity, and Change Management are very closely linked. Proper motivation can increase productivity. Attempts to increase productivity can decrease motivation. Change Management can significantly impact productivity and motivation. There must be a balance. Here are some suggestions:

1. Define the meaining of productivity based on organizational goals. Productivity must be measurable and objective

2. Job responsibilities, career growth, and rewards must be defined in a way that directly or indirectly supports the goals of the organization. This increases motivatation and productivity.

3. Organizations should establish a culture of change where changes are both scheduled, expected, and managed. In other words, when Change should be the norm it is expected and there is less resistance. Acceptance of change should be rewarded which increases motivation and productivity.

4. Morale affects productivity, motivation, and Change acceptance. Sports teams undersand the importance of morale in achieving goals. Too many employers and managers are unconcerned with morale.

Application Portfolio Management Tool Cpabilities

There is growing discussion about Application Portfolio Management but there aren’t many supporting tools.  In order to effectively manage Application Portfolios, the following information should be tracked.

- Profile information about each application including purpose, business owner, support team, technology, interfaces, etc.

- Supported business processes and business benefits

- Schedule information

- Component inventory and relationships

- Financial information (Cost to develop/enhance, cost to support, cost to operate)

- Business priority and disaster recovery priority

- Security/confidentiality and types of data

- Long-term strategy and justification (operate, repair, replace, retire)

- Maintenance requirements (e.g. table maintenance)

- Library locations

Application Remediation Strategy

I was recently asked a question regarding how to create an application remediation strategy.  “Remediation” implies resolution of issues. In order to develop a remediation plan, you need to answer the following questions.

1. What are the goals and objectives the remediation initiative?

2. What are the business requirements that are not addressed by the existing applications?

3. What are the gaps/issues/risks that result from the current Application Inventory?

4. Why do these gaps/issues exist?

5. What are the options for addressing the gaps/issues?

6. What are the costs, risks and expected ROI for each option?

7. What impact will the remediation plan have on existing project and support priorities?