Technology (especially “project management software”) has been and will continue to be an important part of project management discussion and practice. This is justified. The right project management software that is implemented correctly can have significant, positive effects on an organization. However, the wrong software, or software implemented poorly can pull an organization down.
In our experience, we have seen organizations struggle with the proper implementation of the right project planning software. Many times we find this stems from a limited or misunderstood view of the purpose of technology in the first place. For example, organizations may look for a tool that can just “schedule projects”, or they simply do not think through the broader, strategic purpose that the technology should serve. This leads to selecting the wrong technology or not implementing it in a way that provides the most value for the organization.
The purpose of this white paper is to provide a fresh perspective on 5 major purposes of technology (and project management software in particular) in project management.
These purposes come from lessons learned in the aviation field. The aviation field is similar to project management in the sense that it seeks to create predictable, successful outcomes in an activity with inherent risk. It utilizes technology heavily to fulfill that objective. By studying the role of technology in aviation, we can derive the major and similar purposes that technology should serve in project management. In so doing, we can also boost the strategic use of technology to support our organization’s strategic objectives, needs, and processes.
Purpose 1: Situational Awareness
Some of the most important aviation technologies, such as the ILS (instrument landing system), glass panel displays, and GPS (global positioning system) are focused on situational awareness: letting the pilot know at every moment where the aircraft is headed, how it is oriented, how high it is, where it needs to go, how it is performing, or a number of other pieces of information.
Project management technology is no different. It needs to provide situational awareness of each project’s situation, where they are headed, how they are performing, and how they need to proceed. It also needs to provide awareness of the situation of an organization’s entire project “portfolio.” If you cannot utilize your technology to know the current situation of your projects, you are not utilizing technology effectively.
The “current project situation” may be different depending on your organization and its particular processes and objectives. It may mean the status of the project schedules, the quality of the deliverables, the current degree of risk, the satisfaction of the clients, or the state of the budget or profit numbers.
It may mean how current resource utilization will affect the project, what issues have arisen that would derail the project, or what has slipped through the cracks.
The important thing is to always be aware of the project situation so that you can make intelligent, timely, well-informed decisions.
You can factor this into your project management technology implementation by doing the following:
Identify the key information that you need to maintain situational awareness.
Ensure that your PROJECT MANAGEMENT software tool(s) can track and provide this information.
Train your staff on providing this information within the tool.
In aviation, pilots must be able to make quick decisions using accurate data. For example, a pilot needs to know exactly what is wrong with the aircraft to make a good decision on next steps. They need to know how much fuel is remaining to make a decision on weather avoidance.
Similarly, managers need to have accurate data to make decisions in project management. They need to know what is wrong with a project so they can make a good decision on next steps. They need to know resource availability to prioritize efforts and choose directions. In many organizations, this type of information is not readily available, either because the right toolset is not in place or the toolset has not been implemented in a way that supports this strategic purpose.
Comments