Strict Standards: Redefining already defined constructor for class wpdb in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/wp-db.php on line 56

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/cache.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/cache.php on line 384

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el($output) in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el($output) in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/classes.php on line 560

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el($output) in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el($output) in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/classes.php on line 684

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/theme.php on line 540

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

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

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/classes.php on line 216

Warning: Cannot modify header information - headers already sent by (output started at /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/wp-db.php:56) in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/feed-rss2.php on line 2
Handbuch Usability Blog http://www.handbuch-usability.de/blog Ein weiteres tolles WordPress-Blog
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/post.php on line 1682

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12
Wed, 30 Sep 2009 19:40:55 +0000
http://wordpress.org/?v=2.3 DE-Edition en
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26
Vortrag auf der Affiliate Tactixx: Mehr Sales durch optimierte Landingpages
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/vortrag-auf-der-affiliate-tactixx-mehr-sales-durch-optimierte-landingpages/
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/vortrag-auf-der-affiliate-tactixx-mehr-sales-durch-optimierte-landingpages/#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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12
Sun, 21 Jun 2009 21:19:19 +0000
admin http://www.handbuch-usability.de/blog/vortrag-auf-der-affiliate-tactixx-mehr-sales-durch-optimierte-landingpages/ Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82
y3bdhgqm6z Am Donnerstag, den 18.06.2009 hatte ich die Gelegenheit, einen Vortrag über die Optimierung von Landingpages auf der größten deutschen Affiliate-Konferenz “Affiliate Tactixx” zu halten. Diese Veranstaltung, die unter der Schirmherrschaft von explido Webmarketing ausgerichtet und von Markus Kellermann veranstaltet wird, hat sich innerhalb von 3 Jahren zum Hauptevent der Branche entwickelt. An dieser Stelle kann [...]]]>
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

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

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82

y3bdhgqm6z Am Donnerstag, den 18.06.2009 hatte ich die Gelegenheit, einen Vortrag über die Optimierung von Landingpages auf der größten deutschen Affiliate-Konferenz “Affiliate Tactixx” zu halten. Diese Veranstaltung, die unter der Schirmherrschaft von explido Webmarketing ausgerichtet und von Markus Kellermann veranstaltet wird, hat sich innerhalb von 3 Jahren zum Hauptevent der Branche entwickelt. An dieser Stelle kann ich allen an der Organisation beteiligten nur ein großes Lob für die Professionalität aussprechen, mit der das Event organisiert und durchgeführt wurde. Qualifizierte, hochkarätige Referenten und spannende Vorträge machten die Veranstaltung kurzweilig und aufschlussreich.  (more…)

]]>

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/vortrag-auf-der-affiliate-tactixx-mehr-sales-durch-optimierte-landingpages/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26
Online Kreditrechner - Steuerbarkeit par excellence
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/online-kreditrechner-steuerbarkeit-par-excellence/
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/online-kreditrechner-steuerbarkeit-par-excellence/#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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12
Tue, 29 Apr 2008 19:13:04 +0000
admin http://www.handbuch-usability.de/blog/online-kreditrechner-steuerbarkeit-par-excellence/ Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82
Während der Erstellung einer Studie zur Gebrauchstauglichkeit von Online-Kreditrechnern bin ich auf den Online-Rechner der AKB-Bank (Allgemeine Beamten Kasse) gestoßen und war begeistert, einen Antrags-Prozess vorzufinden, der in Sachen Prozess-Steuerbarkeit “das Übliche” bei Weitem übertrifft. ]]>
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

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

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82

Während der Erstellung einer Studie zur Gebrauchstauglichkeit von Online-Kreditrechnern bin ich auf den Online-Rechner der AKB-Bank (Allgemeine Beamten Kasse) gestoßen und war begeistert, einen Antrags-Prozess vorzufinden, der in Sachen Prozess-Steuerbarkeit “das Übliche” bei Weitem übertrifft.
(more…)

]]>

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/online-kreditrechner-steuerbarkeit-par-excellence/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26
Erwartungskonformität durchbrechen um Ziele zu erreichen
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/erwartungskonformitat-durchbrechen-um-ziele-zu-erreichen/
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/erwartungskonformitat-durchbrechen-um-ziele-zu-erreichen/#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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12
Wed, 16 Apr 2008 21:27:53 +0000
admin http://www.handbuch-usability.de/blog/erwartungskonformitat-durchbrechen-um-ziele-zu-erreichen/ Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82
Um die Aufmerksamkeit der Besucher gezielt zu lenken, kann man unkonventionelle Wege gehen. Auf www.quelle.de haben die Verantwortlichen scheinbar bewußt die Erwartungskonformität durchbrochen, um den Fokus auf den Bereich “Meine Quelle” zu lenken. ]]>
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

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

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82

Um die Aufmerksamkeit der Besucher gezielt zu lenken, kann man unkonventionelle Wege gehen. Auf www.quelle.de haben die Verantwortlichen scheinbar bewußt die Erwartungskonformität durchbrochen, um den Fokus auf den Bereich “Meine Quelle” zu lenken.
(more…)

]]>

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/erwartungskonformitat-durchbrechen-um-ziele-zu-erreichen/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26
Usability World 2007 - Rückblick Tag 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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/usability-world-2007-tag-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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/usability-world-2007-tag-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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12
Sat, 03 Nov 2007 20:46:22 +0000
admin http://www.handbuch-usability.de/blog/usability-world-2007-%e2%80%93-ruckblick-tag-2/ Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82
Das Abendprogramm mit einem Rundgang durch das Tropenaquarium und einem dreigängigem Buffet in toller Atmosphäre mit Live-Musik sorgte für die nötige Erholung vor dem zweiten Tag des Kongresses. Für den Rückblick auf den zweiten Kongresstag habe ich lediglich zwei besonders erwähnenswerte Vorträge herausgegriffen: Zu Beginn des zweiten Tages haben alle Teilnehmer mit Spannung den Vortrag von [...]]]>
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

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

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82

Das Abendprogramm mit einem Rundgang durch das Tropenaquarium und einem dreigängigem Buffet in toller Atmosphäre mit Live-Musik sorgte für die nötige Erholung vor dem zweiten Tag des Kongresses. Für den Rückblick auf den zweiten Kongresstag habe ich lediglich zwei besonders erwähnenswerte Vorträge herausgegriffen:

Zu Beginn des zweiten Tages haben alle Teilnehmer mit Spannung den Vortrag von Jakob Nielsen, dem Gründer und Direktor der NielsenNormanGroup erwartet - ganz klar das absolute Highlight der Veranstaltung. (more…)

]]>

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/usability-world-2007-tag-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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26
Usability World 2007 - Rückblick Tag 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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/usability-world-tag-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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/usability-world-tag-1/#comments

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

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12
Thu, 01 Nov 2007 23:34:45 +0000
admin http://www.handbuch-usability.de/blog/usability-world-tag-1/ Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82
Ich möchte SirValUse zum gelungenen Auftakt des World Usability Kongresses 2007 in Hamburg gratulieren. Bereits der erste Tag bot teilweise sehr interessante Einblicke in die Welt des Customer Experience Managements und machte neugierig auf den zweiten Tag. Besonders außergewöhnlich war der Veranstaltungsort. Der Tierpark Hagenbeck bot einen erfrischend unkonventionellen Rahmen, der ein steriles Konferenzzentrum keine Sekunde [...]]]>
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

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

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82

Ich möchte SirValUse zum gelungenen Auftakt des World Usability Kongresses 2007 in Hamburg gratulieren. Bereits der erste Tag bot teilweise sehr interessante Einblicke in die Welt des Customer Experience Managements und machte neugierig auf den zweiten Tag. Besonders außergewöhnlich war der Veranstaltungsort. Der Tierpark Hagenbeck bot einen erfrischend unkonventionellen Rahmen, der ein steriles Konferenzzentrum keine Sekunde lang vermissen ließ.

Obwohl die thematische Ausrichtung dieses Kongresses wohl absichtlich eher unscharf definiert wurde, kamen sowohl Offliner als auch Onliner auf Ihre Kosten. Drei Moderatoren/innen begleiteten die Besucher durch den Tag, einer davon war Frank Puscher, freier Journalist und Geschäftsführer des Spielfigur Verlags. Er betonte die aus Usabilitysicht gelungene Wahl des Termins für diesen Kongress, der es auch süddeutschen Besuchern ermöglichte, trotz des Feiertags Allerheiligen bis in die Puppen zu feiern und zu tanzen. (more…)

]]>

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/usability-world-tag-1/feed/

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

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26
Usability World 2007
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/usability-world-2007/
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/usability-world-2007/#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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12
Sun, 28 Oct 2007 07:58:31 +0000
admin http://www.handbuch-usability.de/blog/usability-world-2007/ Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82
Am 01. und 02. November 2007 findet im Tropen Aquarium des Tierparks Hagenbeck die “Usability World 2007”  statt. Die Experten des Hamburger Instituts für Usability und User Experience SirValUse (siehe Anbieterverzeichnis) veranstalten diesen Kongress zum ersten Mal in Hamburg. Die Liste der Referenten ist vielversprechend. Als Keynote-Sprecher konnte SirValUse Jakob Nielsen gewinnen, den Gründer der Nielsen Norman Group, [...]]]>
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82

Am 01. und 02. November 2007 findet im Tropen Aquarium des Tierparks Hagenbeck die “Usability World 2007”  statt. Die Experten des Hamburger Instituts für Usability und User Experience SirValUse (siehe Anbieterverzeichnis) veranstalten diesen Kongress zum ersten Mal in Hamburg. Die Liste der Referenten ist vielversprechend. Als Keynote-Sprecher konnte SirValUse Jakob Nielsen gewinnen, den Gründer der Nielsen Norman Group, eine internationale Kapazität im Bereich Usability. Und auch namhafte Unternehmen wie Microsoft, Google oder Otto sind mit Referenten vertreten, die über Ihre Erfahrungen, Case Studies und aktuelle Trends berichten werden.  Drei parallele Programme versprechen 2 hochinteressante Tage rund um das Thema Usability, User Experience und Customer Experience.

 Hier die Eindrücke:

World Usability 2007 - Tag 1

World Usability 2007 - Tag 2

Ähnliche Beiträge:

 Kongress 2007

]]>

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/usability-world-2007/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26
Web 2.0 und Usability
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/web-20-und-usability/
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/web-20-und-usability/#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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12
Sun, 30 Sep 2007 13:09:43 +0000
admin http://www.handbuch-usability.de/blog/web-20-und-usability/ Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82
Seit ich mich damit abgefunden habe, dass auch ich dieses Unwort gebrauchen muss, weil man von Experten erwartet, dass Sie mit Fachbegriffen um sich werfen und jeden Hype kennen, mache auch ich mir Gedanken über das Thema Web 2.0 und Usability. Als Experte mit langjähriger Erfahrung im Bereich Webmarketing fragen mich viele Kunden, wie Sie [...]]]>
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82

Seit ich mich damit abgefunden habe, dass auch ich dieses Unwort gebrauchen muss, weil man von Experten erwartet, dass Sie mit Fachbegriffen um sich werfen und jeden Hype kennen, mache auch ich mir Gedanken über das Thema Web 2.0 und Usability. Als Experte mit langjähriger Erfahrung im Bereich Webmarketing fragen mich viele Kunden, wie Sie Ihre Website Web 2.0 fähig machen können. Nach einer kurzen Abstimmung, was jeder eigentlich unter Web 2.0 versteht, sind die  Konzepte meist einfach zu erstellen. Aber bringt Web 2.0 auch etwas im Hinblick auf die Usability? Auch das hängt von der Definition ab. Neben beispielsweise dem “wir”-Gedanken, der allgemeinen Mitmach-Mentalität und Selbstdarstellungssucht fällt mir auf, dass die meisten Seiten sich an die Bedürfnisse insofern angepasst haben, als auf vielen Web 2.0 Projekten nur noch wenig Inhalt und Funktionalität zu finden ist. Das Ergebnis ist Übersichtlichkeit  und durch die fehlenden Möglichkeiten auch eine eingeschränkte aber einfache Bedienung.

]]>

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/web-20-und-usability/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26
Was ist Usability?
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/was-ist-usability/
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/was-ist-usability/#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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12

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

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 26

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/functions.php on line 12
Wed, 26 Sep 2007 17:01:45 +0000
admin http://www.handbuch-usability.de/blog/was-ist-usability/ Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82
Es erschien mir sinnvoll, den ersten Beitrag dieses Blogs der Frage “Was ist Usability” zu widmen. Zwar habe ich mit der Usability Definition dieses Thema in meinem Handbuch bereits ausführlich behandelt, jedoch zeigt mir die Beratungs- und Projektmanagementpraxis, dass das Wesen der Usability oftmals subjektiv unterschiedlich wahrgenommen wird und jeder, der ein wenig guten Menschenverstand hat, denkt, er wäre [...]]]>
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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

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

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/formatting.php on line 82

Es erschien mir sinnvoll, den ersten Beitrag dieses Blogs der Frage “Was ist Usability” zu widmen. Zwar habe ich mit der Usability Definition dieses Thema in meinem Handbuch bereits ausführlich behandelt, jedoch zeigt mir die Beratungs- und Projektmanagementpraxis, dass das Wesen der Usability oftmals subjektiv unterschiedlich wahrgenommen wird und jeder, der ein wenig guten Menschenverstand hat, denkt, er wäre ein Experte. Das ist leider nicht so! (more…)

]]>

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/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d122587373/htdocs/handbuch-usability/blog/wp-includes/link-template.php on line 87
http://www.handbuch-usability.de/blog/was-ist-usability/feed/