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_posts_where() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57

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

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

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

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

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 14

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 14

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28

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-content/plugins/share-this/share-this.php on line 680
Share This : Banking 2.0 Lernen mit Social Software - Teil 1


Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 75

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 89
Was ist das? Von hier aus können Sie den Beitrag Banking 2.0 Lernen mit Social Software - Teil 1 auf Social Web Portalen speichern und damit auch anderen zur Verfügung stellen, oder mit dem E-Mail Formular als E-Mail verschicken.

Social Web


    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
  • del.icio.us

  • 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
  • Digg

  • 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
  • Mister Wong

  • 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
  • Y!GG

  • 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
  • Readster

  • 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
  • Webnews

  • 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
  • LinkARENA

  • 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
  • Furl

  • 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
  • Netscape

  • 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
  • Yahoo! My Web

  • 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
  • Technorati

  • 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
  • Google Bookmarks

  • 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
  • Newsvine

  • 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
  • co.mments

  • 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
  • BlinkList

  • 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
  • reddit

  • 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
  • Blogmarks

  • 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
  • ma.gnolia

  • 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
  • Windows Live

  • 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
  • Tailrank

  • 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
  • StumbleUpon

  • 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
  • Favoriting

E-Mail

E-mail It

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
03. Februar 2010

Banking 2.0 Lernen mit Social Software - Teil 1

Veröffentlicht unter: Management, Leitartikel, Internet und Banking


Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/coolplayer/coolplayer.php on line 134

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/coolplayer/coolplayer.php on line 135

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/formatting.php on line 74

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

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 669

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 669

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 670

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 670

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

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

Einige Lessons learnt habe ich mitgenommen.

Ideenmanagement

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

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

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

Kultur

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

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

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

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

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

Damit werden gewissermaßen zwei Ziele erreicht:

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

Gesetzliche Regeln

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

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

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

Reputation

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

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

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

Zurück zum Beitrag: Banking 2.0 Lernen mit Social Software - Teil 1