Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_posts_where() should not be called statically in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line
57
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_search_where() should not be called statically in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line
57
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_posts_join() should not be called statically in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line
57
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_search_join() should not be called statically in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line
57
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_posts_groupby() should not be called statically in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line
57
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
14
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
27
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
28
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
14
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
27
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
28
Leitartikel
Von Martina Goehring am
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 14
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28
22. März 2010 in Leitartikel, Internet und Banking, Innovation | 1 Kommentar
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/coolplayer/coolplayer.php on line
134
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/coolplayer/coolplayer.php on line
135
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/formatting.php on line
74
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_the_content_filter() should not be called statically in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line
57
Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line
669
Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line
669
Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line
670
Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line
670
Vor kurzem bekam ich eine E-Mail vom Autor des Buches Bank 2.0 Brett King, in der er mir einen Auszug daraus schickte. Auch wenn sich das Konsumentenverhalten in Deutschland z.B. bei der Verwendung von Kreditkarten oder im Verhältnis Privatkunde zur Bank von dem in anderen Ländern unterscheidet, sind dennoch die technologischen Trends vergleichbar. Auch die Zurückhaltung der Banken in Bezug auf Enterprise 2.0 oder das Festhalten an Strukturen aus den 90er Jahren sind global ähnlich.
Daher kann ich die Inhalte von Brett King in seinem Blog Banking4tomorrow unterstützen. Die Paypal-App gibt es schon. Was tun eigentlich die Banken, während sich Apple und andere Hersteller mobiler Endgeräte auf die “Euro-App”, mit der ich in Zukunft meine Einkäufe bezahlen werde, vorbereiten? Ein Beitrag dazu von Brett King.
Da es auf dem Markt nicht sehr viele Bücher zu diesem Thema gibt, stelle ich die Infos hier zur Verfügung.
PressRelease zum Buch Bank 2.0 von Brett King:
Download (2757)
Warning: Creating default object from empty value in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 403
-
-
Artikel im Bankenforum
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
14
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
27
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
28
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
14
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
27
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
28
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
14
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
27
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
28
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
14
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
27
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line
28
Von Martina Goehring am
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 14
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28
25. Februar 2009 in Marketing, Leitartikel, Internet und Banking | 2 Kommentare
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line
75
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line
89
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/coolplayer/coolplayer.php on line
134
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/coolplayer/coolplayer.php on line
135
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/formatting.php on line
74
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_the_content_filter() should not be called statically in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line
57
Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line
669
Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line
669
Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line
670
Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in
/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line
670
Aus der Diplomarbeit von Michael Mertens ist ein Whitepaper entstanden, welches die Quintessenzen sowie relevantes Wissen und die Hebel im Online Marketing zusammenfasst und in Potentialaussagen bzw. Handlungsempfehlungen für Volks- und Raiffeisenbanken mündet.
Ich versuche mal, die wesentlichen Empfehlungen zusammenzufassen und mit eigenen zu ergänzen:
Am Anfang steht das Wissen was und warum
Zunächst sollte das Wissen bei Bankenmitarbeitern über Entwicklungen im Bereich Online Marketing und Kundenverhalten im Internet verbessert werden. Das leistet am besten ein interner Workshop, indem auch Vorschläge und Ideen der Mitarbeiter, die ja direkt mit dem Kunden zu tun haben, aufgegriffen und honoriert werden. Die besten Ideen liegen meist in den Schubladen der Mitarbeiter. Hilfreich sind auch Beispiele anderer, die man mit diesen Ideen auf die eigene Situation überträgt.
Weiterlesen
Online Marketing bei Volks- und Raiffeisenbanken (Whitepaper von Michael Mertens):
Download (2143)
, Banking Strategy 