Deprecated: Optional parameter $function declared before required parameter $page is implicitly treated as a required parameter in /home/swalsh/public_html/wp-content/plugins/cron-view/plugin.php on line 201

Deprecated: Creation of dynamic property autoptimizeImages::$lazyload_counter is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php on line 34

Deprecated: Creation of dynamic property autoptimizeCompatibility::$conf is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeCompatibility.php on line 18

Deprecated: Creation of dynamic property autoptimizeCriticalCSSCore::$criticalcss is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeCriticalCSSCore.php on line 20

Deprecated: Creation of dynamic property autoptimizeImages::$lazyload_counter is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php on line 34

Deprecated: Creation of dynamic property Smush\Core\Modules::$webp is deprecated in /home/swalsh/public_html/wp-content/plugins/wp-smushit/core/class-modules.php on line 109

Deprecated: Creation of dynamic property Jetpack_Publicize::$modules is deprecated in /home/swalsh/public_html/wp-content/plugins/jetpack/modules/publicize.php on line 38

Deprecated: Creation of dynamic property Automattic\Jetpack\Publicize\Publicize_UI::$in_jetpack is deprecated in /home/swalsh/public_html/wp-content/plugins/jetpack/modules/publicize.php on line 101

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/swalsh/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/swalsh/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/swalsh/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/swalsh/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/swalsh/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/swalsh/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/swalsh/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/swalsh/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/swalsh/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/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
Social Media training for players - What can football clubs do? - Digital-Football.com - Football Social Media & Digital Sports news

Social Media training for players – What can football clubs do?

Since football clubs and players started to take advantage of Social Media platforms like Twitter, Facebook and Instagram, the most popular area of discussion has been player mishaps from controversial tweets through to leaking match tactics.

One of the biggest challenges many football clubs face is how can the limit the occurrences of such instances and how do they do this with players from academy level up to the first team. Furthermore, the challenge is made harder by the fact that players regularly come and go, meaning that clubs need to ensure that whatever tactics they do, that it happens constantly.

With this in mind, we look at the options open to football clubs in dealing with the issue of problematic players on Social Media:

social-media-ban1. Ban Social Media

Perhaps not as popular as it was several years ago, banning Social Media is undoubtedly the boldest of options available to clubs and usually stems from the manager’s reluctance to understand the value in Social.

Whilst simply banning players from Social Media sounds like a logical solution for stopping players saying stupid tweets (or anything at all), it’s turned out to be unenforceable and present the club in bad light with their fans. The temptation to ban Social Media might solve the problem in the short term but it never works in the long.

Mauritius_Road_Signs_-_Warning_Sign_-_Other_dangers2. Create a deterrent

Fining players, or even dropping them from footballing duties, due to bad Social Media practice can act as a good deterrent for players, particularly if the deterrent is strong enough. A strong deterrent might deter players from leaking information or making stupid comments.

However, with the wages so high in football and many players making their controversies post-match or in an emotional state, sometimes this minute lapse in thought is enough to cause the crisis.

rules_1668_16683. Provide Social Media guidelines

Social Media guidelines are generally the starting point for most Social Media training campaigns. A good Social Media guideline document provides players with a point of reference for the rules as well as something to help educate players on what’s expected of them.

Guidelines must be engaging, to the point and easy to digest however, as many simply produce several pages of A4 black and white paper that is likely to be shoved into a drawer and never read.

trainingsesh4. Educate with experience

Many clubs have began inviting Social Media training experts into the club to help run sessions with the players where the best and worst scenerios/case studies can be clearly demonstrated and explained. The very best sessions are ones that don’t preach to players but directly engage them.

Pulling out real examples from the squad is a fantastic way of creating an atmosphere where players can enjoy a bit of banter but also see the effects of their tweets for themselves

socialpundit5. Realtime monitoring

A very recent development to Social Media protection for football clubs is a new piece of technology called Social Pundit. The platform allows clubs to monitor players tweets (From academy to senior squad) 24/7 against a database of “trigger words”.

Should a player tweet something that is in the database, it will ping an email alert to the club and record the tweet (regardless if the player quickly deletes it or not). This system helps clubs identify problem players as well as act as a good deterrent to players on Twitter.

pressconference6. Trial and test players

An excellent initiative created and used at Birmingham City FC is the use of mock press conferences and integrating real Social Media content from a players own Social Media to test their reactions and make them aware of how it can be used against them.

Birmingham City cleverly use a players own Tweets (usually the ones of a controversial nature) against him/her to illustrate just how easy it is for something as innocent as a tweet to quickly put the player in a difficult spot.

7. Focus on the positives

Ultimately one of the best tactics a club can undertake is not just focusing on the negatives but encouraging players to use Social Media in a positive manner. Many clubs have success with players by showing them how a good Social Media presence can help them commercially in life after football.

By encouraging footballers to build a strong, honest and engaged Social Media community – clubs hope to avoid mishaps as well as leverage the players own audience for the brand.

Sean Walsh

Founder of Digital-Football.com and leading Football Social Media expert.

You may also like...

1 Response

  1. Gene Wheeler says:

    These are useful tactics but for me, banning the social media will only create chaos. Yes, sometimes social media can be very intrusive but there are a lot of positive sides of this type of media if only used right and not abused. http://www.industrial-dvd.com/

Leave a Reply

Your email address will not be published. Required fields are marked *