Helping you make sense
of the evolving HR landscape.

Our best HR blog posts of 2016, part I

Posted on: December 1st, 2016 | Category: Employee Relations, Government Regulatory & Compliance Issues, HR DirectLink Service, HR Support & Project Work, Human Resources, Our Blog, Talent Management

Wow! Is it December already? We would like to ring out the year by sharing our most memorable HR blog posts from 2016. We covered so many great topics and events over the last 12 months, and we are ready to cover whatever 2017 has in store for modern employers and managers like you. Please enjoy part one of our “Best in Show”, as selected by the myHR Partner team.

Thanks for joining us for our Q1 2016 walk down memory lane. Check back next week for April through June blog highlights, which include posts about medical marijuana and the workplace, HR and new LGBT laws and the DOL‘s attempt at sweeping overtime rule changes.

As always, if you have any ideas for what you’d like to see us blog about in 2017, please let us know. We’d love to hear them!
Tell Me More!

Please fill out the form below or call 610.443.0119 to learn more about what our modern HR services can do for you. We’ll get back to you within one business day—most likely less!
  • This field is for validation purposes and should be left unchanged.

myHR Partner’s periodic publication, MODERN EMPLOYER, is created for business executives, owners and HR professionals who want to maximize their human resource functions using progressive hiring and HR strategies. It’s informative, fun and practical. Oh, and it’s FREE too!

You’ll discover:

  • Tips on hiring, screening, and interviewing
  • Creative ideas to help retain your best employees
  • Ways to put the “human” back in Human Resources
  • How to perform effective reference checks
  • New HR regulations and how they affect you and your employees
  • How small changes in certain processes can have big results
  • How to tell when partnering with an outside provider is in your best interest
  • This field is for validation purposes and should be left unchanged.