Apr 18 - May 8Phase 1May 8 - 27May 28 - Jun 5Jun 7 - Jul 1Phase 2Jul 2 - 14Jul 17 - Aug 14Phase 3Aug 15 - Sep 16
Put HR flavour of the month into reverse. Look at everything you are doing and, unless you have evidence it is working in your organisation, stop doing it.
And by evidence, I mean genuine, statistically valid, experimentally tested results.
Of course, this also means, don't introduce any new initiative until you have proven it will add value, however defined, to your organisation.
To follow my own principles, you might start by testing this "throw it all away" process with some experiments. Work with a local higher education establishement with a maths department to help develop the statictical models you will need (I am assuming that few HR professionals have deep mathethamtical capabiliites). Look for a high maintenance process (eg your competency model), identify some activities that make use of the model (say, recruitment - you will need to define what success means in recruitment terms), split your organisation into experimental groups and use a variety of recruitment approaches. Assess and validate the results.
If there is a difference in outcome, does it generate a sufficient return on the cost and effort of introducing and maintaining the process
HR and many practitioners are stuck in an old way of thinking. They're hooked to a traditional command-and-control thinking that is incabable of recognising the way the world and the workplace now needs to change fundmentally. I would hope these hacks will help, but at the moment I'm really doubtful. It needs revolution not evolution, otherwise HR will be left firmly out on a limb!
This is the whole debate about where OD should sit in an organisation. Sitting with HR, with direct reports to an HR Specialist Manager could result in OD being put 'back in the box' and kept away from the projects they can help to revolutionise. OD's strengths are seen as highly disruptive and inviting risks which HR colleagues deem unnecessary. Our major difference - OD works with conflict for the purpose of innovation, while HR tries to avoid conflict at all cost out of fear of litigation.
Bring on the revolution!
Exactly... OD/Strategic HR, call it what you want may well benefit from being separated from transactional issues/legal/holiday etc. etc. Jim Scully and I kicked the tyres of this one a while back over here.
Stepping back howerver, other functions have created distinct and well understood 'sections' as a result of adopting/implementing new processes, tools and techniques. Six Sigma experts sit within manufacturing or related, but it's quite clear what they do and what they contribute. Equally, the creation of social media marketeers/managers/monitors have all emerged in the last 5 or so years but these roles typically all fall under the marketing department. Likewise, as companies get larger, their finance functions grow in complexity, credit specialists, expense processing, treasury functions, FX hedging activities and so on all emerge as distinct disciplines or specialist parts of finance. The same will be true in IT and elsewhere.
Looking at how other functions have tackled this, perhaps the question is not about splitting HR/OD up but about working out how value is added in a consistent and scalable fashion from different parts of HR e.g. OD/L&D/Payroll/Legal/Comp & Ben etc. Once the methods, techniques and processes are understood and the value added is acknowledged by the wider part of the business, this 'splitting up of OD and Strategic HR' problem disappears quite effortlessly...
I suppose we here have to apply the other principles described elsewhere in the hackathon, namely those of removing hierarchies and having role descriptors rather than job descriptions.
Having overlapping job descriptions appear to cause conflict and resentment, including within HR. Your comment about 'OD/Strategic HR, call it what you want' has caused - within my own reflective self - a discomfort (just being honest) as HR generally hold a qualification while OD will be less likely to have a relevant qualification, which in times of restructures and redeployments cause a lot of conflict and anxiety as traditional recruitment processes still highly value qualifications.
>I suppose we here have to apply the other principles described elsewhere in the hackathon
Agreed - there's also some interesting talking going on about establishing a skunkworks, post hackathon, to turn these ideas into action (as per the link, Peter Cheese is open to this). The idea is that the CIPD acts as a broker between hackers and organisations who want to pilot hacks and innovations.
>Having overlapping job descriptions appear to cause conflict and resentment, including within HR.
Exactly, the ambiguity around OD/Strategic HR/Parterning and so forth is far from ideal. I've been chatting with David D'Souza about this. One of our conclusions is that there's no consensus around a mental model for HR. What is best practice in one organisation might well be alien and unknown to another and so on it goes. Throw in debates about goals, objectives and priorities for the function and things start to get very complex, very quickly. Contrast this with the other departments who, in broad terms, all have a well recognised mental model which translates easily into day to day activities and related approaches and ways of working.
I think this Hackathon has come at a great time, the question remains though, will we all be able to turn ideas into action and genuinely shift the work done and perception of HR? I hope we can, but I think the skunkworks, or something similar is going to be an important part of that journey.
One reservation I have about the pilot work (sorry) is that much of the discussions so far are showing the interdependencies which all make the bigger 'system crash'. Can we really create pilots big enough to show the systematic benefit across a larger organisation? If we are looking for a revolution we are relying on a 'flashmob of people who think differently'. Leave it with me and I'll probably join you on Twitter with some further thoughts on taking this forward.
Sounds good Heidi... I agree that a lot of the hacks do present threats to the larger system, but then I guess it's a case of working within the context and constraints that are presented. For example, is there a department head or several team leaders who would sponsor a new approach, rather than the whole organisation, or is an innovation better in a startup business with no HR infrastructure? Finding out which hacks can be piloted in a given context is one of the steps that needs to happen...
Looking forward to your additional thoughts via twitter...
I believe the trick we have to find is how such ideas as we have can be transferred into the wider business community to provide a vocabulary and framework for understanding and insight, not how we transform the HR function. Then we will have made a difference..
If I've understood you, I think you're on to something here. Regardless of whether one takes an evolutionary or revolutionary approach to enhancing HR, my sense is that the best way to make a difference is to create the catalysts for change such that the business pulls HR in to help on various problems and projects, as opposed to HR constantly needing to push the next initiative and often finding itself struggling to be heard.
HR typically struggles to generate high levels of demand for the expertise and problem solving skills it offers and yet, as you say above, in order to make a difference, the business must embrace whatever variation of HR that is proposed, both strategically and tactically. If this scenario can be created on a regular basis, both within a single organisation and ideally across multiple businesses, then HR will be well on the way to something much more valuable and something very different to what we see today.
Incidentally, there is another hack on push v. pull which Heidi De Wolf wrote - this may chime in with what you're saying. Are you planning on joining any of the hacking teams?
Bruce, Thank you for promoting the Hacking Team on PUSH vs PULL.
This principle has such wide implications so it may be useful to just focus on one particular scenario such as how can HR build better rapport with the services to be invited in? Once we have a hacking team, it may be useful to explore that first so that we can come up with something practical and ease to implement as a pilot.
Hi Heidi, no problem about promoting the Push v Pull hack, I think it's got to be one of the key features of any successful hack, at least if it plans on being implemented and used in practice.
Maybe building rapport with the services is a good place to start. Whatever the starting point is, I'm of the opinion that for any pull-orientated approach to work, decision makers in the business (and ideally as many people as possible in the business) need to be comfortable with the proposed business case/strategy, along with the planned execution/tactics. Once the strategy and tactics are clear and are understood, the conditions for HR to be pulled into the business are set...
>Revolution not evolution - I concur... many of the models and techniques are 20, 30, 40 years or older. Ulrich's Business Partnering was arguably the last major innovation in HR and this has met with a great deal of criticism, not least from the originator himself...
It'll be interesting to see if a group of people with a more radical perspective emerges from this hack...
This has made me think about how simple it is to create something complex and how complex it is to create something simple. If a large team of people struggle with their workload, and in HRs case a workload created to support employees and managers across an organisation, then how will employees and managers cope with this information and integrate it into their daily practice of serving customers? Plus HR is not the only service whose purpose is to support others across the organisation. The only way to simplify support to the organisation is to break out of the silos and collaborate across all the support services.
Thank you for sharing your thoughts!
>Is the problem that HR practitioners have become too busy to think deeply or too afraid to challenge?
I'd say in part, this is a contributing factor. I often come back to the great rush to get level A and B psychometric training completed during the 1980's and 1990's i.e. the paper and pencil years. Working out the statistics, normed scores and various levels of interpretation must have been very tedious and to then have managers fail to embrace and champion this work must have been very demotivating.
You need to register in order to submit a comment.