For many teams, implementing end-to-end automation in one go is too much abrupt change. A "crawl, walk, run" philosophy is better.

For maximum value, automation should be embedded throughout the incident life cycle — all the way from an incoming event signal to final resolution and learning. But for many teams, implementing end-to-end automation in one go is too much abrupt change. 

By Joseph Mandros, Product Marketing Manager at PagerDuty.