Chris Laping,  Author, Co-Founder and CEO at People Before Things, LLC, joins Jan and Jim in a discussion about change — why it seems so straightforward but fails so often. The key to change is a culture of empowerment and respect. Chris shares the genesis of the philosophy of People Before Things and how it grew from his leadership roles in IT. His curiosity led him to explore the conditions that prepare people for change and conditions that block change. Change is not a function of a team’s attitude but of their preparation and capacity. It is the role of the leader to prepare the team, communicate the why and how to them, and grant them the space to perform the necessary change in a culture of empowerment. Key Takeaways   [4:47] Chris explains how he developed the framework for People Before Things. He stepped into IT leadership and found that it was difficult to build organizational buy-in for change. He looked for patterns to explain success or lack of success and he learned that change was not the end user’s problem but a leadership opportunity. [5:35] Chris sees two patterns for successful change: first, enable people for change by nurturing conditions that set people up for change, and second, activate people for change by nurturing conditions that inspire engagement and make team members willing accomplices to the change. Someone who is already heavily scheduled won’t work on the change if it is not given space. [8:06] Respect, collaboration, trust, and a unified vision are the attributes for project success. Leaders don’t always have these in their toolbox. Their toolbox is getting work done, performance, excellence, and continuous improvement. They need to intertwine a culture of empowerment with the tools of getting work done. Chris gauges a company’s health by how they tackle tough problems together. [11:01] There is always change in an IT department. It is not the technology that solves problems. Chris has seen many managers become enamored with technology as an end, and not as a means to an end. Finance and HR leaders are especially susceptible to this. Building business capability is the goal. This is people’s work, not technology’s work. Culture is more critical than technology. [15:43] Initiating technology projects without basing them on the culture sets up failure. Communicating and training on the technology is no substitute for communicating why there is new technology, and how it fits in the mission.   [19:27] In the IT world there is often talk about executive sponsors. It should be executive ownership, not just sponsorship. Executives need to emphasize how important this change is in the organization. They need to show up and be involved all the time. They need to be invested in the team and the team’s success. Executives and their team together need to be accountable to the same outcome and results. [24:20] Chris’s father and other great leaders modeled intellectual curiosity and asking questions. Feedback loops require not just asking for feedback but actually doing something about the feedback. The important thing Chris learned from leaders is that questions led to action about the information. This reinforces the feedback loop. People learn their input will be heard, considered, and used. [27:36] Chris offers two disruptive ideas: first, that change is a leadership opportunity. It’s not about team members refusing to change but about leaders enabling change. The heavy lifting is getting your team into position to win. The second idea is that real change happens at the grassroots level. It is important to get a common voice established in the rank and file. They often hold the key to solutions. [29:57] Chris talks about offsite meetings. If your takeaway is a strategy that you will increase sales and improve profitability, you wasted your time. Your team comes to work daily already knowing this. Rather than spending time stating the obvious, get aligned on a common goal and why that goal is import