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
Unternehmenskultur und Due Diligence | 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 'CEST/2.0/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 'CEST/2.0/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 'CEST/2.0/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 'CEST/2.0/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 'CEST/2.0/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 'CEST/2.0/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 'CEST/2.0/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 'CEST/2.0/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 'CEST/2.0/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 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 26

Unternehmenskultur und Due Diligence

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 'CEST/2.0/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 'CEST/2.0/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 'CEST/2.0/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 'CEST/2.0/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 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 26
11. Februar 2008 • Kategorie: Change Management, 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

Einer der auf Change Management und Post Merger Integration spezialisierten deutschen Berater, Winfried Berner, hat in der Zeitschrift für OrganisationsEntwicklung (Nr. 1/2008) gerade einen interessanten Artikel geschrieben, der vieles aus unserer Tätigkeit bei Fusionsberatungen bestätigt und bekräftigt.
Berner befasst sich mit der Unverträglichkeit von Unternehmenskulturen und zeigt ihre Gründe sehr anschaulich auf. Kernsätze sind: ballett-balken.jpg

  • Nicht nur völlig unterschiedliche Unternehmenskulturen können in Fusionen Reibungen und Konflikte verursachen, die zum Scheitern führen können. Häufig sind es gerade sich sehr ähnliche Kulturen, die durch eine “Kontrastverstärkung oder Wagenburgmentalität” heftige Abgrenzungen und unüberbrückbare Differenzen bewirken.
  • Wichtig ist bei Fusionen sehr schnell ein neues Gefühl der Zugehörigkeit, des Vertrauens zu schaffen. Wenn die Mitarbeiter der fusionierten Unternehmen sich zugehörig fühlen, als Mitglied der Gemeinschaft akzeptiert, könne sie sich voll auf ihre Aufgaben konzentrieren und volle Leistung bringen.
  • Ein geeigneter Weg für eine schnelle Integration ist es, ein gemeinsames neues Problem in den Raum zu stellen, an dem alle einen gemeinsamen “Feind” sehen und gemeinsame Chancen erkennen.
  • Nicht due Kulturen selbst sind die Reibungspunkte, sondern das Spannungsfeld zwischen ihnen, also z.B. völlig unterschiedliche Grundüberzeugungen, Führungsverständnisse uvm.
  • Eine vergleichende Analyse der Unternehmenskulturen ist immer sinnvoll, um die Risikofaktoren z.B. aus Unvereinbarkeiten in Denken, Handeln und Überzeugungen zu identifizieren und an ihrer Behebung zu arbeiten. Neben geeigneten Kulturanalysen empfiehlt Berner hier, eine Situationsanalyse durch teilstrukturierte Interviews.

Auch diese Methode ist für uns vertraut, wir haben sie immer wieder parallel zu bzw. vernetzt mit unserer Kulturanalyse nach dem CIO angewandt.
Mehr dazu können Sie auf unserer Website lesen: http://www.hbcontor.de/img/cio.pdf

Tags: , , , , , , ,

Schreibe einen Kommentar

Du musst eingeloggt sein um einen Kommentar zu schreiben