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
管理咨询项目教练 | 远景管理咨询工作室

管理咨询项目教练

过完国庆回到项目上,开始对客户进行培训,在第一个班的培训上,我讲了大量的理论、项目思路、工具方法,讲的十分深入浅出,客户在听讲的过程中,似乎也有很大的收获,似乎感到通过培训已经能够进行指标提炼,办法起草等工作。但是,经过两天的培训,有几个学员离开课堂,走到电梯间时忽然告诉我,现在他觉得还是什么都不懂、什么都不会做,这令我开始审视项目的辅导方法。

咨询项目的辅导与培训之间有很大差异,其一,培训只解决知识转递问题,培训目的是让客户具有必须的理论知识,其二,培训不解决系统的操作技能传递问题,既然传统的培训具有那么多的局限性,项目上的培训与辅导必须根据项目设定的目标设计不同的培训及辅导项目,将培训及教练紧密结合在一块,以达到使项目形成的方法及思路能够传递给客户的相关人员。

在第二个培训班上,我将理论培训的时间缩短,用尽量简单的实例告诉学员运用的理论,然后开始与学员就人力资源部的岗位指标进行现场提取,最终各个小组都得到了能够使用的岗位指标,学员离开课堂的时候,我问学员回去后能不能提炼指标,他们告诉我,没有问题啦。

看来,在项目的辅导过程中,可能在很多情况下,教练比单纯的培训可能更为有效。

作者: 远景顾问

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

发表回复

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

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