Back to the issue

The whole issue on one page, ready to print or save as a PDF to read offline.

September 2026

Nine conversations on what leaders can control: the team failures that hide behind good individual performance, the talent numbers boards never hear, AI rollouts that fail on change management rather than technology, and the six-dollar gift that moved $75,000 in revenue.

Everyone Saw the Problem

Mason Duchatschek

I had been working outside in the summer heat all day and decided to treat myself to dinner at one of the nicest Mexican restaurants in town.

It was probably twice the price of the typical Mexican restaurant, but the atmosphere was impressive. The restaurant was clean, the employees were friendly, and everything about the setting suggested that the experience would be worth the premium.

I was hungry, but I was even thirstier.

Our server greeted us politely, brought glasses of water along with complimentary chips and salsa, and explained that she would give us a few minutes before returning to take our order.

I quickly finished my water. Then the empty glass sat on the table for the next five to seven minutes.

During that time, at least five different employees walked past our table. Some passed by more than once, yet no one stopped to refill the glass, ask whether I needed anything, or alert our server.

Eventually, I got up, walked to the bar, and asked the bartender for a refill. He was pleasant and took care of it immediately.

Later, after our food arrived, the same thing happened again. My glass was empty. Employees continued walking past the table, and once again, no one responded. I returned to the bartender, who promptly refilled it for a second time.

To be clear, the food was excellent. Our server was polite and checked on us at reasonable intervals. Under normal circumstances, checking every 10 or 15 minutes probably would have been perfectly acceptable.

The problem was not that the server failed to do her job. The problem was that everyone else believed the customer was her job.

Individually, Everyone Performed Well

Nothing about the experience suggested that the employees were careless or unfriendly.

The host appeared to be doing the host’s job. The servers were carrying food, cleaning tables, and attending to their assigned customers. The bartender was serving drinks and responded immediately when I approached him.

On an individual level, they all seemed to be doing what they had been hired to do. As a team, however, they failed.

They failed because multiple people saw an unmet customer need and continued walking. They may have believed the table belonged to another employee, the water glass was someone else’s responsibility, or stepping in would interfere with an established process.

Whatever the explanation, the result was the same. A very small and easily solved problem diminished what could have been an exceptional customer experience.

Job Descriptions Can Become Blinders

Organizations need clearly defined roles. Employees should understand their responsibilities, priorities, and standards.

However, job descriptions can become dangerous when employees interpret them as boundaries around what they should care about.

Those thoughts may never be spoken aloud, but customers experience the consequences.

A customer does not care which department owns the problem. The customer does not know how responsibilities are divided behind the scenes. The customer simply knows whether the organization noticed, cared, and responded.

The same principle applies far beyond restaurants. A salesperson may close the deal and assume customer service will handle everything else. An employee may see a coworker struggling and decide that helping is the manager’s responsibility. A department may hit its own performance goals while creating delays, confusion, and frustration for everyone downstream. Each person can complete an assigned task while the organization still fails to deliver the intended result.

Customer Service Is a Team Sport

I have always believed that two of an organization’s highest priorities should be serving the customer and supporting one another. Those priorities are closely connected.

When employees support one another, customers receive better service. When coworkers watch for opportunities to help, small problems are solved before they become visible failures. When people step outside the narrow limits of their roles, the entire organization becomes more responsive.

The server did not need to visit our table every few minutes. She simply needed teammates who had her back.

One employee could have refilled the water. Another could have told the server that her customer needed attention. The bartender, after seeing me request a second refill, could have asked which table I was seated at or given the server a quick heads-up.

Any one of those actions could have changed the experience.

None required a policy change, additional staffing, advanced training, or managerial approval. They required awareness, ownership, and teamwork.

Good Service Is Not the Same as a Great Experience

Was I angry? No. Would I leave a bad review? No. Was the food good? Absolutely.

Customers don’t always complain when an experience falls short. They do not necessarily confront a manager, post an angry review, or demand compensation.

Sometimes they simply decide not to return.

That makes silent disappointment especially dangerous. The company may believe everything went well because no complaint was recorded, while the customer quietly moves on.

The restaurant did many things right, but premium pricing creates premium expectations. Customers are not only paying for the food. They are paying for the atmosphere, attentiveness, consistency, and feeling that the entire organization is working together to take care of them.

The Leadership Question

Leaders should ask more than whether employees are doing their individual jobs well.

They should also ask whether employees notice what is happening around them, step in when a teammate needs help, and take responsibility for the customer’s overall experience.

Are employees trained to protect their assignments or support the mission?

Do they believe customer problems belong to specific people, or do they understand that every employee represents the entire organization?

Are managers rewarding only individual performance, or are they also reinforcing cooperation, awareness, and shared ownership?

An organization filled with capable individual contributors can still deliver an average experience. A team that serves the customer and supports one another can create something far more valuable.

Everyone at that restaurant appeared to be doing a good job. That was not enough.

Your Best People Already Know What You Won’t Say

Jackson Lynch

Most board meetings run the same way. The CEO lays out strategy. The CFO walks through the financial lens. Operating leaders explain how they will execute against it. Then, with five minutes left and half the room checking their phones, HR gets its slide: engagement is down ten percent, retention risk is up, and nobody in the room connects it back to anything that was just said.

Jackson Lynch, a four-time chief human resources officer and founder of Talent Sherpa, doesn’t think that’s a scheduling problem. He thinks it’s a diagnosis problem. Citing the same math W. Edwards Deming built modern quality management on, he puts a hard number on it: “94 percent of all of your execution problems are system problems, not people problems.” Most CEOs still file talent issues under people problems anyway, then wonder why the fix never holds.

Culture is decision residue.

Engagement Scores Are a Symptom

Ask most HR leaders why they’re investing in a new program and the answer usually stops at the program itself: we’re launching a leadership initiative, we’re improving engagement. Lynch treats that as an unfinished sentence.

Every initiative needs a second half: I’m doing this so that turnover in our most pivotal roles drops, so that time to full productivity shrinks, so that the number on the P&L moves. If a leader can’t finish that sentence within a step or two, they’re managing a cost, not a return.

I’ve watched this play out firsthand. An HR director once walked into a board meeting with real numbers instead of a mood, pulled straight from that morning’s payroll: roughly 16 percent of annual salary to replace an hourly worker, 21 percent for a professional role, well over 150 percent for senior, skilled positions. The CEO pushed back like he didn’t trust his own numbers. She held her ground, because the numbers were right.

Lynch’s read on that story surprised me. He didn’t fault the data. He faulted the frame: starting from retention still treats the problem as an HR issue with a business consequence, instead of a business issue with a talent root cause.

He compares it to a decision paper mills make without blinking, keeping a spare part on hand for a machine that takes a year to replace, so a breakdown costs two weeks instead of twelve months. Companies rarely extend that same logic to people. Lynch puts it in six words: “We have pivotal jobs without benches.” Most executives never diagnose why that gap is more dangerous than an idle machine.

Culture Is Decision Residue

Culture surveys get treated like a thermometer. Lynch treats them like a symptom chart instead. His definition is blunt: “Culture is decision residue.” It’s not the values poster in the break room. It’s the pattern left behind by the last hundred decisions a company made, whether anyone meant to send a signal or not.

He recommends a simple, uncomfortable exercise: pull your last hundred real decisions and hold them against whatever is written on the wall about who you want to be. Most leaders skip this because they already suspect what they’ll find.

Lynch has seen the gap firsthand: “I say I want collaborative people. And then I promote the non-collaborative jerk that has really, really good performance, except for all the dead bodies sitting to the left and right.”

The lesson isn’t subtle, but it’s easy to avoid. People don’t organize their effort around a mission statement. They organize it around what gets someone promoted, protected, or fired. Say collaboration matters all you want. If the person who steamrolls a team gets the corner office anyway, everyone has already learned the real rule, and no town hall language will unteach it.

Hire for the Ability to Connect Disconnected Things

Lynch has asked one interview question for thirty years, and it still throws people off. He asks what someone does for fun, then the harder follow-up: how does that make you better at the job you’re applying for? Most candidates can’t bridge the gap. A handful can, and those are the ones he hires.

He remembers one candidate, a computer scientist named Amy, who said she liked composing music. Pressed on why that mattered, she explained that writing music forced her to think about how parts build on each other in a system, and she used that same instinct when she wrote code. Lynch’s reaction was immediate: “Holy crap, Batman, you’re hired.” Thirty years later, it’s still the model for what he screens for.

That’s why he pushes back on hiring for years of experience alone. I’ve had almost the same conversation with people who tell me they’ve got thirteen years of experience in one narrow lane. What they usually have is one year of experience, repeated thirteen times. Pattern recognition built inside a single, stable environment breaks the moment that environment changes, and the only real defense is a demonstrated ability to move an idea from one domain into a completely different one.

Trade Accountability for Reliability

At times, leadership teams default to one question after something breaks: who’s accountable? Lynch thinks that question makes organizations worse, not better. He puts it plainly: “Accountability is backward-looking, and it is blame-oriented.” It hunts for a person to pin a failure on instead of asking what let the failure happen in the first place.

His alternative is reliability: what has to be true for this outcome to happen the same way every time, and what design gap let it slip this time. That question doesn’t produce a scapegoat. It produces a fix.

He borrows a tool from Cold War military planning: put a cross-functional group in a room, assume a plan has already failed twelve months from now, and ask why before it happens. Done well, it turns an uncomfortable truth into something a team can say out loud without anyone losing their job over it, which is the only way anyone flags a real problem before it becomes a crisis.

Skip that step and the meeting still happens eventually. It just happens after the damage is done, gets called an accountability review, and lands on whoever was standing closest when the system finally broke.

How to Tell the CEO What Nobody Else Will

Every senior HR leader eventually spots a problem above their pay grade: two executives who’ve stopped speaking, a board member who’s lost confidence in the CEO, a pattern everyone half sees but nobody wants to name, because naming it wrong ends careers. Lynch has a rule for that exact moment.

The rule is about positioning, not courage. He puts it this way: “It’s gotta be third-party removed. It needs to be formed as an observation, not an accusation.” An accusation forces the other person to defend themselves. An observation just asks them to notice something too. Push it at the wrong moment, or as an accusation instead, and you become part of the dysfunction you were trying to name.

His mechanism is almost boring: a five-minute block inside his one-on-ones with the CEO, reserved for things he’s watching but not yet asking anyone to act on. In one company, that meant flagging that the CFO had gone quiet in strategy meetings and started managing email instead, three sessions running. He framed it the way he coaches everyone else to: “That’s not a problem to solve. That’s an observation to deliver.” By the time that pattern needed a real decision, it wasn’t the first time the CEO had heard about it.

The Courage to Say What Everyone Already Knows

Succession plans are where this all comes together, and where it usually falls apart quietly. Most companies keep a binder with names next to every critical role, everyone nods when it comes up, and nobody opens it again until the person in that role leaves. Lynch calls that what it is: a well-intentioned fiction, because there’s no forcing function attached to it. A list of ten names nobody has actually vetted works out the same as a list of zero.

The fix isn’t a better binder. It’s a different question. Instead of asking who they’d call if this person left, Lynch asks whether the best available people are already sitting in the roles that matter most, right now, no hypothetical attached. That question has teeth, the same way naming a real turnover number has teeth instead of a vibe.

That’s the thread running through everything Lynch does: replace the comfortable version of a problem with the true one, even when the true one is harder to say out loud in a room that would rather not hear it. He calls it plainly: “It’s by having the courage to name what everyone kind of knows, but no one says out loud.”

That’s the job, not the binder, not the slide, not the survey.

You Don’t Profit From Customer Insights Unless You Take Action

Shep Hyken

How Do Companies Turn Customer Insights Into Profit?

Answer: Customer insights only create value when companies act on them to improve customer experience, reduce problems, and strengthen loyalty.

I recently received an email from Mariusz Gromada, the chief of retail customers at Bank Millennium in Warsaw. He shared some information about his recently released book, Customers First, Value Next. A quote from the book caught my eye:

Insight is a cost. Action is a profit.

As I thought about that quote, I realized, without reading his explanation, that Gromada is spot on.

How do we get insights? They come from what we experience, what customers say, what frontline employees observe, customer complaints, online reviews, survey results, social media comments, and even watching customers’ behaviors and buying patterns.

None of that is free. There is always a cost to gaining insight. It can be the hard cost of putting together a formal feedback program, whether through surveys or technology that tracks customer sentiment and comments. Or it could be the time it takes to talk directly to customers and discuss with your team. Yes, time is money.

Until you take action, all the activity leading up to the insight and the decision to act on it carries a cost. Consider that an investment.

That investment must have a return. It’s not until you take action and see positive results that you get to enjoy the fruits of your labor. And at this point, I must share that any company that intentionally asks customers for feedback and then does nothing with it is not only wasting everyone’s time, it’s also wasting dollars, as in the cost of preparing the survey and creating the system that collects the responses. Without action, you can’t profit from the investment of your effort.

Assuming You Take Action, What’s the ROI of These Insights?

  1. An opportunity to improve products and services
  2. Improved customer service and experience
  3. Fewer complaints
  4. Lower customer churn
  5. The elimination or mitigation of recurring problems
  6. Increased customer loyalty that drives more revenue and profit

Of course, there are other ways to profit from insights, but the six I’ve shared should be enough to reinforce the idea that insights by themselves have no value unless they inspire you to take action.

Collecting feedback without taking action is nothing more than an expensive exercise. Customers notice when their feedback leads to improvements. Employees notice when leadership listens to them. And businesses see the results of their efforts in the form of loyalty, retention, and growth. Insight may be a cost, but when you combine it with action, you find profit.

Silence is Not the Same as Trust

Gal Borenstein

For most of the last century, a company could manage its own reputation. A PR agency wrote the story, an ad campaign polished it, and when something went wrong on the factory floor, it usually died in a hallway conversation before any customer heard about it. That arrangement is gone now. Nobody owns the narrative anymore except the marketplace itself, and the CEOs who still act like they control the story are the ones getting blindsided.

Gal Borenstein has spent nearly 30 years watching that blindside happen, advising CEOs on how to protect their reputation and scale in high-risk environments. His reframe is blunt. Trust is not a value you put in a mission statement next to words like innovation and integrity. It is the mechanism that decides whether a company grows or collapses, because the people who decide whether to trust a brand are no longer newspaper editors. They are customers with a bad experience and phones in their hands.

Trust is no longer just a value. Trust is what drives success and failure.

Why Do So Many Executives Believe Silence Means Success?

I found this out firsthand at a resort in Las Vegas that advertised itself as luxury and delivered something well below it. When I finally got a manager, I found a woman who clearly cared and clearly had no authority to fix anything. I told her plainly that the decisions in place were costing her company plenty of bad reviews and bad word of mouth that would never come off the internet, and she didn’t argue.

Borenstein sees the same pattern across company after company, and he does not dress it up. Executives blame understaffing, an overwhelmed call center, a broken app, anything except themselves for not listening. His answer to that whole category of excuse is short: “This is all bullshit.”

What matters more than listening to the people paying you? Borenstein asks. After all, they are the ones keeping the lights on. A company with zero complaints is not a healthy company. It is a company nobody trusts enough to complain to directly anymore, which is worse.

The Survey That Got an Agency Fired for Telling the Truth

Borenstein once ran a trust benchmark for an information technology client, scoring ten attributes independently through the CEO and through the management team underneath him. One attribute asked a plain question: is this company financially strong?

The CEO answered with total confidence, describing a business that was growing and getting ready to acquire competitors. His own managers, sitting two doors down from that office, scored the same question a one, two, or three out of ten. Several said they simply did not know.

Borenstein’s team presented those results in a room with the CEO present, exactly as promised: non-attributional, aggregated, nothing traced back to a single manager. The CEO fired the agency on the spot.

It played out like the old story of the emperor with no clothes, except this time the tailors got fired for pointing out the obvious. A company that punishes the messenger for an accurate scorecard is not protecting its brand. It is guaranteeing that the next bad number nobody tells it about will be the one that breaks something.

Trust Starts Inside the Building, Not in the Press Release

Borenstein calls his model for building trust the Guardian framework, and it rests on collaboration and transparency inside a company before either one gets to matter outside it. Ask the floor staff, the middle managers, and the executive suite of most companies what the company’s values are, and the three groups will give you three answers that do not agree with each other. That gap is where trust breaks, long before it ever shows up in a bad review.

His fix for that gap is simple to say and hard to do. “You don’t start by taking care of the outside first. You have to take care of the inside.”

He points to an HVAC company running a strong commercial about its cooling season readiness, only to have two technicians badmouth the company inside a customer’s own house, because nobody had ever trained or aligned them on what the company was supposed to stand for. The advertising made a promise the operation never bothered to keep.

The same gap sank Facebook’s credibility with a large number of users who felt like their data and likenesses were casually being sold to advertisers. Rebuilding that trust took years of visible changes rather than a single apology. It’s also why a Burger King ad campaign, admitting the food had slipped and promising to fix it, read as unusual rather than reckless. Most companies would rather bury a weakness than name it first.

There’s an old trial lawyer’s rule I have followed for years: when there’s a weakness in your argument, be the one who brings it up. Hide it, and whoever finds it will present you in the worst possible light there is.

Get Ahead of the Story in the First Twenty-Four Hours, or Someone Else Writes It

The cost of skipping all of this shows up at scale too. A major aviation company built decades of trust on being the safety-first choice in its industry. Then a quality assurance employee flagged a widget that was falling apart. That information never made it up through the layers of management fast enough to matter.

A crash followed, then a year of crisis communication and management changes just to rebuild what silence inside the company had cost it. Nobody in that chain thought they were doing anything wrong. They each just assumed someone above them already knew.

Borenstein’s advice for the first twenty-four hours of any crisis runs against what most legal departments recommend. Lawyers tend to counsel silence, worried that any acknowledgment creates liability down the road.

Borenstein argues the opposite. Respond fast, respond like an actual person, and admit what needs admitting, because “Anything that sounds genuine and creates a conversation kills the sting of a review that is killing your company’s reputation.”

That means setting up basic social listening, even something as simple as a Google Alert for your own company name, and building a small tactical response team. Two or three people in marketing are enough to start, as long as they start before the story breaks rather than scrambling after it does.

Benchmark It Honestly, Then Fix It

Borenstein’s actual system for building trust is less mysterious than the crises that make companies finally ask for it. Score the business honestly across ten attributes, including marketing, sales, quality assurance, operations, HR, and finance. A low score at the start is not a failure. It is data. Build an action plan against it, put it in front of the management team so every department owns its own piece of the score, and measure it again months later.

That is the real shift Borenstein is arguing for, and it holds up precisely because it is not a slogan. “Trust is no longer just a value. Trust is what drives success and failure.”

A company that scores itself honestly at a three has more useful information sitting on its desk than the company that assumes it is already a ten. One of them has a plan. The other has a headline waiting to happen.

Why do so Many Corporate AI Implementations Fail?

Ben Tasker

Many AI implementations fail for a reason that has nothing to do with the technology. Ben Tasker, who has built applied AI certifications for more than 225,000 learners, traces the failure to a discipline most companies never think to apply to AI at all: change management. Organizations buy tools, skip the work of building the skills to use them, and then find that the investment produced nothing they can point to. The figure he attaches to that group is 95 percent.

Eighteen months ago, I knew organizations where using AI was flatly prohibited. Most were nonprofits, but the policy was real, and employees were told not to touch it. Those same organizations are now scrambling to implement, and many are moving faster than their people can absorb. That is a different mistake with an identical ending.

What makes Tasker’s claim of 95 percent worth sitting with is the shape of the loss. These companies don’t fail because the model underperformed. They fail because, in Tasker’s phrasing, “they spend a boatload of money and they get nothing out of it,” whether the AI itself works or not, since there are no people behind it.

Ask First

The first question is not which tool. That one feels strategic because it arrives with a price tag, a vendor list, and a decision date, and it’s where most executive teams start.

Tasker’s argument is that tools have a short shelf life and skills have a long one. The vendor you standardize on this quarter may be acquired, repriced, or gone inside two years. The ability to prompt well, to fit AI into an existing workflow, and to see where it creates exposure carries over to whatever replaces it. “Just because you have AI tools doesn’t mean you have an AI strategy.”

The second question follows from the first, and it’s what separates the 5 percent from everyone else. What’s the change management plan, meaning the plan for how the organization learns, not the rollout calendar? An executive team that can answer the tool question in fifteen minutes and can’t answer this one at all has just diagnosed itself.

The Layers of Learning

Tasker describes an organization as a cake, which sounds cute until you try to use it. The base is the frontline, roughly 80 percent of the workforce, and the question is narrow: which parts of my daily work can this take over, and how do I hand them off without creating a mess? The middle layer is the AI-enabled specialists, the engineers and program managers who work behind the scenes and need enough depth to stand systems up. The frosting on top is leadership, whose job is not to use the tools at all but to explain, credibly, why any of this is happening.

Each of those three layers is asking a different question. The frontline wants to know which parts of the daily job to hand off and how to do it without creating a mess. The specialists need to know how to build and maintain the systems that make the handoff possible. Leadership needs an answer to why the company is doing any of this and what happens to the people who cooperate.

A company that buys one training license for everybody has answered the frontline’s question badly and the other two not at all, and it will find that out at the layer where 80 percent of the work happens.

Just because you have AI tools doesn’t mean you have an AI strategy.

There is a version of this that looks messy from the outside. When the whole organization is encouraged to experiment, the pain points and the failures get surfaced by people who do the work. Those feed a backlog that specialists and leaders can price, rank, and attach risk to. Tasker’s own description of it is “organized chaos instead of unorganized chaos,” and the distinction earns its keep, because the alternative to sanctioned experimentation is not order. It is the same experimentation happening quietly, on personal accounts, with company data.

Responsible AI Isn’t Just Compliance

Tasker declines to file AI risk under compliance as its own separate function. He puts it inside change management and ahead of implementation, which in practice means getting ten to fifteen people in a room before anything ships, drawn from IT, HR, and the business owners who understand the process about to be automated.

The questions are unglamorous and specific. What happens when the system misclassifies a person or a ticket? If the tool is agentic and takes an action it was never meant to take, how fast can it be shut off, and does that switch exist or is it a slide? Plenty of organizations want the most advanced version of this technology without having answered a single one of those questions at the simplest version, and that gap is where the expensive surprises live.

Kodiak is Tasker’s example of the patient version. In 2018, well before driverless technology was a boardroom topic, the company began working toward autonomous trucks inside a fleet of more than a hundred. It took the long way around: design the truck, work out which routes it could handle and which states allowed it, then run a stretch with drivers still in the cab so the paper assumptions could be tested against an actual road. Drivers were paid through the training period and the case made to them was safety rather than efficiency. The outcome Tasker reports is the one nobody predicts, which is that Kodiak ended up needing more drivers rather than fewer.

The Learning Curve

How long is the AI learning curve? According to Tasker, the honest number is eighteen months, and that assumes you are starting from zero. That is Tasker’s estimate for moving an employee from level one, where they could not reliably tell you what AI stands for, to level three, where they can prompt a model, use it for routine work, take the output, and iterate on it. Levels four and five run longer, and the specialist domains like robotics and drones can take five to six years and a degree.

Executives ask how quickly the technology can be implemented. The more useful question is how quickly their own people can be brought along, and the two answers aren’t even in the same unit. Implementation gets planned against a procurement calendar. Reskilling runs on the eighteen months it takes to move one person from level one to level three, and no vendor timeline shortens that.

Tasker’s argument for starting before you have a business case is that every job will eventually be touched by AI. It means reskilling has to begin before anyone can say which roles will need which skills. The alternative is buying each new niche skill on the open market as it surfaces, at the premium the market charges, while humans are still the ones who have it.

Hiring keeps its role for genuinely specialized work, robotics and drones among it, where you cannot train your way in from a standing start. For everything else, Tasker would write prompt engineering and responsible AI into job specs in departments that have never asked for them, partly to see what talent surfaces and partly because that hire becomes the person who brings the rest of the team along.

Adaptability ranks above every technical AI skill on his list. I have watched that shift move through HR strategy sessions over the past two years. The question used to be what a candidate knows, and it’s now how fast they can learn something that did not exist when they applied.

Fear of Job Losses

What do you say to people who are afraid of losing their jobs? The standard answer is that this is about enhancement, not replacement, and employees can see it coming a mile away. A fair number of them are right to be skeptical. Reassuring a nervous workforce that nothing will change buys one quarter of calm at the cost of the credibility you need for the next three years.

Tasker’s position is transparency with something behind it. Walmart handed AI licenses to its entire workforce and told people to use them at work or at home, which moved the question from permission to practice. Other organizations have paired formal learning tracks with a commitment to no AI-related layoffs for a defined window of three to five years, which happens to be the horizon on which the return shows up. The companies that skipped that step are the ones cutting tens of thousands of roles and hiring them back weeks later when the technology turned out to be less capable than expected.

His version of the honest conversation is that jobs are going to change, and that upskilling is what prepares people for the ones that come next. “It’s not a replacement technique.”

I would put it more bluntly to the employee weighing whether to engage. Refusing to learn is a choice, and in any field, in any decade, that choice ends in the same career cul-de-sac. AI only shortens the drive.

The number worth carrying out of all this is that 95 percent, along with a clear sense of what kind of number it is. It’s not a statistic about model accuracy or vendor quality, which is how most executives hear it. It’s a management statistic, one of the very few failure rates in this category that a leadership team can move on its own.

The companies still shopping for the right tool are not early to anything. They are spending first and learning second, which is an expensive sequence.

The Six-Dollar Gift That Added $75,000 in Revenue

Vance Morris

A basket that cost less than a dollar solved one of Chef Mickey’s biggest operational headaches. A gift that cost less than six dollars added roughly $75,000 a year to a carpet cleaning company’s revenue. Neither fix required a bigger budget, a new department, or a consultant’s six-figure invoice.

Vance Morris spent a decade inside Disney, including helping launch Chef Mickey’s, before taking the same principles to NASA, the Smithsonian, and a long list of small businesses that assumed great customer experience was something only companies with Disney’s resources could afford.

They were wrong, and the businesses Morris has worked with prove it daily. The line separating a forgettable business from one customers drive past two competitors to reach has almost nothing to do with money.

It has everything to do with whether an owner is willing to look closely at the boring, mundane parts of the operation and ask what a customer experiences there, not what the owner assumes they experience.

It is not the customer’s job to remember you.

The Cheapest Fixes Produce the Biggest Wow Moments

Morris traces the habit back to his first week at Disney, on the opening team of the Yacht and Beach Club Resort, staring at binders of training manuals for every job on the property. The lesson was never the paperwork. Disney runs every role on three components: what to do, how to do it, and why we do it that way.

Most businesses stop at the first two. The why is what turns a rule into something an employee believes, and belief is what shows up in front of a customer.

That framework produced the bus boy basket. Chef Mickey’s had one mission: move 400 guests through a character dining room in 43 minutes without making the meal feel rushed. Every department got the same question: what do you need to hit that number?

The bus staff said clearing tables took too long because sugar packets, salt shakers, and table tents all had to be picked up one at a time. A basket that gathered everything into a single motion saved about 23 seconds per table. Across hundreds of tables a night, a fix worth pocket change became the difference between hitting the mission and missing it.

The same logic scales up. An independent oil change shop competing against four other stations decided to stop racing to the bottom. The owner had already told himself the truth: “there’s no competitive advantage to being second cheapest.”

Instead of cutting prices further, he put his technicians in bow ties, added a barista station staffed by the same crew on rotation, and turned the wait into an experience instead of a delay.

The shop now charges 45 percent more than its closest competitor, and the only real new expense was a coffee machine. Everything else, including the uniforms, the shop already owned.

Why Do 80 Percent of Owners Believe They Deliver Great Service When Only 8 Percent of Customers Agree?

Morris cites a study, now about two years old, that asked business owners whether their company delivers great service. Eighty percent said yes. Researchers then asked the customers of those same companies the identical question, and only 8 percent agreed. That gap does not close on its own, and it rarely gets discovered by accident.

Part of the problem is structural. Inside most organizations, distance separates the moment a customer interacts with a frontline employee from the moment that information reaches the owner. Employees inside that gap have every incentive to sand down bad news before it travels upward, because delivering it honestly risks blame or worse. The result is a boss who genuinely believes 80 percent of customers are happy, built entirely on secondhand reports from people protecting themselves.

The phone confirms the same blind spot at scale. When Morris partnered with a call center to research 4,000 home service companies, all of them paying for placement on Google Ads, he found that only 17 percent answered the phone live. Everyone else lost the caller to the next name on the list.

Morris has no objection to automation for a solo operator who physically cannot answer mid-job, but he is blunt about where the human option belongs on the menu: first, not buried behind twelve choices nobody wants to sit through.

Morris closes his own version of that gap with a comment card that skips every layer of management and lands directly at his house. He has owned a mold remediation company, an oriental rug washing business, and a carpet cleaning company in Maryland for 19 years.

In that time, the card has surfaced a genuine complaint only a handful of times. That is not proof his service is flawless. It is proof that when feedback has nowhere to hide, an owner learns what is happening instead of what employees assume he wants to hear.

Retention Is Cheaper Than Everyone Pretends

Morris runs the math on his own carpet cleaning business without flinching. It costs him $136 to land a new customer, covering the ad spend, the phone answer, and everything else required to turn a stranger into a client. It costs him $23 a year to keep an existing one. The instant he retains rather than replaces a customer, he is more than a hundred dollars ahead, yet most owners build marketing budgets that spend almost entirely on acquisition and almost nothing on the people who already paid them.

That thinking shapes the process his carpet cleaning technicians follow before they ever touch a stain. They park on the street instead of the driveway, so an oil leak never becomes the homeowner’s problem. They knock instead of ringing the bell, because “friends knock and salespeople ring.”

They hand over a gift that costs less than six dollars, a bottle of spot remover, a small bag of cookies, and a note with Morris’s personal cell number. That gift alone drove a 26 percent increase in mid-tier package sales, worth roughly $75,000 a year, and it took close to a year of small adjustments to get right.

Morris draws a hard line between that kind of loyalty and the punch card kind. “It is not the customer’s job to remember you,” he says, and the responsibility runs the other way. Real loyalty means a customer drives past two competitors to reach you on purpose, not that they are hanging around for a tenth free coffee. A punch card is not loyalty. It is closer to a bribe with an expiration date.

None of this requires more information. Most owners are not short on ideas. They collect them from books, mentors, and their own frontline staff. Most of those ideas sit untouched. The only original line Morris will take credit for is blunt: “Won’t profit unless you implement.”

Pick one idea, even one borrowed from a completely different industry, and put it to work in your own business before moving on to the next one. A business that does something with one good idea will always outperform one that is still collecting them.

The CEO Everyone Admired Called Himself a Loser

Boaz Gilad

John runs a large logistics company in the Midwest. His employees call him an inspiration. His clients call him a top performer with real integrity. By his own description, he’s a loser.

I would fire my ass.

Boaz Gilad has coached elite performers for more than 17 years, from Olympic athletes to CEOs, and he’s heard some version of that contradiction from nearly all of them.

John’s business runs on discipline. His body doesn’t. He’s 300 pounds, doesn’t like how he looks, and has never managed to keep the weight off, despite running a company that depends on exactly the kind of discipline he apparently doesn’t have anywhere else. Gilad’s question in moments like this isn’t why John lacks discipline. It’s where the discipline he clearly already has disappeared.

Why Excellence Doesn’t Transfer Itself

Gilad’s answer starts with a reframe many executives resist. The problem was never that John lacked the capacity for discipline. He proves it every day at work. What he’s never done is bring the operating system that runs his company into the parts of his life where it’s missing.

Gilad compares it to a lifter who’s built serious triceps and a strong chest and keeps doing push-ups because push-ups are what he’s good at, while his legs go untouched. It sounds obvious from the outside. From the inside, it just looks like doing more of what already works.

When Gilad asked John to imagine a version of himself running his business the way he runs his health, and rate the results, John didn’t hesitate: “I would fire my ass.”

That’s not a throwaway line. It’s a CEO applying his own standards to himself and failing the audit, out loud, in real time.

Values Aren’t the Problem

Gilad has spent enough time with thousands of people setting New Year’s resolutions to know inspiration was never the real bottleneck. People are good at making lists of what matters to them. They’re bad at building the structure that turns a list into a life. The gap isn’t between wanting change and knowing what to change. It’s between knowing and doing, and that gap gets filled with reasons to wait until conditions feel more ready.

He points to Michael Phelps, who once described his own regimen during his most dominant years in three words: “I eat, I sleep, and I swim.” Gilad doubts Phelps felt inspired every single morning he climbed into cold water before sunrise. The commitment held anyway, because it wasn’t running on motivation in the first place.

Does Your Calendar Match What You Say You’re Committed To?

Gilad tests this with a blunt question: open your phone right now and look at tomorrow’s schedule. Does it reflect what you say matters most? By his estimate, roughly eighty percent of the time, it doesn’t. Most calendars don’t show commitment. They show whatever fire needed putting out that week.

He saw this play out with two partners who ran a small chain of coffee shops and came to him after a rough stretch. On paper, they wanted the same thing. In practice, one wanted three profitable shops and more afternoons with his daughter.

The other wanted to build a serious independent chain and was still negotiating two cents off paper cup prices while helping run a business that had long since outgrown that kind of attention.

Their friction wasn’t a communication problem. It was two different definitions of winning trying to share one company. Gilad’s fix wasn’t a mediation session. It was a split. She bought him out. He kept a stake in what they’d built and got his afternoons back. Both of them, by his account, ended up closer to what they wanted than they would have if they’d stayed partners and kept arguing about growth.

Success Builds Its Own Cage

The same gap between what people say and what they do shows up again once they win. Gilad calls it the golden handcuffs problem, and he’s watched it catch Olympic champions and CEOs with the same grip.

The clearest version of it involves the sprinter Michael Johnson. He once described sitting on a plane to a world championship and realizing his mind was on whether the pool guy back home had shown up, not on racing the fastest people alive. Somewhere between the effort it took to become world-class and the comfort that world-class success eventually buys, the flexibility that built the success gets traded for cars, houses, and routines nobody wants disturbed.

Gilad has lived the other side of that same trap. He spent 20 years as a real estate developer, took his company public, and ran it for almost seven years before it collapsed. He’d stopped enjoying the work years before that happened, and the Porsche and the family vacations made it easy to keep ignoring how he felt about the job itself.

Looking back now, seven years past the collapse, he doesn’t call it a tragedy. He calls it the fork in the road he wouldn’t have taken voluntarily, and the thing that finally forced an honest answer to what he wanted to do next.

What Would Your Life Look Like If You Were in the Driving Seat?

Gilad’s most direct advice starts with removing the audience. Sit down alone, not with a spouse or a best friend, and ask honestly what your life would look like if every limitation you’re currently citing were set aside, just for the length of the exercise. If the honest answer matches the life you’re already living, he says you’re fine. Keep doing what you’re doing. You don’t need a coach any more than a Toyota Camry needs a pit crew.

If it doesn’t match, there’s one more question, and it’s the one that does the work. Picture a stroke tomorrow morning, the kind that takes away any chance to fix things afterward. Would you look back and call it a great run, or would you have to admit, quietly, that it wasn’t what you wanted?

Gilad doesn’t ask that question to be dramatic. He asks it because it’s specific enough to cut through the story people tell themselves, and honest enough to show which game they’re playing before they run out of time to change it.

Busy is Not a Strategy. It is a Symptom.

Ginny Priem

Some executives who are quietly drowning look completely fine from the outside. The title is right. The salary is right. The calendar is packed in a way that reads as importance rather than what it is: depletion, dressed up as discipline.

Ginny Priem spent more than two decades in corporate leadership finding that out the hard way, and now she runs a framework built around one uncomfortable question: What are you still doing that you should have let go of months or years ago?

The cost of not answering that question rarely shows up on a spreadsheet. It shows up as a team that never quite hits its ceiling, a leader who can’t take a real vacation, and a body that eventually forces the conversation the calendar kept avoiding.

Where would you put yourself? Were you even a consideration for the top five most important people in your life?

Why Does Hiring People Like Yourself Backfire?

Priem built her first teams the way many new leaders do. She hired people who worked the way she worked, thought the way she thought, and moved at roughly her speed. It felt efficient at the time. It also quietly failed, and it took years of running real teams before she understood why.

Five versions of the same person are not a stronger team. They are one person’s blind spots, multiplied by five. What performs better is a group built out of different strengths set next to each other on purpose: someone who connects, someone who communicates clearly under pressure, someone willing to do the operational grind nobody else wants. That is a deliberate staffing decision, not a personality match.

“You’re not going out to brunch. This is work that you’re doing.”

You have to be strategic about who ends up on a team, because being pleasant is not the same as being effective. Leaders who confuse the two pay for it slowly, over years, in a way that never shows up on a single performance review.

Letting Go Is Not the Same as Losing Control

Priem calls her whole philosophy Unsubscribe, and the sunk cost fallacy is exactly what it is built to fight. Once someone has invested years in a job, a strategy, or a relationship, walking away starts to feel like admitting the investment was wasted, so people keep adding to it instead.

Ask anyone who has left a miserable job or a toxic relationship whether they regret hanging on longer. Almost nobody says yes. The regret runs the other direction: people wish they had let go sooner.

Ten years ago, Priem took a vacation and, for the first time in her career, did not work through it. That sounds small until you notice how rare it is among people running teams. She had spent years staying reachable on every day off and telling herself that was dedication. What she learned instead is that a leader who works through vacation is not modeling commitment. She is teaching her entire team that rest is not allowed, whether she says a word about it or not.

Letting go of that control changed how her team performed, and not because she stopped caring. She stopped being the bottleneck. Holding on to every decision, every outcome, every message the second it arrives, is not leadership. It is anxiety dressed up as leadership. Turn off notifications for a day and the emails are still there when you get back to them. Given real room, most teams handle more than the executives above them are willing to admit.

I have made the same trade in a smaller way. My phone stays off during a run or a ride, and I keep zero notifications on email or text, checking both only when I have decided to. Nothing urgent has ever gone unresolved because of it. The message is still there when I get back to it, exactly like Priem describes, and the peace that comes from not being on call for every ping is not something you get by explaining it to people. You get it by doing it.

Burnout Hides Behind Competence, Not Weakness

Burnout rarely looks like someone falling apart. It looks like someone extremely good at their job, refusing to stop being extremely good at their job, long after their body started sending warnings nobody in the room wanted to name.

Priem knows this from the inside. “I had abnormal skin cancer lesions removed from my body. My hair broke off and fell out, and I got shingles on my face in my thirties.” That is not a metaphor for stress. She connects those health problems with a period of chronic stress. She kept telling herself she was fine because her calendar said she was succeeding. Hustle culture trains people to wear busyness like a badge, but everyone gets the same twenty-four hours in a day, and constant motion is not proof that any of it points at what matters.

The fix she teaches is blunt on purpose: notice the reaction before it hardens into a habit. React, observe, respond, in that order, deliberately. Most leaders skip straight from reacting to justifying the reaction, and by the time the pattern gets named, it has already cost them a decision, a relationship, or their health.

Resilience Is Not About Bouncing Back

Priem has a hot take on the word resilience, and it starts with rejecting the way most people use it. The word got worn out during the pandemic, deployed to praise anyone who simply kept showing up. Her view is more blunt: human beings are resilient by default. The people who came through years of lockdowns, layoffs, and uncertainty demonstrated resilience whether they called it that or not.

The leaders and performers she considers genuinely exceptional are not the ones who return to where they started. They use what knocked them down to move somewhere better than where they were before.

“It’s not about bouncing back. It’s about bouncing forward.”

Bouncing back treats a setback as an interruption to recover from. Bouncing forward treats it as information, evidence about what needs to change before the next version of the same problem shows up.

Many performance reviews still reward the first definition. An executive who survives a brutal quarter and returns to business as usual gets called resilient. The one who uses that same brutal quarter to change how the team operates rarely gets the credit, even though that is the harder, more useful response.

The Point of Work

Ask most people to name the CEO of a company they don’t work for, and watch them struggle. She left corporate leadership with a string of titles behind her: director, senior director, associate vice president. None of it mattered the moment she walked out the door, and she says so plainly. People who attach their identity to a role are building on ground that disappears the day the role does. That isn’t an argument against ambition. It’s an argument against mistaking the title for the point of the work.

The same idea follows her into how she talks about feeling stuck. When an executive can’t say why they feel stuck, she doesn’t ask about strategy first. She asks what they find meaningful, in the job or outside it, because pressure has a way of making people perform work that technically succeeds while meaning nothing to the person doing it.

An Important Question for Executives to Ask Themselves

Priem runs an exercise in her keynotes simple enough to try right now. Name the five most important people in your life. Most people rattle the list off fast: a spouse, kids, a couple of close friends.

Then she asks the second question. “Where would you put yourself? Were you even a consideration for the top five most important people in your life?” Most people can’t answer right away, and the pause is the answer. People who spend their careers managing everyone else’s priorities routinely forget to put their own name anywhere on the list, not because they don’t value themselves, but because nobody ever asked them to check.

Write your own name down somewhere on that list. Not necessarily first, but somewhere real, carrying the same weight as everyone else on it. If there’s no room for it without rearranging the whole list, that says more about how you’re running your life than any performance review ever will.

Your People Problem Has an Owner, and It Isn’t Your People

Hanna Bauer

When a CEO tells me the company has a people problem, the useful next question is about ownership, and it rarely gets a warm reception. Who owns the system that produced the problem? The system owners are the leaders, which means most people problems are leadership problems nobody has named yet.

Hanna Bauer, founder and CEO of Heartnomics, states it in six words: “Nothing happens outside of the culture.” Every hire, every promotion, every quiet resignation happens inside whatever your culture currently rewards, designed or not.

Nothing happens outside of the culture.

The harder follow-up is how you would know what your culture rewards. Values printed on a wall don’t count. A mission statement living somewhere on the website doesn’t count either. What counts is who gets promoted, what behavior gets recognized in front of everyone, and what your people privately believe the path to growth is. If they think advancement depends on being in a particular person’s good graces, then that belief is your culture regardless of what the poster in the break room says.

Vision on the Wall

Companies spend real money building a collective vision and then never ask why each individual is there. Bauer learned the difference from a salesperson who outworked everyone on her team.

He had never taken a beach vacation with his own dad. His first child had just been born, and “he really wanted to see his baby’s little toes in the sand.” That was the reason he showed up. The company vision mattered to him only to the degree it made his own possible, and it did. He got the trip.

Someone else in that same office was past retirement age and financially fine, with grown kids who took care of her. She stayed on anyway, running accounts payable and receivable, because “she wanted to end her career well.”

Two people under one roof, two reasons that have nothing to do with each other, and neither one shows up on an engagement survey. Once a leader knows those reasons, the job changes shape. The question stops being how to motivate people and becomes what kind of company has to exist for dreams like those to survive inside it.

Plenty of executives hear this and file it under “soft.” I’ve never bought that. The companies that dismiss it are the same ones where dread starts Sunday night, where people sit in the parking lot working up to walking in, and where somebody cries in a bathroom stall on break because they think nobody can hear.

None of that shows up as a line item. It shows up as turnover, as sick days taken by people who aren’t sick, and as work done at half speed by people who are already looking for another job.

The flip side is just as measurable: people who find meaning in the work stop shopping their resume, and some of them will take less money to stay.

Looking Good on Paper

Bauer recently worked with a team where every visible number was healthy. Revenue was coming in. Nobody had resigned. Everything the leader asked for got done on schedule. The failure was invisible from the outside: every idea in that building originated with one person. The leader set the agenda, generated the options, and made every call, while the same two voices spoke in meetings and everyone else waited it out.

Rigid companies look strong right up until something real hits them. Bauer’s comparison is a tree in a storm, where the trunk that refuses to move is the one that cracks or comes up at the roots. The teams that break first in a disruption are usually the ones that were following every rule, because following rules was the only skill anyone practiced.

Decision-Making and Workload Problems

Bauer cites figures putting professional burnout at 77 percent, with more than 56 percent of leaders saying they don’t feel equipped to make decisions.

Sit with the second number.

Decision-making is one of the leader’s core job functions, and a majority of the people holding the job feel unprepared for it. What exhausts a lot of leaders isn’t just the hours on a calendar. It’s that every decision, including the trivial ones, routes back through them.

Delegation training doesn’t fix this. Neither does an empowerment workshop. People can only decide on their own when they know the organization’s values well enough to use them as a filter, and installing that filter is the step almost nobody completes. Without it, the leader is the filter, permanently, and there is no succession plan no matter what the organizational chart shows.

A second failure sits underneath the first one, and Bauer names it directly: “You cannot speak about responsibility without authority.” Handing someone an outcome they’ll be measured on while keeping every lever that produces it is not delegation. It’s a setup.

The damage concentrates in the middle. Line managers absorb decisions made above them, carry them out without a voice in them, and answer for results they had no power to shape. Bauer’s observation is that this is where the next generation of senior leaders is coming from, which means they arrive at the next level already spent. Anyone worried about a leadership bench should look at what the current middle layer is allowed to decide.

Alignment at Speed

Race teams pull cars off the track for alignment constantly. The sedan that goes to the grocery store and back can go a long time without it. Speed is what creates the need, and that reframe is the one I’d want every executive to hear: “It’s not a bad thing that you’re coming out of alignment. It just means that you’re doing something.” Drifting isn’t evidence of failure. Refusing to schedule the pit stop is.

I learned the physics of this at 16, in a small town about 30 miles south of St. Louis. I had a fast car and a straight stretch of country road with no side roads and almost no traffic, and I told myself I was being responsible by taking it out where I couldn’t hurt anybody.

While driving at 55 miles an hour, a small steering error would usually drift me past the yellow centerline and into the next lane. I had time to correct my course without thinking about it.

At twice that speed, the same small error could cover twice the distance before I had time to react and send both me and my car into a ditch.

Faster is the promise on every AI tool being pitched right now, and plenty of them can deliver it. Speed does nothing for a company that can’t say who it is, what it rewards, and which decisions its people are allowed to make without asking. It just covers more ground with whatever misalignment was already there.

When a business is operating at a slow speed, leaders have plenty of time to react and correct their course. At speed, a misaligned business, just like a car, can crash.

The work to do before you accelerate is subtraction, which is what lean asks for: strip out enough noise that people can see the road, then find out how fast you can really go.