Growth Comes From What You Don’t Have

Growth Comes From What You Don't Have

GUEST POST from Mike Shipulski

If you have more features, I will beat you with fewer.

If you have a broad product line, I will beat you with my singular product.

If your solution is big, mine will beat you with small.

If you sell across the globe, I will sell only in the most important market and beat you.

If you sell to many customers, I will provide a better service to your best customer and beat you.

If your new projects must generate $10 million per year, I will beat you with $1 million projects.

If you are slow, I will beat you with fast.

If you use short term thinking, I will beat you with long term thinking.

If you think in the long term, I will think in the short term and beat you.

If you sell a standardized product, I will beat you with customization.

If you are successful, I will beat you with my hunger.

If you try to do less, I will beat you with far less.

If you do what you did last time, I will beat you with novelty.

If you want to be big, I will be a small company and beat you.

I will beat you with what you don’t have.

Then, I will obsolete my best work with what I don’t have.

Your success creates inertia. Your competitors know what you’re good at and know you’ll do everything you can to maintain your trajectory. No changes, just more of what worked. And they will use your inertia. They will start small and sell to the lowest end of the market. Then they’ll grow that segment and go up-scale. You will think they are silly and dismiss them. And then they will take your best customers and beat you.

If you want to know how your competitors will beat you, think of your strength as a weakness. Here’s a thought experiment to explain. If your success is based on fast, turn speed into weakness and constrain out the speed. Declare that your new product must be slow. Then, create a growth plan based on slow. That growth plan is how your competitors will beat you.

Your growth won’t come from what you have, it will come from what you don’t have.

It’s time to create your anti-product.

Image credit: Pixabay

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

Difference Between Customer Experience Perception and Reality

Difference Between Customer Experience Perception and Reality

GUEST POST from Shep Hyken

This is an important topic that every CEO, business owner, leader, manager, and supervisor must understand. When it comes to customer service and customer experience (CX), there is a difference between perception and reality.

First, how we think our customers perceive our customer service and CX is often not the reality. It’s just our perception. Reality isn’t what we think or believe. It’s what our customers say. Often, there is a big difference between our perception and the reality of our customers’ experiences.

Some may be saying, “Shep, you’ve covered this before.” Yes, however, it is worth covering again, especially since my friend Stephen Van Belleghem released his excellent book, A Diamond In the Rough, where he quotes a Bain survey finding that “80% of CEOs think their company is customer-centric, but only 8% of customers agree.”

One of my LinkedIn followers, Rajat Chawla, read my Forbes article about Van Belleghem’s book and asked, “What’s your best advice to bridge the gap?” As I always promise, if you reach out to me on any social channel and ask a question, I’ll answer it there or in my newsletter, videos, podcast, or on my TV show, Be Amazing or Go Home. So, here’s my answer:

There are at least three strategies for narrowing the gap between these perceptions:

  1. Leaders need to pay attention to their data. After they do a self-assessment, which is their perception, they should – if they haven’t already – survey their customers to discover their reality. That’s the most accurate way to measure the difference.
  2. Leaders should “mystery shop” their companies themselves. They should learn firsthand what it’s like to be a customer. They should be looking for the experiences their customers receive during peak hours or in the middle of the night, what a sales call is like compared to a customer service call, and more.
  3. Finally, leaders should spend time on the front line, either shadowing (listening in) on customer support calls or taking the calls themselves. I addressed spending time on the front line in my first book, Moments of Magic when I covered the All Aboard program in which executives spent one day each quarter with a salesperson visiting customers. In my most recent book, I’ll Be Back, I wrote about how Bill Gates visited the customer support center and asked to take customer support calls. The power of spending time on the front line is undisputed! Experiencing firsthand comments from customers is a powerful dose of reality – hopefully, good reality!

Customer Experience Reality Cartoon

What I love about these three strategies is that other than a little time and effort, there is little or no expense to implement them. So, what are you waiting for? If you haven’t already done so, discover the difference between your perceptions and your customers’ reality. And my wish for you is that there is little or no difference between the two!

Image Credits: Unsplash

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

Innovation Friction Risks and Pitfalls

Innovation Friction Risks and Pitfalls

GUEST POST from Howard Tiersky

There’s a lot to be learned about innovation by looking at good ideas that just didn’t make it. We’d all like to believe that if we have an idea that genuinely improves upon something, and if we execute that idea correctly, the idea will be successful. But there is another factor to consider:

Here’s today’s example:

Back in the early 2000’s, I was running part of the eCommerce practice for Ernst & Young. Around 2003 we moved into a shiny new building at 5 Times Square in New York City, right next to where the ball drops on New Year’s Eve. The building was the first place I had ever seen with a keypad-controlled elevator. Instead of pushing an up or down button, the elevator is called by a numerical pad. You type in the number of the floor you are going to and receive a response from the keypad with a letter (such as D.) That letter corresponds to the elevator that you have been assigned to. You go to “your” elevator and, when it arrives, it automatically takes you to your floor.

This innovation delivers several benefits that improve the elevator experience:

1. It makes the elevators more efficient.

People going to lower floors are clustered together, as are people going to higher floors, and people going to the same floors are put on the same elevator. This allows more elevators to run express. Fewer stops. Less waiting for an elevator and a faster trip in the elevator.

2. It reduces “clicks.”

In a traditional system, an elevator user has to “call” the elevator and indicate their desire to go up or down. Once in the elevator, the user has to pick a floor. The old system was not a massive amount of effort, but the new system reduces two interactions to one. Presumably an improvement.

(Plus there’s no worrying about the kid in the elevator who decides to push all the buttons — there aren’t any!)

Is there a downside to this innovation?

Well, if you’re already in the elevator, there’s no opportunity to change your mind without getting off on the wrong floor and repeating the whole process. The biggest downside of this innovation is simply that it requires users to learn something new. In fact, when I moved into 5 Times Square, I found that when people came to meet with me for the first time, the first 10 minutes of our meeting was inevitably focused on their need to vent their reactions to our crazy elevators and how they couldn’t figure out how to use them!

Truthfully, the elevators were easy to use. Clear instructions were printed above the keypad, and the system worked very well. The problem was that it required users to relearn a skill they had fully and completely mastered (i.e., using an elevator) and start over at a beginner level — even if it only took 30 seconds to learn how to use the new elevator system.

I’ve watched with interest over the years to see if these types of elevators would take off. It turns out they didn’t. Very recently, I was visiting a client in Houston. The building had actually spent money to remove the keypad system and replace it with the traditional 2-step process. Wow. You know your innovation is not doing well when your customers are willing to invest tens of thousands of dollars to get rid of it and go back to the old way.

After much thought, I believe it’s all because of the friction of asking people to re-learn how to push an elevator button. Some innovations don’t require this. The new Boeing 787s have substantial innovation, but from a passenger standpoint, they work in basically the same way as the last round of airplanes. The innovations improve comfort, fuel efficiency, and other factors, but you recline the seat and return your tray table to an upright position in pretty much the same old way. Other innovations require learning: ATMs, DVRs, electric cars. All of these innovations have been successful, despite their learning requirements. However, the need for users to learn new behavior did slow their adoption. Innovation friction slows down adoption of innovations that require substantial behavior change, and even more so if it requires learning. This is especially true if the innovation requires un-learning an old way of doing something. If the friction is greater than the momentum of the benefit of overcoming it, the innovation stops dead in its tracks.

An example of this friction is the metric system, which has made only a very small amount of progress in adoption over the last 50 years, despite being clearly superior to the “English system.” It’s just too darn much trouble to change.

One last story about innovation friction from early in my career.

At that time, I was working with a lot of insurance companies creating web-based interfaces to replace traditional “green screen” systems used by insurance agents to quote and initiate new policies for auto and home insurance. It typically took a new hire 4-5 months to learn the system well enough to complete a policy quote — and well over a year to become truly proficient with it! We proudly designed replacement systems that anyone with basic computer skills could learn in a day or two at most, but found that some users were quite hostile to our efforts. They already knew how to use the green screen systems, and they were pretty darn fast with them. One Customer Support Agent even quoted Charlton Heston to me, saying I would only be able to take away her green screen if I pried it from her “cold dead hands.” Creepy? Yes. But also telling. Those old systems are gone now, because of the huge benefit of being able to train people on the new system so quickly. This benefit put the companies that used the new system in a position to more or less force that innovation onto other users.

Many successful innovations have required change and learning — automobiles, indoor toilets, smartphones. With all of these examples, we’ve seen many people willing to learn, for whom the “pain” of change was outweighed by the perceived benefit. But we also see a substantial number of users who resisted for years, saying, “No thanks, I like my outhouse (or horse and buggy or bank teller) just fine.” When conceiving or launching an innovation that requires learning, it’s important to consider the role innovation friction will play in adoption, where you can reduce it, and where you can increase the user’s willingness to accept it as the cost of the greater benefit.

This article originally appeared on the Howard Tiersky blog
Image Credits: Unsplash, Howard Tiersky

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Five Lessons from the Apple Car’s Demise

Five Lessons from the Apple Car's Demise

GUEST POST from Robyn Bolton

In 2014, rumors started to circulate that Apple was developing a self-driving autonomous car to compete with Tesla.  At the end of February 2024, rumors circulated that Apple was shutting down “Project Titan,” its car program. According to multiple media outlets, the only logical conclusion from the project’s death is that this decision signals the beginning of the end of Apple.

As much as I enjoy hyperbole and unnecessary drama, the truth is far more mundane.

The decision was just another day in the life of an innovation.

As always, there is a silver lining to this car-shaped cloud: the lessons we can learn from Apple’s efforts.

Lesson 1: Innovation isn’t all rainbows and unicorns

People think innovation is fun.  It is.  It is also gut-wrenching, frustrating, and infuriating.  Doing something new requires taking risks, which is uncomfortable for most people.  Even more challenging is that, more often than not, when you take a risk, you “fail.” (if you learned something, you didn’t fail, but that’s another article). 

What you can do: Focus on the good stuff – moments of discovery, adventures when experimenting, signs that you’re making life better for others – but don’t forget that you’re defying the odds.

Lesson 2: More does not mean success

It’s been reported that Apple spent over ten billion dollars on Project Titan and that over 2000 people were working on it before it was canceled. With a market cap of over two trillion dollars, a billion dollars a year isn’t even a rounding error. But it’s still an eye-popping number, which makes Apple’s decision to cut its losses downright courageous.

What you can do: Be on guard for the sunk-cost fallacy.  It’s easy to believe that you’ll eventually succeed if you keep working and pouring resources into a project.  That’s not true, as Apple experienced.  And in the rare cases when it is, executives are often left wondering if the success was worth the cost.

Lesson 3: Pivot based on data, not opinions

At least four different executives led Project Titan during its decade in development, and each leader brought their own vision for what the Apple Car should be.  First, it was an electric vehicle with driver assistance that would compete with Tesla.  Next, it was a self-driving car to compete with Google’s WayMo.  Then, plans for fully autonomous driving were canceled. Finally, the team returned to its original target of matching Tesla’s Level 2 automation.  

Changes in project objectives, strategies, and execution plans are necessary for innovation, so there’s nothing obviously wrong with these pivots.  But the fact that they tended to happen when a new leader was appointed (and that Jony Ive caused an 18-month hiring freeze simply by expressing “displeasure”) makes me question how data-based these pivots actually were

What you can do: Be willing to change but have a high standard for what is required to cause a change.  Data, even qualitative and anecdotal data, should be seriously considered.  The opinion of a single executive, not so much.

Lesson 4: Dream big, build small

Apple certainly dreamed big with its aspirations to build a fully semi-autonomous vehicle and it poured billions into developing and testing the sensors, batteries, and partnership required to make it a reality.  But it was never all-or-nothing in its pursuit of the automotive industry.  Apple introduced CarPlay the same year it kicked off Project Titan, and it continues to offer regular updates to the system.  Car Key was announced in 2020 and is now offered by BMW, Genesis, Hyundai, and Kia.

What you can do: Take a portfolio approach towards your overall innovation portfolio (Apple kept working on the iPhone, iPad, Apple Watch, and Vision Pro) and within each project.  It’s not unusual that a part of the project turns out to be more valuable than the whole project.

Lesson 5: ___________________________

Yes, that is a fill-in-the-blank because I want to hear from you. What lesson are you taking away from Project Titan’s demise, and how will it make you a better innovator?

Image credit: Dall-E via Bing

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

Top 10 Human-Centered Change & Innovation Articles of April 2024

Top 10 Human-Centered Change & Innovation Articles of April 2024Drum roll please…

At the beginning of each month, we will profile the ten articles from the previous month that generated the most traffic to Human-Centered Change & Innovation. Did your favorite make the cut?

But enough delay, here are April’s ten most popular innovation posts:

  1. Ignite Innovation with These 3 Key Ingredients — by Howard Tiersky
  2. What Have We Learned About Digital Transformation? — by Geoffrey A. Moore
  3. The Collective Growth Mindset — by Stefan Lindegaard
  4. Companies Are Not Families — by David Burkus
  5. 24 Customer Experience Mistakes to Stop in 2024 — by Shep Hyken
  6. Transformation is Human Not Digital — by Greg Satell
  7. Embrace the Art of Getting Started — by Mike Shipulski
  8. Trust as a Competitive Advantage — by Greg Satell
  9. 3 Innovation Lessons from The Departed — by Robyn Bolton
  10. Humans Are Not as Different from AI as We Think — by Geoffrey A. Moore

BONUS – Here are five more strong articles published in March that continue to resonate with people:

If you’re not familiar with Human-Centered Change & Innovation, we publish 4-7 new articles every week built around innovation and transformation insights from our roster of contributing authors and ad hoc submissions from community members. Get the articles right in your Facebook, Twitter or Linkedin feeds too!

Have something to contribute?

Human-Centered Change & Innovation is open to contributions from any and all innovation and transformation professionals out there (practitioners, professors, researchers, consultants, authors, etc.) who have valuable human-centered change and innovation insights to share with everyone for the greater good. If you’d like to contribute, please contact me.

P.S. Here are our Top 40 Innovation Bloggers lists from the last four years:

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.






Change the World With a Keystone Change

Change the World With a Keystone Change

GUEST POST from Greg Satell

On December 31st, 1929, the Indian National Congress, the foremost nationalist group on the subcontinent, issued a Declaration of Purna Swaraj, or complete independence from British rule. It also announced a campaign of civil disobedience, but no one had any idea what form it should take. That task fell to Mohandas Gandhi.

The Mahatma returned to his ashram to contemplate next steps. After his efforts to organize against the Rowlatt Act a decade earlier ended in disaster, he struggled to find a way forward. As he told a friend at the time, “I am furiously thinking day and night and I do not see a way out of the darkness.”

Finally, he decided he would march for salt, which impressed almost no one. It seemed to be an incredibly inconsequential issue, especially considering what was at stake. Yet what few realized at the time was that he had identified a keystone change that would break the logjam and the British hold on power. Today the Salt March is known as Gandhi’s greatest triumph.

A Tangible And Achievable Goal

One of Gandhi’s biggest challenges was to connect the lofty goals and high-minded rhetoric of the elites who led the Indian National Congress with the concerns of everyday Indians. These destitute masses didn’t much care whether they were ruled by British elites or Indian elites and, to them, abstract concepts like “freedom” and “independence” meant little.

Salt, on the other hand, was something that was tangible for everyone, but especially for the poorest Indians and the British salt laws provided a clear and actionable target. All you had to do to defy them was to boil seawater to produce salt. What at first seemed trivial became a powerful call for mass action.

In my book, Cascades, I found that every successful movement for change, whether it was a corporate turnaround, a social initiative or a political uprising, began with a keystone change like Gandhi’s salt protests. To achieve a grand vision, you always have to start somewhere and the best place to begin is with a clear and achievable goal.

In some cases, as with voting rights in the women’s movement in the 19th century and, more recently, marriage equality for the LGBT movement, identifying a keystone change took decades. In other cases, such as improving worker safety in Paul O’Neil’s turnaround of Alcoa or a campaign to save 100,000 lives in Don Berwick’s quest to improve quality in medical care, the keystone change was part of the initial plan.

Involving Multiple Stakeholders

The concept of Indian independence raised a number of thorny issues, many of which have not been resolved to this day. Tensions between majority Hindus and minority Muslims created suspicions about how power would be structured after British rule. Similarly, coordinating action between caste Hindus and “untouchables” was riddled with difficulty. Christians and Sikhs had their own concerns.

Yet anger about the Salt Laws helped bring all of these disparate groups together. It was clear from the outset that everyone would benefit from a repeal. Also, because participating was easy—again, it was as simple as boiling sea water—little coordination was needed. Most of all, being involved in a collective effort helped to ease tensions somewhat.

Wyeth Pharmaceuticals took a similar approach to its quest to reduce costs by 25% through implementing lean manufacturing methods at its factories. Much like Gandhi, the executives understood that transforming the behaviors of 20,000 employees across 16 large facilities, most of whom were skeptical of the change, was no simple task.

So they started with one process — factory changeovers — and reduced the time it took to switch from producing one product to another in half. “That changed assumptions of what was possible,” an advisor that worked on the project told me. “It allowed us to implement metrics, improve collaboration and trained the supervisor to reimagine her perceived role from being a taskmaster that pushed people to work harder to a coach that enables improved performance.”

Breaking Through Higher Thresholds Of Resistance

By now most people are familiar with the diffusion of innovations theory developed by Everett Rogers. A new idea first gains traction among a small group of innovators and early adopters, then later spreads to the mainstream. Some have suggested that early adopters act as “influentials” or “opinion leaders” that spur an idea forward, but that is largely a myth.

What is much closer to the truth is that we all have different thresholds of resistance to a new idea and these thresholds are highly contextual. For example, as a Philadelphia native, I will enthusiastically try out a new cheesesteak place, but have kept the same hairstyle for 30 years. My wife, on the other hand, is much more adventurous with hairstyles than she is with cheesesteaks.

Yet we are all influenced by those around us. So if our friends and neighbors start raving about a cheesesteak, she might give it a try and may even tell people about it. Or, as network theory pioneer Duncan Watts explained to me, an idea propagates through “easily influenced people influencing other easily influenced people.”

That’s how transformative ideas gain momentum and it’s easy to see how a keystone change can help move the process along. By starting out with a tangible goal, such as protesting the salt tax or reducing changeover time at a single factory, you can focus your efforts on people who have lower thresholds of resistance and they, in turn, can help the idea spread to others who are more reticent.

Paving The Way For Future Change

Perhaps most importantly, a keystone change paves the way for larger changes later on. Gandhi’s Salt March showed that the British Raj could be defied. Voting rights for women and, later, blacks, allowed them to leverage their newfound power at the polls. Reducing changeover time showed how similar results could be achieved in other facets of manufacturing. The 100,000 lives campaign helped spur a a quality movement in healthcare.

None of these things happened all at once, but achieving a keystone change showed what was possible, attracted early adopters to the cause and helped give them a basis for convincing others that even more could be achieved. As one of Gandhi’s followers remarked, before the Salt March, the British “were all sahibs and we were obeying. No more after that.”

Another benefit of a keystone change is that it is much less likely to provoke a backlash than a wider, sweeping vision. One of the reasons that the Salt March was successful is that the British didn’t actually gain that much revenue from the tax on salt, so were slow to react to it. The 100,000 lives campaign involved only six relatively easy to implement procedures, rather than pushing hospitals to pursue wholesale change all at once.

So while it’s important to dream big and have lofty goals, the first step is always a keystone change. That’s how you first build a sense of shared purpose and provide a platform from which a movement for change can spread. Before the Salt March, Gandhi was considered by many to be a Hindu nationalist. It was only after that he truly became an inspiration to all Indian people and many others around the world.

— Article courtesy of the Digital Tonto blog and previously appeared on Inc.com
— Image credits: Pexels

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.






London Calling

London Calling Braden Kelley

by Braden Kelley

I will be in London attending a reunion soon and have some availability May 15-17, 2024 if anyone would like to book a keynote, workshop, or advisory session while I’m there.

Are you looking to build a continuous innovation infrastructure in your organization?

Would you like to learn more about the Change Planning Toolkit?

Want to learn how to become your own Futurist using the FutureHacking™ suite of tools?

I’m also open to helping promote a get together if someone has a space in central London to offer up for hosting a Human-Centered Change and Innovation community meetup.

Contact me if you have interest in any or all of these!

p.s. Be sure and follow both my personal account and the Human-Centered Change and Innovation community on LinkedIn.






Six Causes of Employee Burnout

GUEST POST from David Burkus

There’s this simple misconception when it comes to burnout. We tend to think that burnout comes from just working too hard—putting in too many hours per week, exerting too much energy, and tipping your work-life scale out of balance. As a result, leaders and companies have sought to combat burnout by offering “rest” as a generic cure-all for their drained and disengaged people.

They’ve added greater flexibility programs (even before the pandemic), brought self-care opportunities into the office, and some have even become more serious about vacation time. And these programs aren’t without benefit, but it became obvious fairly quickly that the returns on the rest investments were limited (again, even before the pandemic added new stress).

The reason is that burnout comes from many sources—and anti-burnout efforts need to address all of these sources to truly be effective. So in this article, we’ll review the six true causes of burnout and offer some practical tips for leaders to mitigate the damage from these causes.

1. Excessive Workload

The first cause of burnout at work is excessive workload—and at first glance excessive workload looks like too much work. But excessive workload refers to juggling multiple projects, not having clarity on which one to focus on, and not knowing what next steps are for some. It’s not about hours worked, but rather the feeling that no matter how many hours are worked, work isn’t getting completed.

Excessive workload often sneaks up on the best performing people, because as they do good work, more work gets assigned to them. To prevent this, leaders need to keep track of how many projects they’re asking their people to take on. And if adding more to the workload, leaders can make priorities clear—even going so far as to state which projects are no longer a priority can go a long way to reducing excessive workload.

2. Poor Relationships

The second cause of burnout at work is poor relationships. Even if the workload of employees isn’t overwhelming and the project requirements aren’t confusing, doing the work with toxic colleagues can quickly lead to burnout. Poor relationships not only trigger feelings of dread as people begin the workday, but during the workday toxic coworkers can trigger many of the other causes of burnout on this list by being too demanding, too critical, or too lazy and adding to the workload of their colleagues as a result.

That’s why smart leaders focus on the relationships and cohesion of a team even more than they focus on whether the team is stacked with talented members. They know that individual performance is a function of team dynamics and work to build bonds on those teams. Leaders can help repair some of the relationship damage by seeking to create shared understanding between the team around differences in personality, preferences, and other contextual factors of the team. In addition, creating shared identity among members reinforces the idea that they’re truly one team and need to put personal differences aside.

3. Lack of Control

The third cause of burnout at work is lack of control. Lack of control refers to how much (or rather how little) autonomy employees have over their work. When individuals get to have a say in what projects they take on, or at least how, when, and where they tackle those projects, they’re more motivated and produce better quality work. But when a micromanager is hovering over their shoulder (or virtually hovering via constant check-ins or monitoring software) then those same people become demotivated and burnt out.

Leaders can’t always decide what projects their teams work on, but there’s always creative ways to increase autonomy on the team. If the project itself is a must-do, then leaders can discuss with the team who does what to get it done. If the deadlines are nonnegotiable, teams can still decide what the checkpoints or smaller deadlines look like. It may not seem like much, but a little autonomy goes a long way toward soothing burnout.

4. Lack of Recognition

The fourth cause of burnout at work is a lack of recognition. When people feel like they’re good work isn’t noticed, it becomes harder and harder for them to motivate themselves to keep working. And when they’re juggling multiple projects through excessive workload or juggling multiple toxic coworkers because of poor relationships, a lack of recognition compounds the problem. It’s difficult to take the time each day or each week to recognize each person’s contribution, especially when the demands of the work keep rising.

But it’s essential that leaders find time to praise the people on their team and express gratitude for their contribution. Moreover, it’s vital that leaders connect that recognition to the work with as little delay as possible. Just keeping track of wins and sharing them later in the annual performance review may get those wins documented, but it won’t reduce burnout in the people performing the work unless those wins are praised in the moment as well.

5. Lack of Fairness

The fifth cause of burnout at work is a lack of fairness. Doing great work and having it noticed is important, but feeling like that work is not getting as much notice as mediocre work done by another person or team can quickly diminish any positive effect from recognition. Likewise, feeling like another person or team is cutting corners or breaking rules and not being sufficiently reprimanded can spike feelings of unfairness that lead to burnout.

Depending on their power or place in the organizational chart, leaders may not be able to do much about an overall lack of fairness in the company. However, that doesn’t mean they’re powerless. In situations of unfair recognition, leaders can fight for the team to get greater notice and make sure people notice the fight. But in situations of unethical behavior, sometimes the best thing is to lead their team to a more just organization.

6. Purpose Mismatch

The final cause of burnout at work is a mismatch between the company’s purpose and the personal purpose or values of the individual. We want to do work that matters, and we want to work for leaders who tell us that we matter. But often in the quest to define an organizational mission statement, grandiose visions about stakeholders and society can actually blur an individuals’ ability to see how their work contributors to something so big. Or, if they see it, they may not feel as inspired about it as the senior leaders who wrote it during a consultant-led offsite and the lavish retreat center.

Smart leaders know their people’s values and what aspect of the work resonates most with them, and they know how to reinforce how the day-to-day work meets that personal desire for purpose. Most often, this is best done by connecting the team’s tasks to the people who are directly served by the team. We often think of purpose as “why we do what we do” but for many people, purpose is better stated as “who we help through the work that we do.”

Conclusion

Looking at the full list, it becomes apparent why merely reducing hours worked or adding a few self-care programs falls short of banishing burnout. Leaders need to take care of more than just the physical when it comes to keeping people productive and healthy. They need to talk about purpose, and make sure that purpose is being served in fair way. They need to make sure people have a clear picture of expectations and are recognized when they meet those expectations. By addressing all of these causes, leaders can turn their culture from one that drains people to one that leaves them feeling more energized than when they started. And that will make a huge difference in whether or not people feel burnt out or whether they feel like they’re doing their best work ever.

If you prefer a video version of this article, you will find it here:

Image credit: Pexels

Originally published on LinkedIn on December 21, 2021

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.






Is It Bad Behavior or Unskilled Behavior?

Is It Bad Behavior or Unskilled Behavior?

GUEST POST from Mike Shipulski

What if you could see everyone as doing their best?

When they are ineffective, what if you think they are using all the skills to the best of their abilities?

What changes when you see people as having a surplus of good intentions and a shortfall of skills?

If someone cannot recognize social cues and behaves accordingly, what does that say about them?

What does it say about you if you judge them as if they recognize those social cues?

Even if their best isn’t all skillful, what if you saw them as doing their best?

When someone treats you unskillfully, maybe they never learned how to behave skillfully.

When someone yells at you, maybe yelling is the only skill they were taught.

When someone treats you unskillfully, maybe that’s the only skill they have at their disposal.

And what if you saw them as doing their best?

Unskillful behavior cannot be stopped with punishment.

Unskillful behavior changes only when new skills are learned.

New skills are learned only when they are taught.

New skills are taught only when a teacher notices a yet-to-be-developed skillset.

And a teacher only notices a yet-to-be-developed skillset when they understand that the unskillful behavior is not about them.

And when a teacher knows the unskillful behavior is not about them, the teacher can teach.

And when teachers teach, new skills develop.

And as new skills develop, behavior becomes skillful.

It’s difficult to acknowledge unskillful behavior when it’s seen as mean, selfish, uncaring, and hurtful.

It’s easier to acknowledge unskillful behavior when it’s seen as a lack of skills set on a foundation of good intentions.

When you see unskillful behavior, what if you see that behavior as someone doing their best?

Unskillful behavior cannot change unless it is called by its name.

And once called by name, skillful behavior must be clearly described within the context that makes it skillful.

If you think someone “should” know their behavior is unskillful, you won’t teach them.

And when you don’t teach them, that’s about you.

If no one teaches you to hit a baseball, you never learn the skill of hitting a baseball.

When their bat always misses the ball, would you think the lesser of them? If you did, what does that say about you?

What if no one taught you how to crochet and you were asked to knit scarf? Even if you tried your best, you couldn’t do it. How could you possibly knit a scarf without developing the skill? How would you want people to see you? Wouldn’t you like to be seen as someone with good intentions that wants to be taught how to crochet?

If you were never taught how to speak French, should I see your inability to speak French as a character defect or as a lack of skill?

We are not born with skills. We learn them.

And we cannot learn skillful behavior unless we’re taught.

When we think they “should” know better, we assume they had good teachers.

When we think their unskillful behavior is about us, that’s about us.

When we punish unskillful behavior, it would be more skillful to teach new skills.

When we use prizes and rewards to change behavior, it would be more skillful to teach new skills.

When in doubt, it’s skillful to think the better of people.

Image credit: Pexels

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.






Are Your Customer Surveys Costing You Business?

Are Your Customer Surveys Costing You Business?

GUEST POST from Shep Hyken

Why does a company send out a customer satisfaction survey? Generally, it is to find out if they did a good job or what they can do to make the experience better.

In the weekly Super Amazing Show I do with Brittany Hodak, we talked about surveys. The general consensus was that shorter was better. After the show, we heard from John Hughes, who is connected with me on LinkedIn. Here is a shortened version of his comment:

“Saying, ‘Short surveys are better,’ is a bit like saying tall people are better at basketball. Yes, it helps, but you still have to be talented and have that extra ‘something’ to be a professional basketball player. … Rather than focusing on short surveys, I would say companies should truly investigate the principles by which customers choose them and then try to match the survey to the customers’ willingness to help. Ironically, customers at top service companies (think Ritz-Carlton, USAA, Chewy, Amazon, and Navy Federal Credit Union) are actually more willing to take longer surveys because they appreciate the relationship. An unwillingness to take a survey can be the most direct measure they do not value the relationship.”

First, I love John’s comment, especially the analogy to professional basketball. I won’t argue that some brands have customers who are more willing to take the longer surveys; however, Brittany and I were talking in general terms. And in general, short surveys get higher response rates. I shared with John that depending on how many surveys are sent out – as in a large number – the company can keep the surveys short and ask different questions, which should give them similar feedback as if they sent out fewer longer surveys.

Shep Hyken Customer Survey Cartoon

Here are some findings from our 2024 Customer Service and CX research (sponsored by RingCentral) that back up my comments:

  1. In 2024, 67% of customers said they don’t complete surveys if they are too long.
  2. Furthermore, almost one in five (19%) of customers stopped doing business with a company or brand because its satisfaction surveys were too long.
  3. And 23% of customers stopped doing business with a company because it kept sending too many surveys.

It’s not all gloom and doom for surveys. There are plenty of people who are happy to complete surveys, and we’ll share some of those findings later this year.

Back to John’s comment about customers at top service companies who will take the time to answer longer surveys. There are some rock star brands that are so good that customers are compelled to share their experience in a survey, be it long or short. But for most of us mere mortals, we should pay attention to what most customers are telling us about customer satisfaction surveys.

Image Credits: Unsplash

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.