Should we design HR processes, or experiences?

curved-strip-right bottom-curved-strip-white bottom-curved-strip-white-mobile

Written by Mandy Chapman, HRCubed.

There is a chapter in Lucy Adam’s new book called “Design Experiences, Not Processes”, writes Mandy.

Considering what HRCubed specialises in, I thought Lucy and I may be on opposite ends of the spectrum. And this short but impactful chapter struck me hard as I mulled over the implications. Was she really suggesting that we don’t design process?

For decades, HR departments have struggled with making processes lean and efficient. Often it leads to real business impacts, and without due care and attention, sometimes the result is poor employee experience.

In fact, I had a client today who asked me to help them improve some recruitment processes to focus more on business need, but they were keenly aware that any changes implemented must also improve candidate experience.

So I wholeheartedly agree with Lucy about the focus needing to shift towards thinking of the experience of the employee, but I’m torn by the suggestion that we should not focus our design thinking on the process.

Processes are made up of inputs, tasks, outputs and outcomes and it’s the outcome that I think Lucy is asking us to think about. What outcomes are we looking to achieve for our candidates, employees, partners and customers? What policies, processes and technologies will we need to support those outcomes?

I think process and experience are inextricably linked and the trusty “People – Process – Technology” trio still hold as fast today as it did when I started in this industry in 2001. What I think Lucy also points to is a need to ask ‘Why?’. Why do we have this process or policy in the first place – is it helping us to achieve the outcome we desire or is it a hindrance?

In my experience the very best of anything involves balance and the need to know when to sway slightly in one direction or the other. I have experienced organisations who are absolutely focussed on the employee experience and work like Trojans to ensure that their messy processes don’t impact the employee in a negative way. The unwelcome paradox here is that they either ultimately do impact negatively or the costs of trying to prevent the impact are too high.

I have also worked with organisations who have very slick automated processes but have lost the focus on employee experience – this is a common scenario and why it is so important to have both.

Process is often a good place to start having real conversations about what’s going on as it’s the area that people feel most pain, both within HR but in the wider business.
Some questions we should always ask ourselves:

  • Why are we doing this?
  • Should we continue to do it?
  • What does it help us to achieve?
  • What outcome do we expect?

So with regard to my client’s recruitment processes, the outcome we want is the right new hires to be warmly welcomed into a role where they can maximise their skills and potential. What do we need to do to make the outcome a reality?

This is “The process” – and I don’t mean just a process map showing the tasks. I mean a real look at what needs to be done operationally to help achieve the outcome. What tools do we need to employ to help support us? “The technology” – with so much technology on the market it is essential that you consider what you need before jumping into a vendor relationship that may not deliver your outcomes.

In her book Lucy Adams says, “You can see how thinking from the standpoint of an experience takes you in all sorts of directions that would never occur to you if your starting point was a process.”

I think taking the view of experience is a great and refreshing idea but needs to be backed with the reliable “People, Process, Technology” trio. This is the joined-up, holistic approach that isn’t always taken, which is perhaps why Lucy Adams feels the need to ‘disrupt’ this thought process.