Merging Corporate Cultures - Role of Intranet
Best Practices by Mark Gallagher

Using Intranet Technology To Facilitate Corporate Merger Goals

Key Points:

  • Lack of information is a primary cause of employee anxiety during a merger
  • Confused employees are unproductive employees
  • Intranet provides employees the information they need to function effectively in the new organization
  • Intranet accelerates the transition of embracing the new organization


Why Intranet Works:

  • Gives employees an easier and more personal look at the new identity, goals and management of the new organization.
  • Allows them to see the positives of the merger…..more locations, more products, more customers, more leadership.
  • The Intranet itself is seen as a modern tool that helps them see change and embrace change.


Early Steps
(after merger announcement and prior to legal Day 1):

  • The intranet support teams form a merger integration team and exchange screenshots of home page, phonebook, HR and search.
  • Approval by  Merger Implementation Team to use intranet as a strategic merger tool.
  • Identify senior management sponsorship from IT, HR and Communications.
  • Quick Hits (with approval from legal):
    • Exchange phonebook data, open firewalls to each others intranets
    • Coordinate all internal news postings to share updates on merger activities
    • Begin work on new intranet home page and design templates
    • Plan for and begin work on key Day 1 deliverables


Legal Merger Day 1 Deliverables:

  • A common home page for all PCs in the new company with the new corporate identity and fully integrated internal news posting including updates on merger goals and accomplishments.
  • The Core Information Utilities with fully integrated data and branded with new company identity:
    •  Employee Phonebook
    •  Yellow Pages Site (products, locations, support resources)
    •  Search
    •  The New Org Chart (user-friendly views into the new organization)
  • Infrastructure that fully connects the networks.


Updated: June 2005
by Mark Gallagher

 

mark@gallagher.com

 

gallagher.com < - - - return