Every project requires a certain amount of communication — perhaps a weekly report to the project team, quarterly presentations to the executive team, or meetings whenever a milestone is at risk. In the rush to start and finish a project, however, an organized approach to communication is often overlooked, which can result in increased calls to the help desk or support center, lower user acceptance, and in some cases, outright resistance to new technologies. This article presents a methodology for creating a communications plan to minimize such risks. It walks you through an example scenario, and provides tips and tricks along the way for improving communication during an SAP implementation project.