Episode 450Product MarketingOrg DesignMessaging Strategy

Why product marketing teams should be structured like newsrooms with Mike McGee

Mike McGee, Director of Product Marketing at Vantaca, argues that when your G2 category has 97 listings and the category average is 75, sounding like everyone else is a death sentence — so he is building his PMM team to look less like a traditional org chart and more like a digital newsroom, with product marketers assigned to specific customer roles the way reporters are assigned to beats. In this Content Amplified episode, Mike walks through where the idea came from (Nilay Patel's Decoder, specifically the Brian Chesky episode on how Airbnb blended product, PMM, and program management), the internal precedent at Vantaca (support and implementation already reorganized around customer roles instead of platform modules), and the Seth Godin 'who's it for, what's it for' lens he uses to pressure-test every messaging decision. He explains why selling at the executive buyer is the easy part, and why life-cycle marketing falls flat the moment you try to talk to every persona at once with the same voice. Mike also gets honest about when not to overhaul an org: look at what is predictable and replicable first, find the gaps, and only do a major restructure when there is no tenable way to get from where you are to where you want to go. His closing test for every team decision is whether the team is serving its customers to the utmost of its potential.

Mike McGee

Mike McGee

Director of Product Marketing, Vantaca

20 min

Key Takeaways

  • 1Stop structuring PMM like your competitors — if you copy the traditional functional-specialty or product-management-pod org chart, you also inherit every pitfall that comes with it, and in a 97-listing G2 category like community association management, that is a death sentence for differentiation.
  • 2Use the digital newsroom as your model: assign product marketers to customer roles the way reporters are assigned to beats, layer editorial oversight on top, and treat persona-based messaging as the editorial product itself rather than a deliverable that comes after the org chart is set.
  • 3Borrow from Nilay Patel's Decoder — Mike specifically points to the Brian Chesky episode where Airbnb restructured product management, product marketing, and program management into a blended model — and use it as proof that 'the rules don't apply' is a viable operating posture, not a slogan.
  • 4Pressure-test every messaging decision through Seth Godin's 'who's it for, what's it for' — at Vantaca, that lens is what forces clarity with product teams and internal stakeholders about the stated goal and outcome of any go-to-market motion before resources get committed.
  • 5Do not restructure for the sake of disruption — start by inspecting what is predictable and replicable in the current org, find the gaps, and only do a major overhaul when there is no tenable path from where you are to where you want to go, because forced change with no grounding will backfire.

About this episode

When your G2 category has 97 listings and the average is 75, sounding like everyone else is a death sentence. Mike McGee, Director of Product Marketing at Vantaca, is building his PMM team to look less like a traditional org chart and more like a digital newsroom — product marketers assigned to specific customer roles the way reporters are assigned to beats. In this episode, Mike walks through the inspiration (Nilay Patel's Decoder, the Brian Chesky episode on how Airbnb blended product, PMM, and program management), the internal precedent at Vantaca (support and implementation already reorganized around customer roles instead of platform modules), and the Seth Godin 'who's it for, what's it for' lens he uses to pressure-test every messaging decision. He also gets honest about when not to overhaul an org: look at what is predictable and replicable first, find the gaps, and only do a major restructure when there is no tenable way to get from where you are to where you want to go. If you are scaling a PMM team and tired of inheriting your competitors' pitfalls, this one is worth your time.

Topics covered

  • PMM org structured like a digital newsroom
  • Reporters on beats vs. functional specialty teams
  • Differentiation in a saturated G2 category
  • Seth Godin's 'who's it for, what's it for'
  • When to restructure vs. patch the gaps

Notable quotes

If you look at our G2 category, there are, I think last I looked, there was 97 listings in our category alone. I think the average is somewhere around 75 or 80. How does a buyer evaluate all those options and how do you make sure you're the one that stands out from the pack?

Mike McGee(0:02)

If you do things the way that everyone else is doing them, especially the way your competitors are doing it, you also tend to sort of inherit all the trappings and the pitfalls that everyone else encounters.

Mike McGee(4:46)

I always come back to just this whole Seth Godin-ism of like, who's it for, what's it for?

Mike McGee(5:35)

You don't really want to force a big change on your team just for the sake of disruption. I think that could easily backfire. Folks don't feel grounded. They don't feel bought into the mission.

Mike McGee(18:18)

Resources mentioned

  • Framework

    The Newsroom Model for PMM

    Structure your product marketing team the way a digital publication structures its newsroom. Assign each PMM to a specific customer role — the same way a reporter is assigned to a beat — so they own the language, the pain, and the lifecycle of one persona end-to-end rather than ping-ponging across modules. Layer editorial oversight on top to make sure the persona-by-persona coverage adds up to a coherent brand voice. The output is messaging that creates deep empathy with each audience instead of generic platform copy that lands the same with everyone and resonates with no one.

  • Framework

    Who's It For, What's It For

    Adopt Seth Godin's two-question filter as the standing pressure test for every messaging and go-to-market decision. Before any campaign, page, or launch gets resources, force a clear answer to who specifically the work is for and what specifically it is supposed to accomplish. The point is not to slow work down — it is to surface ambiguity early, especially in cross-functional conversations with product teams where 'we need to talk about this' is often code for five different unstated goals. Clarity at this layer is what makes the newsroom model executable instead of aspirational.

  • Checklist

    When to Restructure a PMM Team

    Before you blow up the org chart, walk through Mike's diagnostic. First, inventory what is currently predictable and replicable — those are the load-bearing parts of the team you do not want to disrupt. Second, identify the gaps where outcomes are inconsistent or where messaging is falling flat for specific personas. Third, ask whether the gaps can be closed inside the existing framework with new hires, new swim lanes, or new rituals. Only if there is no tenable path from where you are to where you want to go should you do a major overhaul, because forced disruption without a grounded reason will erode trust faster than the old structure ever did.

Full Episode Transcript

Mike McGee00:02If you look at our G2 category, there are, I think last I looked, there was 97 listings in our category alone. I think the average is somewhere around 75 or 80. How does a buyer evaluate all those options and how do you make sure you're the one that stands out from the pack?

I think ultimately that boils down to just the whole what's in it for me of the whole thing. Really, we're trying to earn someone's time and attention and we're hoping to affect change. And so the way that you kind of present all that and talk about yourself, I think you really have to be rigorous in how you organize that messaging and how you kind of come to the table with who's going to really create that deep empathy with the audience.

Benjamin Ard01:08Welcome back to another episode of Content Amplified. Today I'm joined by Mike. Mike, welcome to the show.

Mike McGee01:13Thanks for having me.

Benjamin Ard01:14Yeah, Mike, I'm excited. This is going to be a fun conversation. In the 400 plus episodes we've done on Content Amplified, we have not covered this subject, so I'm excited. I'm going to put that little teaser out there, but before we dive into it, Mike, let's get to know you, your background, your history, everything so that the audience can kind of know you before we get into the subject for the day.

Mike McGee01:34Yeah, absolutely. My name is Mike McGee. I'm the director of product marketing at Vantaca. Vanica is leading the connected future of community association management and we do that through technology, pro services and education.

Benjamin Ard01:48Very cool. I love it. How did you get into marketing? How did you get into the space? Tell us a little bit about your background.

Mike McGee01:53Yeah, absolutely. So I got into marketing through customer success. A long story to how I got to that point. But about eight years ago or so I started at a company that was in property management software. I was a customer success manager really managing the relationships of some of our largest customers. And I did that for a few years. It was really enlightening and impactful for me to really kind of understand our customers' goals and aspirations and trying to figure out how to help them take those goals and map them to the tools that we had available to them such that they were really able to see the full value of the investment that they put into the software, right? So I had done that for a few years. I was really into these one-on-one relationships and figuring out how to message things in certain ways that would break through to create that sort of change that you're looking to instill in someone to help reach these mutually beneficial goals, right? So as I was thinking about what the next step would be in my career and what kind of things I wanted to do and how I wanted to leverage all the stuff that I had already learned to do, I really wanted to get closer to building things and being part of how we bring some products to the market and services and how we talk about those things. I think that was kind of a skill of mine as a customer success manager. So I was thinking, how do I take what I do on a one-to-one basis and bring that on a one-to-many basis? That was kind of the impetus for getting into marketing. But yeah, from there it's been kind of a roller coaster and it's been a few years now of constant change and constant fluctuation and really just trying to understand how I can make the most impact at any given time given the circumstances.

Benjamin Ard03:45I love it. That's amazing. Mike, I'm excited. This is going to be a fun conversation. This is something I don't have a ton of expertise in, but I'm excited to learn more about. What we're going to talk about is PMM org planning. So to kick things off, when you think about the traditional way of organizing PMM teams, why do you think that traditional way of structuring these teams may be broken?

Mike McGee04:05Well, two things. So for one, I don't know that I would necessarily call myself an expert on this either. I'm a relatively new leader to the space. I just started with FANICA back in May of 2025. So we're still working through how to scale this properly. But all that being said, I don't know that fail is even necessarily the right word either. I do think a lot of companies and team structure can work just fine. It depends on the product that you're selling, depends on the depth of the solution that you have, the market dynamics, the people involved, the stage of the company's trajectory, all that kind of wrapped up into one. As much as I like to break the rules and sort of go my own way, I think there is obviously some merit to the tried and true things, as much as I don't tend to follow that. The way things are done, they're done because they tend to work or they wouldn't be rules in the first place. Right. So I get all that. But I also believe that if you do things the way that everyone else is doing them, especially the way your competitors are doing it, you also tend to sort of inherit all the trappings and the pitfalls that everyone else encounters. So for us, we have a really highly differentiated product. And it's sort of a product marketer's dream in that sense. To stand out and clearly articulate how we're different, we really can't talk like everybody else and we can't do the things that everybody else is doing. So our competitors, they can say that they solve a lot of the same problems just by virtue of being a provider of community association management software. But ultimately I think it's really important to hold how you work up to scrutiny and the rules don't necessarily have to apply. We can kind of do whatever we want, right? So I always come back to just this whole Seth Godin-ism of like, who's it for, what's it for? But ultimately it's really just trying to be really clear with product teams and everyone internally about what are the stated goals and outcomes and what exactly do we want to happen? So I think it just really kind of boils down to clarity.

Benjamin Ard06:06I love that. And I love your definition. Like there are things out there. The traditional way isn't broken. People do it for a reason. That's a great place to be, but it's interesting that you're also saying, hey, let's look at the competitive landscape. And if we're doing exactly what our competitors are doing, we're going to have the exact same outcomes. We're going to have the same structures. We're going to talk about things the same way. We're going to be kind of one of the companies out there, just like everyone else. But if our objective is to be different, we're going to have to be different in a few different ways. And I like the way of looking at that and saying, it's not broken, but if we want to be different, we're going to have to be different. So I think that's really cool.

Mike McGee06:44Yeah. And I would add to that too. I mean, this is something that we talk about quite a bit with new sales reps, new business development reps. If you look at our G2 category, there are, I think last I looked, there was 97 listings in our category alone. I think the average is somewhere around 75 or 80. How does a buyer evaluate all those options and how do you make sure you're the one that stands out from the pack? I think ultimately that boils down to just the whole what's in it for me of the whole thing. Really, we're trying to earn someone's time and attention and we're hoping to affect change. And so the way that you kind of present all that and talk about yourself, I think you really have to be rigorous in how you organize that messaging and how you kind of come to the table with who's going to really create that deep empathy with the audience.

Benjamin Ard07:33I love that. That's cool. So when we were emailing back and forth about finding a subject for today, this theme kind of came up. And you talked about publication models. And you use that for inspiration. So for my next question, what are publication models? What do you mean by that? And what are the traits that you're looking at from these publication models that you feel like could really help benefit a marketing org?

Mike McGee07:55It's an interesting one. And I would say that I'm sort of going back to scratching my own personal itch, I guess you could say. I had originally in the early days of my foray into tech, I really got deep into publications like The Verge and Wired and, you know, you name it. There's so many different opportunities for how these publications kind of present themselves. And one of the things that really stood out to me, and this is kind of a plug, I guess, but like Decoder from The Verge with Nilay Patel is one of the shows that I just, I listen to every episode. Nilay has said multiple times that it's sort of a show about org charts. There's always a question around how are you structured? Who does what? Kind of really in the weeds discussions. And I find it super beneficial just to hear how other leading companies are thinking about these things. And one in particular episode stood out was the one with Brian Chesky from Airbnb, or at least the most recent one. I think he's been on a few times, but he had been talking specifically about how the team had been, how they restructured their product management and product marketing and program management and sort of blended these roles into a unique need for their business. And just hearing the thought process behind it was something that just started the gears turning in my head a little bit. And not to say that we're emulating that specific model. It was just a way to think, again, the rules don't apply. We can do whatever we want really. And there are structures around these sort of things, but when I was looking at say how digital newsrooms are structured, it really started to become clear that the way that our business at least operates has a lot of parallels with, say, reporters and their beat and editors and all these different layers of persona based messaging. So that's something that really stood out to me as something to chase down and inspect. Simultaneous to all this, our internal teams had started going through a transition sometime last year. So our customer support team, historically we have a broad platform, right? So it's kind of a monolithic set of modules and configuration and different opportunities to learn and master certain workflows. And when you are a support agent on the other end of the phone who has to know every tiny little detail of the platform, because you never know what the call is going to be on the next call on queue, that's a lot. It's a lot to ask people. It creates a long ramp up time to become kind of an expert in the software. And it really makes it challenging to kind of maintain that staff over time. And the really good people will obviously, they'll kind of move into new roles and things like that. So what they ended up doing was they reorganized the team around the roles that exist on our customers' side. So you would get a functional specialist based on your particular role in your company who knew exactly what to say and how to say it and could speak your language and really only was responsible for being an expert in that one area of the software. It works so well that we've expanded that into our implementation and onboarding programs. And now same type of thing where when you're going in through an implementation, you are talking to people who know your job just as well, or maybe not just as well as you do, but they know how the software maps to your specific job. And that started to really feel like it spoke to a lot of our product differentiation to me. And I started to realize that as we scale the product marketing function, it would be really cool to basically have product marketers who know the roles on the other side. Beyond just sort of like the executive buyer layer, I think historically we've done a lot of selling directly at the buyer and we say, this is what the platform can do. And here's the ROI and all of that. But for individuals who are using the software after it's been bought and implemented, some of that life cycle marketing can fall flat sometimes when you're trying to message to everybody. So this is something that I'm really feeling passionate about in that sense to make sure that every persona involved has someone that is speaking directly to them and can tell them what they really should care about as we're increasing release velocity and really trying to solve things on a granular scale.

Benjamin Ard12:33I love that. I think that's so cool. You're organizing the whole business around who are the users, who are the people that are engaging with our business and how can we provide them the most relevant support, most relevant content, onboarding. I mean, all of these different functions to say, okay, great. We know you inside and out and we're going to provide this value. So with this change as everything is kind of going down this road, how is this impacting things? What is the goals that you set? How is it making a difference? What are you feeling the difference in the org structure is doing for the team?

Mike McGee13:07Well, there's a couple of changes that I see afoot. We're scaling the team, right? So I think as of right now, I have two very talented members of my team who are kind of holding down the fort on a lot of these things. We'll have hired maybe by the time this is out, three new people on our team. And that was part of the impetus for why are we doing this right now. As we grow this team, as we start assigning work, how do we figure out exactly what people's individual swim lanes are? I believe that the impact around this structure and strategy will lead to a deeper level of empathy for our users. It will allow for a stronger sense of ownership for individuals on our team to really kind of just really dig in and fully grasp the people on the other side of the computer. One thing I really love about the company and our customers is every time you ask our customers what they love about working, or not even that, you just ask them broadly, what is your experience with FANICA? Every single answer is always about the people. Much more so than the products and the services and the solutions and the, you know, et cetera. And I really liked this approach of just really putting faces to names and saying, you know, as we reach out through email marketing, as we put on webinars, like the person who knows your role is a very specific person. And we've kind of gotten away as a company from using the marketing team as the email sender, right? It's a person and we get all the out of offices as well. So there's all the failings of that strategy. Regardless, I think ultimately structuring around, structuring our entire business around how our customers do business really speaks to our origin story as a company. Ultimately a lot of competitors in the space were sort of born out of different industries, whether they were originally a tech platform or they were in a different vertical and had expanded or came from a sort of tangential industry like banking. And our system was built by a community management company that tried everything in the industry and just nothing worked the way they thought it should. So in a lot of ways we have that grounded approach to, we understand what the challenges are traditionally with community management software. And we understand how to solve that better than anyone else. That's kind of a lot of what we're after with putting the right people in place so that all these problems are solved.

Benjamin Ard15:53I find it fascinating because there's this huge trend where businesses are really putting, like you said, a face to a name. They're letting their internal teams really have the microphone. They're letting them send the emails. They're letting them be on the webinars. And it feels like people are building personal relationships. In this day and age of AI, I feel like it's even more important for people to say, I want to know the person behind the company. And we're seeing this trend. I love that the organization naturally has shifted into a position where, you know, the persona. And now they're like, sweet. I know the three people in the company, you know, on the support side, the implementation side, the product marketing side. I'm seeing the same three people all the time. And I know them by name. I know their little personality quirks. I know who they are, but they talk about only me. I feel like I have a relationship with them. Okay. I think this is fascinating. I love how you're organizing the org for that. Mike, we're almost out of time. So one final question. What did the transition look like? And I know you're going through the transition. For anyone in a business who's asking themselves, hey, maybe we should look at this, but I don't know what getting from A to B is going to look like, what the process will be, what steps we need to take, any kind of pieces of advice, things that you've seen in transitioning the org into that different kind of a system.

Mike McGee17:19Yeah. So what I will say around product marketing is, you know, I don't feel like I've ever been in a place where my job felt very static, right? So product marketing is kind of change in and of itself. You're kind of always trying new things and doing things differently. Obviously teams can be structured very differently depending on the needs of that business. So you can go by discipline and functional specialty. You can go by scrum team or product management pods or vertical or market segment. None of those are necessarily wrong. You just need to try things on for size and see how well it connects to your customers and to your business. The other thing I would say is I don't necessarily know how easy it would be to execute a big change like this in some companies. I'm fortunate to be in a company that has its origin story so deeply rooted in differentiation. And I do think I'm afforded some trust to kind of color outside the lines a bit and deliver on some brand promises in ways that are less tested and less proven. But I think, if I was thinking about like what that change could look like, or just ways to start inspecting that, I think the first place I'd look to is more like what's working well and what's predictable and replicable. You don't really want to force a big change on your team just for the sake of disruption, right? I think that could easily backfire. Folks don't feel grounded. They don't feel bought into the mission. So I would kind of look more at like the gaps and inspect whether you can fit that into your existing framework. And if you can't and there's no tenable way to get from where you are to where you want to go, then maybe a more major overhaul is probably worth thinking through. But ultimately I think it's really just important that you look straight at your customers and make sure ask yourself whether you are serving them to the utmost of your potential.

Benjamin Ard19:08Love it. That's awesome. Well, Mike, thank you so much for the insights and the great conversation today. It's been awesome. For anyone listening who wants to reach out and connect with you online, how and where can they find you?

Mike McGee19:18Probably LinkedIn is the best place to find me. Again, Mike McGee at Vantaca. But yeah, that would probably be the best place to go.

Benjamin Ard19:25Love it. For anyone listening, scroll down to the show notes, regardless of what platform you're on. We will link directly to Mike's LinkedIn profile. Click on the link, connect with Mike, say hello, say you're from the podcast. Be great to connect with him. Mike, again, thank you for the insights and a wonderful conversation today. I really do appreciate it.

Mike McGee19:42Thanks, Ben. I appreciate it.

About the guest

Mike McGee

Mike McGee

Director of Product Marketing, Vantaca

Mike McGee is the Director of Product Marketing at Vantaca, where he leads the team responsible for messaging and go-to-market in community association management software. Mike got into marketing through customer success, spending several years managing the largest customers at a property management software company and learning how to translate one-on-one relationships into one-to-many storytelling. He joined Vantaca in May of 2025 and is currently scaling the PMM team from two people to five. Mike believes in breaking the rules when the rules just inherit your competitors' pitfalls, and he comes back constantly to the question of whether the team is serving customers to the utmost of its potential.

Connect on LinkedIn

Continue Exploring

Story Drift Analyzer

Check how clearly your positioning survives across your website, content, and AI surfaces.

Try the tool

Get new episodes in your inbox

Join listeners who get episode summaries, key takeaways, and content strategy insights every week.

Frequently Asked Questions

Mike is careful to say the traditional structure is not broken — it works for a lot of companies and exists because it tends to deliver results. The risk shows up in a hyper-saturated category like community association management software, where Vantaca's G2 category has roughly 97 listings against a category average of 75 to 80. In that context, copying competitor org structures also means copying their pitfalls and trappings, and the messaging starts to sound interchangeable. For a product Mike describes as a 'product marketer's dream' on differentiation, sounding like everyone else is the actual failure mode.

Mike credits two inputs. The first is Nilay Patel's Decoder podcast — he calls out the Brian Chesky episode specifically, where Chesky walks through how Airbnb blended product management, product marketing, and program management into a structure built for their business rather than a generic SaaS template. The second is Vantaca's own internal precedent: support and implementation had already reorganized around customer roles instead of platform modules, with functional specialists who knew one role on the customer side deeply rather than every workflow shallowly. Seeing that model work for support is what convinced Mike to extend it into PMM.

He treats it as the standing pressure test for every messaging decision and every cross-functional conversation with product teams. The point is to force clarity on the stated goal and outcome before anyone commits resources — what exactly do we want to happen, and who specifically is this for. Mike notes that internal alignment usually breaks down because 'we need to talk about this' hides five different unstated goals across stakeholders. The two-question filter surfaces that ambiguity early and is what makes the newsroom-style persona ownership executable instead of aspirational.

Mike's strong default is patch first, restructure last. He recommends starting with what is currently predictable and replicable in the team — those are the load-bearing parts you do not want to disrupt — and then inspecting where the real gaps are. If you can close the gaps inside the existing framework with new hires, new swim lanes, or new rituals, do that. Only when there is no tenable path from where you are to where you want to go does a major overhaul make sense, because forcing change for the sake of disruption tends to leave the team ungrounded and erodes trust in the mission.

EP 45916 min

Why audience-first content beats cranking out specs and features with John Henkel

with John Henkel

Stop cranking stuff out. That is the first move John Henkel wants every product marketer to make before they touch another asset. In this Content Amplified episode, John, who leads product marketing for the AV segment at Netgear, shares how he keeps content tied to a real user and a real purpose instead of a list of specs. John walks through where engineering-led companies drift away from the problem they actually solve, how he uses trade-show conversations and weekly sales-team meetings to validate the user before a piece ships, and the trick of picking up the phone to get integrators invested in feedback so they tell you what is wrong instead of saying 'looks great.' He also shares the simple spreadsheet audit he is running right now at Netgear, mapping every asset to its audience and desired action so the team can see what to keep, kill, or rebuild. If your content calendar is full but your sales team is not asking for what you ship, this one is for you.

May 28, 2026Listen
EP 43518 min

How to Turn Data Into Narratives People Actually Remember with Kirsten Von Busch

with Kirsten Von Busch

Data is only interesting if it tells you what to do next. In this episode of Content Amplified, Kirsten Von Busch, Director of Product Marketing at Experian Automotive, shares how her team turns one of the richest datasets in the auto industry into content that marketers, dealers, lenders, and OEMs actually use. Kirsten walks through her 'treat it like a science experiment' approach: start with a hypothesis, let the data confirm or kill it, then build a narrative people can act on. She explains when brand messaging still matters, how partner stories add proof to the data, why you have to publish the same insight in three or four different formats, and which metrics actually tell you if the content hit.

April 16, 2026Listen

Get new episodes in your inbox

Join listeners who get episode summaries, key takeaways, and content strategy insights every week.