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 » Innovation 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 /> Bank 2.0: Ein Buch zum Thema
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/03/22/bank-20-ein-buch-zum-thema/
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/03/22/bank-20-ein-buch-zum-thema/#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, 22 Mar 2010 10:59:30 +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
BankingBanking Strategymobile BankingOnline MarketingOpen SourceSocial BankingWeb 2.0 http://www.bank-zweinull.de/2010/03/22/bank-20-ein-buch-zum-thema/ 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

Buch Bank 2.0 LogoVor kurzem bekam ich eine E-Mail vom Autor des Buches Bank 2.0 Brett King, in der er mir einen Auszug daraus schickte. Auch wenn sich das Konsumentenverhalten in Deutschland z.B. bei der Verwendung von Kreditkarten oder im Verhältnis Privatkunde zur Bank von dem in anderen Ländern unterscheidet, sind dennoch die technologischen Trends vergleichbar. Auch die Zurückhaltung der Banken in Bezug auf Enterprise 2.0 oder das Festhalten an Strukturen aus den 90er Jahren sind global ähnlich.

Daher kann ich die Inhalte von Brett King in seinem Blog Banking4tomorrow unterstützen. Die Paypal-App gibt es schon. Was tun eigentlich die Banken, während sich Apple und andere Hersteller mobiler Endgeräte auf die “Euro-App”, mit der ich in Zukunft meine Einkäufe bezahlen werde, vorbereiten? Ein Beitrag dazu von Brett King.

Da es auf dem Markt nicht sehr viele Bücher zu diesem Thema gibt, stelle ich die Infos hier zur Verfügung.

]]>

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/03/22/bank-20-ein-buch-zum-thema/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 Leitartikel,,Internet,und,Banking,,Innovation Martina.Goehring@centrestage.de no No

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 /> Die 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/2010/01/23/die-bank-2015-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/01/23/die-bank-2015-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
Sat, 23 Jan 2010 18:54:05 +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.GallenStudie http://www.bank-zweinull.de/2010/01/23/die-bank-2015-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

CC Sourcing LogoWie sieht die Bank 2015 aus? Dieser Frage ging das Kompetenzzentrum Sourcing in der Finanzindustrie des Instituts für Wirtschaftsinformatik un des Schweizerischen Instituts für Banken und Finanzen der Universität St. Gallen sowie das Institut für Wirtschaftsinformatik der Universität Leipzig nach und befragte dazu 104 Universal-, und Privatbanken sowie Provider in Deutschland, Österreich und der Schweiz.

Sowohl die Ergebnisse der Studie als auch die zehn ergänzend durchgeführten Experteninterviews belegen zunächst bekannte Trends. So wollen sich Banken bis 2015 noch stärker auf ihre Kernkompetenzen Beratung und Vertrieb konzentrieren und strategisch wenig relevante Bereiche auslagern. Hierzu zählen IT oder Beschaffung, Ausführung und Abwicklung sowie Produkte und Kompetenzzentren, für die die Studie einen aktuellen Eigenfertigungsanteil zwischen 78 und 84% ermittelt hat.

Warum sollte diese Veränderung nun bis 2015 stattfinden? Hierzu vermitteln sieben in der Studie als Treiber und Veränderungsbereiche enthaltene Fragekomplexe einen genaueren Einblick.

Eine Zusammenfassung zu diesen sieben Bereichen findet man HIER.

Die Studie Transformation zur Bank 2015 kann zum Preis von 165,- Euro (250,.- CHF) unter bezogen werden.

]]>

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/01/23/die-bank-2015-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 /> 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 /> Statements von der Bankenfachtagung Bank und Zukunft 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/05/06/statements-von-der-bankenfachtagung-bank-und-zukunft-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/05/06/statements-von-der-bankenfachtagung-bank-und-zukunft-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
Wed, 06 May 2009 19:44:53 +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
Bank+ZukunftIBMSmava http://www.bank-zweinull.de/2009/05/06/statements-von-der-bankenfachtagung-bank-und-zukunft-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

Die Bankenfachtagung „Bank und Zukunft 2009“, veranstaltet vom Fraunhofer IAO und IBM hat gestern in Frankfurt im IBM-Finance Center stattgefunden. Einige Statements der Referenten habe ich als Lessons Learnt mitgenommen.

“Es war nie einfacher (als in einer Krise) Kunden zu gewinnen.” sagte IBM-Geschäftsführer Matthias Hartmann und hat den Banken dazu vier Strategien empfohlen

  1. Die Institute müssen sich konsolidieren und spezialisieren.
  2. Die Institute müssen den Missing Link zwischen Strategieplan und Umsetzung schließen. Es gibt zu viele Pläne in den Schubladen, die nie umgesetzt werden.
  3. Die Institute müssen nach dem Prinzip Client First handeln: der Kunde zuerst

  4. Die Institute müssen die Globalisierungschancen nicht nur produktionsseitig sondern auch marktseitig nutzen und Kosten- und Skalierungseffekte entlang der Wertschöpfungskette realisieren.

Martin Engstler vom Fraunhofer IAO stellte die Ergebnisse der neuen IAO-Bankenstudie 2009 vor. Einige sind mir aufgefallen, die zwar nicht unbedingt neu, aber bei den Banken jetzt auch angekommen sind:

  • Jede zweite Bank stellt sich zurzeit die Frage nach ihrer Positionierung im Markt und nach ihren Produkten.
  • Bei den meisten Instituten wird es keinen Investitionsstopp geben, aber Verschiebungen von Investitionen aufgrund der Krise sind durchaus an der Tagesordnung.
  • Die Internetseiten der meisten Banken spiegeln eher das Organigramm als den Kundenprozess wider. Die Kundenperspektive wird dennoch als eines der wichtigsten Trendthemen genannt.
  • Die Automatisierung von Prozessen soll durch Optimierung der Kooperationsstrukturen der Partner erreicht werden. Bislang wurde das Automatisierungsthema immer als reines IT-Prozessthema gesehen. Neu ist, dass nun auch auf Kooperation gesetzt wird, nicht nur intern sondern auch nach außen. Auch wenn Prozessoptimierung nicht alleiniges Ziel sein darf, es ist ein Anfang.
  • Die Trends für 2015 sind Konzentration auf Vertrieb und mehr Zeit für persönliches Kundenbeziehungsmanagement. Dieser Trend wurde wichtiger im Vergleich zu den letzten Jahren.
  • Interessant war, dass sich 50% der Institute gut vorbereitet fühlen für die Herausforderungen der Zukunft. Mit Blick auf die internen Strukturen wurde dieses Ergebnis vom Referenten allerdings bezweifelt. Demnach meinen aber die anderen 50%, nicht gut vorbereitet zu sein.

Ob diese zum Teil Extrempositionen nun Ausdruck von Ignoranz und Hilflosigkeit oder der Beginn eines grundlegenden Wandels einer Branche sind, die bislang als weitgehend stabil und unveränderbar galt, wird sich bald zeigen. Es erinnert mich an den vor ca. zehn Jahren begonnenen und als Megatrend bezeichneten Umbruch in der Medienindustrie. Diese hat sich, wie man inzwischen weiß, strukturell und in den Geschäftsmodellen grundlegend verändert. Da wir zurzeit am Ende eines Konjunkturzyklus nach Kondratieff sind, werden auch Paradigmenwechsel im Finanzmarkt nicht ausbleiben können.

Bernhard Keller von TNS Infratest berichtete aus der aktuellen Kundenstudie, die der Frage nachging, was Kunden von Banken und insbesondere von den Filialen erwarten. Da inzwischen 40% der Kunden ihre Bankgeschäfte online durchführen, muss man sich fragen, was machen die anderen 60% in der Filiale. Die meisten sind dort an den Automaten anzutreffen. Nur 8% der Filialgänger ist dort für eine qualifizierte Beratung (im Untersuchungszeitraum). Drei Viertel wissen nicht, warum sie in eine Filiale gehen sollten. Die Botschaft am Ende: die Banken müssen das Vertrauen der Kunden wieder gewinnen, das auf persönlichen Beziehungen basiert und nur in der Filiale funktioniert. Deshalb werden neue Filialkonzepte benötigt.

Persönliche Beziehungen lassen sich nicht nur in einer Filiale herstellen. Die Banken sollten sich auch mal fragen, wie man die Konzepte der sozialen Netzwerke und Communities im Internet für das eigene Kundenbeziehungsmanagement nutzen könnte.

Beim Vortrag von Tristan Reckhaus von IBM haben sich viele Banker vermutlich gefragt, was hat denn die Barbie-Community mit ihrer Bank zu tun. Bei den vielen Beispielen aus der Web 2.0 Welt im Vortrag habe ich mich zwar zuhause gefühlt, allerdings haben mir auch Hinweise auf eine Übertragbarkeit in die Bankenwelt gefehlt, insbesondere unter dem Aspekt Vertrauensbildende Maßnahmen, Kundenkommunikation und Marketing.

Ein Highlight aus meiner Sicht war der Vortrag von Alexander Artopé, Geschäftsführer von smava, dem online Marktplatz, der private Kredite von Menschen an andere Menschen vermittelt. Ich erinnere mich noch genau, wie ich dieses Modell bei einem Kundenbesuch 2007 als Beispiel vorgestellt habe und es dort belächelt wurde mit den Worten: „Ich kann mir nicht vorstellen, dass es Menschen gibt, die übers Internet völlig Unbekannten Geld leihen. Was haben sie davon? Was passiert, wenn nicht zurückgezahlt werden kann? Welche Sicherheiten gibt es denn, die doch nur eine Bank bieten kann?“ Diese Punkte und einiges mehr wurden sehr klar und überzeugend beantwortet.

„Vertrauen zum Kunden, Beziehungen zum Produkt und zu Menschen, Sicherheit aber auch Spaß am Geld anlegen“ alles Werte, die von den Referenten, insbesondere der Großbanken, in ihren Vorträgen als sehr wichtig herausgestellt wurden und die man zurück erobern müsse, sind in diesem innovativen Geschäftsmodell und der Community von smava realisiert.

Bei der Preisverleihung zur Geschäftsstelle des Jahres 2009 hat es mir dann für einen kurzen Moment etwas die Sprache verschlagen. Die vorgestellten Preisträger-Filialen sind allesamt ganz hübsch anzuschauen und ich persönlich bewege mich auch lieber in einem schönen hellen Raum mit angenehmer und moderner Atmosphäre, zumindest beim Einkaufen. Aber „Wartelaunches“ und „entspannte Wartezonen“ als innovative Kundenkonzepte einer Filiale zu verkaufen, ist nicht gerade zeitgemäß. Ich kenne keine Kunden, die warten wollen, wenn sie einen Termin haben, auch nicht in einem weißen Designer-Ledersessel. Dennoch, die italienische Filiale der Cassa Rurale di Treviglio hat mir am besten gefallen, weil sie die Raiffeisen-Philosophie sehr gut umgesetzt hat.

]]>

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/05/06/statements-von-der-bankenfachtagung-bank-und-zukunft-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

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 /> Neue Forschungsphase für “Bank & Zukunft” startet
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/2008/07/04/neue-forschungsphase-fuer-bank-zukunft-startet/
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/2008/07/04/neue-forschungsphase-fuer-bank-zukunft-startet/#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, 04 Jul 2008 12:24:40 +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+Zukunft http://www.bank-zweinull.de/2008/07/04/neue-forschungsphase-fuer-bank-zukunft-startet/ 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

buz_logoAb Juli 2008 startet das Fraunhofer-IAO gemeinsam mit Anwendern und Herstellern der Finanzdienstleistungsbranche in die bereits fünfte Forschungsphase des Innovationsform “Bank&Zukunft“, an der sich interessierte Unternehmen noch beteiligen können.

Was können Sie erwarten?

  • Sie entwickeln gemeinsam mit Partnern der Finanzbranche unter wissenschaftlicher Begleitung strategische Konzepte für die Zukunft von Banken.
  • Sie erhalten Einblick in innovative Technologien, mit denen Sie sich künftig verstärkt beschäftigen müssen, um deren Potenziale für sich zu erschließen.
  • Sie tauschen sich mit anderen Anwendern, Herstellern über neue Konzepte, Produkte, Lösungen aus.
  • Sie können mit uns zusammen Strukturen und Prozesse Ihrer Bank im Hinblick auf zukunftsfähige Ansätze auf den Prüfstand stellen und weiter entwickeln.

Nähere Informationen und Ansprechpartner dazu finden Sie auch hier.

]]>

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/2008/07/04/neue-forschungsphase-fuer-bank-zukunft-startet/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 /> Herausragende Web 2.0 Angebote sind möglich
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/2008/05/28/herausragende-web-20-angebote-sind-moeglich/
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/2008/05/28/herausragende-web-20-angebote-sind-moeglich/#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, 28 May 2008 10:48: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
StudieWeb 2.0 http://www.bank-zweinull.de/2008/05/28/herausragende-web-20-angebote-sind-moeglich/ 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

Bank2.0_LogoImmer wieder werden wir angefragt, ob es Übersichten oder Charts gibt zum Einsatz von Web 2.0 bei Banken und Versicherungen. Sofern wir davon hören, lesen und erfahren, werden wir hier darüber berichten. Uns sind mindestens drei Diplomarbeiten bzw. Studien bekannt, die derzeit noch laufen. Sobald diese abgeschlossen sind, werden wir versuchen, Ergebnisse zu bekommen. Da sie aber im Rahmen von Unternehmen durchgeführt werden, ist nicht ausgeschlossen, dass sie unter Verschluss bleiben. Das muss man auch in einer Web 2.0 Kultur akzeptieren. Noch ist es so, das sich Finanzdienstleister durch den Einsatz von Web 2.0 von anderen differenzieren könnten. Da werden dann solche Ergebnisse auch wettbewerbsrelevant.

Dennoch: Nach der Untersuchung zum Einsatz von Web 2.0 im Bankenvertrieb vom Kompetenzzentrum Finanzen der Georg-Simon-Ohm-Hochschule Nürnberg, über die wir bereits berichtet haben, gibt es nun von dort weitere Ergebnisse zum Angebot von Web 2.0-Diensten auf den Websites der Finanzdienstleistungsbranche, die im Rahmen der Benchmarking-Studie 2008 ermittelt wurden. Die Schlussfolgerung liest sich zunächst vielversprechend:

  • Die Kriterien zu Web 2.0 beinhalten keine überzogenen oder übermäßig innovativen Anforderungen.
  • Web 2.0 birgt noch ein hohes Differenzierungspotential.

Zu den ersten Ergebnissen im Einzelnen gelangen Sie hier.

]]>

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/2008/05/28/herausragende-web-20-angebote-sind-moeglich/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 /> Banken sind auf die Zukunft noch nicht vorbereitet
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/2008/05/05/banken-sind-auf-die-zukunft-noch-nicht-vorbereitet/
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/2008/05/05/banken-sind-auf-die-zukunft-noch-nicht-vorbereitet/#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, 05 May 2008 09:10:30 +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+ZukunftStudie http://www.bank-zweinull.de/2008/05/05/banken-sind-auf-die-zukunft-noch-nicht-vorbereitet/ 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

buz_logoAuf die erwarteten Veränderungen im Bankenmarkt und im Banking fühlen sich die meisten Banken heute noch nicht hinreichend vorbereitet. So sieht sich heute nur jede vierte Bank sehr gut bzw. gut aufgestellt. Rund 44 Prozent sehen in Detailfragen noch enorme Defizite oder sehen den Bedarf umfassender Veränderungen (31 Prozent), um sich den zukünftigen Anforderungen stellen zu können.

Die Schlüsselrolle bei der Umsetzung der strategischen Konzepte spielen die Mitarbeiter. Lediglich 11 % gaben an, dass ihre Mitarbeiter bereits heute gut auf die zukünftigen Herausforderungen im Bankenmarkt vorbereitet sind. Es wird viel erwartet vom “Banker der Zukunft”. Sein Qualifikationsprofil zeichnet sich neben der fachlichen Kompetenz aus durch die Kompetenz im Umgang mit neuen Technologien und ein hohes Maß an Sozial- und Kommunikationskompetenz, um im Umgang mit den Kunden Differenzierungsmerkmale gegenüber anderen Banken zu verdeutlichen.

Die neue Studie des Fraunhofer IAO zeigt eine Fortsetzung der strategischen Herausforderungen im Bankenmarkt: weiter steigender Preiswettbewerb bei Standardprodukten (96 Prozent), zunehmender Vertrieb von Finanzprodukten über Nichtbanken (73 Prozent) sowie das Eindringen ausländischer Banken in den Inlandsmarkt (47 Prozent). Mit welchen Projekten 2008 wird man die Herausforderungen angehen?

  • Die Umsetzung regulatorischer Auflagen wird von den Banken heute als wichtigste Aufgabe adressiert (87 Prozent).
  • Für die Zukunft sehen insbesondere die Sparkassen noch große Potenziale durch Kostensenkungsprogramme und die Einführung optimierter Steuerungsinstrumente um effektiver am Markt agieren zu können (46 Prozent).
  • In der Gruppe der Genossenschaftsbanken hingegen stehen Projekte zur Einführung des Prozess- und Qualitätsmanagements (40 Prozent) im Mittelpunkt.
  • Unabhängig vom Bankentyp und der Bankengröße hat die Zielsetzung der Implementierung eines Innovationsmanagements, im Vergleich zu den letzten drei Jahren, signifikant zugenommen.

Eine Zusammenfassung der Studienergebnisse finden Sie in der Anlage. Die Studie selbst wird ab Mitte Mai 2008 herausgegeben und kann im IAO-Shop für 60,- Euro erworben werden.

]]>

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/2008/05/05/banken-sind-auf-die-zukunft-noch-nicht-vorbereitet/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 Neues,in,der,Sidebar,,Leitartikel,,Innovation Martina.Goehring@centrestage.de no No

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 /> Neue Technologien für die Sicherheit
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/2007/12/04/neue-technologien-fuer-die-sicherheit/
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/2007/12/04/neue-technologien-fuer-die-sicherheit/#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
Tue, 04 Dec 2007 15:06:35 +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
Bank+ZukunftFTDInnovationSecurity http://www.bank-zweinull.de/2007/12/04/neue-technologien-fuer-die-sicherheit/ 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

rlogoImpressionen zur FTD-Serie Bank der Zukunft

Die zehnteilige Serie der Financial Times Deutschland zu Aspekten der Bank der Zukunft wie die IT, die Zielgruppen und den Vertrieb habe ich mir durchgelesen. Meine Lessons learned und persönliche Analyse waren dabei, die ich hier zusammenfassen möchte.

Neue Technologien für die Sicherheit:

Auch wenn biometrische Verfahren im Onlinebanking aus Expertensicht noch nicht ausgereift sind und teure Hardwarelösungen am heimischen Computer benötigen, wird Biometrie laut der Fraunhofer IAO Studie in der Zukunft zum Sicherheitsstandard werden. In den Forschungslabors wird daher schon fleißig experimentiert und getestet wie z.B. Handflächenscanner am Geldautomat oder Irisscan als Zugangskontrolle.

Die TAN ist out. Der Nachfolger heißt Psylock und steht für „psychometric locking“. Die Software, entwickelt bei Prof. Bartmann von ibi research an der Uni Regensburg, analysiert das Tippverhalten des Nutzers und wertet wie ein digitaler Grafologe Anschläge, Schreibrhythmus u.a.m. aus und liefert den individuellen und eindeutigen „Fingertippabdruck“.

]]>

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/2007/12/04/neue-technologien-fuer-die-sicherheit/feed/