Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dayanging/public_html/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dayanging/public_html/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dayanging/public_html/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dayanging/public_html/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dayanging/public_html/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dayanging/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dayanging/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dayanging/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dayanging/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dayanging/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
Communication Aspect of Change Management | 远景管理咨询工作室

Communication Aspect of Change Management

Change management involves people to modify and adapt something new and different, but first, they must informed about reason, direction and way to change. In change management process, communication becomes crucial and center, open communication system can facilities the whole process. On the contrary, without formal communication mechanism, grapevine and rumor will prevailing, in the end, change process jeopardizes productivities of whole enterprise.
For business consultant in change management project, some tacit can help establishing communication system which can insure smoothly transformation.
Report Process: Before project launch, designing clearly path way of reporting is necessary and requisite. Generally, change management project impact whole system, and should be reported according to firm hierarchy system. Carefully design meetings with functional manager, pay attention to and listen carefully to their demand, emotional appeal can make project ran smoothly. During communications with functional manager, consultant face with problem of information overload, and should distinguish between usefully and wasted ideas. From reporting process, consultant should draw basic conclusions and verified by data analyzed.
Decision Process: After reporting to functional manager, and change strategy designed, consultant will involve themselves in decision process. Finding economic buyer and find their preference is of vital importance. Step by step buy in higher officers before reporting can insure there is no discrepancy between them and makes reporting easy and discussion free. For argument and debate in meeting means extra work and risks for consultant.
Propaganda Tacit: Change management project with aim to modify and mobilize all people involved, so propaganda strategy should be given special consideration. Like commercial promotion, consultant should use all resource available, internal meeting, email, and social media, to clearly deliver messages of change direction, purpose and relevant benefit. Message should be realistic and without exaggeration. Some special group whose interesting is impacted by change process should be given extra consideration and design special method and way of communication.
Success of change management project depend on many factors, but communication play large part of it, without system thinking and designing of communication system, change management project is bound to fail.

作者: 远景顾问

Business consultant, focus on improving people, process and performance.

发表回复

您的电子邮箱地址不会被公开。 必填项已用*标注

此站点使用Akismet来减少垃圾评论。了解我们如何处理您的评论数据