<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sherry Heyl on Medium]]></title>
        <description><![CDATA[Stories by Sherry Heyl on Medium]]></description>
        <link>https://medium.com/@SherryHeyl?source=rss-a7113085f5ad------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QQJyC1JMMFyc-gCSzobEjQ.jpeg</url>
            <title>Stories by Sherry Heyl on Medium</title>
            <link>https://medium.com/@SherryHeyl?source=rss-a7113085f5ad------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 20:14:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@SherryHeyl/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[When Silence Gets Expensive]]></title>
            <link>https://medium.com/@SherryHeyl/when-silence-gets-expensive-89c4b82cda5a?source=rss-a7113085f5ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/89c4b82cda5a</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[change-leadership]]></category>
            <category><![CDATA[chnage-management]]></category>
            <dc:creator><![CDATA[Sherry Heyl]]></dc:creator>
            <pubDate>Sun, 04 Oct 2026 15:33:50 GMT</pubDate>
            <atom:updated>2026-10-04T15:33:50.171Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Y8xfIVHjMzk--5Kpi6h6Q.png" /></figure><p>Think back to the last time you sat in a meeting where leadership announced a significant change. Maybe it was a new AI platform, a restructuring, or an operating model designed to make the company more efficient. The presentation was well organized, the rationale made sense, and the timeline was ambitious but achievable. When the leaders finished explaining what would happen next, they opened the floor for questions.</p><p>What did the room sound like when they asked for questions? Maybe there was a little polite back-and-forth, a clarification about timing or a question about training.</p><p>Maybe one person kept raising his hand, asking about exceptions, about workload, and about what happens when the new system doesn’t match how the team really works.</p><p>Do you remember how the room responded to him? Were people glancing at the clock, quietly hoping he’d let it go so everyone could get back to work? And when he finally stopped, did the meeting end a few minutes early, with everyone a little relieved to get back to their desks?</p><p>If you were one of the leaders in that room, you probably walked away feeling good. The questions had all been answered, and the meeting stayed on schedule, so the change seemed to have landed remarkably well. If you were sitting in the audience, you may remember a very different conversation happening in the hallway afterward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gop7z8DpEstd7z8CEI-gPw.png" /></figure><p>Now consider what might really be going on in moments like that. When a room is quietly willing one person to stop asking questions, does that mean everyone else understands the plan? Or have they decided the matter is settled, that their input won’t change anything, or that raising a concern will earn them the same impatient looks? The person asking all those questions may be the only one still telling you what he sees. I’ve come to believe one of the most dangerous moments in organizational change comes when everyone seems to understand and have no questions or expressed concerns; it might look like success, but if your room has gone that quiet, treat it as a warning sign and start asking why.</p><p>We’ve Learned To Treat Resistance As The Problem<br>There’s a reason so many leaders treat resistance as the enemy, and much of it is simple human psychology. After months of building a plan, pushback can feel like a verdict on your judgment, and most of us instinctively hear disagreement as something to defend against. Momentum feels like progress, so anything that slows it down starts to look like an obstacle. Traditional change management has reinforced that instinct for decades by teaching leaders that people fear uncertainty, protect the status quo, and need to be persuaded and brought along. I don’t dismiss that entirely. Change creates real uncertainty, people do get attached to familiar ways of working, and sometimes resistance really does need to be overcome.</p><p>Somewhere along the way, though, many organizations began reading the absence of resistance as proof of success. If people aren’t complaining, they must be accepting, and if they’re accepting, they must be adopting. That creates a dangerously simple equation.</p><p>No resistance = alignment = adoption = success.<br>Organizations rarely work that way. An employee can disagree with a change and still be deeply committed to making it succeed. Another can smile, complete the required training, and quietly keep working exactly the way they always have. So which of those two people is actually more resistant?</p><p>Resistance Is Information<br>Think about what has to happen before someone openly challenges a change. They have to notice something, compare it with what they know about the customer, their role, or how the work really gets done, and decide the problem is worth the interpersonal risk of raising it. That’s engagement. It may be uncomfortable or poorly phrased, and the person may turn out to be wrong, but they’re still participating.</p><p>When someone says, “There’s no way our team can implement this by November without dropping something else,” they’ve handed you information. The same is true when someone points out that the new system doesn’t account for how the team handles exceptions, or reminds you that a similar effort broke three years ago and explains exactly where. You don’t have to agree with any of them. Labeling them resistant, however, means you may be discarding the very information you need to make the change work.</p><p>That’s why I’ve come to think of resistance as information, and of silence as a possible information failure.</p><p>Silence Can Look A Lot Like Alignment<br>I understand why people stop speaking up. Maybe they raised concerns during the last initiative and nothing happened, or they watched a colleague get tagged as “negative” for challenging a decision. Maybe every question they’ve asked has been met with an explanation of why leadership is right. Or maybe they’ve simply calculated the cost of speaking up and decided it isn’t worth it.</p><p>There’s another reason people go quiet, and it’s one leaders rarely notice in themselves. During transformation, we ask employees to think critically, champion the change, and behave like owners. Then someone says, “I think we’re making a mistake,” and critical thinking suddenly gets relabeled as negativity. We tell people to think like owners until they disagree with the owner. People learn quickly, and if speaking up is rewarded only when it confirms what leadership already believes, they’ll stop offering the information leadership needs most.</p><p>The CIPD, the UK’s professional body for HR and people development, describes employee silence as choosing to hold back despite having something to say. Its research notes that people stay quiet when the personal risk of speaking seems to outweigh the likely benefit, and roughly one in four employees reported high levels of silence.</p><p>This is where Amy Edmondson’s work on psychological safety becomes so relevant. She describes psychological safety as a shared belief that a team is safe for interpersonal risk-taking. Google’s Project Aristotle research found that its most effective teams were ones where people felt able to ask questions, admit mistakes, and offer divergent views without fear of embarrassment or punishment. Psychological safety leaves plenty of room for accountability and firm decisions. What it protects is a person’s ability to raise a problem without being humiliated for doing so.</p><p>When people don’t believe they can challenge the plan, leadership loses access to information it can’t get anywhere else. The executive team knows the strategy and the technology team knows the platform, but the employee doing the work every day knows where customers get frustrated and what happens at 4:45 on a Friday when the clean process map meets the messy reality of the business. That’s the person who can flag a workflow problem before hundreds of people are trained on the wrong process, or an unrealistic timeline before your best people burn out. Concerns raised early usually cost far less to address than problems discovered after rollout. Dashboards and steering committees have value, but your earliest warning system is often the person asking the questions everyone else wishes he’d stop asking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-jq0mjW8TJkC6xE5yI6Luw.png" /></figure><p>So what do you do when the room goes quiet? The answer starts with how you respond to the people who are still willing to talk.</p><p>Ask What This Person Is Seeing<br>People resist because they’re afraid, because the change threatens their status or expertise, or because they haven’t yet built the skills the new way requires. Sometimes they’re working from incomplete information, and sometimes they’re simply wrong. Leaders still have to lead, and the goal is to stay curious about resistance long enough to understand what’s underneath it before deciding what to do.</p><p>The shift I encourage leaders to make is a small one. Instead of asking, “How do we get this person on board?” start with, “What is this person seeing that we aren’t?” Maybe the answer is nothing, and better communication will resolve the concern. Maybe they’ve spotted something important. You’ll only find out if your first instinct is to listen.</p><p>Listen For What’s Underneath<br>The words people use when they push back often point toward a different issue. Consider an employee who says, “This new AI tool is going to make everything harder.” That sounds like resistance to technology. Underneath it, the employee might mean they don’t understand how to use the tool, or that they’re already overwhelmed and this adds one more responsibility. They might have tested it on their own work and found the output unreliable. They might worry about being held responsible if they use it incorrectly, or they might be noticing that leadership measures adoption without ever explaining what successful use looks like.</p><p>Those are five different problems requiring five different responses. If you label all five people “resistant to AI,” you lose the ability to diagnose what’s actually happening. McKinsey’s 2025 guidance on change management for generative AI makes a similar point, recommending that organizations involve employees directly in identifying where AI fits into their workflows and use training to reduce anxiety and build confidence. Adoption problems tend to surface closest to the work, so that’s where leaders need to look.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2YYH_wYUJ0KGti_I-lJoYA.png" /></figure><p>The same pattern shows up in restructuring. An employee who says the new structure doesn’t make sense may be protecting territory, or may understand a customer dependency that never made it onto the new org chart. A leader’s job is to diagnose before dismissing.</p><h3>Build Pushback Into The Process</h3><p>“My door is always open” is an invitation, and invitations put the burden on employees. They have to decide whether the issue matters enough, whether leadership really wants to hear it, and whether raising it could hurt them. The CIPD’s <a href="https://www.cipd.org/globalassets/media/knowledge/knowledge-hub/reports/2025-pdfs/8868-good-work-index-2025-report-web1.pdf">2025 Good Work Index</a> found that only 37% of respondents said their managers allowed employees or their representatives to influence final decisions. Access to a channel means little when people can’t see a connection between speaking up and what happens next.</p><p>During significant change, leaders should go looking for uncomfortable information. That’s a central part of the Assess stage of the <a href="https://amplifiedconcepts.com/2024/11/01/resistance-as-an-opportunity-in-change-management/">PATH Framework</a>. After establishing what’s Present, meaning what already works and shouldn’t be disrupted unnecessarily, the organization needs to understand what’s actually happening across the business. That picture may differ considerably from what executives believe or what the implementation plan assumes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wTpSXotfzkC8bkChufSYOg.png" /></figure><p>Getting there means asking better questions. Ask where the change conflicts with how work really gets done, what would make someone hesitant to adopt it, and what people are worried about that nobody’s discussing. One of the most useful questions is this one: “If this fails six months from now, what do you think will have caused it?”</p><p>Asked that way, resistance becomes intelligence you’ve gone out to gather.</p><h3>Close The Loop</h3><p>People need to know their concerns will be considered, even though every concern won’t decide the outcome. Leaders often weigh financial, competitive, regulatory, and contractual factors that employees can’t see. Sometimes they’ll hear an objection, understand it completely, and still move forward. That’s leadership.</p><p>The difference lies in how they close the loop. “We heard you, but we’re doing it anyway” teaches people to stay quiet next time. “We heard you, here’s what we learned, here’s what we’re changing because of it, and here’s what we’re keeping and why” teaches them that telling the truth is worth it here. Over time, that consistency is how trust gets built.</p><p>One principle I use in my work is that <a href="https://amplifiedconcepts.com/resources/calculators-assessments/trust-assessment/">Trust = Alignment + Truth + Consistency.</a> During change, leaders naturally focus on alignment, making sure people understand where the organization is going, why it’s going there, and what their role will be. Alignment without truth, though, slides into compliance. Everyone repeats the right language, the dashboards turn green, and people quietly tell one another after the meeting that this isn’t going to work. Truth is what lets leadership tell real alignment from its appearance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*20Lh5-lpYvUzPzuWPgJILQ.png" /></figure><h3>Treat Employees As Customers Of Change</h3><p>Leadership sees what the organization needs to become, and employees often see what it will take to get there. A strategy can be completely right at the executive level and still struggle in implementation because of realities leaders couldn’t see from where they sit.</p><p>This idea comes straight out of my own career. I spent decades in marketing and consulting, helping leaders who understood their offering well come to understand their customers even better. When customers struggle with a new product, good marketers get curious. They investigate where people got stuck and what they’re doing instead, and they use what they learn to improve the product.</p><p>That’s why I believe employees should be treated as customers of change, and why organizational change deserves the same curiosity. When adoption stalls, the first question should sometimes be what needs to change about the change.</p><h3>Think About Your Last “Resistant” Employee</h3><p>Some of the people we’ve labeled resistant may be among the most invested in the organization’s success. They care enough to argue and to risk being seen as difficult. Once the label sticks, though, leaders start hearing every new concern as more proof of resistance, and eventually they stop listening. The employee notices. One day that person stops arguing, and leadership may experience it as progress when it’s actually surrender.</p><p>So I’ll ask you to try something I’ve found genuinely useful. Think about the last person in your organization who earned that label. Set the label aside for a moment and ask what they were actually saying, what they saw, and what happened after they raised it. Then ask the hardest question of all, which is what they were right about.</p><p>In many organizations, an honest look back would show that at least some of the people who created friction during change were pointing toward problems that later became obvious to everyone. By that point, those problems cost far more to fix.</p><p>I’ve come to believe that good change leadership builds an organization where people push back early enough for you to do something about it. So the next time a room goes quiet after a big announcement, I hope you’ll pause before you celebrate. The moment everyone stops challenging the plan may be the moment you’ve lost your early warning system, and that should worry you far more than resistance ever did.</p><h3>Oh, And One More Thing…</h3><p>If this conversation resonates, you’ll find more of it on my podcast, <a href="https://amplifiedconcepts.com/podcast/"><em>Navigate Change. Amplify Potential.</em></a> Each episode features real leaders sharing real stories about navigating change and unlocking people’s potential. They’re candid conversations with executives, entrepreneurs, and changemakers about leadership, AI, innovation, workplace culture, and the human side of transformation. The episodes are short enough for a break and worth every minute of your time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MYdwvH5JNfG_owen_r3WFA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89c4b82cda5a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Most Enthusiastic Change Champions May Be Carrying the Most Risk]]></title>
            <link>https://medium.com/@SherryHeyl/your-most-enthusiastic-change-champions-may-be-carrying-the-most-risk-8522f6fb1eb8?source=rss-a7113085f5ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/8522f6fb1eb8</guid>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Sherry Heyl]]></dc:creator>
            <pubDate>Sat, 03 Oct 2026 20:52:47 GMT</pubDate>
            <atom:updated>2026-10-03T20:52:47.735Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*59ypEdmfJfzneTlqfnThtg.png" /></figure><p>Every leader looks for them. They’re the team members who volunteer for the pilot, show up to the optional training, and start experimenting with the new AI tool before anyone asks. I know them well, because in past roles, I was one of them.</p><p>Leaders love them, and I understand why. Change is hard enough when people feel skeptical or overwhelmed, so finding someone who’s genuinely excited about what comes next feels like a gift.</p><p>What I’ve watched happen next follows a familiar pattern. We give them more. First they test the new system, then they help coworkers use it, then they join a feedback meeting, and eventually they’re championing the whole initiative. Before long, colleagues bring them every problem. They answer questions in Teams, build workarounds, report issues to leadership, and coax a frustrated coworker into giving the new process another try. And they’re still doing the job they had before any of this started.</p><p>From the outside, this may look like successful change management. Adoption climbs, problems get solved, and leadership points to these employees as proof that the change is working.</p><p>When I look closer, I often find something else. The change looks healthier than it really is because a few people are quietly absorbing its gaps. Their willingness covers capacity problems, their resourcefulness patches broken workflows, and their extra hours make unrealistic workloads look manageable. One of the most valuable people in the building has become the invisible infrastructure holding the change together.</p><p>That’s a burnout concern for them. For the business, it’s a cost that never shows up on the implementation budget.</p><h3>How AI Is Changing Change Management</h3><p>For years, change management centered on adoption. Leadership made a decision, and employees learned what to do differently.</p><p>AI has changed that. No executive team can map every way AI should fit into every workflow. The people closest to the work understand where time gets wasted, which tasks need judgment, and which processes exist only out of habit. So organizations are asking those employees to help shape the change itself by experimenting, finding use cases, redesigning their own workflows, and coaching skeptical colleagues.</p><p>I think that’s a healthy shift. The people doing the work deserve a real voice in how it evolves. What I often see missing is the support to match their efforts. The person who volunteers as an AI champion ends up acting as trainer, coach, troubleshooter, and informal change leader, usually without preparation for any of those roles and with the same quarterly goals they had before.</p><p>There’s a bigger shift underneath all of this, too. Change used to arrive one project at a time, with a launch date, a rollout, and a finish line. AI has made change continuous. New tools arrive while the last ones are still settling in, so champion work rolls straight into the next initiative, usually on the shoulders of the same people.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ieXNP8IcOT-ecxjoqKo04w.png" /></figure><h3>Where Willingness And Change Readiness Split Apart</h3><p>The distinction I find myself explaining most often is the one between wanting to help and being ready to help. Commitment to a change is one piece of change readiness. The organization’s real capacity to carry it out, given the workload, resources, and conditions people are working in, is another.</p><p>A raised hand tells me someone believes in the direction. It can’t tell me whether they have five free hours next week, whether their manager sees this as a priority, whether they have the authority to change the workflow, or what should come off their plate to make room.</p><p>Picture a finance analyst who volunteers for the AI pilot and learns quickly. Soon one colleague tells her the tool doesn’t fit their process, and another worries AI will eliminate part of their job. A third gave up after one bad result, while a fourth is enthusiastically pasting sensitive information into an insecure tool. Leadership is counting on her to raise adoption numbers, and each of these colleagues needs something different from her. Should she push, listen, coach, correct, or escalate? Nobody taught her how to tell the difference, and her accounting degree didn’t come with that training.</p><p>Then there’s time. A weekly champion meeting, testing the latest release, helping three coworkers, and documenting a use case each seem small, but together they add up to another job. Because she volunteered, she may hesitate to say she’s overwhelmed. So she squeezes the work between meetings, answers questions over lunch, and catches up on her “real” job at night. She keeps delivering, so leadership sees nothing wrong.</p><h3>The Champion Paradox</h3><p>When I came across a <a href="https://link.springer.com/article/10.1186/s43058-026-00959-2">2026 study</a> that named this pattern the champion paradox, it confirmed something I’d been watching for a long time. The researchers found that the same qualities that make champions so effective can leave an organization dependent on them, with knowledge concentrated in a few people and little pressure to build lasting systems. Their setting was early childhood education, but the pattern translates directly to the AI rollouts I see in business.</p><p>Here’s how it tends to play out. Sarah knows how to fix the AI workflow when it breaks, so fixing the workflow never becomes a priority. Marcus explains the new system better than the formal training does, so nobody notices the training falls short. Janelle builds a spreadsheet to bridge a gap between the new system and an old process, and within six months her workaround has quietly become the process. It works right up until Janelle takes another job.</p><p>This also shapes what leadership sees. The dashboard shows strong adoption and few escalations, and all of it may be accurate. What it can’t show is that five employees are spending four extra hours a week propping up everyone else. Leaders end up reading extraordinary individual effort as organizational capability, and they make investment decisions based on that reading.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L7hpSwat4nkNPeWLJz7lqw.png" /></figure><h3>What It’s Costing The Business</h3><p>When I walk executives through this, I start with simple math. Count the people acting as champions, estimate the extra hours each spends on champion work every week, and multiply by their loaded hourly cost and about 48 working weeks. Five champions giving four hours a week at $75 an hour comes to $72,000 a year in change labor that the implementation budget almost certainly doesn’t show.</p><p>That’s usually the smallest number in the conversation.</p><p>The bigger costs come from what those hours displace. The people who volunteer tend to be your strongest performers. When a top salesperson spends five hours a week supporting a rollout, those are selling hours, and when your best manager becomes the unofficial help desk, their own team gets less coaching. Every month that adoption depends on a handful of people is a month the full return on your investment waits.</p><p>AI makes the math even more interesting. Say an employee discovers AI can shrink an eight-hour task to three. On paper, the organization gained five hours. Then she becomes the AI champion, and those hours flow into working groups, prompt help, testing, troubleshooting, and documentation. The productivity gain in the business case has shifted into change management work that helps her colleagues adopt the tool, and that investment rarely shows up in anyone’s tracking.</p><p>However, that shift can pay off handsomely, since helping twenty colleagues become more productive could return far more than five hours. In my experience, it pays off when leaders treat champion work as an investment and manage it like one.</p><p>That starts with making the role official. Write the champion work into her job description and performance goals so her manager and her reviews recognize it as real work. Document what she’s learned, including the prompts that work, the questions people keep asking, and the fixes she’s built, and store it somewhere anyone on the team can find it. Then have leadership formally sanction the role with a named executive sponsor, a set number of hours each week, and clear authority over the decisions she’s expected to make. Once her work is formalized, documented, and sanctioned, the capability she’s building belongs to the organization, and it stays there if she moves on. Because change now comes in a steady stream, that documented knowledge also lets the organization pick up where it left off when the next AI capability arrives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SH1KLVH15wlnYfnBKzO3eQ.png" /></figure><p>When a critical workaround lives in one person’s head, their departure takes it with them. Gallup estimates that replacing an employee can cost between one-half and two times their annual salary, and that figure leaves out the implementation momentum that walks out the door with a burned-out champion.</p><h3>Building Change Capacity</h3><p>This is where I see the biggest difference between change management and change leadership. Change management tracks whether people adopted the new tool. Change leadership asks whether the organization has built the capacity to keep adapting without relying on a few heroes. With change now continuous, that capacity has to become institutional, so the habits that make a great champion effective, like surfacing problems early and sharing what works, become part of how the organization operates every day.</p><p>When I work with leadership teams, I start by finding out where champion work is actually happening and what it’s costing. My <a href="https://amplifiedconcepts.com/guiding-you-through-change/">PATH Framework</a> assesses readiness and willingness separately for exactly this reason, because a team can be eager and still under-resourced. I also treat <a href="https://amplifiedconcepts.com/2024/11/01/resistance-as-an-opportunity-in-change-management/">resistance as information</a> that often points straight to the capacity gaps. From there, we define what champions are there to do, where their responsibility ends, who removes barriers for them, and what comes off their plate. The goal is an organization where each change teaches it something it carries into the next one.</p><p>I also pay close attention to what gets rewarded. Imagine one employee says, “Absolutely, I’m excited, I’ll figure it out,” and another says, “I support this, but I’ll need some of my current responsibilities to shift so I can take it on.” Most managers want to hear that the change will be easy, so the first answer earns the champion role while the second gets labeled resistant. The champions I value most can say “I believe in this” and “Here’s what’s making it hard” in the same breath.</p><h3>The Questions I Ask Every Champion</h3><p>The first question to ask your change champion is:</p><p>“What would make this impossible for you to sustain six months from now?”</p><p>Then keep going. Ask which responsibilities would need to change, what decisions they’re expected to influence without the authority to make them, and what people hesitate to tell leadership because they don’t want to seem resistant. Ask what would stall if they took two weeks off. Ask what they’ve been asked to do as a champion that nobody ever taught them how to do.</p><p>Those answers tell me far more about change readiness than any survey measuring excitement, and they show exactly where the return on change is leaking.</p><p>So celebrate the people who raise their hands, because you need them. Then follow “Thank you for volunteering” with “What do you need from us to make this work?” and listen closely. Your most enthusiastic people may be carrying more risk than you realize, and they’re also carrying some of your best information about where the change is working. Support them well, and they’ll help you build an organization capable of carrying the next change, and the one after that, together.</p><p>If you try those questions with your own champions and the answers surprise you, the <a href="https://amplifiedconcepts.com/path-assessment/">PATH Assessment</a> offers a private way to reflect on where your organization stands, and you’ll find more tools in my <a href="https://amplifiedconcepts.com/resources/">change management resources</a>. I’m always glad to compare notes, too. And if you know a leader wrestling with this, <a href="https://amplifiedconcepts.com/refer/">I’d welcome an introduction</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*71csDYr3eNV-11pxKRs1lw.png" /></figure><p>Oh, and one more thing…</p><p>If you enjoy stories about how real leaders navigate change, check out my podcast, <a href="https://amplifiedconcepts.com/podcast/">Navigate Change. Amplify Potential.</a> Each episode features candid conversations with executives, entrepreneurs, and changemakers about leadership, AI, innovation, workplace culture, and the human side of transformation. The episodes are short enough to fit into a break and worth every minute.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8522f6fb1eb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s Time to Prepare for Extinction Events]]></title>
            <link>https://medium.com/@SherryHeyl/its-time-to-prepare-for-extinction-events-c283ba953d1c?source=rss-a7113085f5ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/c283ba953d1c</guid>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Sherry Heyl]]></dc:creator>
            <pubDate>Sat, 03 Oct 2026 20:26:33 GMT</pubDate>
            <atom:updated>2026-10-03T20:26:33.117Z</atom:updated>
            <content:encoded><![CDATA[<p>Everyone I know has a different answer to the question of whether AI will end humanity. I spent the past week asking, and the most common response was a shrug that translated roughly to, “Fine. Add it to the list.”</p><p>The bright side is if AI does end humanity, we’ll have very few problems left to worry about. Skills gaps, quarterly earnings, return-to-office debates, and performance reviews will all become moot. There will be no more bills to pay, no more votes to cast, no more next new thing to learn.</p><p>However, I’d rather spend my energy on the scenario where we stick around, but in that one, our influence over the direction we go depends on our participation. And how we participate depends on knowing what we want from this future we are building toward.</p><h3>The People Closest To AI Disagree About The Risk</h3><p>The disagreement among experts is real. In a 2023 survey of 2,778 AI researchers who had recently published at leading AI venues, the median respondent put at least a 5 percent probability on advanced AI eventually causing human extinction or similarly permanent and severe human disempowerment. Depending on how the question was framed, one version produced a median estimate of 10 percent. Those medians are opinions about an uncertain future, and a 5 percent chance of anything that consequential deserves attention.</p><p>The conversation picked up again on September 8, when Jacob Coxon, a researcher who had spent three years working at both OpenAI and Anthropic, announced on X that he was resigning from Anthropic. He wrote that the people building AI sincerely believe it could kill us all by the end of the decade, and that neither company is acting responsibly while racing toward self-improving superintelligence and “gambling with our lives.” Within hours, Evan Hubinger, who leads a group at Anthropic focused on making sure AI does what its creators intend, replied that he personally puts the odds above 10 percent within the next decade. The coverage that followed has been enormous, with some people treating it as a warning and others questioning the motives behind it.</p><p>Some of the people who have spent their careers building and studying these systems believe that losing control of increasingly capable AI deserves serious attention. Others believe the extinction scenarios rest on a chain of assumptions about capabilities we don’t have and may never develop.</p><p>I spent several hours this week listening to both sides. If you’d like to see how wide the gap is, I recommend <a href="https://www.youtube.com/watch?v=OhOmLqR5nN4">this debate on The Diary of a CEO</a>, where Roman Yampolskiy and Nate Soares make the case for existential risk while Andrew McAfee and Ed Zitron push back hard. It’s long and occasionally contentious, but it’s worth the time. <a href="https://youtu.be/cPgwnUr1sbE?si=x_uZqeMR4X3a0BmE">This shorter explanation of AI misalignment</a> is also worth a watch.</p><p>You don’t have to believe AI will kill us to see why misalignment matters. At its simplest, the problem looks like this:</p><blockquote><em>What we tell a system to optimize for may produce something other than what we intended.</em></blockquote><p>The classic illustration is the paper clip problem, a thought experiment popularized by philosopher Nick Bostrom. Imagine an AI given one goal, to make as many paper clips as possible. It pursues that goal so effectively that it starts converting everything it can reach, including the resources people need to live, into paper clips. Nobody wanted that outcome, but the system did exactly what it was told.</p><p>We’re already seeing versions of this. In April, a Melbourne man asked his AI agent to get him into a popular gym class that was hard to book. When he was still fourth on the waitlist, the agent found that the gym’s booking system never checked who was allowed to cancel a reservation, so it cancelled another member’s spot to move him up. It couldn’t undo the change afterward. In July, OpenAI disclosed that two of its models, running a cybersecurity test with safeguards deliberately dialed back, broke out of their locked-down environment and hacked into Hugging Face, which held the answer key to that test. One Cambridge researcher told Fortune the models never left their assignment and simply found an aggressive route to finish it. Earlier this year, both Anthropic and OpenAI disclosed models getting around sandbox restrictions in their own tests. Each example is a small version of the paper clip problem, and together they help explain why the alarm is going off.</p><p>Alignment starts on the human side of that problem. It looks like builders, buyers, and regulators saying out loud what a system should achieve, testing whether it does, and keeping people in a position to correct it when it drifts. That work belongs to more people than the researchers, because everyone who deploys AI is also deciding what it optimizes for.</p><h3>Apparently, We’re Not That Worried</h3><p>I also spent part of the week talking to really smart people I know about whether they’re actually worried that AI could cause human extinction, and so far nobody seems particularly concerned.</p><p>I heard several explanations. Some people think the warnings are at least partly strategic, since slowing things down might benefit AI companies while the economics, competition, and eventual public-market opportunities sort themselves out. Others pointed to earlier technological revolutions and the catastrophic predictions that came with them. Electricity was dangerous. Nuclear technology gave humanity the very real ability to destroy itself. We learned to live with both the benefits and the risks.</p><p>Then one conversation took an unexpected turn. I was reminded of the Carrington Event of 1859, when a massive solar storm generated electrical currents powerful enough to disrupt telegraph systems, shock operators, and start small fires. Imagine something comparable hitting a world that depends on satellites, power grids, GPS, and the internet. Add asteroids, pandemics, and climate risk, and I would say artificial intelligence needs to stand in line if it wants to destroy us.</p><p>It occurred to me that everyone alive today has spent their whole life knowing humanity could go extinct. Maybe we’ve grown numb to existential risk. We make coffee, take the kids to school, answer email, sit through meetings, argue about politics, and plan vacations while the knowledge that a nuclear war, pandemic, asteroid, or solar event could radically alter life on this planet hums along in the background. When someone announces that AI might kill everyone, our collective response seems to be Fine. Add it to the list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AYKT26vDDI7KAq07KZS7IA.png" /></figure><p>It’s not that we shouldn’t take the concern seriously. Misalignment is worth understanding, and AI safety deserves serious investment, along with cybersecurity, safeguards against misuse, environmental impact, appropriate oversight, and hard questions about how much autonomy increasingly capable systems should have. We should also think carefully about what happens if we get this catastrophically wrong.</p><p>But when I really think through it all, I think AI is going to cause quite a few extinction events, and some of them may be overdue.</p><h3>Will Jobs Go Extinct?</h3><p>This is where most conversations about AI and work begin, with the question of how many jobs AI will eliminate. Some will disappear, and I expect new ones to appear, because I expect we’ll keep finding problems worth solving.</p><p>The labor-market forecasts tell a more complicated story than “AI takes all the jobs.” The World Economic Forum’s Future of Jobs Report 2025 projects that the forces reshaping work, including technological change, demographic shifts, economic uncertainty, and the green transition, could create 170 million jobs globally by 2030 while displacing 92 million. That’s a net increase of 78 million jobs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I6BRv0scP6QCFLjSBKI4mw.png" /></figure><p>That number will feel hollow to some people. If yours is one of the 92 million jobs disappearing, hearing that another job was created somewhere else doesn’t help much. The real challenge is transition.</p><p>Thirty years ago, video rental clerks, one-hour photo technicians, typists, toll booth collectors, and travel agents held jobs that I would guess they thought were steady. Streaming, digital cameras, electronic tolling, and online booking have since taken over much of that work, and I doubt many of the people in those roles saw it coming.</p><p>Very few jobs disappear overnight. Technology usually shrinks a role, restructures it, or absorbs its tasks into someone else’s job. New work tends to fill the gap, often under job titles nobody has heard of yet. When I was in college, no one was talking about a career as an app developer, UX designer, data scientist, podcast producer, or social media manager.</p><p>Sandy Hofmann, whose story appears in my book <a href="https://amplifiedconcepts.com/learn-to-love-the-roller-coaster/">Learn to Love the Roller Coaster: Stories of Change, Resilience, and the Future to Come</a>, lived this. Early in her career, as computers began entering the workplace, she watched how people reacted the first time they used them. She noticed that new systems created new roles for people who could translate and humanize change, and she found herself doing information development, which meant helping people who weren’t engineers succeed with the technology. “I never would have aspired to be a technical writer,” she told me. “That job didn’t exist. The need created it.” That work opened the way for her to executive leadership at a technology company.</p><p>The economy doesn’t run out of problems to solve. It creates different ones.</p><p>What concerns me more is whether we’re preparing people to solve those problems. That raises a question I’d like to see in the jobs debate: which problems do we want people to spend their working lives solving?</p><p>Alignment here looks like employers, schools, and communities agreeing on which problems are worth solving and then investing in the people who will solve them. That includes retraining that begins <em>before</em> a layoff, roles redesigned around outcomes, and transitions that treat displaced workers as the talent the next problem needs.</p><h3>Maybe Education Needs An Extinction Event</h3><p>Employers surveyed by the World Economic Forum expect 39 percent of workers’ core skills to change by 2030. They expect AI and big data, cybersecurity, and technological literacy to grow in importance, along with creative thinking, resilience, flexibility, curiosity, lifelong learning, leadership, and analytical thinking.</p><p>That creates a contradiction. We’re entering an economy in which people may need to keep reinventing what they know and how they contribute, and much of our education system is still organized around an assumption that made more sense in a slower-moving economy. You learn first and work second. You go to school, choose a career, earn a degree, find an employer, attend the occasional training, and hope what you learned stays relevant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zwlrp2tVGzP-eT5Mm--7tg.png" /></figure><p>That’s an alignment problem. We built a system optimized to produce graduates, and it measures success by what a student can recall and reproduce on the day of the exam. That model made sense when information was scarce and access to it conferred power. AI puts the world’s information at our fingertips, so the skills that matter most now sit in curiosity and judgment, along with the willingness to keep learning long after graduation. We increasingly need a system designed to produce lifelong learners.</p><p>In my book, I wrote, “The best educators were never information delivery systems. They were guides, mentors, and translators of curiosity.” A system built for lifelong learning would put more weight on that kind of teaching, and it would care far more about how a person thinks than about the degrees and certifications they hold. I’m starting to wonder whether we still need those credentials at all, since they tell an employer where someone has been and reveal very little about what that person aligns with or how they judge. Such a system would also make it easy for people to return to learning at 35, 50, or 65 without starting over. Skills are changing quickly enough that a career spanning several decades will include multiple reinventions, and each one should build on the judgment and experience a person has already developed.</p><p>Alignment in education looks like schools, employers, and learners agreeing that the destination is a person who can think, judge, and keep growing. Assessments would show how students reason, employers would help shape what gets taught, and returning to school at 50 would feel as ordinary as starting at 18.</p><h3>Secrets Are Getting Harder To Keep</h3><p>Another advantage AI will steadily erode is knowing something your competitors don’t. Expertise is getting dramatically easier to access, methodologies can be replicated, information can be synthesized, and best practices can be discovered. Capabilities that once required an expensive team can increasingly be reached by a small company, and sometimes by one person.</p><p>Companies won’t all become the same as a result. Differentiation moves to a new place. The question shifts from what do we know that you don’t? to what is it like to work with us? Experience, trust, judgment, relationships, reputation, taste, and how you make people feel start to matter more, as does whether customers believe you understand them and whether employees believe their contribution matters.</p><p>Organizations built around holding information tight will feel this first. In my book, I wrote that institutions operating from a poverty mindset “hoard control and resist redesign.”</p><p>Companies that built their advantage on being the only ones who knew how something worked have the most to lose, because that knowledge now sits a few keystrokes away from anyone with curiosity. Their instinct is often to guard it more tightly, add approval layers, and treat every new tool as a threat to defend against. The poverty mindset says opportunity is scarce, so every gain looks like someone else’s loss and the goal becomes preservation. A creator mindset asks how to apply what you know better than anyone else can, which is why those organizations with a creator mindset share knowledge freely and put their energy into the work that only their people can do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ReE3-zyuTN8iuW97WmAt5A.png" /></figure><p>As AI makes knowledge easier to replicate, human experience stays much harder to commoditize. As artificial becomes abundant, authentic may become more valuable. The destination question here is what we want it to feel like to work with us.</p><p>Alignment here looks like a company deciding what it wants people to feel when they work with them and then building the habits, incentives, and daily interactions to deliver that experience. Customers notice when a company’s words match its behavior, and so do the people who work there.</p><h3>Why Should Talented People Work For You?</h3><p>This one may make some employers uncomfortable. For generations, working for a company gave people access to things that were hard to get independently, including capital, technology, infrastructure, distribution, customers, colleagues, and expertise. Those barriers have been falling for decades. The internet, cloud computing, and the gig economy lowered them and made freelancing more possible, and AI is lowering them again. One person can increasingly do what recently required a team, and a small company can reach capabilities that once belonged almost exclusively to large organizations.</p><p>Companies will keep existing, but they’ll need to answer a question they haven’t always had to answer well: why should someone talented choose to work for you?</p><p>The answer has to go beyond a paycheck. What can people accomplish here that they couldn’t accomplish independently? What can they learn, who can they become, what relationships can they build, and what problems can they solve? The old employment bargain rested partly on the assumption that employees needed access to the organization. Increasingly, organizations have to show why talented people should choose access to them. Answering well requires an employer to know who it wants to be.</p><p>Alignment shows up when an employer’s purpose, growth paths, and everyday work point the same way as what its best people want to build. Talented people notice quickly whether a mission statement matches daily practice, and they choose the places where it does.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mfDy7JqVkZYywBhI_2hMrA.png" /></figure><h3>Influence Starts With Knowing Where We’re Headed</h3><p>Here’s where my thinking has landed so far. AI will make plenty of things extinct whether we’re ready or not, and what we can still shape is what grows in their place. That requires a destination.</p><p>Technology also tends to make existing problems bigger. Automate an outdated workflow and you get outdated work faster. Optimize people for output when you need outcomes and you get more output. Eliminate junior employees because AI can perform their tasks, and five years later you may find you’ve also eliminated the place where senior employees learn to become senior. Give employees tools that save five hours a week and immediately fill those hours with more work, and you may have misunderstood the opportunity entirely. The AI worked in each case, but the thinking behind it needed work.</p><p>That’s the lesson I keep taking from the alignment debate. The AI safety community is asking how we make sure increasingly powerful systems stay aligned with what humans want, and that question has a prerequisite: humans have to know what they want. In the book, I put the business version this way: “A system is aligned when doing the ‘right thing’ for people is also the most rational thing for the organization operating it.” Companies that haven’t decided who they want to be end up steering by whatever is easiest to measure, such as hours logged, emails sent, or reports produced, and those numbers quietly become the goal. Schools that haven’t decided what a learner should become optimize for graduates. People who haven’t decided where they’re headed follow whichever current is strongest.</p><p>Another line from the book keeps coming back to me. It describes asking “whether the direction you’re headed is one you chose, or one that momentum quietly chose for you.” That question applies to individuals, and I think it applies just as much to organizations. The leaders, companies, and people who will have influence over where this goes are the ones who can say who they want to be and where they want to go, and who then use AI to get there.</p><p>Here’s what that looks like in practice. A leader writes down who the organization wants to be in five years, picks a few outcomes that would prove it, and checks each AI decision against them. An individual can do the same with a career by deciding what they want to be known for and letting that guide what they learn and where they say yes.</p><h3>Deciding What Goes And What Stays</h3><p>There are things AI threatens that we should protect, including human agency, human judgment, security, privacy, opportunity, our environment, and humanity itself.</p><p>There are also things AI threatens that we may not need to fight so hard to preserve, such as outdated processes, education designed for a different economy, jobs defined by output when the outcome is what matters, corporate cultures built around information hoarding, employment relationships based on dependence, and definitions of productivity inherited from the industrial age.</p><p>We love the word transformation because it sounds like becoming something new, but becoming something new means ceasing to be something old. Transformation asks us to release some of what we’ve been.</p><p>Alignment makes those choices easier. It looks like keeping one short list of what we protect and another of what we release, revisiting both as the technology changes, and letting the protect list set the limits on what AI is allowed to change.</p><p>So I’m leaving these questions where I’m still working through them myself. Which extinctions are overdue? Who do I want to be on the other side of them? Where do I want to go?</p><p>But remember, you cannot have transformation without some extinction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t64Gntj7zbK9yfQVQtoiCA.png" /></figure><p><em>Oh, And One More Thing…</em></p><p>I’ve made it easier to refer people to me. If something in this article sounds like a conversation someone you know is having, I built a page at <a href="http://amplifiedconcepts.com/refer">amplifiedconcepts.com/refer</a> that lists what leaders tend to say when change gets hard, such as “We invested in AI, but we are not seeing the ROI” and “Half the team is excited about AI and half the team is terrified of it.”</p><p>When you know someone who fits, the “Make the introduction” button opens an email with a note already started and me copied in. You add their email address, finish the note, and hit send.</p><p>Resources</p><p>Understanding the AI extinction debate</p><p><a href="https://youtu.be/OhOmLqR5nN4?si=4_tvBMMpKyZBnhuP">The Diary of a CEO debate with Roman Yampolskiy, Nate Soares, Andrew McAfee, and Ed Zitron</a></p><p>Understanding misalignment</p><p><a href="https://youtu.be/cPgwnUr1sbE?si=UZVrzgUdD2naYAD1">AI misalignment explainer</a></p><p>AI researcher attitudes toward existential risk</p><p><a href="https://wiki.aiimpacts.org/ai_timelines/predictions_of_human-level_ai_timelines/ai_timeline_surveys/2023_expert_survey_on_progress_in_ai">2023 Expert Survey on Progress in AI (AI Impacts)</a></p><p>The survey included 2,778 AI researchers who had recently published at six leading AI venues. Across several question variants, median estimates placed at least a 5 percent probability on advanced AI causing human extinction or similarly severe and permanent disempowerment.</p><p>Jobs and skills</p><p><a href="https://www.weforum.org/publications/the-future-of-jobs-report-2025/">World Economic Forum, Future of Jobs Report 2025</a></p><p>The report projects 170 million jobs created and 92 million displaced globally by 2030 as several macrotrends reshape employment, for a net increase of 78 million. Employers surveyed also expect 39 percent of workers’ core skills to change by 2030.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c283ba953d1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Blind Spot Every Leadership Team Shares]]></title>
            <link>https://medium.com/@SherryHeyl/the-blind-spot-every-leadership-team-shares-e9066a4d4a8f?source=rss-a7113085f5ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9066a4d4a8f</guid>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[change-leadership]]></category>
            <dc:creator><![CDATA[Sherry Heyl]]></dc:creator>
            <pubDate>Mon, 21 Sep 2026 19:05:56 GMT</pubDate>
            <atom:updated>2026-09-21T19:05:56.819Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hYLFzHFnKR7VkwYKk2J-7w.png" /></figure><p>I spent decades helping leaders who understood their offering and their business inside and out realize they needed to understand their customer even better. The same principle holds true inside the business. Leaders can describe their strategy and direction in detail. Far fewer can tell you, with the same confidence, how their own people actually feel and think about it. That gap is where most change initiatives quietly go to die, and it’s the subject of this week’s piece.</p><p>You’ve probably heard some version of this while navigating a change of your own.</p><p>“I don’t know whose idea it was to change this, but the other way worked better.”</p><p>“We can’t implement that. It’s going to mess up the dependencies down the line.”</p><p>“If we’re going to change that, then I want to be able to do this too.”</p><p>“Wait. Who owns this now?”</p><p>“That sounds good in theory, but that’s not how it actually works.”</p><p>“Has anyone talked to Finance about this?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3vnfnH0tBUVlet32-OLcVA.png" /></figure><p>This is what change sounds like from inside an organization. To the executive responsible for moving things forward, it can sound like resistance, obstacles, frustration, political games, conflict. But buried inside the pushback and the concerns are real emotions, real insights, and real opportunity.</p><p>The hard part is figuring out which is which.</p><h3>When Friction Becomes Infrastructure</h3><p>Organizations aren’t designed once and then operated exactly as intended. They evolve. A process breaks, so someone builds a workaround. A manager is difficult, so people learn how to approach him. A department doesn’t deliver reliably, so another team adds an extra step to compensate. One employee becomes the person everyone calls when something goes wrong. Two executives don’t work well together, so their teams learn how to route around the tension. A mistake happens, so another layer of approval gets added on top of the last one.</p><p>Some of these adaptations are smart. Some are inefficient. Some are political. Some would look completely irrational to anyone who didn’t know the history behind them. But eventually people stop noticing them as the workaround stops being experienced as a workaround. It becomes simply how things get done here.</p><p>This is what Present, the first stage of my <a href="https://amplifiedconcepts.com/path-assessment/">PATH™ Framework</a> for leading change, is really asking leaders to see:</p><ul><li>Understanding current conditions as they actually are, not as the org chart says they should be</li><li>Naming what isn’t changing, so people feel grounded</li><li>Mapping the informal workarounds and accommodations already holding the organization together</li></ul><p>Most organizations skip this step, and it’s not hard to see why. Naming what’s actually happening on the ground means naming the emotions underneath it, and business culture still treats emotion as taboo. There’s a real fear driving people to avoid confronting it in the first place. Leaders worry that stopping to engage with the friction will:</p><ul><li>Slow the business down</li><li>Cost money</li><li>Give people an opening to disengage or walk away</li></ul><p>So they move straight to designing the future state instead, without ever mapping the accommodations holding the current one together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mO0uqHKbnCrbw3bu87Odzg.png" /></figure><h3>Change Doesn’t Create the Friction. It Exposes It.</h3><p>When a change initiative is announced, such as a restructuring that changes reporting relationships, AI eliminating part of a workflow, an acquisition bringing two teams together, a new leader questioning an old process, or growth requiring decisions to happen faster than they used to, the accommodations that made the old organization function suddenly don’t fit anymore. That’s when you start hearing the concerns, pushback, and demands.</p><p>Change doesn’t create most of the friction we associate with transformation. It exposes friction the organization had already learned to live with. That distinction matters, because it changes how executives should interpret what happens next. The comments in that meeting aren’t a referendum on whether people support the initiative. They’re a map of everything the organization quietly built to survive its own dysfunction.</p><p>Research on change readiness increasingly pushes back on the idea that resistance is one thing with one cause. Employee participation has been linked to stronger commitment and better change outcomes, while current change-management practice calls for diagnosing the specific barrier underneath an objection, whether that’s a capability gap, a trust issue, a workflow dependency, or a policy nobody has revisited in years, rather than treating every pushback as an attitude problem. That doesn’t mean every concern is valid. It means not every concern is just fear either.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tp_mTP1fbF4eRE-OUqgGcA.png" /></figure><h3>The Friction Feels Personal Because It Is Personal</h3><p>Organizations experience change structurally. People experience it personally. The company sees a workflow redesign. Someone sees three years of work being set aside. Leadership sees greater efficiency. Someone wonders what their new task or responsibilities will be. The organization sees a reporting change. Someone loses access to the leader who helped her get things done. Leadership sees democratized access to information through AI. Someone sees the expertise that made him indispensable becoming available to everyone.</p><p>This isn’t irrationality. It’s how people assess risk under uncertainty. Change research consistently points to uncertainty, trust, perceived threats to job security, and the anticipated loss of status, autonomy, or competence as common sources of friction. The work looks structural from the executive suite, but the consequences get interpreted through each person’s role, relationships, credibility, and future.</p><p>You can’t understand organizational friction without understanding the human experience underneath it. Once something feels personal, perspective narrows. People start looking at the change through what they stand to gain, lose, protect, or control, and that’s true at every level of the org chart.</p><p>It’s tempting to assume employees have personal stakes while executives have the business perspective. But executives championed the strategy. They selected the technology. They hired the leader now driving the change. They promised the board an outcome. They built some of the very processes now being questioned. They have relationships, loyalties, and assumptions running through the organization too. Everyone in the room has a stake in what changes and what stays the same. That’s why simply gathering people and asking for honest feedback doesn’t automatically produce an accurate picture of what’s happening. The CEO can’t unknow that she wants the initiative to succeed. One employee can’t shake the feeling that he’s being replaced. Another doesn’t know how she’ll fit in with the new team.</p><h3>The Missing Layer</h3><p>This is where a credible listening structure becomes necessary rather than optional. It might be an external facilitator, an internal person with genuine independence, confidential interviews, or small-group sessions employees actually trust. The design matters less than the condition it creates. People need to be able to name risks, confusion, workarounds, and distrust without being immediately reassured, corrected, or labeled resistant. There needs to be somewhere an employee can say, “This makes no sense,” or “I don’t trust what’s happening,” or “Nobody understands what my team actually does,” and receive nothing but curiosity in return. Not reassurance. Not correction. Not an explanation of why leadership made the decision. Just, “Tell me more.”</p><p>Listening isn’t agreeing, and being heard isn’t the same as getting your way. But concerns, complaints, half-formed ideas, and even office gossip carry real information about how the organization actually functions. The work is separating the signal from the emotion around it, which is exactly what it looks like to listen for the conditions affecting change instead of starting from an assumption about why people aren’t changing fast enough.</p><p>An outsider can be an especially effective design for that structure, though not the only one. It’s not that an outsider understands the company better than the people inside it. The value runs the opposite direction: an outsider hasn’t learned what to ignore yet. Someone says, “We have to send it to Bob first.” Why? Everyone else already knows you send it to Bob. The outsider doesn’t. “We can’t change that. That’s just how our customers expect it.” Do we actually know that, or did we stop asking years ago? “Finance would never approve it.” Has anyone asked recently?</p><p>Questions that sound almost naive can expose assumptions nobody has examined in years. Insiders bring the context. Outsiders bring the contrast. An organization needs both. The employee knows things the outsider could never know. The outsider notices things the employee stopped noticing were unusual a long time ago.</p><h3>Creativity Is an Underrated Change Leadership Skill</h3><p>Once friction becomes visible, organizations tend to frame the problem as a choice. Keep this or eliminate it. Centralize or decentralize. Automate it or leave it alone. Their department owns it or ours does. Keep my job the same or eliminate my job. But transformation should expand what’s possible, not force a choice between two options that already existed before the change started.</p><p>Go back to that comment from the opening: “If we’re going to change that, then I want to be able to do this too.” That could be scope creep. It could also be imagination. The change disrupted an old assumption, and now someone can see a possibility that wasn’t available before. This is the question worth asking in almost any transformation: what’s possible now that wasn’t possible before?</p><p>That question is where PATH’s Assess stage does its work, recognizing the patterns already in motion rather than jumping straight to a fix. A neutral facilitator asking that question can push further. Is there a third option here? What are we actually trying to accomplish? What assumption are both sides making without realizing it? What would become possible if this constraint disappeared? What could this person’s expertise be used for instead of what it’s being used for now? Creativity turns friction from something to overcome into something to build with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LxsXZyKWF08gJ1vToxBifg.png" /></figure><h3>The Question Executives Should Be Asking</h3><p>When leaders encounter resistance during change, the instinctive question is usually some version of how do we get people on board. A better question is what is this friction revealing. Is it revealing a dependency nobody mapped? An old conflict that never resolved? A broken process everyone routes around? A legitimate risk? A loss of trust? A threat to someone’s identity? An outdated assumption? An organizational workaround built for a problem that no longer exists? Or a better idea than the one currently on the table?</p><p>You don’t know until you investigate it, and that investigation is the work many transformation efforts skip.</p><p>The point isn’t that leaders should hand every decision to consensus. It’s that they need an early, repeatable way to test assumptions with the people closest to the work, through workflow reviews, pilots, and listening sessions that visibly inform what happens next. Early engagement and two-way communication are consistently linked to stronger ownership and to catching barriers before they turn into implementation failures.</p><h3>Don’t Waste the Disruption</h3><p>Change is expensive, and organizations are already carrying more of it than they used to. McKinsey reports the average employee now moves through roughly ten planned change programs a year, up sharply from a decade ago, and Prosci’s ongoing benchmarking research has found that roughly three-quarters of organizations are operating near, at, or beyond their capacity to absorb more of it. In that environment, a skeptical comment in a meeting is rarely about one decision in isolation. It often carries the weight of every change people were already asked to absorb before this one arrived.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xJTWeD2ZQCsJy39JKwbV2A.png" /></figure><p>Change consumes attention, creates uncertainty, and forces people to reconsider things they’d otherwise leave alone. Don’t waste that disruption by rushing everything back to comfortable as fast as possible.</p><p>When people start saying we can’t do that, that’s not how it works, nobody asked us, or if we’re changing that then why can’t we change this, pay attention. Something that had become invisible may be becoming visible again. Some of it will be noise. Some will be fear. Some will be politics. Some will be legitimate constraints leadership genuinely needs to understand. And some of it may be the beginning of a much better idea than the one that started the meeting.</p><p>Change shakes loose whatever an organization had quietly learned to call normal. A good change leader helps that organization see what falls out, listen to what it’s actually telling them, and imagine what could take its place.</p><p>If your organization is in the middle of change and you’re not sure whether what you’re hearing is resistance or information, let’s talk. I help leaders build the listening structures that tell the difference before the transformation stalls.</p><p>Oh, and one more thing… If you’re new here, subscribe so the next one lands in your inbox instead of floating around out there in the algorithm somewhere. And if you’re already a subscriber and this one resonated, forward it to someone who’s knee-deep in a change right now. They’ll probably recognize themselves in it, and they’ll thank you for the insight.</p><p>Sources</p><p>- McKinsey Quarterly, [“Change is changing: How to meet the challenge of radical reinvention”](<a href="https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/change-is-changing-how-to-meet-the-challenge-of-radical-reinvention">https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/change-is-changing-how-to-meet-the-challenge-of-radical-reinvention</a>)</p><p>- Prosci, [Change Saturation](<a href="https://www.prosci.com/change-saturation">https://www.prosci.com/change-saturation</a>) (Best Practices in Change Management benchmarking research)</p><p>- Gartner, [“Gartner HR Research Finds Just 32% of Business Leaders Report Achieving Healthy Change Adoption by Employees”](<a href="https://www.gartner.com/en/newsroom/press-releases/2025-07-08-gartner-hr-research-finds-just-32-percent-of-business-leaders-report-achieving-healthy-change-adoption-by-employees">https://www.gartner.com/en/newsroom/press-releases/2025-07-08-gartner-hr-research-finds-just-32-percent-of-business-leaders-report-achieving-healthy-change-adoption-by-employees</a>)</p><p>- Prosci, [“Reinforcement and Sustaining Change Management”](<a href="https://www.prosci.com/blog/reinforce-and-sustain-change">https://www.prosci.com/blog/reinforce-and-sustain-change</a>)</p><p>- Sahay, S. &amp; Goldthwaite, C., [“Participatory Practices During Organizational Change: Rethinking Participation and Resistance”](<a href="https://journals.sagepub.com/doi/10.1177/08933189231187883">https://journals.sagepub.com/doi/10.1177/08933189231187883</a>), Journal of Change Management</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9066a4d4a8f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Where Did the AI ROI Go?]]></title>
            <link>https://medium.com/@SherryHeyl/where-did-the-ai-roi-go-b02e6b5114d5?source=rss-a7113085f5ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/b02e6b5114d5</guid>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[change-leadership]]></category>
            <dc:creator><![CDATA[Sherry Heyl]]></dc:creator>
            <pubDate>Sat, 19 Sep 2026 18:44:40 GMT</pubDate>
            <atom:updated>2026-09-19T18:44:40.076Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hlKf2T-3Ke7qsq0LjIGqmw.png" /></figure><p><em>Turning new AI capabilities into real business value is where the actual work begins now.</em></p><p>I was recently challenged with the question: if people are already adopting AI, what does change leadership actually add?</p><p>The numbers support the challenge. AI use has become widespread. McKinsey’s latest global survey found that 88% of organizations report regular AI use in at least one business function. Deloitte found that two-thirds of organizations, 66%, report productivity and efficiency gains from AI.</p><p>Change leadership is judged by the goals an organization actually reaches. Adoption is just one step along the way. If adoption is climbing and productivity is rising, why are so few companies seeing real financial results? BCG’s most recent research found that only 5% of companies are generating measurable AI value at scale, while 60% report no material value at all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yaLhbksBBR2ZE_kCQmy5GA.png" /></figure><p>That gap tells me we’ve been measuring the wrong finish line.</p><p>Adoption tells us people are using AI. ROI tells us whether the organization became more valuable because they did. Efficiency created and value captured are two very different outcomes, and most organizations are only tracking the first one.</p><p>If AI is being used and employees are becoming more productive, where is the value actually going?</p><h3>AI Creates Capacity. Capturing It Is a Separate Job.</h3><p>Picture someone who used to spend eight hours producing a report. AI now helps them finish it in three. Five hours just opened up.</p><p>Those five hours are potential value. They aren’t ROI yet.</p><p>Without a goal already in place for that time, what fills the time saved? Do those five hours go toward customers? Innovation? Better decisions? New revenue? Building new capability? Or does another meeting simply appear on the calendar to fill the space?</p><p>BCG found that 42% of regular frontline AI users save at least eight hours a week, essentially an entire workday. And yet, 66% of those employees say they get little or no guidance on where that time should go.</p><p>The capacity is real. What organizations do with it is still an open question.</p><p>Where is that day going?</p><h3>We Never Decided What Value AI Was Supposed to Create</h3><p>Most organizations start with the wrong question: How can we use AI?</p><p>A better starting point asks three things instead. What are we trying to achieve? What’s possible today that wasn’t possible before? What does our organization need to become capable of next?</p><p>AI has to connect to a business outcome the organization can actually name: revenue, margin, productivity, or innovation.</p><p>Efficiency is a given at this point. Every competitor can chase the same cost savings, which turns pure cost-cutting into a race to the bottom. The real question is what return the AI investment actually produces beyond the efficiency it delivers.</p><p>Here’s a diagnostic question worth asking before you look at any usage dashboard. What measurable business outcome was this AI investment supposed to change? If your executive team can’t answer that quickly, you already have a value leak.</p><h3>We Skipped the Baseline</h3><p>Before deciding what to implement, the better process starts by listening across the organization, identifying key workflows, and understanding their current state before deciding where AI could free up capacity.</p><p>That groundwork matters because “AI made us faster” isn’t a measurement. Faster than what? By how much? At what cost? Producing what, and at what level of quality?</p><p>The real measurement chain runs like this: baseline, AI intervention, efficiency created, capacity created, capacity redirected, business result. Skip the baseline and every step after it becomes a guess.</p><h3>We Made Today’s Work Faster Instead of Questioning Tomorrow’s Work</h3><p>There’s a bigger question hiding behind most AI rollouts. What’s possible now that wasn’t possible before?</p><p>Most organizations only ask how AI can make an existing process faster. Few ask whether that process would even exist in its current form if they were designing the work today, knowing what AI can do.</p><p>Deloitte found that only 30% of organizations are redesigning key processes around AI, while another 37% are using AI with little or no process change at all. McKinsey found something even more telling. Out of 25 organizational attributes it tested, workflow redesign had the strongest relationship with EBIT impact of any factor measured.</p><p>That’s a real opportunity most companies are leaving on the table. The biggest ROI often doesn’t live inside the existing workflow. It lives in realizing the existing workflow doesn’t need to exist at all.</p><h3>We Trained People on AI Without Building the Conditions to Use It</h3><p>I’ve spoken with a number of leaders whose teams already have AI training in place. They describe their people as stuck. People know the tools but struggle to find time to apply what they’ve learned, and many still need significant hand-holding to actually use AI in their day-to-day roles.</p><p>Having access to a tool, using that tool, building real skill with it, and creating measurable value from it are four separate milestones. Getting through one doesn’t guarantee the next.</p><p>That’s exactly the kind of friction leaders need to look for. The training exists. Leadership supports the initiative. Employees have access. And something is still standing between the training and changed behavior.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q90PdQMBgBEUHRe5WTZmxA.png" /></figure><p>Their stories reminded me of my own experience early in my recruiting career, when a new database was introduced. At first it felt like extra work, because I was maintaining my old system while also learning the new one. My habits changed the moment I saw coworkers using the database to land placements I was missing. People don’t resist new tools out of stubbornness. They resist them when the new tool creates more work before it creates any visible benefit, and that’s happening with AI right now.</p><p>Here’s a hypothetical worth running with your own team. Suppose AI removes 30% of a workflow. What do you want people doing instead? The capacity that opens up could go toward better customer experiences, new products, sharper decisions, more time with designers, real experimentation, or genuine innovation. If you don’t decide where that capacity should go, don’t expect to find it on the P&amp;L.</p><h3>We Treated AI Transformation as a Technology Problem</h3><p>Capturing AI value takes four capabilities working together, not one capability working alone.</p><p><strong>Business.</strong> Can AI produce revenue, margin, productivity, or innovation? This depends on naming the outcome up front.</p><p><strong>Technology.</strong> Do we have the tools, data, and governance this requires? This depends on infrastructure.</p><p><strong>Human. </strong>Do people understand how their value is changing, and do they have the confidence to work differently? This depends on skills and judgment.</p><p><strong>Organizational.</strong> Can leaders create room for experimentation and let decisions move across functions? This depends on workflow redesign and leadership.</p><p>Technology capability alone can’t answer the human and organizational questions. An organization doesn’t capture meaningful AI ROI by maximizing just one of these four. They have to move together.</p><h3>The Missing Variable Is Friction</h3><p>Back to the original challenge. If people are already adopting AI, what does change leadership add?</p><p>Change leadership adds the ability to see and work with friction, the thing adoption alone can’t touch. Adoption measures whether people are using a tool. It says nothing about whether they feel steady doing it, whether they understand what it means for their role, or whether anyone has told them what to do with the time or judgment AI frees up. That gap is where the friction lives, and it’s exactly the terrain change leadership is built to work.</p><p>The leaders I’ve spoken with described that friction in concrete terms. AI shows up as something added on top of everything their teams already do, rather than something that replaces or simplifies existing work. It doesn’t feel like it’s in their control. The weight of getting a whole team AI-ready tends to land on a handful of leaders, who are being asked to make that happen without the time or capacity to do it well.</p><p>Friction rarely sounds like outright refusal. It sounds like real questions. When am I supposed to do this? What does this mean for my job? Why change a process that already works? What am I supposed to do with the time I save? Am I even allowed to change this workflow? Who decides?</p><p>AI also introduces something most previous technology rollouts didn’t carry at the same scale. Some employees have genuine moral objections to the technology itself, and leaders can’t simply wave those concerns away.</p><h3>So Where Did Your AI ROI Go?</h3><p>Run your own organization through these eight questions, and notice exactly where your answers get thin.</p><p><strong>1. Intended value.</strong> What measurable business outcome were we trying to create?</p><p><strong>2. Baseline.</strong> What did the work cost, require, and produce before AI?</p><p><strong>3. Capability created.</strong> What can people or the organization do now that wasn’t possible before?</p><p><strong>4. Workflow changed.</strong> Did we redesign the work, or just make the existing process faster?</p><p><strong>5. Capacity redirected. </strong>What are people actually doing with the time AI created?</p><p><strong>6. Workforce capability.</strong> Have we developed people for the higher-value work we now expect from them?</p><p><strong>7. Organizational friction.</strong> What’s preventing people from changing how the work actually happens?</p><p><strong>8. Business result.</strong> Where can we point to the result in revenue, margin, productivity, innovation, or customer value?</p><p>Ask this at each step: at which point does your evidence disappear? That’s probably where your AI ROI went.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f7XA7SF4XlX_Alv0oKORLw.png" /></figure><h3>Adoption Is Where the Transformation Starts</h3><p>People are adopting AI. That’s genuinely good news. It means this change stopped being theoretical.</p><p>Jobs are changing. Workflows are changing. Expectations are changing. Capacity, skill requirements, and decision-making are all changing right along with them.</p><p>Adoption doesn’t reduce the need for change leadership. It’s exactly when the real work starts, because the goal was never to get people to use AI. The goal was, and still is, to build a more capable organization because AI exists.</p><p>— -</p><p><em>Oh, and one more thing.</em> If this got you thinking about how your own organization handles change, my book, <a href="https://amplifiedconcepts.com/learn-to-love-the-roller-coaster/">Learn to Love the Roller Coaster</a>, digs into exactly that. It’s built from real stories of people who have navigated change in their own lives, paired with frameworks that make the ride more enjoyable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1SMl6mBDlQnxNC6dTLjRzA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b02e6b5114d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The More AI Can Do, the More Expertise Matters]]></title>
            <link>https://medium.com/@SherryHeyl/the-more-ai-can-do-the-more-expertise-matters-2c461e107cc2?source=rss-a7113085f5ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c461e107cc2</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Sherry Heyl]]></dc:creator>
            <pubDate>Sat, 19 Sep 2026 17:23:03 GMT</pubDate>
            <atom:updated>2026-09-19T17:23:03.390Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ULyLyTey-AHPXcZTLeJtw.png" /></figure><p>I recently sat in on a breakout session where we learned the basics of vibe coding using Lovable.</p><p>I have never thought of myself as someone who builds applications. I have plenty of ideas about what technology could do, but there was always a wide gap between having one of those ideas and turning it into something real. I needed to find someone who could code, explain what I wanted, answer their questions, and wait through a few rounds of back and forth before an idea became something I could actually use.</p><p>With vibe coding, that gap can close in minutes.</p><p>You describe what you want. The AI builds it. You look at what came out, ask for changes, and watch it update in front of you. You add a feature. Then another. Before long, something that started as an idea is sitting there looking like a real product.</p><p>That is genuinely exciting. It is also worth being honest about what it actually lets you accomplish, and about the blind spots it leaves you with, the ones you don’t even know are there.</p><h3>It Works Is Not the Same as It’s Ready</h3><p>Once I can make an application work, it becomes easy to feel like I know how to build applications. I don’t. I know how to use a tool that lets me participate in building one. Those are different skills.</p><p>Say I build a simple app for my business. The buttons work. The forms submit. It looks professional, and the people I show it to immediately understand what I was going for.</p><p>It works. But is it secure? How is authentication handled? Where does the data go? What happens if someone tries to use it in a way I never intended? Will it hold up for someone with a visual, cognitive, or physical disability? Does it introduce a data governance problem I haven’t considered? Does it solve the right problem in the first place?</p><p>I don’t know the answers to most of those questions. More importantly, I might not even know they need to be asked.</p><p>That is one of the clearest gifts expertise gives us. An experienced developer doesn’t just write better code than I do. Years of experience taught that developer everything else that needs to be true before something becomes part of a real business. A cybersecurity professional catches the vulnerability I would walk right past. An accessibility expert notices the barrier I would unknowingly build in. A product leader asks how people will actually use something instead of simply whether it runs.</p><p>AI gives us access to the visible output. It doesn’t automatically hand over the knowledge behind all the decisions that kept problems from ever showing up in that output. That is what makes this moment tricky. The danger was never that AI would produce something obviously bad. Bad work is easy to spot. The harder problem is that AI can produce something genuinely good and still incomplete, and a polished result can quietly stand in for a finished one.</p><h3>AI Can Accelerate Ideas. It Can Also Paralyze Execution.</h3><p>AI is not only changing who can create. It is changing how much we can create, and that shift carries its own risk.</p><p>For most of history, ideas cost something. If a team developed three campaign concepts and someone wanted twenty more, that meant more work, and the cost of continuing to explore eventually outweighed the benefit of one more option. That friction forced decisions.</p><p>AI removes the friction. Don’t love the three concepts on the table? Generate twenty more. Curious what a completely different direction looks like? You can have it in seconds. That feels like abundance, but it can quietly become paralysis.</p><p>Picture a creative team that has done the due diligence. They talked with stakeholders, considered the audience, thought about the brand, and rejected dozens of weaker ideas before landing on the three they present. Then an executive takes those concepts home, runs them through an AI tool overnight, and comes back with twenty-five alternatives.</p><p>The original question was which of these directions to pursue. The new question becomes what else is possible. Those are different questions, and because reopening exploration is now nearly effortless, organizations can drift backward through their own decision process without noticing it is happening. A team can spend weeks refining a strategy only to watch someone generate a fresh alternative the night before it gets approved.</p><p>This is where expertise starts to change shape. When ideas were expensive to produce, the most valuable person in the room was often the one who could generate them. When ideas become abundant, the most valuable person becomes the one who can narrow them and explain why. Not because they lack imagination, but because they understand what matters enough to say: these options violate a constraint we already established, these are interesting but don’t serve the objective, and this is the direction I recommend.</p><p>That is informed constraint. It keeps possibility connected to purpose, and it depends on someone being able to explain their reasoning out loud.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fr7anrENif8qEzmHNwSQDg.png" /></figure><h3>Expertise Has to Become Visible to Stay Valuable</h3><p>If you are the expert in the room, “because I know better” doesn’t carry the weight it used to. Someone can build a competing prototype, generate a rival strategy, or challenge your conclusion with AI in the time it takes you to finish your coffee.</p><p>Experts increasingly have to translate what they see instead of simply asserting it. A designer who says a concept doesn’t work needs to explain why. A leader who calls a decision final needs to walk people through the reasoning that got them there. That takes communication, patience, and the willingness to teach rather than guard territory, and none of those have traditionally been treated as part of expertise itself.</p><p>The responsibility runs both directions. Building a working app doesn’t make someone a software engineer. Writing a clean paragraph with AI doesn’t replace years spent developing an ear for structure and audience. When someone brings AI-assisted work to the expert who actually owns that discipline, the healthiest response sounds something like, “Look what I was able to create. Now help me understand what I don’t know.” That sentence holds real excitement and real humility at the same time, and it is exactly the culture worth building around AI in any organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zo5MgDnObe-rpZGToSwlyA.png" /></figure><h3>What Expertise Does That Output Can’t</h3><p>We spend a lot of time asking whether AI can do something. Can it write, code, design, analyze, strategize? Increasingly, yes to all of it. That question is becoming one of the least useful ones we can ask, because jobs were never just a collection of outputs. The output is what everyone sees. Expertise is what happens before, around, and after it.</p><p>The more useful question going forward may be this one: what do we expect to learn from another option that would actually change this decision? If there’s no good answer, it’s probably time to stop generating and start executing.</p><p>AI can create indefinitely. A business can’t explore indefinitely. Somebody still has to understand the larger picture, make the tradeoffs visible, recommend a direction, and help everyone move forward together. The more AI can do, the more those people matter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*383ukN23rIGmJwrvzTA31g.png" /></figure><p>If your organization is generating more AI-driven ideas than it can execute, that’s rarely a technology problem. It’s a collaboration and communication problem, the kind that shows up when experts and non-experts don’t yet have a shared way to translate what they’re seeing to each other. That’s exactly where I help. Let’s talk.</p><p>Further reading</p><ul><li><a href="https://theproductjourney.substack.com/p/ai-didnt-kill-expertise-it-split">“AI Didn’t Kill Expertise. It Split It in Two.”</a>, The Product Journey — on PwC’s 2026 Global AI Jobs Barometer, which found roles built around judgment growing faster and paying more than roles AI has simply made accessible.</li><li><a href="https://leonfurze.com/2026/03/01/expert-signals-why-human-expertise-matters-more-than-ever/">“Expert Signals: Why Human Expertise Matters More Than Ever”</a>, Leon Furze — on the kind of hard-won, contextual knowledge AI can’t replicate, and why experts have to actively transmit it rather than just possess it.</li><li><a href="https://spintheory.ai/the-future-of-work-ai-is-changing-the-value-of-expertise/">“The Future of Work: AI is Changing the Value of Expertise”</a>, Spin Theory — on how AI is unbundling expertise, making retrieval and first drafts cheap while judgment and stakeholder alignment become the differentiators.</li><li><a href="https://www.linkedin.com/pulse/ai-decision-paralysis-navigating-paradox-infinite-age-andre-4y9xe">“AI and Decision Paralysis: Navigating the Paradox of Infinite Choice”</a>, LinkedIn — on how AI-generated abundance can stall organizational decisions, and the case for bounded choice sets and clear thresholds.</li><li><a href="https://www.leadershipiq.com/blogs/leadershipiq/analysis-paralysis">“Analysis Paralysis”</a>, Leadership IQ — on the decision-science research behind too many options producing fewer decisions, and practices for moving from exploring to executing.</li></ul><p><em>Oh, and one more thing…</em></p><p><em>If this resonated, you might enjoy </em><a href="https://amplifiedconcepts.com/podcast/"><em>Navigate Change. Amplify Potential., my podcast f</em></a><em>eaturing real leaders and real stories about navigating change and unlocking people’s potential. Candid conversations with executives, entrepreneurs, and changemakers on leadership, AI, innovation, workplace culture, and the human side of transformation. Episodes short enough for a break, worth every minute.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c461e107cc2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are We Developing the Wrong Skills for Today’s Problems?]]></title>
            <link>https://medium.com/@SherryHeyl/are-we-developing-the-wrong-skills-for-todays-problems-40e35af0f672?source=rss-a7113085f5ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/40e35af0f672</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[future-of-work]]></category>
            <dc:creator><![CDATA[Sherry Heyl]]></dc:creator>
            <pubDate>Sun, 23 Aug 2026 18:43:14 GMT</pubDate>
            <atom:updated>2026-08-23T18:43:14.043Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5XoM3UIjdvlCrp4-s4U4HQ.png" /></figure><p>Tuesday night, I hosted the first Reflection Series.</p><p>The idea behind the Reflection Series is simple: bring thoughtful people with different experiences into a room, introduce a topic worth thinking about, and give ourselves permission to have a conversation without rushing toward an answer.</p><p>We’ve built a business culture obsessed with speed. We want faster decisions, faster execution, faster learning, faster answers.</p><p>Now AI can give us an answer in seconds.</p><p>So what happens when getting the answer is no longer the hard part?</p><p>One book that we reflected on was David Epstein’s <em>Range</em>. In it, Epstein explores the difference between what psychologists call “kind” and “wicked” learning environments.</p><p>Kind environments have recognizable patterns, established rules, and relatively predictable outcomes. You do something, receive feedback, and adjust. Over time, repetition makes you better.</p><p>Chess is a classic example.</p><p>Epstein tells the story of László Polgár, who believed exceptional performers could be deliberately developed through intense specialization. He and his wife raised their three daughters with chess at the center of their education. All three became exceptional players. Judit Polgár eventually became one of the world’s best chess players.</p><p>It’s an extraordinary story of what specialization can accomplish. But chess is also exactly the kind of problem computers became very good at solving.</p><p>The rules don’t change. The board is bounded. Moves can be evaluated, and patterns repeat.</p><p>In 1997, IBM’s Deep Blue defeated world chess champion Garry Kasparov.</p><p>That doesn’t make the Polgárs’ accomplishments any less remarkable. But it raises an important question about how we’ve structured work.</p><p>For decades, we’ve built organizations around many of the same principles that make someone successful in a kind environment. We created departments so people could specialize, workflows so work could be standardized, and certifications to demonstrate mastery of established bodies of knowledge. We created job descriptions asking for increasingly specific experience and built career paths that encouraged people to go deeper and deeper into a particular domain. And we rewarded people for becoming faster and more efficient at executing processes they already understood.</p><p>That made sense, but AI is becoming very good at exactly that kind of work.</p><p>Wicked environments are the opposite. Epstein borrows a phrase from psychologist Robin Hogarth to describe them: “Martian tennis.” You can see people playing a game, rackets in hand, but nobody has told you the rules. You have to figure them out as you go, and they can change without warning. Feedback is delayed or unclear, and the same move can produce different results depending on timing, context, or who’s involved.</p><p>AI can also be useful in wicked environments. It can surface options, identify connections, simulate scenarios, and challenge our first assumptions. But producing an answer is different from exercising judgment.</p><p>In a wicked problem, someone still has to decide what matters, whose interests carry weight, what risks are acceptable, and what tradeoffs an organization is willing to make. Those aren’t merely technical questions. They’re human and leadership questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*blLtTuMxF-0NynPEe85nuw.png" /></figure><h3>What Happens When the Only Problems Left for Us Are Wicked?</h3><p>Think about the last time a decision at work didn’t have a clean answer. Maybe it was whether to reorganize a team, how to respond to a competitor’s move, or what to do when a longtime process suddenly stopped working and nobody could say exactly why. There was no rulebook to check. The people around the table disagreed about what even counted as success. The problem may involve technology, psychology, culture, economics, and organizational politics all at once, and there isn’t necessarily a best practice because the situation you’re facing may not have existed before.</p><p>AI integration is filled with these kinds of problems. Which work should we automate? Where should humans remain involved? How will changing one workflow affect another department?</p><p>What happens to trust when someone’s role suddenly changes? How do we capture productivity gains without unintentionally deskilling our workforce? What happens when the technology changes again six months after we redesigned everything around it?</p><p>There isn’t a certification that gives you all those answers. And having more information doesn’t necessarily solve the problem. Sometimes we don’t need more data. We need a better frame for understanding the data we already have.</p><p>An example in <em>Range</em> that really captured this tension was the Space Shuttle Challenger disaster.</p><p>Engineers were trying to understand the risk associated with the shuttle’s O-rings and cold temperatures. On the night before the January 1986 launch, engineers had data from 23 previous flights showing O-ring damage, and the forecast for launch morning was far colder than any of those flights had been. There was data. There were experts. There were analyses. The problem wasn’t simply a lack of information. It was how that information got organized. The engineers presented their concerns to NASA managers using charts that listed each flight in order of launch date, mixing together flights that had no O-ring damage with flights that did, without ever lining them up by temperature. Read that way, the data looked scattered and inconclusive: some cold flights were fine, some warm flights had damage, and no clear pattern jumped out. Had someone plotted the same data with temperature on one axis and O-ring damage on the other, the relationship would have been obvious: every flight below 65 degrees had shown damage, and the coldest flight on record was still far warmer than what was forecast for launch morning. Nobody made that chart. The launch proceeded, and the O-rings failed exactly as the data, properly arranged, would have predicted.</p><p>That lesson feels particularly important right now.</p><p>AI is making information incredibly abundant. We can ask for another analysis, another scenario, another comparison, another projection, another 20 sources, and we can have them almost instantly. But wicked problems aren’t solved by volume. More information doesn’t necessarily produce better judgment.</p><p>AI adds another complication: it can make an answer sound more complete than it is. A well-written response can create the feeling that a problem has been understood when important context, disagreement, uncertainty, or missing evidence has simply been smoothed over.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3B892g-1isind4iI0Y2Wkg.png" /></figure><p>That makes reflection more important, not less. We need people who can ask:</p><ul><li>What assumptions are embedded in this answer?</li><li>What evidence is missing?</li><li>Who would see this differently?</li><li>What would have to be true for this recommendation to work?</li></ul><p>The scarce resource in an AI-enabled organization may not be information. It may be judgment.</p><p>There’s early evidence that the work itself is shifting in that direction. PwC’s 2026 AI Jobs Barometer found that the new tasks being added to AI-exposed roles are 2.5 times more likely to depend on skills such as empathy, judgment, and creativity, capabilities that grow more valuable as AI absorbs some routine work.</p><p>That doesn’t mean human work becomes easier. It may become less repetitive but more ambiguous. It becomes less about producing an answer and more about evaluating one, less about following a process and more about deciding when the process no longer fits.</p><p>AI doesn’t just risk replacing tasks. It’s already sitting closer to the decisions themselves than many people realize. In Deloitte’s 2026 Global Human Capital Trends survey of more than 9,000 business and HR leaders, 60% of executives said they now regularly use AI to support their decisions, and Gartner projects that by 2027, half of all business decisions will be augmented or automated by AI agents. If we consistently delegate framing, analysis, evaluation, and decision-making to it, we may weaken the very human capabilities we’ll need when its answer is incomplete, wrong, or inappropriate for the situation.</p><h3>Which Raises a Problem With How We Develop People</h3><p>If the problems increasingly left for humans are wicked, are we developing people to solve them?</p><p>I’m not sure we are.</p><p>The scale of the challenge is significant. The World Economic Forum reports that employers expect 39% of workers’ core skills to change by 2030. Analytical thinking remains the most sought-after core skill, identified as essential by seven in ten employers.</p><p>Yet most development systems still lean heavily toward immediately applicable, role-specific training. We still organize people into silos where they encounter similar problems, similar perspectives, and similar ways of thinking. We still tend to hire the person whose résumé most closely matches the job description. Twenty years in the same industry can look safer than someone who has moved between industries, functions, or careers.</p><p>We still tend to view learning through the lens of immediate applicability. What certification does someone need? What skill will make them more productive in their current role? What training produces the fastest return?</p><p>And we often fill people’s calendars so completely that curiosity becomes something they have to pursue on their own time.</p><p>But range develops differently. It comes from exposure: working with people who see the world differently, learning things that don’t appear immediately useful, moving between disciplines, and trying things you’re not already good at. It comes from encountering enough different situations that, when you face something you’ve never seen before, you have more places to look for an analogy.</p><p>This can’t be left entirely to individual initiative. If curiosity, reflection, and cross-functional learning happen only after hours, they’ll remain privileges for people with the most discretionary time and energy.</p><p>Organizations that want better judgment may need to design for it: protected time for learning, cross-functional problem-solving, rotations and stretch assignments, structured dissent, and conversations where people can raise questions before a decision hardens into a conclusion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rw4b-ECC5BIFPL5xobN6OQ.png" /></figure><h3>Maybe Efficiency Isn’t the Goal for Everything</h3><p>This is why I launched the Reflection Series.</p><p>We didn’t gather to become more efficient. There was no workflow to optimize and no certification at the end. Instead, we created space for people with different experiences to think together.</p><p>In most organizations, that kind of time can look unproductive, and I think we’re going to have to reconsider that.</p><p>If AI saves us time, the temptation will be to fill that time with more work. We produce more, respond faster, make more decisions, and move on to the next thing. That temptation is already becoming real. In a 2026 U.S. Census Bureau survey, 55% of U.S. workers said they’d used AI on the job. Among people who’d used it recently, nearly one-third said it saved one to two hours, while 30% said it saved them at least three hours.</p><p>The leadership question isn’t simply whether AI creates capacity. It’s what we choose to do with that capacity.</p><p>Perhaps some of that time should be protected to increase and diversify our range.</p><p>Read something outside your field.</p><p>Talk with someone from another department.</p><p>Explore an idea without knowing whether it’ll lead anywhere.</p><p>Ask why something has always been done this way.</p><p>Sit with a problem a little longer before asking AI to solve it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wptrjvp-ZKvc7qvcrj4mOw.png" /></figure><p>Organizations say they want adaptable, innovative thinkers. But we can’t design every minute of someone’s work around efficiency and then wonder why they struggle when confronted with something that doesn’t have an established process.</p><h3>We May Need to Rethink Expertise</h3><p>None of this means expertise is becoming less valuable. I think the opposite may be true, but the kind of expertise that matters may be changing.</p><p>Deep knowledge will still matter. So will experience. The difference is that we may increasingly need people who can combine that depth with breadth: people who can move between perspectives, recognize patterns across disciplines, question assumptions, and remain comfortable when the answer isn’t immediately obvious.</p><p>That should influence how we hire, how we develop people, how we structure teams, how much movement we encourage across functions, and even how we think about someone’s seemingly nonlinear career.</p><p>We spent decades preparing people to become exceptionally good at solving kind problems. AI is becoming exceptionally good at many of those same problems.</p><p>The next phase of workforce readiness isn’t simply teaching people to use AI faster. It’s developing people who can frame ambiguous problems, test assumptions, integrate competing perspectives, and take responsibility for difficult tradeoffs.</p><p>That may require something our efficiency-obsessed workplaces have slowly eliminated.</p><p>Time to think.</p><p>If this raises more questions than it answers for you and your organization, that’s the point. Start with one: where are you still training people for kind problems that have already become wicked? Sit with that question before you hand it to AI.</p><p>Oh, and one more thing…</p><p>If you’re in the Atlanta area and interested in joining a Reflection Series, <a href="https://amplifiedconcepts.com/reflection_series/">click here</a> for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40e35af0f672" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Is Changing the Work. Who Is Developing the Workforce?]]></title>
            <link>https://medium.com/@SherryHeyl/ai-is-changing-the-work-who-is-developing-the-workforce-2a8305f4f227?source=rss-a7113085f5ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a8305f4f227</guid>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Sherry Heyl]]></dc:creator>
            <pubDate>Sun, 23 Aug 2026 18:23:12 GMT</pubDate>
            <atom:updated>2026-08-23T18:23:12.986Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s_z5_3LOgAKvXQ8zScPW1g.png" /></figure><p>I host a podcast, “<a href="https://www.youtube.com/@AmplifiedConcepts/podcasts">Navigate Change. Amplify Potential.</a>,” and I’m a contributing writer for <a href="https://highlightgeorgia.com/author/sherry-heyl/">Highlight Georgia</a>. Both give me the chance to talk with a lot of leaders across a lot of industries. This week, I sat down with three of them. <a href="https://www.linkedin.com/in/vickiwhamilton/">Dr. Vicki Wright Hamilton, MBA</a> came on the podcast still lit up from decades of climbing her way through the C-suite, helping people see the leader they couldn’t see in themselves. <a href="https://www.linkedin.com/in/alanboyer1/">Alan Boyer</a>, who has spent his career figuring out how colleges and companies actually build capability in people, not just hand them a syllabus. And <a href="https://www.linkedin.com/in/bennyleedesign/">Benny Lee</a>, who brings big brand experience, a problem solver’s instinct, and a fierce protectiveness over the creative process.</p><p>There was a common theme running through every one of those conversations.</p><p>Businesses are expecting AI to change how work gets done in a way that increases productivity and efficiency. What they aren’t paying nearly enough attention to is how people build the capability this new work actually demands: working effectively alongside AI, questioning what it produces, exercising judgment, thinking strategically, collaborating across functions, adapting quickly, and bringing real creativity and initiative. Without those skills, none of it works out.</p><p>AI is changing the work. Who is developing the workforce?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Caf16ZaHaw8kJyoGfI2t4w.png" /></figure><h3>This problem started long before AI</h3><p>I spent years at New Horizons Computer Learning Centers, back when technology change had a rhythm you could plan around. Microsoft would roll out a new version of Office, then Cisco would roll out an update to its networking certifications. Companies figured out what their people needed to know, and training followed.</p><p>Then the pace changed. Cloud computing, Web 2.0, SaaS, social media and continuous digital disruption broke that old training cycle wide open. Companies couldn’t predict what people would need to know next quarter, let alone next year. So professional development became self-service.</p><p>You could watch the whole shift happen in three stages. First it was we’ll train you. Then it became here’s the learning library. Now it’s go figure out what you need.</p><p>Somewhere in that shift, we confused giving people access to learning with actually developing them.</p><p>AI is making the weakness in that model impossible to ignore.</p><h3>Figure it out yourself is reaching its limit</h3><p>Organizations today need people who can work effectively with AI, question what it produces, exercise judgment, think strategically, collaborate across functions, adapt quickly, spot opportunities, experiment and create. None of that develops because someone assigns an AI course or buys a seat on a learning platform.</p><p>And the pace of change means a company can’t build a curriculum once and call the workforce trained. The workforce isn’t just learning new tools. The nature of the work itself keeps moving.</p><h3>Giving people AI isn’t the same as preparing them for AI</h3><p>Benny put this well when I talked with him. His definition of AI literacy goes past knowing how to operate the technology. It’s knowing where AI belongs, where it doesn’t, what it can actually do today, and where our expectations have gotten ahead of reality. He talked about how AI is built to sound confident even when it’s wrong. It picks the tokens and the format that look right, whether or not the underlying answer is right. For a lot of everyday tasks, that’s a minor annoyance. When people start leaning on it for financial decisions, medical decisions, or something as personal as therapy, the stakes climb fast.</p><p>Alan brought the human side into focus when we talked. “Teaching with AI is not the same as working with AI,” he told me. Knowing how to use the platform is one skill. Knowing how to validate the output, how to catch the hallucination buried on page twelve of a twenty-page document before it throws off everything downstream, is a different skill entirely. When he ran a capability assessment for a university AI program, the gaps that showed up weren’t in the computer science content. They were in global and cultural fluency, in the ability to influence and persuade, and in what he calls fluid adaptation, the capacity to keep working on your original data set while five new ones land on your desk in the same afternoon.</p><p>Put those two together and a real distinction emerges. AI proficiency is knowing how to use the technology. AI readiness is knowing how to think while you’re using it.</p><h3>We’re asking for capabilities many workplaces spent years suppressing</h3><p>Widen the lens past AI for a second. Companies are suddenly asking for curiosity, creativity, adaptability, initiative, and cross-functional collaboration. Meanwhile, a lot of organizational systems were built around compliance, specialization, standardization and permission.</p><p>Alan’s work on enterprise risk and governance points to part of why that tension exists. He talks about needing a fence that’s twenty times higher for AI than for software, because access and data flow through so many more doors. Companies build guardrails for good reasons. But those same guardrails, applied without much thought, can quietly train people to ask permission instead of taking initiative.</p><p>You can’t spend years rewarding people for staying in their lane and then announce an AI initiative and expect everyone to become curious, experimental, cross-functional thinkers overnight. This is a leadership and organizational design problem. It isn’t an employee deficiency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*02eva5hGeEKiQcp2A0k3XA.png" /></figure><h3>Employees have responsibility too</h3><p>I don’t want any leader reading this to think the responsibility for developing capability sits with the organization alone. Dr. Vicki Wright Hamilton would push back hard on that reading, and she should. Her framing is that everybody is the CEO of their own life. That means paying attention to your skills, your network, your resources, your reputation, and where your value is moving next.</p><p>Here is one example she provided. Before AI, a content writer’s job was to write the content. After AI, the content gets written in seconds. So the writer has to reposition. “Bring me all the AI you got,” she says. “I’m going to take it and make it better. I’m going to validate it. I’m going to humanize it.” AI can get you from step one to step three, she told me. The human still has to get you from step three to step ten.</p><p>Employees should own their careers. Leaders still have to develop their workforce. Those two things aren’t in competition. They’re complementary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L5h1wrTIpCJlDMTn9vVAnA.png" /></figure><h3>Stop thinking about development as training</h3><p>The answer isn’t rebuilding the corporate training model from twenty years ago. Training has its place, but capability gets built through experience. Alan put it about as plainly as it can be put: “Elevate the human, you got to. There’s no choice.”</p><p>If you want people to develop judgment, give them room to make decisions. If you want curiosity, give them room to explore. If you want innovation, let them experiment. If you want collaboration, stop rewarding the silo behavior your incentive structure is quietly encouraging. If you want AI literacy, let people work with AI in a properly governed environment and learn firsthand where it holds up and where it doesn’t.</p><p>You don’t build an adaptable workforce by telling people to be more adaptable. You build environments where adaptability gets practiced.</p><h3>AI can become part of the development system</h3><p>This is where AI stops being just the disruption and starts being part of the answer. Benny described using AI to compress the mundane middle of a task rather than replace the whole process. The human sets the direction, AI accelerates the pieces in between, and the human evaluates and decides. He compared it to running a large company. You don’t personally handle every decision at every level. You delegate, and you save your own judgment for the calls that actually need it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oxkZku56_umt5lh4rAnf1Q.png" /></figure><p>I’ve found the same thing true in my own writing. When I don’t have a room full of people to bounce an idea off of, AI becomes something close to a third space, the kind of place where ideas used to get challenged and expanded over coffee. It pushes back on my thinking before I ever start writing. That only works if I’m using it to think, not handing my thinking over to it.</p><p>AI can be a tutor, a brainstorming partner, a challenger, a simulator, a research assistant, and a source of fast feedback. But only if people are encouraged to think with it instead of surrendering the thinking to it entirely.</p><h3>Leaders need to ask a different question</h3><p>Most leaders are still asking what AI tools they should deploy. The better question is what capabilities their people will need because of the changes the business is already making. From there, ask what capabilities you already have, where the real gaps are, which of those gaps need formal training and which need experience, what has to change about incentives and authority and workflow, and where AI can actually help people develop instead of just produce.</p><p>And ask yourself honestly what you’re still leaving employees to figure out entirely on their own.</p><h3>The new learning bargain</h3><p>Dr. Hamilton would say people need greater ownership of their own careers. Alan would say that as AI accelerates the work, organizations have to intentionally elevate human capability. Benny would say AI literacy means having enough judgment to know where AI belongs and where it doesn’t.</p><p>The old bargain was, “We’ll train you.” Then it became, “Figure it out yourself.” The next version has to be closer to this: “You own your development. We will build the environment where you can actually develop.”</p><p>We can’t predict every skill our people will need five years from now. We probably can’t predict most of what they’ll need two years from now. That doesn’t mean leaders are powerless. It changes what we’re developing.</p><p>We’re not simply preparing people for the next piece of technology. We’re developing people who know how to learn, question, experiment, collaborate, judge, create, and adapt as the technology keeps changing underneath them.</p><p>AI is changing the work. That part isn’t up for debate anymore. Employees have a responsibility to keep developing themselves, to stay curious about where their value is headed instead of waiting to be told. But here’s the part leaders can’t hand off. If your business strategy depends on people validating AI output, exercising judgment, adapting to problems nobody wrote a playbook for yet, and those capabilities don’t exist in your organization today, then building them isn’t a nice-to-have sitting next to your strategy. It is your strategy. A plan that assumes capabilities you haven’t developed isn’t a plan.</p><p>So who is developing your workforce?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dllNRbwZGP5B_ixXWAwQ-Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a8305f4f227" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Incremental Advantage in the Age of AI]]></title>
            <link>https://medium.com/@SherryHeyl/the-incremental-advantage-in-the-age-of-ai-5486c8408202?source=rss-a7113085f5ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/5486c8408202</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[change-management]]></category>
            <dc:creator><![CDATA[Sherry Heyl]]></dc:creator>
            <pubDate>Mon, 10 Aug 2026 21:56:26 GMT</pubDate>
            <atom:updated>2026-08-10T21:56:26.417Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4M1rJC09yx9vK_uGXGpsbw.png" /></figure><p>Everyone is talking about the race to AI. The race to automate. The race to improve productivity. The race to prove return on investment.</p><p>There is a temptation to believe that the competitive advantage is in being faster, but many of us know the fable that challenges that assumption. The tortoise and the hare. We remember it as “slow and steady wins the race.” I think there’s more to learn from that story, and two recent events show why.</p><h3>The Hare’s Real Mistake</h3><p>The hare didn’t lose because he was fast. Speed was never his problem. Once he’d built up a big enough lead, he stretched out by the side of the road for a nap, confident nothing could catch him. He treated the finish line as the only thing that mattered, so he stopped paying attention to the steps in between. He assumed his lead was enough, and he had no way to prove otherwise until he woke up and found the tortoise already there.</p><p>The tortoise won for a different reason than the one we usually tell. It wasn’t patience for its own sake. Every step he took was visible and accountable. Anyone watching could see exactly where he stood at any point in the race.</p><p>That’s the distinction I think matters right now. Some organizations are racing toward a finished result: how much work did AI complete, how fast did we get there, what’s the ROI. Others are building something incrementally, one visible, checkable step at a time. Those aren’t the same race, and this week gave us two clear examples of what happens when you run the first one and assume it’s the same as the second.</p><h3>When the Finish Line Isn’t Enough</h3><p>An Australian government department paid Deloitte roughly A$440,000 for a report reviewing the IT systems behind its welfare penalty program. It reached the department looking finished: polished, authoritative, ready to act on.</p><p>A Sydney University researcher found it full of fabricated citations, including a quote falsely attributed to a federal court judgment and references to academic papers that never existed. Deloitte revised the report, refunded part of the fee, and disclosed that a generative AI tool had been used in producing it (<a href="https://apnews.com/article/australia-ai-errors-deloitte-ab54858680ffc4ae6555b31c8fb987f3">AP News</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9fyOYgh3jChfhu31RxwitQ.png" /></figure><p>Deloitte made the hare’s exact mistake. The hare got far enough ahead that he stopped worrying about anyone checking his pace, and coasted. Deloitte got a report far enough through a polished, credentialed process that nobody thought to check the pace of the work behind it either, until an outside researcher did what Deloitte’s own review should have done. Racing toward a finished deliverable and racing toward a trustworthy one are not the same effort, and Deloitte spent its energy on the one that only had to look right at the finish.</p><h3>Losing Trust Without Losing Accuracy</h3><p>Hank Green has spent nearly 20 years building one of YouTube’s most trusted platforms, as half of the Vlogbrothers but the creator behind SciShow and CrashCourse. He has more than 12 million followers and roughly 32 million subscribers across his channels, built almost entirely on the premise that his audience can trust what he tells them. His story is the subtler version of the same mistake, and I think it’s actually the more important one.</p><p>Green apologized to his millions of subscribers after fans noticed the phrase “I appreciate the pushback” in one of his videos, a stock phrase common in chatbot responses, and concluded he must have read from an AI-generated script. Green said that specific line was an ad-lib responding to a guest, not AI text, and on that narrow point, he was right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YlqgwCads_2qQW9QWpIA7Q.png" /></figure><p>But the apology didn’t stop there. Green also acknowledged using ChatGPT to prepare the video, describing it at first as research and generated notes, and conceded the finished piece had an “AI feel” to it. In a longer Reddit post, he explained he uses AI models to locate papers and source material, not to supply his conclusions or write the words he says on camera. He admitted he’d become too reliant on the tools regardless, largely because he’d overcommitted himself and was producing under pressure.</p><p>His audience didn’t fully accept the distinction, even though nobody proved his actual conclusions were wrong. Many viewers felt that AI-assisted research alone was enough to undermine the standard they expected from him, given ongoing concerns about hallucinated citations, weak source evaluation, and the mismatch between his reputation for careful, human-centered work and the workflow he’d just described. What broke down wasn’t accuracy. It was trust in the process behind the work.</p><p>Green admitted that his own process wasn’t clear to him anymore. He’d been moving so fast that he’d lost track of it himself.</p><p>Deloitte’s failure was a visible error somebody eventually caught. Green’s was in some ways more instructive. His actual output may have held up fine, yet the trust still collapsed, because the steps behind the work had stopped being visible to anyone, including him. He’d been running like the hare without realizing it. All finish line, no accountable steps along the way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QO-9UrWqdve5qQXKhpc2bw.png" /></figure><h3>The Incremental Advantage</h3><p>Put the fable and both stories together, and the real lesson comes into focus. The race to ROI treats the finish line as the whole point. Incremental improvement treats every step as something that has to hold up on its own, whether or not anyone happens to be watching.</p><p>You don’t have to be fast to win. You have to be deliberate. The tortoise just kept putting one foot in front of the other, the whole way, and that steady, visible pace is what made him someone you could count on before the race ever ended.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*87qJB1hHekuGhQbMl0ZePA.png" /></figure><p>When people ask me how I’m using AI, I don’t have a lot of impressive automation stories to offer, even though I probably use it more than the average person does. I have information flowing to me automatically at the right moments, and I’ve built AI rules that keep me consistent and help me make decisions that stay aligned with my goals. What I’m not doing is rushing to build agents or looking for what I can hand off entirely. I focus on what I actually need and how AI can enhance it, and I stay involved in every step until I know I can trust what comes out the other end. It’s helped me fill in the gaps where I have known weaknesses, moving forward at a steady pace instead of a fast one.</p><p>That approach hasn’t made me faster. It’s made me incrementally better, and I think that’s worth considering at the organizational level too. Not how much work did AI complete, but how much better did our process actually get while we used it. Could someone else follow the steps we took and see real improvement, not just more output?</p><h3>Three Checks Before Your Next Deliverable</h3><p>“Legible process” is easier to act on than it sounds. Before your next AI-assisted deliverable goes out the door, three questions will tell you which race you’re actually running.</p><p>Can you trace who reviewed it. Not whether it looks reviewed. Whether a specific person can say what they checked and when.</p><p>Is AI’s role disclosed anywhere it materially shaped the outcome. Not buried in a policy document nobody reads. Visible to whoever is trusting the work.</p><p>Would the process survive someone asking you to walk them through how it got made. If the honest answer is “I’d have to reconstruct that,” the process was never actually legible. It just looked finished.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tkTJtM2XudEDtFmLYX2QKA.png" /></figure><p>None of these slow work down in any meaningful way. They just make sure the steps that got you to the finish line could survive being looked at, which is exactly what neither Deloitte’s report nor Green’s research process could do when someone finally asked.</p><p>Those two questions build very different organizations. One optimizes for a finished result. The other builds something people can actually trust, one verifiable step at a time. And that’s the race that actually compounds. The organizations that win it won’t simply be the ones that automate the fastest. They’ll be the ones whose process stays legible at every step, not just polished at the finish line.</p><p><em>A note on how this was made: I used Perplexity for research and fact-checking, Claude to help organize my thoughts and work through structure, and Notebook to create the images. Each piece still takes me 4 to 6 hours to produce. The ideas, arguments, and words are mine.</em></p><p>Oh, and one more thing…</p><p><em>Navigate Change. Amplify Potential.</em> features real leaders and real stories about navigating change and unlocking the potential of people. Through candid conversations with executives, entrepreneurs, and changemakers, we explore leadership, AI, innovation, workplace culture, and the human side of transformation. Episodes are broken into conversations short enough to watch on a break, but long enough to be worth your time. <a href="https://www.youtube.com/@AmplifiedConcepts/podcasts">Give it a listen.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5486c8408202" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shadow AI Isn’t Just a Security Issue. It’s a Leadership Issue.]]></title>
            <link>https://medium.com/@SherryHeyl/shadow-ai-isnt-just-a-security-issue-it-s-a-leadership-issue-c62152e721e1?source=rss-a7113085f5ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/c62152e721e1</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[future-of-business]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Sherry Heyl]]></dc:creator>
            <pubDate>Sun, 02 Aug 2026 15:34:31 GMT</pubDate>
            <atom:updated>2026-08-02T15:34:31.692Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4cwPj5qWM4bk9vtXHWFh_w.png" /></figure><p>A few years ago, most employees had ideas about how to improve their work. They just didn’t have the ability to do much about it.</p><p>If you wanted a new tool, you submitted a request. If you wanted to automate a process, you waited for IT. If you wanted to redesign how work happened, you hoped someone with authority agreed.</p><p>Today, a marketing manager can build an AI assistant before lunch. A salesperson can automate proposals. An HR director can redesign onboarding. An operations manager can create an entirely new workflow. They can do it rogue, without asking permission and without telling anyone.</p><h3>The Inheritance Problem</h3><p>Most leaders see this as a technology story. I see it as an inheritance story. The industry has a name for it: shadow AI, tools built and used without anyone in IT or leadership ever signing off. But calling it a security problem undersells what’s actually happening. Every tool an employee quietly builds becomes something the whole organization has to live with, whether or not anyone chose it. There’s no security review. No consistency, because five teams can end up solving the same problem five different ways, each with their own tool, their own logic, and their own version of the truth. No record of what the tool does or how it makes decisions. And when an employee leaves, the tool often leaves with them, or the knowledge of how it works and whether anyone can safely turn it off does.</p><p>Imagine a company with 300 employees. Marketing builds custom GPTs for campaigns. HR builds its own interview workflows. Finance automates reporting. Sales creates proposal generators. Operations builds project trackers. Every one of those tools might be excellent on its own. Together, they can create chaos: different assumptions, different terminology, different data structures, different security practices, different customer experiences. And it doesn’t stop at the department level. Three people on that same sales team might each build their own version of a proposal generator, none of them aware the other two exist, each one trained on slightly different assumptions about what a good proposal looks like. People aren’t just bringing their own devices anymore. They’re bringing their own intelligence systems, one person at a time, and that’s a leadership challenge organizations haven’t had to solve before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PuFkXW3lE_JS_A_Mz_Ug6g.png" /></figure><p>This isn’t a hypothetical. Start with individual behavior: Microsoft and LinkedIn’s 2024 Work Trend Index found that 78 percent of AI users already bring their own AI tools to work rather than wait for a corporate-sanctioned option, a habit the report calls “<a href="https://news.microsoft.com/source/2024/05/08/microsoft-and-linkedin-release-the-2024-work-trend-index-on-the-state-of-ai-at-work/">Bring Your Own AI</a>.” That figure doesn’t measure how many people use AI. It measures how the people who already use it behave once they do.</p><p>Now layer in how fast that pool of people is growing. Gallup’s latest quarterly tracking shows i<a href="https://www.gallup.com/workplace/712736/organizational-adoption-jumps-six-points.aspx">ndividual AI use at work has grown from 21 percent to 52 percent in three years</a>, and organizational adoption jumped six points in a single quarter this year, from 41 percent to 47 percent. The Federal Reserve found that 78 percent of the U.S. labor force now works at a firm that has adopted AI in some form. Put those trends together, and the math gets uncomfortable fast. If even a fraction of that same bring-your-own-AI habit holds as adoption climbs, the number of employees quietly building with tools nobody sanctioned isn’t holding steady. It’s compounding in step with adoption itself.</p><p>The tools are already inside your organization. The real question isn’t whether anyone can see them. It’s what they’re already doing to your organization’s future.</p><h3>The Readiness Gap</h3><p>Recently, I was listening to <a href="https://www.cnn.com/2026/07/26/business/video/gps-0726-microsoft-interview-satya-nadella">Fareed Zakaria’s interview with Microsoft CEO Satya Nadella on CNN</a> when he described how he’s “developing” again. When he thinks of a tool that would make his work easier, he simply builds it with AI.</p><p>That reminded me of a conversation I had with <a href="https://highlightgeorgia.com/2026/07/14/curiosity-creates-innovation/">Salil Kulkarni, founder of Virima</a>. When I asked him about his patents, his answer wasn’t about technology. He noticed friction. He built something that made the work easier. Then he moved on to something more meaningful.</p><p>That’s what innovators have always done. AI didn’t invent that mindset. It just made the tools to act on it available to millions more people.</p><p>The readiness gap and the inheritance problem are the same issue seen from two different angles. Readiness means the thinking ability, courage, and training to act on what they see. Inheritance is what happens to what they build once it’s out in the world, and right now most organizations don’t have a plan for either.</p><p>Here’s the thing. Handing everyone the same AI tool treats it like software, not intelligence, and that limits what’s actually possible. Software is something you install once and expect everyone to use the same way. Intelligence adapts to the person using it, which is exactly what a single standard deployment can never capture. Employees will keep building their own personalized solutions anyway, because no single tool fits how everyone thinks. Leadership’s job isn’t to stop that. It’s to give it a sanctioned path, so personalization happens in the open instead of in the shadows.</p><p>But a sanctioned path isn’t enough on its own. AI removes the technical barrier to building something. It doesn’t give anyone the thinking ability to spot the right problem, the courage to question how things work, or the training to build something that holds up. That’s the real difference between an employee who owns a problem and one who’s just been handed a tool. For most of the Industrial Age, organizations trained people to follow a process, not question it. Now they need to train people to be innovative and creative in a way they never were before. Skip that step, and the readiness gap turns into inequality between employees, along with real inefficiency and lost productivity across the organization.</p><p>That’s the part most organizations haven’t reckoned with. Access to AI is now nearly universal inside a company. The readiness to use it well is not, and neither is a structured way for one person’s good idea to become something the whole team can use. Some employees will look at a clunky process and immediately see three ways to fix it. Others will use the same tools to do the same work slightly faster and stop there, not because they lack access, but because no one ever taught them to see their work as something they’re allowed to redesign, or gave them anywhere to bring the redesign once they had it.</p><p>AI democratizes building. It does not democratize systems thinking, and it doesn’t build a sanctioned path that turns a person’s fix into everyone’s advantage. Someone can build a workflow that saves them four hours a week while quietly making life harder for everyone downstream, and that’s classic local optimization: the organization grows more fragmented even as each individual becomes more productive. Without a sanctioned path, personalization and fragmentation are the same thing. With a sanctioned path, personalization becomes the source of the organization’s best ideas instead.</p><p>A real plan starts with an honest assessment of where the readiness gap actually sits, team by team, instead of assuming everyone crossed the same starting line the day the AI tools arrived. From there, it means building training that teaches people to question a process, not just prompt a chatbot. And it means creating an actual intake channel, a place where a personal build gets reviewed and tested. Some of it will be worth adopting org-wide. Some of it will only ever help the one person who built it, and that’s fine too, as long as it has the guardrails that protect the company.</p><h3>Why the Gap Is Visible Now</h3><p>For years we’ve told people to own their careers, keep learning, build their networks, develop new skills, and stay relevant. We shifted the responsibility for growth from the organization to the individual, and people accepted it. Now AI hands them the means to act on that responsibility. Some people were already prepared to use it. Others were told to think like an owner without ever being given the training or the room to practice it.</p><p>That gap used to be invisible. When building a tool required an engineering team and a budget line, almost nobody could act on their ideas, so the gap between people who noticed problems and people who didn’t rarely showed up in results. Now it shows up everywhere. Two people with identical access can produce wildly different outcomes, and the difference has nothing to do with the technology. Both of them have access to the same AI, the same tools to build with, the same ability to create their own solution. Technology plays a role here, but it isn’t the deciding one. What separates them is curiosity and the courage to act on it: whether anyone ever taught one of them to question the process in front of them instead of just accepting it, and whether either of them has anywhere to take a good answer once they find one.</p><p>That’s the inconsistency leaders need to plan for. It isn’t a rollout problem you fix by buying more licenses. It’s a capability gap that existed before AI arrived and that AI is now making visible inside every team.</p><h3>The Trust Problem</h3><p>For most of the Industrial Age, organizations hired people to execute work. Today, they’re increasingly hiring people to improve the work. Execution requires compliance. Improvement requires ownership, and ownership requires both trust and preparation. An organization that hands out AI tools without building the thinking skills and the psychological safety to use them is just widening the gap.</p><p>I think of healthy organizations as ecosystems of partners rather than hierarchies of employees. Employees complete assigned work. Partners build something together, challenge assumptions, and improve the system because they believe they’re creating something larger than themselves. That partnership only works when the organization invests in giving people the judgment to act, not just the software to act with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C3i7ZuHY6UAqX6uGPS7c-g.png" /></figure><h3>Closing the Gap</h3><p>The technology is not the constraint. The organization is, and that means the fix isn’t a better tool. It’s a different definition of what leadership does.</p><p>That comes down to three deliberate moves.</p><ol><li>Build readiness before access. Teach people how to spot the right problem, question how work currently gets done, and know when to stop optimizing their own corner of the business and think systemically instead. Access without that training just produces more people building the wrong things faster.</li><li>Claim the inheritance before it claims you. Define what problems are worth solving, what standards everyone builds to, and what data gets shared instead of siloed. Give employees a visible, sanctioned path for building and sharing what they create, so nobody has to go rogue to get something built. A good experiment becomes an organizational capability instead of staying one person’s personal productivity hack, and the work stays inside the organization instead of walking out the door with whoever built it.</li><li>Build trust before you ask for ownership. Partnership only works in both directions. You can’t ask people to challenge assumptions and build like owners while treating their judgment as optional the moment it’s inconvenient. Trust is what turns access into ability, and it’s the one part of this that no amount of structure can manufacture on its own.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zMNRUSIDQnOtlSQrO1UAcA.png" /></figure><p>AI isn’t changing organizations because it writes better emails. It’s changing them because it exposes a gap that was always there between employees who were ready to build and employees who were only ever asked to follow instructions. AI didn’t create that gap. It just made it visible and impossible to ignore. Leadership’s choice now is simple: close that gap deliberately, or watch it widen on its own.</p><p>Your employees are already building the future of your company. The question is whether you’ve given all of them what they need to build a successful one.</p><p>If you’re not sure where your organization’s readiness gap actually sits, l<a href="https://amplifiedconcepts.com/letsgetstarted/">et’s talk.</a></p><h3>Oh, and one more thing…</h3><p>Each week I like to share something practical alongside these ideas. This week, it’s my resource library: a growing collection of tools, assessments, books, and videos organized around the challenges leaders are actually facing right now, including a full collection on AI readiness and adoption. Take a look at <a href="http://amplifiedconcepts.com/resources">amplifiedconcepts.com/resources</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c62152e721e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>