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
Change Management Consulting Project Consideration | 远景管理咨询工作室

How to deal with function leader in change management project

Change management always initiated by higher leaders in organization hierarchy, whose purpose of change is sometimes jeopardize function leaders interests. Work as change management consultant, we have to deal with both high level leader and function leader. Some tacit can keep us free from trouble and makes both satisfied.
Remember and keep in mind who pay bill is most important.

When reform and change process goes deep, divergence emerging between function leader and high level office. If cooperate communication system break down during change process, function leaders will give consultant greatest pressure to maintain their benefit and resist change process. On the other hand, high level office urge to see outcome of project. All the pressure puts consultant at most difficult and dangerous situation. To get out of trouble, consultant first should understand who trust the assignment and its purpose, second make proposal appeal to all party involved, third listen to high leader and figure out their solution.
Consider proposal implementation carefully and makes all party involved. When implementation, consultant works as change facilitator, makes function leader involved: to lay out change plan, to find successor or to give lecture to subordinate and this activity can alleviate resistance and makes change process more smoothly. Draw function leader into change process and make them truly understand reason and purpose of change and unlikely they were against what they design and believe. More importantly, when function leader participate in change process, the divergence between them and high level office begin to shrink.
Report to high level office directly. Some function leader works as doorkeeper and watch out and check change project outcomes. When proposal goes opposite with their interest, they will hindrance process and make difficulty. To get project on track, consultant should find chance and channel to communication and report to high level office directly. If high level office approve proposal, the only thing function leader can do is get project on track and be careful about their behavior.

作者: 远景顾问

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

发表回复

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

这个站点使用 Akismet 来减少垃圾评论。了解你的评论数据如何被处理