FX

Frank X. Shaw

Things Frank Says on Podcasts

Where to Find Them

Frank X. Shaw has been a guest on GeekWire , Doing Customer eXperience Right‬ In The AI Era | Stacy Sherman and On Top of PR with Jason Mudd .

Recently: “Exit interview: Microsoft’s comms chief on CEOs, reporters, what he got wrong, and stories that stuck” on GeekWire (October 2026); “Shaping the future of PR with AI: Insights from Microsoft’s Frank X. Shaw” on On Top of PR with Jason Mudd (March 2026); “95. How AI Is Transforming Communication & Customer Service with Microsoft Leader, Frank X Shaw” on Doing Customer eXperience Right‬ In The AI Era | Stacy Sherman (July 2023).

What They Said

“You're bad at your job because you think your job is getting positive stories and you should be thinking about your job as having interesting stories that showcase something about the company. And sometimes those are going to be less positive, but they're going to be more memorable.” — Frank X. Shaw, GeekWire

Shaw recounting what a reporter told him during a heated phone call early in his time at Microsoft; he says he pulled his car over to take it. He thought the reporter was wrong at first, then decided he was exactly right.

GeekWire · 2026-10-24 Permalink → Listen →
GeekWire Around 26:06 into the episode
Speaker 4

…was Rob Guthback because he would call me all the time. And I would say, oh my God, I have to call Rob Guthback. And so she thought his name was Rob Guthback. But anyway, I mean, I was driving through Madison Park and I had to pull over because we were yelling at each other about this story. Were

Todd Bishop

your kids in the back?

Speaker 4

No, they were not in the back. This was just me solo, but I figured I really needed to pull over for this one. And what he said is he said, like, you're bad at your job because you think your job is getting positive stories and you should be thinking about your job as having interesting stories that showcase something about the company. And sometimes those are going to be less positive, but they're going to be more memorable.

Frank X. Shaw

Whoa.

Speaker 4

And I was like, you're so wrong. And then I went off and I thought about it. And I realized he was exactly right. And so if you're doing a really good job working with anybody who is reporting about the company in the broadest possible sense of the world, what you hope for is you hope that they are…

Mary Jo Foley

us an example. Like, what's a story that you feel like it was risky, but we did it. And we feel like even though it wasn't completely positive, it did do a good job reflecting the company.

Speaker names from our own diarization · position estimated from where the line sits in the episode
“And I did not say anything. And I didn't say anything because I couldn't figure out how it was in my area of expertise to have an opinion. I'm the comms guy. I'm not the business person. … And of course, we launched it. 43 days later, we pulled it.” — Frank X. Shaw, GeekWire

Shaw recalls a meeting where Microsoft's leadership went round the table on whether to launch the Kin phone, which he privately doubted would work. He now says he should have framed his doubts as brand risk, which was squarely his job.

GeekWire · 2026-10-24 Permalink → Listen →
GeekWire Around 43:54 into the episode
Speaker 4

…You know, I was new to the company. We had a meeting and it was at Mobile World Congress. We were in a hotel. We were in a big conference room at the top of the hotel. There were all the executives that are responsible for this thing sitting around the table. You know, Steve Ballmer was there.

Todd Bishop

Robbie Bach.

Speaker 4

…with this. And I didn't think we were going to be successful with it because we were later to the market and it was going to be more expensive than people thought because it required a data plan. So that, and so I said, like, I don't think we're going to be successful with this. And so everybody went around the table. And Steve said, should we do this? Should we do this? Should we do this? And I did not say anything. And I didn't say anything because I couldn't figure out how it was in my area of expertise to have an opinion. I'm the comms guy. I'm not the business person. You know, I'm not the technology person. I'm not the partner person dealing with Verizon and others. Right. So I'm just, I just happened to be in the room, so I didn't say anything. And of course, we launched it 43 days later. We pulled it. You know, it cost us a lot of money with and bad will with Verizon. And I think about that, thought about that later. And I said, what I missed is that this…

Todd Bishop

What about Nokia? Were you in on those discussions? I'm sure you were.

Speaker 4

Yes.

Todd Bishop

How do you feel about that in hindsight? And what did you think about it at the time?

Speaker names from our own diarization · position estimated from where the line sits in the episode
“Facts are easy to dispute. If you're going to dispute something, you can dispute facts. Narratives are sticky. And so you got to work a lot harder and a lot faster if there's a narrative out there that you don't like or you believe is inaccurate.” — Frank X. Shaw, GeekWire

Shaw looks back on Vanity Fair's "lost decade" story about Microsoft, which he says the company underestimated because it got little immediate pickup. Reporters then brought up the "lost decade" in every interview for years, and he says it took a new CEO to reset it.

GeekWire · 2026-10-24 Permalink → Listen →
GeekWire Around 49:38 into the episode
Frank X. Shaw

Tell us about the Vanity Fair piece. So for people who didn't

Todd Bishop

know, this was the Lost

Speaker 4

…that time was something that every reporter read. And so it became part of the perceived narrative of the company. And every interview, every reporter for the next four years would reference the lost decade. And so I should have seen that as a sticky narrative that needed to be fought. And this is the, you know, like, this is the point I was trying to make in my LinkedIn thing: is that you can, facts are easy to dispute. If you're going to dispute something, you can dispute facts. Narratives are sticky. And so you got to work a lot harder and a lot faster if there's a narrative out there that you don't like or you believe is inaccurate. And so it took us, you know, a new CEO to be able to sort of reset that.

Todd Bishop

It's funny because. Right around the same time, Amazon had a similar experience with the New York Times. And it wasn't exactly the same. And I'm not talking about the reporting tactic. This was the

Speaker 4

crying at your desk.

Todd Bishop

Yeah, this was the Amazon's quote bruising workplace. I still remember the word bruising from the headline. And again, the reporters did not use the tactic that you mentioned, but it had a similar effect where initially it was like, huh, that's probably one New York Times story. And it became an…

Speaker names from our own diarization · position estimated from where the line sits in the episode
“The idea that somebody came up with a product, we built it perfectly, and everybody loves it is just boring. There is no story there. And sometimes that's what we're asked to tell, a story of just an unimpeded march to greatness. It's like, that's dull. That's like the plane landed safely. Nobody cares, right? Except for the people on the plane.” — Frank X. Shaw, GeekWire

Microsoft's departing communications chief, in an exit interview, on the reporter who once told him he was bad at his job for chasing positive stories. He says he came round to the view that good coverage illuminates the company in a memorable way, and that always comes with tension.

GeekWire · 2026-10-24 Permalink → Listen →
GeekWire Around 26:41 into the episode
Speaker 4

…he said, like, you're bad at your job because you think your job is getting positive stories and you should be thinking about your job as having interesting stories that showcase something about the company. And sometimes those are going to be less positive, but they're going to be more memorable.

Frank X. Shaw

Whoa.

Speaker 4

And I was like, you're so wrong. And then I went off and I thought about it. And I realized he was exactly right. And so if you're doing a really good job working with anybody who is reporting about the company in the broadest possible sense of the world, what you hope for is you hope that they are going to create something that illuminates part of the company in a memorable way. And that always comes with tension, 100% of the time, comes with tension. And you have to embrace that because the idea that somebody came up with a product, we built it perfectly, and everybody loves it is just boring. There is no story there. And sometimes that's what we're asked to tell, a story of just an unimpeded march to greatness. It's like, that's dull. That's like the plane landed safely. Nobody cares, right? Except for the people on the plane. So if you stop and you think about that a little bit, it's like, what are you doing to illuminate a piece of the company in a memorable way? It opens you up to much more interesting conversations. Give

Mary Jo Foley

us an example. Like, what's a story that you feel like it was risky, but we did it. And we feel like even though it wasn't completely positive, it did do a good job reflecting the company.

Speaker 4

There's just so many of them. You know, I think about the New Yorker story that broke about OpenAI with Kevin Scott just after the blip happened. The

Todd Bishop

blip meaning Sam Altman's ouster.

Speaker names from our own diarization · position estimated from where the line sits in the episode