Introduction
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 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.
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 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.
