Strict Standards: Redefining already defined constructor for class wpdb in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/wp-db.php on line 52

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/cache.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/cache.php on line 389

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 556

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 678

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/theme.php on line 508

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/disclose-secret.php on line 102

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/manager.php on line 44

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/manager.php on line 58

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/manager.php on line 59

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/manager.php on line 60

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/cache.php on line 28

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/cache.php on line 37

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/option.php on line 156

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/option.php on line 403

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/migrator.php on line 24

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/migrator.php on line 27

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/migrator.php on line 30

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/migrator.php on line 33

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/migrator_post_levels.php on line 117

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/config_ui.php on line 71

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method JAWPopularPostsWidget::load() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 160

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method Ajax_Comment_Preview::init() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 160

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGenerator::Enable() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 160

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_query_vars() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57

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 137

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 114

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: 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/classes.php on line 212

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: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_tag_templates() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 160

Warning: Cannot modify header information - headers already sent by (output started at /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/wp-db.php:52) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/feed-rss2.php on line 2
Bank 2.0 » Management http://www.bank-zweinull.de IT-Trends und Innovationen für Banken
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 137

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
Mon, 28 Jul 2014 17:10:49 +0000
http://wordpress.org/?v=2.2.3 en © Martina.Goehring@centrestage.de () Martina.Goehring@centrestage.de IT-Trends und Innovationen fuuml;r Banken Martina.Goehring@centrestage.de No no http://www.centrestage.de/banking/wp-content/plugins/podpress/images/powered_by_podpress.jpg Bank 2.0 http://www.bank-zweinull.de 144 144
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
<br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> Banking 2.0 Lernen mit Social Software - Teil 2
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
http://www.bank-zweinull.de/2010/02/04/banking-20-lernen-mit-social-software-teil-2/
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
http://www.bank-zweinull.de/2010/02/04/banking-20-lernen-mit-social-software-teil-2/#comments

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
Thu, 04 Feb 2010 07:03:14 +0000
Martina Goehring
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_add_tags_to_rss() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57
Enterprise 2.0InnovationLernenTwitterZürich http://www.bank-zweinull.de/2010/02/04/banking-20-lernen-mit-social-software-teil-2/ 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

Logo der Fachhochschule NordwestschweizIm Workshop Teil 2 zum Thema  “Banking 2.0- Lernen mit Social Software” veranstaltet von der Uni Zürich und der Fachhochschule Nordwestschweiz haben wir die Einsatzpotenziale von Web 2.0-Anwendungen in typischen Lernsituationen in einem Unternehmen diskutiert. Einige Diskussionspunkte werden hier zusammengefasst:

Web 2.0 im Vertrieb

Es wird trotz grundsätzlich kritischer Betrachtung des Themas ein hohes Potenzial im Vertrieb und bei den Bankenberatern gesehen. Da geht es einerseits um das Wissen für aber auch über den Kunden und andererseits um das Wissen, das die Bankberater benötigen, um qualitativ hochwertige Dienstleistungen liefern zu können. Letztlich geht es hier um eine laufend aktuelle Qualifizierung.

Je mehr komplexe Produkte und fachübergreifende Produktbouquets angeboten werden, desto weniger reicht das Wissen des Einzelnen aus, die Kunden umfassend zu bedienen. Dieses für eine umfassende Beratung notwendige Wissen können einzelne Berater nicht mehr selbst aufbringen. Das Wissen entsteht und liegt in den Netzwerken, sowohl in den Persönlichen, als auch in sozialen Communities, in denen sich Experten austauschen. Diese Netzwerke machen keinen Halt an der Unternehmensgrenze. Umso wichtiger werden daher auch die Aspekte zur Kultur, Regeln und Reputation (siehe Teil 1). Für einen guten Vertrieb und eine exzellente Beratung müssen Wissensnetzwerke ein zentrales Thema für Banken werden.

Formales versus informales Lernen

Vielleicht weil es auch so schön einfach ist, wird hier oft die 80:20-Regel angewandt. Lernen findet zu 20% in formalen Kursen und 80% informell am Arbeitsplatz statt. Es gibt dazu viele Studien, die dieses Verhältnis auch belegen.

Web 2.0 ermöglicht es nun aber, diese Regel aufzubrechen. Zum einen dadurch, dass es vielfältige Formen der Nutzerbeteiligung zulässt und zum anderen durch das Mixen und Mischen von formal und informal. Wie muss man sich das vorstellen?

In formalen Lernprozessen werden Kommunikations-, Kollaborations- und Community-Möglichkeiten eingebunden, die adhoc Konversationen erlauben, eine situative Zusammenarbeit ermöglichen oder einen Experten zum gesuchten Thema schnell finden lassen.

Formales und informales Lernen verschmilzt zunehmend zu sozialem Lernen.

Gestaltungsaspekte für soziales Lernen

Betrachten wir Web 2.0 im Lernen, wird immer wieder die Frage gestellt: In welchen Bereichen von Lern- und Wissensprozessen können die Konzepte, Methoden und Technologien des Web 2.0 Unterstützung und Verbesserungen insbesondere durch Kommunikation, Kollaboration und Vernetzung bringen? Erste Gestaltungsaspekte wurden angesprochen:

  1. Lerninhalteproduktion mit Wikis und Microblogging, sozialen Medien unterstützen.
  2. Curriculum mit Wikis entwickeln.
  3. Individuell Lernen mit Blogs für das persönliche Wissensmanagement oder Communities für den Wissensaustausch.
  4. Gruppenlernen mit Kommunikation im Microblog, Vernetzung in Communities und gemeinsame Inhalteerstellung in Wikis.
  5. Seminare mit Twitter begleiten, um Nutzerinhalte einzubeziehen.
  6. E-Learning Inhaltedesign und –produktion mit Wikis und Microblogging.
  7. Blended Learning nicht nur ein Mix aus E-Learning und Präsenzphasen sondern erweitert durch “Web 2.0 Phasen” mit Blogs, Twitter, Microblogging, Communities und Wikis.
  8. Persönliche Lern- und Arbeitsprozesse mit einer Personal Learning Umgebung (PLE) am Arbeitsplatz unterstützen.
  9. Lernen und Wissensaustausch in Arbeitsteams mit Blogs, Twitter, Microblogging, Communities verbessern.

Meine Beiträge zur Veranstaltung

Kurzpräsentation zum Thema “Lernen mit Twitter”:

Zum Download auf slideshare.

Präsentation zum Thema “Banking Innovations und Einsatzpotenziale von Web 2.0″:

Zum Download auf slideshare.

Update vom 07.02.2010:

Eine kritische Bestandsaufnahme und Ergänzung des veranstaltenden Kollegen Matthias Rohs findet sich in seinem Blog 2headz. Er wirft die Frage auf:

“Kann man Banking 2.0 als Beschreibung für den Einsatz von Web 2.0 in der Kundenkommunikation mit internem Lernen unter Einsatz von Web 2.0 verbinden oder gar gleichsetzen?”

Ein erfolgreiches Unternehmen ist auch ein lernendes Unternehmen. Das hat Peter Senge schon vor zehn Jahren mit der fünften Disziplin in The Learning Organisation nachgewiesen. Lern-, Wissens- und Bildungsprozesse im Unternehmen zu separieren von der Qualität im Arbeitsprozess, in der Führung oder vom unternehmerischen Handeln ist nicht zielführend, wenn ein lernendes Unternehmen auch ein erfolgreiches Unternehmen sein soll.

]]>

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
http://www.bank-zweinull.de/2010/02/04/banking-20-lernen-mit-social-software-teil-2/feed/

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
<br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> Banking 2.0 Lernen mit Social Software - Teil 1
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
http://www.bank-zweinull.de/2010/02/03/banking-20-lernen-mit-social-software-teil-1/
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
http://www.bank-zweinull.de/2010/02/03/banking-20-lernen-mit-social-software-teil-1/#comments

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
Wed, 03 Feb 2010 10:43:34 +0000
Martina Goehring
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_add_tags_to_rss() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57
ComplianceEnterprise 2.0InnovationLernenOpen SpaceReputationZürich http://www.bank-zweinull.de/2010/02/03/banking-20-lernen-mit-social-software-teil-1/ 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

Logo der Uni ZürichMontag, 01. Februar war ein interessanter Workshop, veranstaltet von der Uni Zürich und der Fachhochschule Nordwestschweiz zum Thema “Banking 2.0- Lernen mit Social Software“. Die Teilnehmer waren aus Schweizer Banken und Finanzdienstleistern sowie eine Referentin der Deutschen Bank. Es ging um den Einsatz von Web 2.0 bei Banken und Versicherungen. Der Themenfokus war Lernen im weiteren Sinne verstanden als Kommunikation, Wissensmanagement und HR.

Es waren sich alle einig, dass Web 2.0 in den Banken bislang eher verhalten ankommt. Experimentier- und Pilotanwendungen sind zwar durchaus bei einigen im Gange. Umfassende Konzepte zur Integration in die geschäftlichen Prozesse und Erfolgsmessungen sind aber nur bei wenigen an der Tagesordnung. Aktuelle Studien vom IAO und IBI bestätigen dies. Man muss wohl in dieser Branche noch etwas Geduld haben.

Einige Lessons learnt habe ich mitgenommen.

Ideenmanagement

Positive Erfahrungen wurden z.B. im Ideenmanagement gemacht. Eingebettet in ein Open Space Programm mit anschließender Kommunikation in Blogs, kann Web 2.0 die Beteiligung von Mitarbeitern an den Prozessen der Bank insbesondere in einer Krise erhöhen und kollektive Kräfte freisetzen. Der Grund dafür wurde von einem Teilnehmer an einem netten Beispiel verdeutlicht:

„Wenn ich in Basel in den Rhein pinkle, ist es auch in Köln und Düsseldorf noch vorhanden, aber keiner sieht mehr was davon.“ Im Gegensatz dazu „komme ich mit Web 2.0 immer wieder an den Anfang zurück.“

Und am Anfang steht das Individuum. Ideen Einzelner werden ergänzt, erweitert, verändert, bewertet, aber sie werden nicht verwässert. Man kann immer nachvollziehen, von wem sie stammen. Diese Transparenz und Anerkennung schaffen Vertrauen darin, Wissen zu teilen und weiterzugeben.

Kultur

Kontrovers waren für mich die Aussagen von Teilnehmern aus Großbanken auf die Frage: Gibt es eine Web 2.0 Kultur?

Ein Teilnehmer: “Die grundsätzlichen Werte einer Bank “Disziplin und Kontrolle” passen nicht zu Web 2.0.”

Anderer Teilnehmer: “Es gibt keine Kultur, die nicht Web 2.0 fähig ist. Der Erfolg liegt im organisatorischen Setting. Methoden und Tools des Web 2.0 ersetzen nicht das Setup.”

Das Setup wurde als eine gelungene Mischung aus neuen Technologien und alten Formaten beschrieben.

Beispiel: Erfolgreiche Blogbeiträge von Mitarbeitern werden in der Mitarbeiterzeitung namentlich abgedruckt.

Damit werden gewissermaßen zwei Ziele erreicht:

  1. zum einen erhalten die Mitarbeiter Anerkennung durch die Veröffentlichung ihrer Beiträge und
  2. zum zweiten werden auch Mitarbeiter erreicht, die mit neuen Technologien und Web 2.0 eher zurückhaltend sind. Sie werden sanft an das Thema herangeführt und eingebunden.

Gesetzliche Regeln

Die Einhaltung der gesetzlichen Anforderungen an Banken wurde als das größte Killerargument für Web 2.0 gesehen. Bevor hier noch keine Umsetzungskonzepte vorliegen, wird es Web 2.0 als Kanal nach außen bei Banken schwer haben. Einige Banken haben aus diesem Grund bereits angelaufene Kanäle in Twitter oder Communities schon wieder geschlossen. Es wurden aber auch erste, wie ich finde, pragmatische Lösungen diskutiert.

So dürfen die Mitarbeiter in einem Bankeninstitut nicht mehr mit der Firmenmailadresse bloggen, Kommentare einstellen oder in sozialen Netzwerken auftreten, um zu vermeiden, dass persönliche Meinungen fälschlicherweise als Firmenstatements gewertet werden.

Öffentliche Aussagen von Mitarbeitern zu internen Informationen der Bank sind ein Abmahnungs- und Kündigungsgrund. Das ist aber in der Web 2.0-Welt nicht anders als vor Web 2.0 oder in der realen Welt am Stammtisch.

Reputation

Kann man die eigenen Mitarbeiter durch Regeln und Governance “Web 2.0-fähig” machen, so geht doch die Sorge um, enttäuschte Kunden oder verärgerte Anwender könnten im Web 2.0 erheblichen Schaden anrichten. Angesichts der durch die Krise verprellten Anleger durchaus berechtigt. Als Beispiele herhalten müssen dabei immer die altbekannten Fälle Dell und Kryptonite oder aktuell auch Wolfskin.

Natürlich muss man sich gegen unlautere Methoden und Verleumdung im Netz vor Reputationsverlusten schützen. Hierfür gibt es inzwischen auch schon gute Ansätze geeigneter Konzepte, Tools oder Verhaltensregeln. Man darf dabei aber zwei wesentliche Aspekte nicht vergessen:

  1. Nicht Web 2.0 ist schuld am Reputationsverlust, in der Regel sind es schlechte Produkte.
  2. Die meisten Firmen haben durch unverhältnismäßige oder falsche Kommunikation und Pressearbeit im Web 2.0 selbst zum Reputationsverlust beigetragen bzw. diesen verstärkt.
]]>

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
http://www.bank-zweinull.de/2010/02/03/banking-20-lernen-mit-social-software-teil-1/feed/

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
<br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> European Trend Survey »Banks & Future 2009«
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
http://www.bank-zweinull.de/2009/08/31/european-trend-survey-banks-future-2009/
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
http://www.bank-zweinull.de/2009/08/31/european-trend-survey-banks-future-2009/#comments

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
Mon, 31 Aug 2009 15:16:00 +0000
Martin Engstler
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_add_tags_to_rss() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57
Bank+ZukunftGeldinstituteStudieSurvey http://www.bank-zweinull.de/2009/08/31/european-trend-survey-banks-future-2009/ 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

Laut einer Studie von Faktenkontor glauben 60 Prozent finanziell geschädigter Anleger, dass ihre Bank keine Lehren aus der Finanzkrise gezogen und konkrete Verbesserungen umgesetzt hat. Bei den über 55Jährigen sind es sogar über drei Viertel, deren Vertrauen in Banken erheblich getrübt ist. So wird vermutet, dass die Wechselwelle unter den Instituten noch längst nicht vorbei ist.

Was machen die Banken tatsächlich, welches sind ihre Strategien in der Zukunft?

  • Über 70 Prozent der Banken bewerten das gewachsene Misstrauen in die Banken bzw. die gesamte Bankwirtschaft als strategische Herausforderung.
  • Die Studienergebnisse zeigen, dass die Banken ihre Pflichtaufgaben im Bereich des Risikomanagements (84 Prozent), des Qualitätsmanagements (66 Prozent) und
    Geschäftsprozessmanagements (64 Prozent) mit einer hohen Bedeutung verfolgen wollen.
  • Im Vertrieb besteht Konsens darüber, dass bestehende Kundenbeziehungen zu intensivieren und zunehmend auch die Neukundenakquisition zu verstärken sind.
  • Beim Thema Innovation hingegen bestehen noch viele Unsicherheiten. Neue Geschäftsfelder auszuloten, können sich in diesen Zusammenhang erst 25 Prozent der Banken vorstellen.
  • Innovationsmanagement (20 Prozent) und Kooperationsmanagement mit Wertschöpfungspartnern (10 Prozent) spielen hingegen noch immer eine untergeordnete Rolle als Managementstrategie.
  • In der eigenen Einschätzung sehen sich aber 51 Prozent der europäischen Banken bereits gut oder sogar sehr gut für die künftigen Herausforderungen gerüstet. 56 Prozent hatten diese Einschätzung vor der Krise.

Dies ist ein Auszug aus der aktuellen Trendstudie »Banks & Future 2009«, an der Bankführungskräfte aus 16 europäischen Ländern teilnahmen. Die Trendstudienreihe »Bank & Zukunft« von Fraunhofer IAO wird seit dem Jahr 2007 auch Europa-weit durchgeführt. Die detaillierten Ergebnisse der Studie gibts demnächst bei Bank und Zukunft.

]]>

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
http://www.bank-zweinull.de/2009/08/31/european-trend-survey-banks-future-2009/feed/

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
<br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> Transformation zur Bank 2015
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
http://www.bank-zweinull.de/2009/01/09/transformation-zur-bank-2015/
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
http://www.bank-zweinull.de/2009/01/09/transformation-zur-bank-2015/#comments

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
Fri, 09 Jan 2009 11:41:58 +0000
Martina Goehring
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_add_tags_to_rss() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57
St.GallenStudieSurvey http://www.bank-zweinull.de/2009/01/09/transformation-zur-bank-2015/ 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

CC Sourcing LogoNicht nur die jüngste Finanzkrise sorgt dafür, dass Anpassungen von Finanzsektor und –instituten in aller Munde sind. Wie aber wird sich die Bank 2015 von der heutigen unterscheiden? Wie verändert sich die Branche von Kundenanforderungen, über Front- und Backoffice hin zum Interbankenbereich? Wie sehen die Geschäftsfelder und Bankennetzwerke in Zukunft aus? Diese Fragestellungen stehen im Mittelpunkt einer vom “Competence Center Sourcing in der Finanzindustrie” an der Universität St. Gallen durchgeführten Delphi-Studie mit dem Titel “Transformation zur Bank 2015“.

Da in diesem Themenbereich vielfach strategische Entscheidungen zu treffen sind, richtet sich die Studie an das Management von deutschen, schweizerischen und österreichischen Banken und banknahen Dienstleistern. Der zeitliche Aufwand beträgt ca. 30 Minuten, der Erhebungszeitraum endet am 15. Februar 2009. Alle Teilnehmer erhalten exklusiv eine Auswertung aller anonymisierten Ergebnisse. Wenn Sie wissen möchten, was die Voraussetzungen für eine erfolgreiche Transformation sind, sollten Sie sich die Zeit nehmen.

Den Fragebogen können Sie am Ende dieses Beitrages herunterladen oder online beantworten: Fragebogen der Studie!

Im “Competence Center Sourcing in der Finanzindustrie” kooperieren seit Juli 2004 Forscher der Universitäten St. Gallen und Leipzig mit Experten aus der Praxis, um detaillierte und umsetzbare Zukunftskonzepte für die Finanzindustrie zu entwickeln. Eine enge Zusammenarbeit mit Partnerunternehmen aus der gesamten Bank-Wertschöpfungskette sichert dabei deren Praxisnähe und Anwendbarkeit.

Wir danken für Ihre Zusammenarbeit und stehen Ihnen für Fragen gerne zur Verfügung.
Ihr CC Sourcing (E-Mail an: sourcing@unisg.ch)

]]>

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
http://www.bank-zweinull.de/2009/01/09/transformation-zur-bank-2015/feed/
00:01:01 br / bStrict Standards/b: 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 ge br / bStrict Standards/b: 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 b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 b/homepages/3/d24003326/htdocs/bank-zweinull/wp Management,,Leitartikel,,Innovation Martina.Goehring@centrestage.de no No