Monitor Post-Implementation Performance

The solution development process is iterative. The previous steps focus attention on the maintenance and operations of assets and programmatic solutions, and through that process we can identify performance gaps. Those performance gaps feed into the planning process where we identify needs. If a solution warrants a new programmatic strategy or asset, it will pass through the design process and implementation. That new asset or program will then enter back into the Maintenance Operations process. In some cases, the strategy will be implemented primarily by partner agencies, who will need to provide post-implementation performance data.

Monitoring the performance of this asset or program and identifying any need for modifications are key to the success of this process. The insights from this review can feed back to the asset management task and possibly lead to the identification of additional needs within a corridor or subarea. 

Do measures need to be evaluated after implementation?

The answer depends on the work you are doing and the measure you are using. WSDOT reports some measures (e.g. MAP-21 measures) on an ongoing basis due to federal requirements, some measures (e.g. Annual hours of delay per traveler as reported for each biennium by WSDOT’s Office of Financial Management) periodically due to state requirements, and some measures WSDOT tracks over a longer time frame to gauge effectiveness (e.g. Commute Trip Reduction measures). Other measures are used to make specific decisions. Refer to the guidelines in your business area for how long to collect information about and report on performance measures.