Two municipal library systems merge and staff still use two catalog passwords and two dress codes. What should HR sequence so patrons and staff experience one employer?
Select an answer to reveal the explanation.
Short Explanation
Two name badges and two logins means there are still two libraries with a shared press release. Merge the everyday stuff—passwords, dress, how a patron gets help—or the public will keep asking which library this is.
Full Explanation
When two municipal library systems merge and staff still use two catalog passwords and two dress codes, HR should sequence everyday practical and cultural norms—systems access and workplace rules—alongside the org chart, not after it. Two name badges and two logins mean patrons still experience two employers with a shared press release. Integration that stops at titles leaves the lived employer fragmented.
Org-chart titles only, leaving passwords and dress codes to 'evolve naturally,' postpones the friction patrons and staff feel daily. A three-year freeze on any shared system so nobody relearns software preserves dual operations. Immediate closure of the smaller system's branches to avoid integration is service destruction posing as simplicity.
Exam caveat: sequencing practical norms does not require reckless cutovers; migration can be staged, but it must be intentional and timed with structural merger. The concept is lived-employer integration, not chart-only merger.
Operational check: prioritize single sign-on or catalog access and a unified dress/customer-service standard in the integration roadmap; train staff before cutover; measure patron complaint themes about 'which library'; and retire legacy access only after stability criteria are met.