Are we underestimating the importance of a well thought Change Management Strategy when developing Communications and Business Readiness deliverables?
Soon enough I learned that if you underestimate the need of Change Management you're going to end up in a pretty hot mess or in a lot of meetings pointing fingers, blaming each other on the project team. And I can tell you neither of those things are pleasant!
Letting personal opinions or rule of thumb govern critical engagements are costly mistakes, especially when implementing technologies that affect a large number of users across the board. Why would you take the risk of underestimating users' reactions when the project you're working on will change their way of working? There are multiple cases studies demonstrating how projects failed for overlooking the importance of human interactions and for not having a Change Management Strategy in place.
Then again if you bottle everything and carelessly continue preparing deliverables just to check the boxes; then, don't expect anything more than lack of support from impacted users. No proper Business Readiness Assessment or Communications Templates can be delivered, if you don't have thorough Change Management Strategy to start with.
Really, if you aspire to achieve more than ordinary results in your technology implementation projects and minimize push-back from end users, just give Change Management the place it deserves in every engagement and don't make the mistake of oversimplifying people's impact. Instead, plan accordingly and build some contingency in your projects to account for stakeholders' resistance, which is an inevitable response to any major to change.