Why are so many HR leaders talking about design thinking?
Longtime readers might know that I founded and co-host with Trish McFarlane the popular HR Happy Hour Show, a podcast covering HR, HR tech, HR leadership and more. In the last several months, a number of the show’s guests–HR leaders from Red Hat, T-Mobile, General Motors and NBCUniversal, for example–have brought up a phrase that, even as recently as last year, I don’t recall hearing.
That phrase is “design thinking,” and while you probably have heard the term, you might not have considered it from an HR or HR-technology point of view. Design thinking has been described as an iterative process that tries to understand a business problem, as well as who and what it is impacting. Those using this strategy challenge existing assumptions and approaches to solving a problem, and ask questions to identify alternative solutions that might not be readily apparent. Design thinking is a solution-based approach and usually prescribes a series of specific phases, stages and methods to help designers and business teams arrive at improved, user-focused solutions.
For HR-tech projects, make sure that the project managers and HR leaders actually spend time with and observe the “real” employees who use the HR and workplace technologies in their jobs. All too often decisions around software selection, implementation and configuration are made by central project teams, consultants or vendor staff who have gotten limited to no involvement or input from the users whose jobs and work processes will be impacted the most by any new HR or workplace tech. Project teams can’t empathize with employees if they don’t include employees in a meaningful manner at all stages of the process.
During this stage, designers and project leaders gather all the information and input from the initial phase. The team can then review and assess this information with the goal of defining the core problems identified. But a key element of design thinking is the goal to make “humans” the central point of the problem you are seeking to solve.
For example, think of a target metric, such as, “We need to decrease the number questions for the employee call center about payroll and benefits by 10 percent this year.” Instead, a design-thinking approach would define the problem as, “Employees should be provided a platform for payroll and benefits that is easy to use, understand and where they can find information.”
In this stage, the designers and project team gather their ideas to establish the required solution features, functions, and any other process-design elements to address the problem in a human-centered way.
The goals of almost all HR-technology initiatives can be expressed in “human” terms. Make access to information faster and easier for front-line workers. Give managers better guidance to mentor and coach new employees. Arm new employees with resources that welcome them and show them that the organization is ready to support them. These are “human” expressions that have more meaning to project teams and employees than metrics and abstract corporate goals. It is hard to rally most people around meeting a metric, so the goals of any HR-tech project should resonate and connect in a human way, especially with those whom you will ask to make (sometimes substantial) changes in how they get their work done.
During this stage of the design-thinking process, the project team is able to start generating specific ideas and approaches. With the understanding of the users of the solution and their needs from the empathize stage, the more detailed observations and desired solution features from the define stage, and clarity about what the team is working towards that is specified in the human-centered problem statement, the team can begin generating ideas. This is often the time where team members are encouraged to “think outside the box” to identify new solutions to the problem statement you’ve created, and these ideas often feed back to the define stage, as participants often discover different ways to look at the problem. In this process, all ideas should be considered, as it is important to get as many ideas or problem solutions as possible unearthed as you begin this phase.
There are plenty of ways that rapid, iterative and creative ideation can manifest in HR-technology projects. Let’s take just one recent example–the move of many organizations away from annual performance reviews to a more rapid, lighter and feedback-driven approach to guiding and improving employee performance. By thinking creatively about how best to coach, develop, and reach organizational performance objectives, HR leaders have been able to drive significant changes in how employee performance is managed, and how the HR technologies that support these processes have developed and evolved. A similar kind of evolution has been happening with employee-engagement surveys. The larger point being Design-thinking approaches create an environment in which many kinds of ideas can be proposed, even those that just a few years ago would have been considered crazy.
In the prototype phase, the project team’s goal is to produce fast, lightweight and iterative solutions or, if it is an actual product, different versions or specific features of the product, with the goal of evaluating these solutions for effectiveness in solving the problems identified in the Define stage.
The project team can experiment with many potential solutions to find the optimal approach for each of the problems identified in the first three stages. Potential solutions can be implemented on a pilot or small scale, investigated by the project team and end users, and decisions can be made about whether to continue with a given solution, seek to improve it or reject it entirely. At the end of this prototype stage, the project team will have a better understanding of the available solutions, how a given solution addresses or fails to address the defined problems and will better understand how a given solution will impact users, as well as their influence on the potential success or failure of the solution.
A great example of prototyping in HR tech involves a vendor of talent-assessment and interviewing solutions. Its client was in the process of opening two similar retail locations at about the same time in two demographically similar cities. Each location had about the same number and type of jobs to fill prior to opening.
For HR-tech projects (leaving out areas like payroll), the best outcome of the testing process is getting validation from the end users that the problems you identified in earlier phases will actually be addressed successfully by the solutions you have designed and will deploy. Too often in HR-tech testing, we focus on things like process completion, error rates and output reports. While all are important, design thinking challenges project teams to make sure their users positive about the proposed solutions, and that their needs (remember, we started with empathize) are going to be met. “How do you feel about the solution?” is a question you should ask as often as possible during the test phase. Once you’ve gone live, it is usually too late.
While the concepts surrounding design thinking are not new and are well-understood by the design, engineering and maybe even the marketing industry, they have not always been applied to the kinds of challenges that HR leaders face. But as many experienced and progressive HR leaders have been telling me lately, design-thinking concepts and approaches are becoming more common and are having a positive impact on the design, delivery and success of HR programs and HR-technology solutions. There’s plenty of opportunity here for HR leaders to use these approaches to create better solutions and experiences for their employees.
For a deeper, more granular and more targeted way to better understand how new and emerging technologies are changing work and workplaces, be sure to mark your calendar for the HR Technology Conference and Exposition Sept. 11-14 in Las Vegas.