Strict Standards: Redefining already defined constructor for class wpdb in /homepages/39/d39529389/htdocs/wordpress/wp-includes/wp-db.php on line 57

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/39/d39529389/htdocs/wordpress/wp-includes/cache.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/39/d39529389/htdocs/wordpress/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/39/d39529389/htdocs/wordpress/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/39/d39529389/htdocs/wordpress/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/39/d39529389/htdocs/wordpress/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/39/d39529389/htdocs/wordpress/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/39/d39529389/htdocs/wordpress/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/39/d39529389/htdocs/wordpress/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/39/d39529389/htdocs/wordpress/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/39/d39529389/htdocs/wordpress/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/39/d39529389/htdocs/wordpress/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/39/d39529389/htdocs/wordpress/wp-includes/classes.php on line 684

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/39/d39529389/htdocs/wordpress/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/39/d39529389/htdocs/wordpress/wp-includes/theme.php on line 540

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGenerator::Enable() should not be called statically in /homepages/39/d39529389/htdocs/wordpress/wp-includes/plugin.php on line 164
Heute schon gel?chelt? Analyse der Unternehmenskultur ? einmal ganz anders | Hamburger BeraterContor
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/kses.php on line 692

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 'CET/1.0/no DST' instead in /homepages/39/d39529389/htdocs/wordpress/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 'CET/1.0/no DST' instead in /homepages/39/d39529389/htdocs/wordpress/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 'CET/1.0/no DST' instead in /homepages/39/d39529389/htdocs/wordpress/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 'CET/1.0/no DST' instead in /homepages/39/d39529389/htdocs/wordpress/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 'CET/1.0/no DST' instead in /homepages/39/d39529389/htdocs/wordpress/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 'CET/1.0/no DST' instead in /homepages/39/d39529389/htdocs/wordpress/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 'CET/1.0/no DST' instead in /homepages/39/d39529389/htdocs/wordpress/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 'CET/1.0/no DST' instead in /homepages/39/d39529389/htdocs/wordpress/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 'CET/1.0/no DST' instead in /homepages/39/d39529389/htdocs/wordpress/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 'CET/1.0/no DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 26

Heute schon gelächelt? Analyse der Unternehmenskultur – einmal ganz anders

Von admin
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 'CET/1.0/no DST' instead in /homepages/39/d39529389/htdocs/wordpress/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 'CET/1.0/no DST' instead in /homepages/39/d39529389/htdocs/wordpress/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 'CET/1.0/no DST' instead in /homepages/39/d39529389/htdocs/wordpress/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 'CET/1.0/no DST' instead in /homepages/39/d39529389/htdocs/wordpress/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 'CET/1.0/no DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 26
20. Mai 2008 • Kategorie: Aktuelles, Kultur

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/formatting.php on line 82

Warum machen wir von HBC es mit unseren Kunden eigentlich so tiefgründig, könnte man fragen, es geht doch eigentlich auch viel einfacher. In der wunderbaren Kolumne von Mark Hübner-Weinhold in der Tageszeitung „Hamburger Abendblatt“ ist es nachzulesen (und hier fast wörtlich zitiert):

Werfen Sie einen Blick auf die Firmenparkplätze des betreffenden Unternehmens. Das ist so etwas wie ein Psychogramm von Arbeitgebern.

Also ein neuer Ansatz: Kulturanalyse by Company-Car-Analysis (CCA):

Protzige Geländewagen (SUV= Sports Utility Vehicles genannt), Golf GTI oder 3er-BMW mit Breitreifen und Chromauspuff (nichts gegen solche Fahrzeuge, sie sind ein Teil unseres BIP-Wachstums) deuten auf eine ausgesprochen männlich dominierte und „autoritäre“ Unternehmenskultur hin. Wimmelt es dort von Mini Cooper, VW Beetle oder Fiat 500 / parkingkloesterli.jpg                  20060923-parkplatz.jpg                                                 Peugeot 207 Cabrio o.ä., werden Sie im Unternehmen zahlreiche attraktive Frauen treffen. Viele Minivans vom Typ Touran, Scenic oder Picasso sind demgegenüber ein sicheres Indiz für eine familienorientierte Belegschaft (und was das für die Kultur bedeutet erklären wir Ihnen gerne). Und wenn man eine große Zahl ähnlicher Fahrzeugtypen entdeckt mit ähnlichen Kennzeichen, spricht dies z. B. dafür, dass das Unternehmen „generös“ mit geldwerten Vorteilen wie Dienstwagen umgeht, was an sich nicht negativ ist. Ja, und wie es um das Innenleben eines Arbeitgebers bestellt ist, erkennen Sie auch bereits an der Anzahl reservierter Parkplätze. Sie dienen nämlich meistens nicht Besuchern, sondern Führungskräften, die so wichtig sind, dass ihnen das Gekurve auf der Suche nach einer engen Lücke nicht zuzumuten ist. Solche VIP-Parkplätze sind zwar oft frei, dürfen aber trotz chronischen Stellplatzmangels nicht beparkt werden. In Indien nennt man diese Parkplatzregelung übrigens „Kastendenken“. Gelächelt? Schön. Habe ich auch beim Lesen! Wenn Sie mehr Beiträge dieser amüsanten Kolumne,  zu Fragen rund ums Arbeitsleben lesen möchten, hier der Link:  http://www.abendblatt.de/z/plog/blog.php/beruf__erfolg   Wenn Sie sich intensiver (und doch tiefgründiger) mit dem Thema Analyse der Unternehmenskultur auseinandersetzen und lesen möchten, welche harten Folgen dieser für manche SO softe Faktor Unternehmenskultur haben kann und wie man misst, ob sie Ihrem  Unternehmen das Leben schwermachen könnten (gerade in Veränderungszeiten), dann klicken Sie doch einmal hier:  

Tags: , ,

Schreibe einen Kommentar

Du musst eingeloggt sein um einen Kommentar zu schreiben