Unfortunately, the unintended consequences of this might be that insufficient planning takes place or an appropriate level of stakeholder engagement is not achieved. In both cases, stakeholder dissatisfaction and increased numbers of project issues and change requests arising from missed requirements are likely to be the outcomes. You might argue that an agile project lifecycle would avoid this situation, but even with such projects, cutting corners by reducing effort spent on key architecture or design work in early sprints will result in waste in later sprints.
Sometimes the request from stakeholders is not to focus on reducing the time to complete planning, but rather to shorten overall duration before the very first deliverable is implemented. This is a reasonable expectation – projects are investments, and the longer the customer has to wait to realize the expected outcomes, the greater the likelihood that external influences will reduce benefits.
One of the more common unintended consequences of a push to reduce change delivery duration is reduced deliverable quality. As we know, increased defects results in a higher cost of quality including waste, damaged relationships with suppliers and customers, reputational damage and an increased likelihood of legal action against the company. Worse yet, such a focus can have long term behavioral impacts on the organization – once staff learn that leadership emphasis is on the speed of delivery instead of how those results were produced, it can be extremely difficult to re-instill a culture of quality.
But let’s say that deliverables are still being produced with acceptable levels of quality – should we claim mission accomplished?
In such cases, change sustainability might be the Achilles heel of the reducing time to market movement. Just because project deliverables have been implemented, doesn’t mean that desired change outcomes have been realized.
When corners are cut in analyzing change impacts on stakeholder communities, preparing these stakeholder communities for the change, progressively communicating to affected stakeholders, cultivating change champions and advocates, and using high touch approaches of overcoming short term resistance and soliciting feedback, expected behavior changes are likely to be short-lived.
This impacts not only the successful realization of a given project’s benefits but will result in a corresponding increase in the levels of change stress in affected stakeholders which in turn will cause reduced resilience and appetite for further changes.
So how can the unintended consequences resulting from a focus on reducing time to market be avoided?
The key is to design a performance evaluation model which utilizes a holistic approach to measuring project success. While time to market, or cost of delivery are important, there also needs to be post-project metrics focusing on the volume of defects, quantifying the degree of compliance with expected behaviors, measuring stakeholder satisfaction, and evaluating overall benefits realized.
You can only manage what you measure, but if you short-change what you decide to measure, you will get what you paid for!
Don't forget to leave your comments below.