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
雇主品牌之—什么时候需要雇主品牌(When Need Employer Branding) | 远景管理咨询工作室

雇主品牌之—什么时候需要雇主品牌(When Need Employer Branding)

企业总是在出现问题的时候开始考虑外部劳动力市场的问题,正如企业的薪酬政策一样,当企业发现大量的优秀员工流出企业,才开始意识到系统性的问题。笔者原来工作过的一家企业,负责研发的科研人员在一周之内有5人离职,致使企业的研发工作完全停摆,一打听才发现竞争对手以高于公司薪酬标准的60%强力挖掉了我们的研发队伍。对雇主品牌也一样,企业在出现招聘问题时,才开始认证思考在那里出现了问题。


雇主品牌是雇主在劳动力市场上的幽灵,无论雇主承认与否,在本地的就业市场上,雇主的口碑(word of mouth)就是某种意义上的品牌,只是这种品牌是蹩脚的而已,甚至是负面的。尤其是在网络时代的今天,雇主的负面东西会传播的比病毒还快,其影响范围非常之大,甚至影响到公司品牌本身。正如一世界五百强招聘高级经理所说的:“应聘者到我们公司参加面试,如果体验是很糟糕的,那我他会离我们而去,甚至终身彻底抛弃我们的品牌。”所以,当企业在本地就业市场上的口碑出现问题时,通常需要考虑雇主品牌建设。
雇主品牌的研究始于招聘及劳动力市场,当企业的财务人员发现招聘的费用过大时,尤其是对高端人才招聘的费用过大时,应该思考进行彻底的雇主品牌建设。猎头顾问的兴起与雇主品牌力量的微弱是成正相关的,研究发现越是依赖于猎头的公司,其雇主本身的品牌或口碑就越差,同时,企业付给猎头的费用也是不菲的,大概是年薪的10-20%。如果企业招聘的优秀员工在18个月内离职率不断攀升,那么企业真的需要进行雇主品牌的建设。研究发现,新入职人员的离职通常是在应聘过程中雇主的承诺与在企业中实际工作的感受完全相悖时发生的,因此,很有必要进行雇主品牌建设,使优秀员工感觉到雇主言行的一致性,感觉到自己的决策是正确的完美的。在实际研究过程中发现,人们通常不情愿自己的熟人与自己的雇主建立某种商务性的联系,同时,也不情愿与其他人谈论自己的雇主;有的人从内心来说喜欢自己的雇主,但是不知道怎样去诉说,雇主品牌就是一种强有力的沟通与交流工具,方便雇员清晰的告诉别人,他在为随工作、为什么为这样的雇主工作。当企业内部员工开始挖苦雇主各种流言蜚语漫天的时候,这种现象应当引起企业的人力资源部门的高度重视。产生这种现象的原因是很多的,但雇主与雇员之间的心理契合(psychological engagement)出现问题是通常的原因,这时开始雇主品牌建设,有助于在问题的早期将雇主与雇员之间的裂痕弥补。
总之,企业发现自己在本地就业市场的口碑出现问题,发现招聘费用攀升,尤其是高端人才的招聘过度依赖猎头公司,发现雇员不愿意告诉他人自己的雇主是谁,发现企业内部的员工对雇主的微言甚多时,企业确实需要认证思考怎样在劳动力市场上建立雇主品牌,并用品牌的力量解决更大范围的人力资源与员工关系管理问题。

作者: 远景顾问

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

发表回复

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

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