FIR #533: The Two Distinct Realities of AI Adoption
In this long-form October 2026 episode of For Immediate Release, Neville and Shel report on FGS Global’s research, “Winning the Debate on AI.” More than 7,000 people across seven countries rate AI as the least trusted technology in widespread use, yet 37% became more positive after hearing about its benefits. Shel looks at Microsoft’s move of communications into its corporate, external, and legal affairs group, and its plan to put employees out front telling the company’s story. Neville examines OpenAI’s Locked Chats and the gap between the name and what the feature delivers. Shel reports on Fresh’s finding that 28% of employees meet company news through an AI summary first, and on how to write content that survives it. Neville asks what a Northern Ireland council’s return to a printed newsletter says about channels and measurement. Shel closes with the Wharton 2026 AI Adoption Report, in which managers and the employees they manage describe two very different workplaces. In his Tech Report, Dan York reports on the critical PHP vulnerabilities fixed in the October 21 security release. The two remote code execution flaws affect any server hosting a PHP application, which is why WordPress and other platforms urged immediate updates. Dan covers why the release was coordinated, the role AI plays in the story, and the xkcd comic that captures how much of the internet depends on a few critical components. He then turns to Freedom House’s Freedom on the Net 2026 report, “Seismic Shifts on the Global Internet,” and to the French government’s pressure on Meta, TikTok, and other platforms as protests spread this weekend. He closes with two fediverse stories: the Social Web Foundation’s Fediverse Multimedia Grants, funded by a $200,000 Interledger Foundation grant, and what’s coming in Mastodon 5.0, including a redesigned composer and navigation. We’d love to hear from you: comment on LinkedIn, Facebook, Threads, or WhatsApp, email [email protected] with or without an audio file attached (or use the voicemail button on the FIR website to record a comment directly from the web). Links from this episode: New research: Winning the debate on AI Radar Pulse: Winning the debate on AI Microsoft Rethinks Communications As Employees Take On Storytelling Role Using locked chats in ChatGPT OpenAI Adds Locked Chat Feature to ChatGPT to Hide Sensitive Convos Behind PIN Codes AI summaries overtake workplace communications, Fresh says AI Research Summaries ‘Exaggerate Findings,’ Study Warns Ruwiki explains: Why AI summaries need more context Council to spend £30,000 on print title amid low views of digital newsletter Council goes back to printed newsletter as no appetite found for digital edition 2026 AI Adoption Report Links from Dan York’s Tech Report Security advisory: Critical remote code execution vulnerabilities, update now Critical PHP Security Release Dependency [HEADLINE NEEDED] Seismic Shifts on the Global Internet France puts Meta, TikTok, other platforms on notice over riot content as “Acte II” protests loom Interledger Foundation awards $200,000 to Social Web Foundation to support decentralized social media Fediverse Multimedia Grants 5.0: Laying the foundation 5.0: A closer look The next monthly, long-form episode of FIR is tentatively scheduled to drop on Monday, November 30. We host a Communicators Zoom Chat most Thursdays at 1 p.m. ET. To obtain the credentials needed to participate, contact Shel or Neville directly, request them in our Facebook group, or email [email protected]. Special thanks to Jay Moonah for the opening and closing music. You can find the stories from which Shel’s FIR content is selected at Shel’s Link Blog. You can catch up with both co-hosts on Neville’s blog and Shel’s blog. Disclaimer: The opinions expressed in this podcast are Shel’s and Neville’s and do not reflect the views of their employers and/or clients. Raw Transcript: Neville Hobson: Hi everyone, and welcome to the For Immediate Release podcast, long-form Episode 533 for October 2026. I’m Neville Hobson in Somerset, England. Shel Holtz: And I’m Shel Holtz in Concord, California. Neville Hobson: This month we have our usual six great stories to share with you, plus, as usual, Dan York’s Tech Report. But first, let’s begin with a recap of the episodes we’ve published over the past month and some listener comments. In the long-form Episode 529 for September, published on the 28th of September, our lead story reported on a Press Gazette investigation that found dozens of experts quoted in the mainstream media who don’t actually exist. And PR agencies are unwittingly sharing them with the press. This poses a credibility issue for the agencies and the media, we said, requiring a layer of verification unlike anything we faced before. Other stories include a crisis communication handbook for boards from the CIPR and the UK Institute of Directors. And we’ve got a handful of comments here, don’t we, Shel? Shel Holtz: Yeah, we have a couple. Philippe Borremans, our friend, said, “Thanks for covering the CIPR and Institute of Directors handbook. It was a great collaboration with colleagues, and I think the final result is really worth a look.” And Jane Wilson said, “Love the line, ‘You can’t communicate your way out of a crisis you behaved your way into.’ I use a similar line: you can’t communicate out of a crisis while the fire is still burning. There needs to be operational behavior, resolution, or a plan to resolve. For comms to do our jobs. And I agree wholeheartedly, it’s a governance issue.” And Neville, you had a reply to Jane. You wrote, “Deepwater Horizon is such a powerful illustration of this point. No amount of carefully crafted messaging could change the reality that oil kept pouring into the Gulf, and Hayward’s remark just compounded an already disastrous situation. It’s a reminder that what leaders say matters enormously, but what the organization actually does matters even more. Which brings us right back to governance and accountability, long before anyone starts drafting a holding statement.” Neville Hobson: Good comments Jane made, I thought. So in FIR 530, on the fifth of October, we discussed a Financial Times report claiming that the volume of AI slop appearing as thought leadership on LinkedIn has led to a surge in interest in human ghostwriters. And this is the one that attracted quite a few comments, right, Shel? Shel Holtz: This attracted 14 comments. This one really seemed to strike a nerve with people. It’s too much to read all of the comments as they were written, but we do have a summary. Chris Norton kicked things off. He was hosting a GEO/AEO event the week after he shared his post, and has been talking with SEOs and copywriters. One of them ran a 300-person SEO and copywriting agency and just closed it because the market vanished. Chris still believes people want taste and human authenticity in 2026. We’ll accept some automation, he says, but we’d still rather talk to a human at the co-op checkout than pack our own bags. And Neville, you replied that the scarce commodity may no longer be words at all, but judgment, taste, and genuine perspective, and that those become more valuable as AI makes competent content effortless. Dennis Howlett uses Claude to draft his FOIAs and his posts. He trained it on the Diginomica library for style, then edits everything, often rewriting. He runs it through Grammarly, then passes it back to Claude for a legal check. It makes him more efficient. Jeff DeCanya says it definitely matters. Working with a human ghostwriter isn’t the same as feeding a prompt to an algorithm. Neville, you called that the strongest argument on the other side, since the human process involves challenge, interpretation, and a real relationship with the subject. Mac Worsham offered a useful test for any byline: could the named author explain the prompt and why each point is there? If so, the drafting tool matters less than critics fear. If not, a human ghostwriter wouldn’t fix it either. He also commented on a different post. Neville, you posted and I posted, and he commented on both of our posts sharing the episode. He said the line about not being able to communicate your way out of a crisis you behaved your way into is maybe the most powerful sentence in the profession right now. That’s actually from the previous episode; I don’t know why he left it on this one, but well. It treats crisis communication as governance and moves the question upstream, to the gap between what an organization says and what it does. He sees the fake expert story, that previous story, as the same lesson from the other side. Back to this episode. Sherilyn Starkey wondered whether calligraphers had the same debate when Gutenberg unveiled movable type, asking whether it had really done the thinking. Authenticity, she says, has always had a technology problem. Megan Thomas says ghostwriting for leaders who give zero input always feels wrong to her, and she sees no difference between that and using AI with no input or care. She’s fine with AI used responsibly and with appropriate human attention, and she loves that authentic comms are back in demand, “ums,” “ahs,” and typos included. Rita Zonia says AI helps enormously with the mechanics of writing, but tends to stay skin-deep on its own. She finds it amusing that a lot of organizations thought they could decimate comms teams and let AI pick up the work, only to discover the tool is only as good as its operator. So great comms people are making a comeback. Experienced writers and ghostwriters know how to get beneath what someone says, ask the extra questions, and spot the little odd comment that’s actually the story. Finding what’s worth saying, and saying it authentically and succinctly, is still a very human skill. Sharon O’Day has seen tools that generate a podcast from your news articles or presentations, with vendors pitching materials in your CEO’s voice. Philosophically, she says, that’s no different from ghostwriting text, and yet it gives her what the kids call “the ick.” Catherine Atkinson, replying to Sharon, said she’s doing that kind of writing now, with many years of experience in writing voice from journalism and screenwriting. What she’s seeing is a rush to fix big problems. And Joe, who has a name that’s interesting to pronounce. It’s S-Z-N-K-O-W-S-K-I. So, “Znowski,” I’m going to guess. I apologize, Joe. Joe has been ghostwriting since 2008 and says the desire for authenticity is boomeranging back to where it was before ChatGPT. That puts ghostwriters in a great spot, but only if they’re willing to do the hard work and fun work of interviewing, research, and collaboration. And Melissa Edwards found it all encouraging for communicators. A lot of comments from that episode. Neville Hobson: Terrific. That’s really terrific, getting that qualitative insight into people’s different views. Okay, so “Factual Accuracy Isn’t a Comms Strategy” was the theme of our discussion in FIR 531 on the 12th of October. We considered research suggesting that using familiar language can help accurate information compete with misinformation. But we asked, where’s the line between persuasion and manipulation? In FIR 532 on the 19th of October, we asked, does a seat at the executive leadership table give communicators genuine influence, or does influence come from being the trusted advisor a CEO turns to? We revisited this perennial debate about communicators having a seat at the top table, with some different perspectives. And now you’re up to date on FIR episodes. Shel Holtz: One more episode to bring you up to date on, and that is Circle of Fellows, the monthly panel conversation, usually moderated by yours truly, sometimes by Brad Whitworth. It is a panel of four IABC Fellows from the International Association of Business Communicators. This was part two of our discussion about artificial intelligence and communication leaders’ moment. Adrian Cropley was back for this episode, along with Mary Hills, Robin McCasland, and Cyrus Mavalwalla. The next episode of Circle of Fellows is titled “Lead, Communicate, and Connect.” We’ll be talking about the communicator’s role in creating workplaces where people feel seen and appreciation becomes part of how we lead, communicate, and connect. Zora Artis, John Clemens, Catherine DuCharme, and Jennifer Waugh will join me for this conversation. It is scheduled for 6 p.m. Eastern time on Thursday, October 29th. And one last note: we had a lot of comments on a couple of our episodes over the past month. We love those comments. We love having other perspectives brought into the show, and we would be very grateful for your comment. There are lots of ways to do that. Every comment we got over the last month came through LinkedIn, from people who left their comments on the posts where we share the announcement of a new episode’s availability. So that seems to be the easiest and most popular way to comment, and we encourage you to do that. We also share on Facebook, on Threads, and on WhatsApp, and I check those too for comments, so you can comment there. You can send us email at [email protected]. You can attach an audio file to that. We would love to play your voice speaking your comment out loud. You can do that through your own recording mechanism and attach it to that email. You can also use the tool we have on our website: go to the site and click the button that says “Send voicemail” and record your comment. Or leave your comment in the show notes. And you can comment on absolutely anything you want, including any of the six topics that we are going to be discussing today. And Neville, those are going to start right now with you. Neville Hobson: That’s true. So I’ve been reading an interesting new research report from FGS Global, a strategic communication consultancy, called “Winning the Debate on AI.” It explores public attitudes towards artificial intelligence based on a survey of more than 7,000 people across seven countries, including the UK and the US, alongside interviews with political, regulatory, and business leaders. What caught my attention was a striking contradiction. AI is being adopted at remarkable speed, yet public sentiment towards it remains surprisingly negative. For example, 71% of people surveyed said they’d used AI in the previous six months, yet when asked how positively they viewed different technologies, AI came at the bottom of the list, even below social media. But here’s where it gets interesting. When people were presented with AI’s potential benefits, 37% said their views became more positive. FGS sees this as evidence that public opinion remains open to persuasion and that organizations have an opportunity to shape the debate. That sounds like good news for communicators, but it raises a question I’ve been thinking about: is AI’s reputation problem really something we can solve through better communication? Or does the technology industry need to change some of its behavior before people have good reason to trust it? There are a few things I think are worth exploring here. Are people skeptical about AI because they don’t understand its benefits, or because they have legitimate concerns about how it’s being developed and deployed? Where’s the line between helping people understand AI and trying to persuade them to accept something they might reasonably distrust? And what should communicators be doing? Promoting AI’s benefits, or helping their organization build the transparency, accountability, and safeguards that earn public confidence? One other finding struck me. When researchers asked about AI’s benefits, everyday convenience resonated much more strongly than sweeping promises about economic growth. Perhaps that’s telling us something quite simple. People don’t necessarily want to hear about how AI will transform the global economy. They want to know how it will improve their lives and what safeguards are in place when things go wrong. Which brings me back to the title of the report, “Winning the Debate on AI.” I don’t think the real challenge is winning the debate at all. I think it’s earning the trust that makes persuasion unnecessary. How do you see it, Shel? Shel Holtz: Yeah, I couldn’t agree with you more on that. There is a tremendous amount of persuasion that needs to be happening. I think that the industry needs an association. I have not seen the equivalent in artificial intelligence, among the frontier labs for example, of the pharmaceutical association or the oil and gas association. I used to interact regularly with the Toy Manufacturers Association when I worked at Mattel. They represented the industry. They had the investment, of course; they got all of the money from the organizations that belonged to the association, which were all of the big companies. They conducted the research. They identified the issues. They worked with PR agencies or had their own in-house communicators, or both. They framed the approach that was going to be taken and fed that back out to the member organizations, who were all in lockstep then about how they were going to wield this influence and build this trust, rather than each one doing its own thing. Right now you have Dario Amodei coming out and saying, “Yeah, 10% chance this could kill us all.” Well, you have Google taking a completely different approach, and OpenAI saying other things. In fact, OpenAI saying conflicting things. And God knows what’s coming out of xAI. It’s a hodgepodge. There’s no coordinated messaging, there’s no common understanding or common agreement among these companies about what the issues and challenges are. The information that’s in this report would be invaluable if there was a coordinated effort in the industry. Knowing that people are interested in “what’s in it for me,” well, that’s not rocket science. That shouldn’t be a shock to people. But “what’s in it for me” covers a lot of ground, everything from “it can make my life easier when I want to book dinner and a movie as a date night” to “this could cure my lung cancer or prevent me from getting it.” So, talking about this in realistic terms. But right now what you have is this combination of so many different issues associated with AI coming at people from so many different directions. You have the concerns about the future of civilization. You have the concerns about what this means to work. You have the concerns about the data centers, everything from “my electric bills are going up” to “it’s creating health hazards.” You have the concerns about its impact on the economy and what happens if the AI bubble bursts, and there are a lot of people who are reading and hearing about that. There are so many different issues coming at people from so many different directions, and there isn’t a coordinated effort to address them. It’s being dealt with almost entirely defensively. “Here comes another one, let’s react.” And you don’t build trust that way. No matter how hard they try, there really needs to be a different approach to building and gaining that trust. And by the way, you do that through action. You do need communication so that people know that you’ve taken these actions, but communication alone is not going to address this. These organizations need to behave in a way that builds trust. And you’re seeing the beginnings of it with the data centers. No more nondisclosure agreements with the cities and counties where they’re getting the agreements to build them. They’re now going in and having town halls first, to hear the concerns of the local residents and come back with proposals to address them. You’re now seeing money pumped back into the community, so people’s kids are going to new schools and health clinics are opening because of the revenues coming from these data centers. They’re taking steps to address the concerns that people have about noise and water use, with closed-loop systems and the like. But all of this is in reaction to the ton of hate that was coming at them when it was learned what was going on behind closed doors, with no concern for all of these things. So they need to be proactive about these things, and they need to build and earn that trust. And they need communications to let people know that this is what they’re doing. Neville Hobson: Yeah, agreed. That’s well summarized, I think. It is a major, major issue, the misinformation that’s out there. Much of it is not deliberate; it’s well meaning. But you go on any social network and you’ll find any regular Joe with an opinion, and he will share it. I’ve lost count of how many people leaving such posts on LinkedIn where I’ve asked a question, “What’s your source?”, because they don’t cite a source for anything, and I don’t get answers to those questions. So you don’t pay any attention to those kinds of comments. But most people do. I think of a handful of people I know who are skeptics, very much so, about all this. They react constantly: “Look at what I just read,” and another one saying the world’s going to end tomorrow. They look alarmed about what they’re doing with ChatGPT, so they stop doing it even. I think it leads to misunderstanding, because not only do you not have enough information to clearly explain what’s going on, it’s conflicting, because some say different things. But I think the significant thing about earning trust is utter clarity in explaining what’s in it for you, and in our own organizations, what’s in it for all of us. It reminds me a bit of podcasting. Not in the early days, but things I’ve noticed over the years, particularly over the last couple of years, where I see people posting “here are the benefits of podcasting,” and they justify what they’re trying to talk about by saying the global take-up is X, and this guy Joe Rogan’s got three million listeners, look at what he’s getting out of it. That doesn’t relate at all to the real world for most people. So talking about how AI is going to help us all be economically beneficial in five years’ time just goes over the heads of most people. If you say it’ll enable you to get the best deals on your holiday, or it’ll help you understand something you’ve been trying to do… A good example as well, one that should interest most people, is the role AI played in the PHP issue that arose these past few days, where AI discovered the fault that had lain hidden in the code. No one knew, or people in the tech community certainly did nothing about it, for 22 years. Which, as an aside, raises the question: what the hell was the tech industry doing? They didn’t fix this. The answer I read from someone was that they believed the chances of anyone taking advantage of this were close to zero. Well, guess what? And I think that comes back to the owners of the AI tools, who should be doing more. OpenAI and Anthropic, in my opinion, instead of getting the headlines about “this latest cool thing we can do,” and we’ve got a story coming up about ChatGPT shortly, should talk more about what it means to the average Joe and the average company, and focus on something that they know people are concerned about. They do enough surveys themselves. So I think communicators, and again, let’s bring this back to reality for people: what do you need to do in your organization to help people understand all this? In the absence of any kind of handy toolkit or playbook you can get that makes sense to you, you have to understand this, promote the benefits, and help the organization build transparency and accountability. These are messages we’ve been talking about for quite a while on the podcast. And I think the point I made earlier holds: everyday convenience resonates much more strongly than sweeping promises about economic growth that people can’t relate to. Shel Holtz: Yeah, there are other things that I think communicators can help these organizations do, things that we have seen in other industries, like the computer industry. So let’s take, for example, OpenAI announcing that they have solved one of the twelve Millennium math problems. And this came as a complete surprise to the mathematics community. Now, these are people who have gotten PhDs, they have devoted their whole lives to mathematics, and many of them pick one of these challenges and spend their careers working on it. And suddenly here’s OpenAI announcing, “We solved it. It took two weeks.” And they did this without the involvement of the mathematics community. Now, if they had used their PR capabilities appropriately, they would have said, “Here’s what we’re working on.” And a good PR person would have said, “You should do this in concert with representatives from the mathematics profession, in the open, so that they are engaged with this.” They can, first of all, be involved in making sure that the process is a valid one. Even if it solves the problem, maybe it went about it a bad way, or there’s not sufficient documentation to prove that this actually is the solution. And then you figure out how mathematicians can use this, rather than end up where we are today, which is with mathematicians furious about this and also terrified that there’s going to be no need for them within the next couple of years. And everybody who’s heard this story, they’re not going, “The poor mathematicians.” They’re going, “My profession is next.” And that’s how you erode trust. If they had partnered with mathematicians and come out and said, “Here is how AI and humans work together, where each provides what they’re best at, to solving these problems and identifying new ones,” then everybody’s optimistic. That’s how it’s going to go for my profession too. And they had no clue about this, probably because they never consulted their communicators. Neville Hobson: Yeah. There are tons of things we could continue discussing on this, but that’s a foundational overview, let’s say, on what you need to do. You’ve got to build trust. So I’m sure we’ll be returning to this topic soon. Shel Holtz: No doubt. But for now, let’s turn away from AI altogether and talk about how Microsoft is rethinking the way it communicates. On September 24th, internal memos from Satya Nadella and Brad Smith, reported by GeekWire, moved the communication function out of marketing. It now sits in Brad Smith’s corporate, external, and legal affairs group. Okay, that makes sense to me. Brent Colburn is leading it on an interim basis. Frank Shaw, who has run Microsoft’s communications for, well, nearly 20 years, is leaving at the end of the year and moving into an advisory role in the meantime. The bigger piece here, though, is the strategy. Microsoft wants employees and executives out front, telling the company’s stories in their own voices, quote, “under a shared strategy and set of principles,” end quote. The press has called this “building in public.” Forbes, which is where I spotted this, frames it as a trade-off: more voices, less control. Now, so far nobody has published those principles. The way I see it, this is essentially a strategic narrative. I developed one of these where I work for pretty much the same purpose, so that our people, leaders, people out in client interviews, the marketing department developing proposals, all speak in their own voice and tell their own stories, but guided by a set of principles. But we haven’t heard anything about that yet for Microsoft, nor have we heard anything about the approval process or what training might be required before employees can post. Where are they going to post? How can they post? Can they do a podcast? Can they do TikToks? We haven’t even seen a timetable. So it’s hard to assess how this might work or might not work. Before we get to the pros and cons of this approach, I do want to make the point that this is hardly new. Some of you may remember Robert Scoble. In the early days of blogging, he was a Microsoft employee. He was writing as the Scobleizer. It was an early blog. In fact, in 2005, The Economist wrote about it, and I’m quoting here: “He has become a minor celebrity among geeks worldwide who read his blog religiously. Impressively, he has also succeeded where small armies of more conventional public relations types have been failing abjectly for years. He has made Microsoft, with its history of monopolistic bullying, appear marginally but noticeably less evil to the outside world, and especially to the independent software developers that are his core audience.” That was the Scobleizer in 2005. By 2006, roughly 3,000 Microsoft employees were blogging on the company’s developer network. Neville, you and I interviewed Robert in March of 2005. You can still hear that interview over on our archive site, and we covered his departure from Microsoft in 2006. One report said he was the third best-known employee at Microsoft, behind Steve Ballmer and Bill Gates at the time. So, what’s different this time around? A couple of things. First, this is a stated enterprise strategy that came from the CEO. Second is the home for it. It’s not sitting under marketing; it’s under the legal and policy side of the house. When we debated reporting lines on Episode 532, I joked that comms should report to legal, and that’s what Microsoft did, though I doubt they’d say it that way. Third, there are the platforms. Channel 9 and Microsoft blogs were owned; Microsoft controlled the stage. Today those voices live on X and LinkedIn, platforms Microsoft can’t control. And all of this is in the middle of an AI race where every competitor’s engineers are doing the same thing, and under real regulatory scrutiny. What are people saying about this? Named practitioner reaction is pretty thin so far. Mostly it’s just media coverage. GeekWire noted that Shaw’s shift surprised some people inside the company. The sharpest analysis I found was from ContentGrip, which says the communications job becomes one of designing a system of credible voices rather than being the voice. And real quickly, just some pros and cons. On the plus side is credibility. An engineer explaining her own work is more believable than a press release. It’s faster. It reaches more of the right people through fragmented channels that no media list covers. It gives you a listening post; Scoble used his blog as a free focus group. And in an age of AI-generated everything, verifiably human voices are going to carry some weight. On the minus side, there’s, well, a lot. There’s inconsistent messaging. There’s legal and regulatory exposure, especially for a public company facing antitrust attention. There are disclosure risks and leaks. There’s uneven participation: some employees are going to shine at this, and others are going to feel pressured into doing it. There’s a loss of control, which is part of the whole point, but it’s also the whole problem. And with the issues, we’re just scratching the surface. It’s not like things don’t happen like this all the time with organizational support or indifference. Where I work, we have people posting videos from construction sites to LinkedIn all the time. Are we upset by it? Hell no. We cross-post most of it to our official accounts. We love it. So if you’re doing this at your organization, the Microsoft story points to three things. Publish clear principles people can actually remember. Train and coach the people you’re asking to speak, because enthusiasm isn’t a skill. And build an escalation path and monitoring so someone can help fast when a post goes sideways. Neville Hobson: Yeah, there’s a lot here, Shel, I must say. A key point in my mind, when I hear this kind of story, is that the Scobleizer, and indeed IBM, did something similar to this, which is where we met Philippe Borremans, when he was at IBM involved in the blogging initiative. Shel Holtz: That’s right. Neville Hobson: Right. The landscape is utterly, utterly different to what it was then. There are more people, apart from anything else, and there’s more access to opinions and to anything other people say online. Back 20 years ago, you were still on dial-up for a large part. DSL might be your fastest choice. Mobile networks weren’t anything to speak of at all. So it was limited what people could do. But also the awareness and the desire weren’t fully formed yet. That’s emerged over the last two decades. Now everyone’s online, we’ve got AI on the scene, and attitudes are shifting away from the command-and-control behavior exhibited by companies 20 years ago, Microsoft being one of them: official spokespeople only, no one’s allowed to say anything publicly. That was the mantra in the ’90s, certainly. Now it’s different, so encourage it. It’s no small thing, though, for large enterprises to suddenly shift tactics and do this. But the trend, I’ll call it that, is clearly there to do this, and Microsoft may well be a great ongoing live case study on how this works. I can think of, for instance, when I was working at IBM a decade ago, involved in mobile app development, I was using tools that would help employees share content on social networks with pre-created messaging. That was so fake, in my humble opinion. Now you want it to be natural, and with it comes the inherent risk that they’re going to say something that, by mistake, is not really what you would like people to be talking about. It’s not about “you can only talk about certain things.” I think you’ve got to say, talk about what you want related to work. But you mentioned something really significant, which is you’ve got to have guidance and training from the very, very outset. And undoubtedly there are other things you could do to lessen what some people might see as pressure to do this. There’s no pressure. You don’t have to do this. You need to make that message very clear. Equally, if you don’t do it, there’s no penalty, but peer pressure will help improve that, I would imagine, if you do it right. We don’t have time to go into a lot of detail on this, but I think finding champions within the organization who can lead the charge, who stimulate people to do all this, would be great. But I think you’ve still got another issue, which I don’t know how you would solve, which is that much of what employees in a big company like Microsoft post is going to be just so much noise amongst all the other noise that’s out there. You’re competing for people’s attention. So I doubt you can expect to achieve mass conversion to people paying attention to what you say online in that kind of environment. So maybe you need to concentrate on small communities that you have a relationship with. But the idea, I think, is really good. And I think IBM is probably the best model, because at the time there wasn’t really anyone else doing it the way they did it. They published guidance, examples, manuals that were publicly accessible by anyone, and that helped drive awareness of what others could do. That was really quite something. It’d be interesting if Microsoft does something like that with this. But I think it’s a good step. I read the Forbes article. I didn’t think they were quite right with their title, by the way, which was “Rethinking Communication as Employees Take on a Storytelling Role.” That looked to me like there’s a keyword they put in the headline so it shows up. This is way, way beyond just storytelling. This is something where you are an extension of the organization in how you communicate externally and, indeed, even internally. So it’s a huge task, I think, and I wish them well. I think it’d be great to see how they get on with this. Shel Holtz: Yeah, I think this is a step beyond advocacy, because in employee advocacy programs you’re asking people to amplify a message that you have already distributed. And in this case, you’re telling people, go out there and tell your own stories and engage in your own conversations with people. There is nothing new about this. Not only did Microsoft do it before IBM, we had General Motors with a social media team engaging in the car blogs, and not about GM stuff, just becoming part of the community. Dell had a program that I think was on par with IBM’s. I remember speaking at one of their certification programs for the people who were going to become bloggers on behalf of Dell. There were a couple of hundred people in this program, and I think there were 11 of us speaking there. Christopher Barger was there. Richard Binhammer was at Dell at the time. Neville Hobson: I did similar with Dell in the UK. The same thing. It was a global thing they were trying to do. Shel Holtz: Right. But they trained people heavily. They trained people very deeply in all of this. Neville Hobson: Yeah. There are so many examples we could spend the rest of the show just talking about what others did. It’s not new, you’re absolutely right. But it needs revisiting again, because I think people have forgotten this. Shel Holtz: Well, this is why I raised the story. Here we go again, with somebody saying employees are authentic, their voices are authentic, it’s going to have more credibility than sending out a press release or putting something on our media site. I think that’s great. Why hasn’t it become the standard? It’s because too many organizations don’t take the time and trouble to do the training and to provide the resources to make it easy. They don’t think through what this means to employees who may feel pressured to participate. They don’t teach you where the regulatory risks are. Don’t mention another employee’s health problem in the United States. For God’s sake, that’s a HIPAA violation. So there are all kinds of risks here. You can mitigate them with the appropriate program before you just tell people, go out and blog, or go out and post on LinkedIn and X and whatever. Neville Hobson: Yeah, it’s good. So I mentioned earlier that we had a story about ChatGPT to mention. Here it comes. OpenAI has just introduced an interesting new feature for ChatGPT called Locked Chats. It lets you hide individual conversations from your normal chat history and protect access to them with a four-digit PIN. It’s being rolled out across ChatGPT’s consumer and business plans, including Enterprise. At first glance this seems like a useful addition. But here’s where it gets interesting. OpenAI is quite explicit that locking a conversation doesn’t encrypt it separately, doesn’t change how long the company retains it, and doesn’t override an organization’s compliance policies. In Enterprise and Edu workspaces, the content can still be available through authorized compliance systems. So a locked chat isn’t necessarily a confidential chat in the way some users might imagine. Consider what an employee might reasonably assume when they see a feature called Locked Chats. They might think the conversations are now completely private, even from their employer, or that sensitive corporate information becomes secure simply because the conversation requires a PIN. Neither assumption is necessarily correct. OpenAI’s own documentation makes some important distinctions. Locking isn’t encryption; the feature doesn’t create an end-to-end encrypted vault. Data retention doesn’t change; locked conversations remain subject to the same retention and model improvement settings. Organizational oversight remains; locked chats in Enterprise and Edu workspaces are still included in message logs available through OpenAI’s compliance platform. And forgetting the PIN has major consequences: resetting it permanently deletes the locked conversations and the protected content that you might have shared with ChatGPT. And this raises some questions for communicators. For example, are employees becoming increasingly comfortable discussing sensitive workplace matters with AI assistants, perhaps without fully understanding who can access that information? How clearly are organizations explaining the distinction between privacy, confidentiality, and security when they introduce AI tools? And is there a danger that features like this create a false sense of security, encouraging people to share information they perhaps shouldn’t be putting into an AI system in the first place? I think there’s a broader issue here about AI literacy, though. We often talk about teaching people how to use AI effectively, but perhaps we aren’t paying enough attention to helping them understand the implications of using it. And there’s another thought. As ChatGPT and similar systems have become more integrated into everyday work, employees may increasingly regard their AI conversations as personal spaces, even when they’re using company-provided tools. That could create some interesting tensions between individual expectations of privacy and an organization’s legitimate responsibilities for governance, security, and compliance. So is a feature like Locked Chats simply a welcome improvement to the user experience, or does it highlight a bigger challenge for organizations trying to establish sensible boundaries around AI at work? Shel Holtz: Well, I’m going to use it, because any extra degree of security is a good thing. But this is clearly a branding issue as far as I’m concerned. The word “locked” suggests more protection than it obviously provides, based on everything OpenAI has told us about it. I think that’s a pretty good example of how product naming shapes the expectations of the user, and of the gap between a help center disclosure and what people assume. Calling it “locked” is going to set an expectation for people who don’t pay attention to the fine print, and it’s going to be misleading. As a communicator, I probably would have advised a different name for it. I don’t know; I haven’t given any thought to what I would call it. That could be a listener exercise. Send us your ideas for what you would have called it. But yeah, I think it’s a poor branding choice. I think it sets a bad expectation. It is still up to the organization, when we’re talking about the use of something like this in the enterprise, to make sure employees understand what it is, what it can do, and what it can’t do. If we are involved in a lawsuit, in discovery, those chats are still going to be accessible. The fact that you locked it doesn’t mean it’s not going to end up in the court records and in the hands of the adversary in the lawsuit. So this becomes governance in the organization. It becomes part of the training, the ongoing training. This is why we talk about the fact that AI training in the organization is not a one-and-done thing. This technology continues to evolve and change dramatically, and it will be incumbent upon communicators, the trainers, and the IT department to work together to make sure that employees understand: this is the utility that you can get out of this feature, and this is what it will not do for you. Neville Hobson: Yeah. And I think also, I read in one article commenting on this that you can have guidelines written and published on a website accessible to all employees. No guarantee they’re going to read it. Well, yeah, that’s true, but you still have to do it. You should communicate it and make it available and help people understand all this. But you need to do more to help people understand the consequences. That’s the point that strikes me. Not how to use ChatGPT, but the consequences of this. So that, I think, is one way of addressing expectations of privacy that balances that out with organizations’ responsibility. These are communication issues. I think, like you, I’m going to give it a go when I see it in my copy of ChatGPT. It is rolling out, as I mentioned; I haven’t got it yet. Would I use it? I’m a bit different to everyone else employed in an organization, because my use of these tools has now changed in terms of workplace needs, so there’s not an awful lot that I would be alarmed about if it was accessible. That said, I don’t want it to be just open to anyone to look at if they don’t have a need to. So there’s that issue. But it comes down to, this is related to what we’ve been talking about earlier, too: building trust. And you think the employer needs to do more than they might think they need to do with the addition of a feature to this tool. Undoubtedly Claude, maybe Gemini, will come up with something like this as well. Shel Holtz: Of course. I was just going to say, Anthropic and Gemini will look at the criticism that’s coming out of what OpenAI did and come out with versions that address some of those, and they’ll be able to market that “ours doesn’t do this” or “ours is better because of that.” Neville Hobson: That’s right. So lots to consider on this from a communicator’s point of view and from a user’s point of view. Just be aware of the limitations. [Dan York’s Tech Report] Shel Holtz: Thanks for that report, Dan. It arrived just moments before we started recording, so we have not had a chance to listen to it. I know that it’s a little late because of your travels. I read your post that it took you about 30 hours to get home from the conference you were attending, and I’m very grateful that you still found time to record your report. I’m looking forward to hearing about it. I’m definitely interested in your take on that PHP vulnerability that we discussed briefly earlier, and interested in hearing about the features of Mastodon 5.0, since I still host the mastocom.org Mastodon instance. So I appreciate that. Internal communicators, this one’s for you. You craft a message. You know the kinds of messages you craft: benefits change, reorganization, safety policy. You consider the structure, the tone, what leadership wants to say, and how employees will react to it. And then your employees never read it, because instead they paste it into an AI tool and read what comes back. That’s not hypothetical. Fresh, an intranet company, surveyed a thousand professionals in the UK and the US, both communicators and employees. 88% of employees say they use AI to summarize workplace communications. 28% now encounter company news through AI first, before the intranet, before the leadership email, before word of mouth. Only 12% read internal communications in full. 95% of employees trust AI to capture the key points accurately. Yet 92% of internal communicators say those summaries distort emotional tone and intent. Both of these things can be true, because the employees can’t see what got left out. That’s the nature of a summary. And just a third of organizations have any formal monitoring or policy for how their content gets reinterpreted. So, how accurate are these summaries? Well, there’s research, although not about internal comms. There was a study in Royal Society Open Science that looked at almost 5,000 AI summaries of scientific abstracts and articles. The summaries were far more likely than the originals to overgeneralize, and the newer the model, the worse it got. Llama 3.3 was 39 times as likely to produce generalized conclusions. ChatGPT-4o was nine times as likely. In one example, “a diabetes drug was better than placebo” in the original became “effective and safe treatment” in the summary. The qualifiers just disappeared. The researchers told the bots to stay faithful to the source and not introduce inaccuracies, but they still produced about twice as many generalized conclusions. So “just tell the AI to be careful” isn’t a fix. Now, scientific abstracts aren’t an all-hands memo, but the failure is the same one we worry about: the conditions, the exceptions, and the caveats get dropped in the summaries. “We’re moving to the new system, with exceptions for field staff pending approval” might turn into “We’re moving to the new system.” A piece in Digital Journal points out that summarizing means choosing what to leave out, and a short answer is a starting point, not a substitute for the source. So what do we do? First, write content that survives the summary. David Bowman of Fresh, the UK organization that did that study, put it this way: “To be heard in 2026, organizations must design content to survive the summary.” In practice, that means lead with the point. Put what’s happening, who it affects, what they need to do, and by when in the very first few lines. I know you want to write in that feature style, with an example before you get into the news, to make it human. It doesn’t survive the summary. Write your own one-sentence bottom line. If you don’t supply the summary, the machine is going to do that. Keep qualifiers attached to the claim. Don’t bury “this only applies to this cohort of employees” in paragraph six. Label what’s decided and what isn’t. Cut, shorten. The way Bowman said it, subtraction is now a strategic necessity. Fewer messages means the important one is less likely to get mangled. And test it. Run your own announcement through whatever AI tool your employees use and see what comes back. You may not like it. Second, consider channels that don’t invite the paste-and-summarize habit. This might include live town halls, manager-led team conversations, and face-to-face with people who aren’t at a desk all day. Conversation carries the context and the tone that a summary strips out, and you can see in the room whether it landed. I’ll be honest, though, this isn’t a wall. Meetings get transcribed, and video can be summarized. The point isn’t to hide from AI. It’s to put the important stuff where a human explains it to another human. And then there’s governance. Only a third of organizations have any policy. Find out how your employees actually consume your content. Tell leaders that sending isn’t the same as being understood, and that the summary is now a channel they don’t control. The audience isn’t skimming anymore. They’re delegating the reading. Our job is to make the message hold up when the reading is done by the machine. Neville Hobson: Yeah, it’s an interesting scenario you’ve described, I think, Shel. One of the articles you shared, in IT Brief, I found quite interesting. A couple of quotes struck me. The report presents the issue less as a technical shift than as a behavioral one. That makes total sense to me. This is largely behavior, it seems to me. But the conclusion makes sense to me too. It underlines how quickly AI tools are moving from optional assistance to frontline filters for corporate information. 28% of employees now are seeing company news through AI before any original source. I don’t see that changing at all. And I think the reality is that this is how people like to share information. It gives them a sense of control, I suppose. It could be that they might reinterpret what the official news from a company is, maybe with a hint of skepticism about what they really mean. And you’ll even find some who’ll say, “This really means this.” And that kind of content will spread outside the organization. So it’s a complicated landscape, it seems to me, and I think there are no easy answers. Shel Holtz: No, I think it is important, though, for internal communicators to find a way to poll your population and find out the degree to which this is happening in your organization. Because I firmly believe that if you find out that some significant percentage of your employees are engaging with organizational content this way, and I’m not talking about best practices or things that are in the archives. I’m talking about the news that’s being presented, the information that leaders are sharing in their emails, the things that you’re sharing through your intranet that you think are important for all employees to understand. The new policy, right? The fact that there is a laptop swap program coming up and all employees need to go and fill in this information about their current company equipment. This is important, that employees get this. And if you find that a preponderance of employees in your organization are using the summaries, you need to restrategize your whole approach to communication. It may end up relying more on face-to-face. And I’m actually thinking about this as subject matter for a new book: that we are going to come to rely on managers like we have never relied on managers before to become the conveyors of this information directly to the members of their teams. We’ve been talking about this in internal communications for decades, but it is now a required part of the strategy, if in fact your ability to get the message across is being eroded by the summaries that employees are creating. It’s also going to change the approach you take to writing and where you put this stuff for people to get. So I think you need to ask your employees where they’re at with this, and keep doing that so that you’re ready. Even if they’re not doing it now, when they start doing it, which I think is probably inevitable. Neville, I do this with all the newsletters that I get on AI through Gmail. I have a skill set up in Claude. I subscribe to probably 20 AI-related emails. There is absolutely no way that I’m going to be able to read all of those every day. But my Gmail summary skill does a great job of telling me, “Here are the things that they’re all covering. The Neuron covered this, and TLDR covered that, and Casey Newton’s newsletter covered this other thing.” I can skim that in about two or three minutes, and it’s great. But am I getting the context? Am I getting the nuance? Am I missing something? Is it skewing some of that information as it creates a summary? Yeah, I read this knowing full well that that’s possible. But it’s better than not being able to read them at all. And I’m sure that there are employees who are tremendously busy on their jobs who feel the same way about reading the information that comes to them from the company. Neville Hobson: Yep, makes total sense, I agree. Okay, so here’s an interesting story, nothing to do with AI, utterly nothing, from Northern Ireland, that caught my eye. A local council is abandoning its digital newsletter for residents and going back to a printed magazine delivered through letterboxes. Lisburn and Castlereagh City Council says readership of its digital newsletter has collapsed. One edition in 2024 attracted around 1,650 views, but a more recent edition managed fewer than 120. So the council is spending £30,000, which I would say is probably about $38,000, on a trial printed magazine, which will go to 60,000 households. Now, I rather like the idea of print making a comeback. We’ve talked a number of times before about how traditional communication channels still have a place in an increasingly digital world. But what really interests me is why the digital newsletter failed so spectacularly. Was it the format? Was the content not sufficiently interesting or relevant to residents? Did people even know the newsletter existed? Was it promoted effectively? Or perhaps the council simply didn’t understand how its residents wanted to receive information. And there’s this. The council has an online registration form for its digital magazine. It asks residents for their name, address, postcode, and email address, together with consent to receive emails about accessing the publication. That raises another possibility: was a digital edition sufficiently easy to discover and access? We can’t tell from the registration form alone how residents actually received or found the newsletter, and the articles I’ve read don’t really talk any more about this. But it’s another reminder that the experience surrounding a publication can matter as much as the publication itself. We don’t know the answers, as I mentioned, and the reports I’ve seen don’t really explore them. There’s more, such as the question of measurement. The council knows its digital newsletter attracted very few views. But how will it know whether the printed magazine is any more successful? Delivering 60,000 copies doesn’t mean 60,000 households will read it. So there are a few questions worth exploring. For example, are organizations sometimes too quick to blame a communication channel when the real problem might be their content, their audience understanding, or the distribution strategy? Could returning to print actually be a sensible decision, particularly when communicating with an entire community rather than a self-selecting digital audience? And how should we measure success? Is it enough that people receive or read a publication? Or should we be looking for evidence that they understand something, take action, or engage more with the organization? And I think there’s a wider issue here as well. Digital isn’t automatically better simply because it’s digital, and print isn’t automatically outdated. What matters is reaching the right people with something that’s relevant to them, in a format they’re willing to engage with. So here’s a closing thought: a channel can deliver your message, but it can’t make people interested in it. Shel Holtz: I have so many thoughts about this, I’m not even sure where to start. In terms of the declining readership of the digital publication, did they ask people why they weren’t reading it? Did they survey their residents? They might have been able to make changes. Neville Hobson: We don’t know any of that. Shel Holtz: No, I understand we don’t, and it would be very helpful to know. If they asked, and people said, “We don’t care what information you provided or in what digital format, we’re not going to read this because we just don’t care,” that’s one thing. But if they came back and said, “You’re talking too much about this when I’m actually interested in that,” then you can make changes and probably increase your open rates. Did they do any other research, into the reasons that people may not be opening it? We don’t know. Was it going to their spam folder, for example? Was it reaching them at all? Did it have the appropriate kind of subject line that was going to entice people to open it? Did they do A/B testing on their subject lines? There are so many questions about why the digital version didn’t succeed. Will a print version succeed? Well, maybe. The councillors kept over and over again pointing to older residents, which is a reminder to segment your audiences. The debate about digital versus print is sometimes hiding the real question, which is, who are we trying to reach? Now, you and I are in our seventies, and we are digitally savvy. Our work lives involved all of this stuff. Neville Hobson: Digitally native. Shel Holtz: Yeah, we are. We’ve been working online since what, the 1980s? Neville Hobson: The ’80s. Shel Holtz: Yeah. So I don’t buy this “older people only read print.” I think that may have been true 30 years ago. But this is what these councillors seem to believe. And as long as that’s their belief, it does allow us to remember that segment, and who we are trying to reach, and who’s more likely to pay attention to what kind of content. But the question that I really have is, why in the world wouldn’t you do both? Accommodate the people who would rather get print and the people who would rather have digital, and let the people who are reading digital opt out of print so you can save a little money, for goodness’ sake. I graduated from college in 1976. I get a four-color magazine from my university four times a year that goes immediately into the recycling bin. It looks like it is well written, it looks like it is beautifully designed, and I simply don’t care. I just don’t have the time or interest. I have no connection anymore to my university beyond some of the people I went to school with there. I have no time to read the Atlantic Monthly that I pay money for. I’m not going to take the time to read this, so it goes straight into the bin. Wouldn’t they like to know that, and stop sending it to me and reduce the cost of their print run? So yeah, I think there are ways to manage this stuff. You know I’m a fan of print. You know what I think the advantages of print are, especially for the people who are going to take a minute to at least flip through it and go, “My goodness, I didn’t expect to find this article here.” That hardly ever happens online, because you get what you’re looking for, and print allows that serendipitous discovery of really interesting or important content. I wish I could send a print magazine to the homes of my employees. You know why? Not only would they flip through it, and you know what employees look for first when they’re flipping through a magazine: pictures of people that they know. But their families would get to see it and suddenly feel like they’re a little bit more a part of the company their husbands, wives, fathers, and mothers are working for. I think there’s tremendous value in the tactile nature of print. But does that mean it’s necessarily going to work in this instance, without the research to figure out what people want to read about, what people need to know about, how to ensure they’re going to pay attention to it? This all sounds to me like a research failure, and I would really need to know more about what research they did. They’re also going to need to do research to figure out if the print publication is working. They’re going to need to ask. Neville Hobson: Yeah, I agree. It’s a shame that there isn’t more information. I didn’t dig any further than that. In fact, the links to the two publications in Northern Ireland that had the story are in the show notes for this episode, so you can read more detail there. But not the answers to what did they do, why did they do this, why didn’t they do that, did they do research, et cetera. I’d also be keen to know of any listener in Northern Ireland who has any insight into this story. If you’d like to share your insight with us, we’d really like to know that. Shel Holtz: Yeah. And I’ll leave this report with one thought: what a great opportunity for human-led design. Because the one thing about print is that you can’t escape its notice. Even if it comes in the mail, you go through it quickly and you see it. And how good is the cover design, right? That becomes vital to people stopping and going, “Maybe I’ll flip through this.” It’s so easy to skip a subject line in a list of today’s email in your inbox. It’s harder to skip that print publication when you’re holding it in your hand and the cover is in your face. It had better be a good cover, or it’s going into the recycling bin. Neville Hobson: Your comment about your university magazine I found quite interesting. If you’ve been getting this thing for years, and each time you stick it in the recycling bin, don’t they email subscribers occasionally saying, “We’d like your views about the magazine, do you like it?” Or I guess not. Shel Holtz: No, no. I occasionally get one from the journalism department, and I’ll pay attention to that, first of all because it will report on people that I know, and second because I am very interested in what they are teaching journalists these days in university, especially since many of them are going to come into corporate communications. But the one from the university that talks about all the other departments that I don’t care about? Nope, don’t care. Well, some listeners may think that I have saved the most interesting item for last. The 2026 AI Adoption Report from Wharton Human-AI Research and GBK Collective was published on October 13. It’s the fourth annual edition. It is long, and it is full of data on ROI and agents, so I’m going to try to stick to just what matters to us as organizational communicators. They asked about 1,400 full-time employees at U.S. private-sector companies with more than a thousand employees. Those were the people who were surveyed in July. About a thousand were managers and above. This is the first year they also surveyed 409 entry- and mid-level employees, which is great, because that’s where it gets interesting. In the report’s own words, there is no group in this study where managers and the employees they manage describe the same working environment. I want to say that again: there is no group in this study where managers and employees were aligned. So, the numbers. 79% of managers and above say leadership has provided a clear long-term AI vision. Among entry- and mid-level employees, it’s 64%. 84% of managers say managers are empowered to lead AI change. Employees say 65%. And the biggest gap of all is training. 78% of managers say employees get adequate AI training. Only 56% of entry- and mid-level employees agree. There’s also a general alignment measure: 39% of managers describe an organization that clears four or five alignment factors for employees; for employees, it’s only 26%. Now, the report doesn’t have a section dedicated to communication, and probably should, but a gap where leaders believe they’ve explained the vision and provided training, and employees say they haven’t, is pretty clearly a communication problem. We have seen this pattern before. It’s the “we told them” syndrome. The sentiment numbers say the same. 84% of managers say their view of AI has improved over the past year. For entry- and mid-level employees, it’s 68%. For a positive impact on society, managers are at 76%, employees at 55%. And 46% of entry- and mid-level employees worry their own skills are declining from AI use. Now, that fascinates me. They fear that their own skills are declining because AI is doing the work. The report is careful to say, and this is a quote, “far from a backlash against technology,” but it’s not the same experience as the one that leaders are having. So let’s move on to the business results. Companies using AI in a way the researchers call “transformational” are far more likely to report strongly positive ROI: 67%, versus 19% for companies whose AI use isn’t described as transformational. Departments with strongly positive ROI were also more likely to have changed their management structure because of AI, 64% versus 47%, and they didn’t report more layoffs or hiring freezes. A few other correlations. Among organizations with a newly designated chief AI officer, 58% report strongly positive ROI, versus 8% with no such role. Those standardized on a single approved platform, 50% versus 9% for those still experimenting. Again, those are correlations and not causations. One more finding, on agents. Two-thirds of departments say they use AI agents, but only 17% let an AI agent finish a task without a person approving each step. Brian Smith of GBK says most companies are, quote, “paying for autonomy and then reviewing every action.” So what do we do with this? Well, and this is getting to be a litany: don’t assume your message has landed. Measure the gaps. Ask employees the same questions leaders get asked. Is the vision clear? Is the training adequate? Do you know what you’re allowed to do? If you find the same gap Wharton found, you have a case. Second, claim a role in AI training communication. Department leadership gets named for user training by 51% of respondents, the C-suite by 30%. Communication isn’t on the list. Communicators who can make the training findable, practical, and understandable will win. They’ll matter. Third, equip managers. There’s that message about managers again. They’re the channel employees actually trust, and the data suggests they’re more optimistic than the people they manage. Give them the real questions employees are asking, not just talking points. Fourth, be honest about jobs. 37% of managers say AI has led to staff reductions, and they expect fewer entry-level hires. Employees notice when you’re silent about that. And last, govern what you’re communicating. If your company is adopting agents and platforms, the communication plan for who’s accountable and what the rules are belongs right there with the technology plan. There’s a lot there, Neville. What jumped out at you? Neville Hobson: There is a lot, Shel. I haven’t read the report; it’s big. But I did pay attention to the key takeaways on the page they posted on the website describing the report. A couple of things from that jumped out at me, related to something you mentioned about the chief AI officer. If you look at the acronym, CAIO, I think it’s fabulous, absolutely fabulous. Shel Holtz: Ha! Ciao. Neville Hobson: So it’s interesting that someone with dedicated AI ownership, says Wharton… Well, they may say more about that in the report. I’d like to know what they mean by “dedicated AI ownership.” Is the person’s prime role this, nothing else on their plate they’ve got to pay attention to, or what? That would be helpful to know. But 58% of organizations with someone in that role report positive ROI. Again, it’s only 8% for a company that doesn’t have anyone with a dedicated role. Well, there’s good evidence of what you should be doing in an organization, if you’re able to. It may well be that you need to have someone with that role as part of something else he or she is doing as well, because you may not have the resources to have someone just dedicated to that. That would be better than not having anyone, I would say. The bit about agents, where they’re putting steps in place to check everything at each stage, sounds counterproductive, but it could well be that those doing that are going to say, “I told you so, these agents are dangerous,” if you look at what’s been written in the tech press over the last couple of weeks. I remember when we talked about this specific topic in one of our short episodes earlier in the year, about the growth of agents and how they’re going to take over various things in organizations. Largely that’s happening. But we’re now seeing a strong pushback based on some of the scare stories. For instance, I read one in the Wall Street Journal, I think it was, about AI agents gaining access to people’s bank accounts without permission. And you’re thinking, this plays into the reporting about AI taking control and “we’re all going to die.” It’s that kind of talk. So I think that makes it inevitable that you’re going to have big handbrakes on some of these things without oversight. But again, determining what’s best there is the CAIO’s job, I would say. From what I read about this, and hearing what you’ve explained, what Wharton calls “adaptive organizations,” there are some really good examples here of what adaptive organizations do differently from those who are not thinking about these developments. So I think there’s plenty here. I’m not sure I’ll have time to read the full report, but I see there’s an executive summary. I’ll download that and see what it says. But it’s interesting, Shel, that this survey has credibility, I think, and this kind of study is worth paying attention to, it seems to me. Shel Holtz: I dropped the whole report into Claude and asked it to extract and summarize the elements that would be relevant for communicators, and that’s how I crafted the report I just delivered. I’m glad you focused on the chief AI officer. I was really fascinated by this particular data point, for a number of reasons. We talk all the time about companies creating the “chief blank officer” role for trendy things. I think we just recently mentioned that there were companies that had chief metaverse officers there for 15 minutes. But in this case, I think it makes sense. There are a lot of companies that are hiring a senior AI person, probably sitting in the IT department. But are they speaking strategically to the organization about the non-IT parts of this? We have reported on data that said there are CEOs who have decided that AI is so important that they are becoming the leader of the AI effort. But they’re speaking to employees and to other stakeholder audiences about so many other topics that the AI stuff may get lost in there. If you send the message to your employees, and frankly to outside audiences who are interested as well, that this is such an important thing in our organization that we have elevated it to a board-level officer position, with all of the regulatory responsibility that goes along with a true officer position, then people pay attention. That person has credibility when they speak, and employees are going to listen, as opposed to hearing some of it from the CEO and some of it from HR and some of it from legal and some of it from IT, and “what do I make of all of this?” It’s easy for me to see why employees in an organization with a chief AI officer feel better about what’s happening and understand it more than in organizations that haven’t named one. Neville Hobson: Yeah, absolutely. I agree with you. Although I have to say, the acronym stuck in my mind. I can see that: “Hey, ciao, ciao, ciao.” Shel Holtz: Yeah, ciao. Well, you could always go with the U.S. government’s insistence now that we call it superintelligence, and that would make it a chief SI officer. Neville Hobson: Oh my God. Shel Holtz: It’s a whole other topic. Neville Hobson: Yeah. Let’s not talk about the midterms. Okay, that’s a big topic. So I think that’s a great report, Shel. I’m going to take a look at that executive summary to understand what they’re saying here. So thanks for sharing it. Shel Holtz: My pleasure. And that will draw to a close this episode of For Immediate Release, Episode 533, our long-form episode for October 2026. Our next long-form episode is scheduled to drop on Monday, November 30th. Neville, you and I will record that on Saturday, November 28th, right after Thanksgiving here in the U.S., anyway. Neville Hobson: Yep. Shel Holtz: So I look forward to talking to you then. But of course, we will be recording some shorter midweek episodes between now and then. I hope you will all subscribe. If you’re not already subscribed to the podcast, we’ve already let you know where to leave comments. Your ratings and reviews are of tremendous value to us, and we are immensely grateful for the time and effort that you take to do that as well. So until our next short midweek episode, that will be a 30 for this episode of For Immediate Release. The post FIR #533: The Two Distinct Realities of AI Adoption appeared first on FIR Podcast Network.