The document discusses how to support and respond to change. It notes that while plans may be worthless, planning is essential. It advocates for continuous learning and discovering change, and emphasizes that change should be made as easy as possible. It stresses the importance of automated testing, evolvable code design, encapsulation, and good tests to create a safety net that is willing to change. The document concludes that while change is hard, experience, knowledge, and focus will help organizations try, try again to implement changes successfully.