Ruth Bader Ginsburg: “A court ought not be affected by the weather of the day, but will be by the climate of the era.” Martin Ginsburg: “The law is never finished. It is a work in progress, and ever will be.” (On the Basis of Sex, 2018)
Culture fit is an interesting topic. Some revere it, while others revile it. (OK, maybe not that extreme… but wasn’t that fun to say/read?!)
About a year ago, I wrote about hiring for culture fit because around that time I was seeing more and more revile than revere for this topic. The topic has resurfaced in recent weeks, especially as it relates to diversity and inclusion.
I mentioned over the last couple of weeks that there are some important takeaways from the current crisis. Here’s another takeaway.
There’s a little bit of irony in the title of today’s post. Why do we have to make sure the customer experience is crisis ready? (Employee experience, too! This post applies to both!)
I write about organizational culture and core values quite often. One of my most recent articles on this topic was about whether or not employees believe in their companies’ core values. In that post, I shared this statistic from Gallup: only 23% of U.S. employees believe that they can apply the core values to their work, while only 27% believe in the values. That’s pretty dismal, and I think I know why that’s the case.
This is a modified version of a post I originally wrote for CallidusCloud. It appeared on their blog on June 14, 2018.
If you want to move beyond cosmetic changes and lip service to real changes in both the employee experience and the customer experience, the first thing you have to look at is your company’s culture.
What is a Culture Committee? And do you need one? (The short answer is "Yes!")
Last month, I wrote a two-part series about how to stand up your team of CX Champions. Without a doubt, they are an important part of the customer experience transformation governance structure and transformation success.
This blog reflects the personal opinions of individual contributors and does not represent the views of Futurelab, Futurelab's clients, or the contributors' respective employers or clients.