First-Time Marketing Manager: What No One Tells You Before You Lead a Team

Nobody hands you a manual when you become a manager for the first time. You get a title change, maybe a congratulations from your own manager, and then you’re expected to lead a team of people whose work you were doing alongside them last week.
In marketing specifically, this transition is particularly disorienting. Marketing roles are highly individual. The best content strategist, the sharpest demand gen analyst, the most effective brand manager — they succeed through the quality of their own thinking, their own output, their own creative judgment. That individual excellence is almost always what gets someone promoted into management. And then management asks them to stop doing the thing they’re excellent at and start doing something entirely different: enabling other people to do it instead.
Most first-time marketing managers are not told clearly that this is what’s actually being asked of them. They assume management is an extension of their individual contributor role, with some people oversight added. It isn’t. The job changes fundamentally, and the skills that made them excellent as individual contributors are not the skills that will make them effective as managers.
This article covers what that transition actually requires — not the corporate platitudes about leadership, but the specific adjustments that marketing managers need to make in the first few months and the mistakes that derail the ones who don’t.
The Biggest Mindset Shift: Your Job Is No Longer to Do the Work
The most important thing to understand about becoming a manager is the simplest and the hardest: your job is no longer to produce excellent marketing work. Your job is to produce excellent marketing results through a team of people doing the work.
This sounds like a semantic distinction. It isn’t. It changes almost everything about how you should spend your time, where your attention should go, and how you should evaluate whether you’re doing your job well.
As an individual contributor, you were measured by what you personally produced. Your output was visible, attributable, and directly connected to your reputation. Being better at the work made you more valuable.
As a manager, you’re measured by what your team produces. Your own output — the brief you wrote, the campaign you managed yourself, the analysis you personally built — is largely irrelevant compared to the aggregate output of the people who report to you. The manager who is individually excellent but whose team underperforms is failing at their job. The manager whose team consistently produces excellent work, even if that manager’s personal contributions are minimal, is succeeding.
This shift is uncomfortable for most first-time managers because it requires giving up the thing that felt good about the individual contributor role — the direct satisfaction of doing excellent work — and replacing it with something more diffuse: the satisfaction of building the conditions where other people do excellent work.
The managers who don’t make this shift end up doing their team’s job instead of their own. They take over the work when it doesn’t meet their standard, produce output that should be produced by the team, and create a dynamic where the team never develops because the manager is always filling the gaps. The team gets weaker as a result, because they’re not being challenged or developed. And the manager is exhausted, because they’re doing two jobs — managing and doing — with enough time and attention for neither.
The First 60 Days: What to Do Before You Try to Change Anything
The instinct when stepping into a new management role — especially one you’ve been promoted into from within the team — is to demonstrate leadership by changing things quickly. Restructuring how the team works, introducing new processes, fixing the problems you could see clearly as a peer but couldn’t act on.
Resist it for at least 60 days.
The reason is not that the changes aren’t warranted. It’s that you don’t yet have the full picture. You know the team from your peer perspective, which is valuable but incomplete. As a manager, you have access to information you didn’t have before — about each person’s development, their challenges, their career goals, the history of decisions that led to current structures. Making changes before you have that picture often means solving the visible problem while missing the actual one.
What to do in the first 60 days instead:
Have individual conversations with each person on your team. Not performance reviews — conversations. What’s working well in how the team operates? What’s frustrating them? What do they wish they had more support on? What are their goals for the next year? These conversations give you a much clearer picture of the team than any amount of observation, and they signal to each person that you’re interested in their experience, not just their output.
Learn what you don’t know. There are things about how the marketing program operates that you didn’t know as a peer — decisions made before you joined, historical context for current structures, external relationships that aren’t visible from your former vantage point. Find out what those things are before assuming the current way of working is wrong.
Establish your working style clearly but not rigidly. Tell the team how you like to work — how you want to be updated on projects, how you prefer to give feedback, what you need to see before approving work. Set these expectations clearly without over-systematizing everything in week one. The working relationship needs room to develop before it gets locked into formal processes.
Do less than you’re tempted to. The first 60 days feel urgent because the role is new. Most of what feels urgent isn’t. The things that genuinely can’t wait will be obvious. Most decisions, changes, and improvements can wait until you have the picture you need to make them well.
How to Set Expectations with Your Team
One of the most common failures of first-time managers is setting expectations poorly — either not setting them at all (assuming people know what’s expected) or setting them in ways that are so vague they don’t provide real guidance.
Clear expectations answer three questions for each person on your team: what does success look like in their role, how will you evaluate their work, and what does the working relationship between you look like.
What success looks like in their role. This is not a job description — it’s your articulation of what excellent performance looks like for this specific person in this specific role at this specific stage of the business. It should be specific enough that both of you could evaluate against it, and it should be calibrated to what you actually believe is possible, not to an idealized standard that nobody could meet.
How you will evaluate their work. What does feedback look like from you? How often? In what format? Will you review work in progress or only final output? Will you give real-time feedback or save it for scheduled conversations? People do better work when they know how they’ll be evaluated — not because they’re gaming the system, but because clarity about standards is genuinely useful information for doing the job well.
What the working relationship looks like. How often do you meet? What do you need them to communicate proactively versus what will you pull from them in regular check-ins? What decisions can they make independently and what do they need to bring to you? These norms don’t need to be exhaustive — they develop over time — but giving people a starting framework prevents the ambiguity that creates unnecessary anxiety in the first weeks of a new management relationship.
The Accountability Conversation You Need to Have Early

Accountability is not a comfortable topic for first-time managers, particularly ones who were promoted from within the team and want to maintain the ease of peer relationships. But it’s the one that needs to be established early, because it’s the hardest to establish retroactively.
The accountability conversation is not a threat. It’s a clear statement of what the working relationship expects and what happens when expectations aren’t met. It can be folded into the expectations conversation — it doesn’t need to be a separate formal moment.
The elements: I have clear expectations of what this role requires and what your performance should look like. I will give you regular, specific feedback on how you’re doing against those expectations. If I see a gap between where you are and where you need to be, I will tell you directly and give you the opportunity to address it. I expect the same directness from you — if you’re not getting what you need from me to do your job well, I need to hear that.
That last part matters. Accountability runs in both directions. A manager who holds their team accountable while not acknowledging that the team can hold them accountable has created a one-directional power dynamic that erodes trust. The best working relationships are ones where both parties can tell each other directly when something isn’t working.
Running Effective 1:1s
One-on-one meetings are the primary management tool — the recurring context where the actual work of managing happens. First-time managers often run them poorly, either turning them into status updates (a waste of the format) or skipping them when things get busy (a reliable way to lose visibility into what’s actually happening on the team).
A useful 1:1 is not a status update. You can get status through Slack, project management tools, and written updates. The 1:1 is for the things that don’t surface in those channels: how the person is actually doing, what’s blocking them that they haven’t raised elsewhere, what they’re thinking about their work and their development, and what’s coming up that they want input on.
A few structural principles:
The agenda belongs to them more than to you. Your direct report should own most of the 1:1 agenda — it’s primarily a space for what they need, not for what you want to communicate. If you have things to communicate, do it; but the 1:1 is not the right format for status reviews or top-down information that could be shared in another way.
Ask questions that produce real answers. “How’s it going?” produces “fine.” “What’s the one thing about the current project that’s most uncertain for you right now?” produces something useful. The quality of what you learn in a 1:1 is largely a function of the quality of the questions you ask.
Follow up on what was said last time. The fastest way to signal that 1:1s don’t matter is to start each one with no memory of what was discussed in the last. Keep notes. Reference them. The person you’re managing is telling you things that matter to them — treating those things as disposable destroys the value of the format.
Don’t cancel them. Canceling 1:1s signals that they’re low priority — which signals that the person’s development and wellbeing are low priority. When scheduling pressure is real, shorten them rather than cancel them. A 20-minute 1:1 is significantly more valuable than no 1:1.
Giving Feedback That Is Specific, Timely, and Doesn’t Damage the Relationship
The thing most first-time managers fear most — giving critical feedback — is actually the thing that builds trust the fastest when it’s done well. What damages relationships is not feedback. It’s feedback that is vague, late, or delivered in a context that humiliates.
Specific. Feedback that doesn’t identify what specifically happened is not useful. “The campaign brief wasn’t strong” tells the person nothing they can act on. “The campaign brief was missing the competitive positioning section and the success metrics weren’t tied to any of the business goals we discussed last quarter” tells them exactly what needs to change.
Timely. Feedback delivered two weeks after the thing that warranted it lands differently than feedback delivered within 48 hours. The person has moved on mentally. The event is no longer fresh enough to learn from in detail. And the gap between the event and the feedback makes it look like you’ve been sitting on the information — which feels calculated rather than genuine. Give feedback close to the event, consistently.
Private. Feedback that concerns an individual’s performance never belongs in a group setting. Ever. Even gentle, positive-framed feedback delivered in front of the team about something that’s actually a concern creates public awkwardness and private resentment. The private 1:1 format exists precisely for this.
Actionable. Feedback that names a gap but doesn’t indicate what better looks like leaves the person with a criticism and no path forward. “The positioning was weak” is a judgment. “The positioning should be tighter to the specific pain points of the CFO audience — here’s what I mean” is feedback they can act on.
The test for whether feedback is landing correctly: is the person’s behavior actually changing? Feedback that produces defensiveness and no behavioral change hasn’t landed, regardless of how well-delivered it was. Sometimes the delivery needs adjusting. Sometimes the relationship needs more trust before the feedback can be received. And occasionally the feedback is wrong and the person is right — which is worth genuinely considering rather than dismissing.
Managing Up

New managers often focus entirely on managing down — their relationship with their team — while underinvesting in managing up — their relationship with their own manager. Both matter.
Managing up doesn’t mean performing for your manager or gaming how you’re perceived. It means keeping your manager informed of what’s happening in a way that maintains their confidence and gives them what they need to support you — without requiring them to chase you for it.
The basics: your manager should never be surprised by something significant happening in your team. If a project is significantly off track, they hear it from you before they hear it from someone else. If a team member is underperforming and you’re addressing it, they know. If a significant decision is coming that will affect other parts of the organization, they’re in the loop early enough to weigh in.
Beyond keeping them informed, managing up means being clear about what you need from your manager to do your job well. New managers often wait passively for their manager to provide what they need — guidance, resources, air cover on a difficult decision — rather than asking for it directly. Ask directly. Managers are not mind readers, and the relationship works better when both sides are explicit about what they need from each other.
For more on building the team structure and organizational design that gives new managers the right scaffolding to succeed in, the marketing org design guide covers spans of control, role clarity, and team structure in the context of a growing marketing function. And for the team productivity practices that are most relevant to new managers getting their teams to perform consistently, the marketing team productivity guide is a useful companion.
The Most Common First-Time Manager Mistakes in Marketing Departments
Doing the work instead of enabling it. The most common and most costly mistake. Taking over campaigns because the brief isn’t right, rewriting copy because the draft isn’t good enough, personally managing the agency relationship because the team member doing it isn’t as effective as you’d be. This produces short-term quality at the cost of long-term team development, and it doesn’t scale.
Giving feedback that’s too soft to be useful. Framing critical feedback as a question (“do you think there might be room to strengthen the positioning?”) or burying it in positive framing to the point where the concern doesn’t land. The person leaves the conversation not knowing they received critical feedback. The problem continues.
Avoiding accountability to maintain likability. Setting expectations but not following up on them. Letting a pattern of underperformance continue because the confrontation feels like a risk to the relationship. The team notices — and the manager loses credibility with the people who are performing, not just with the one who isn’t.
Running 1:1s as status meetings. Treating the 1:1 as a project update format instead of a development and relationship conversation. The person leaves having transferred information but not having been managed.
Trying to be the smartest person in the room. First-time managers who came from high-individual-performance often feel pressure to demonstrate their expertise in team settings. The result is over-contributing to conversations, not creating space for the team’s thinking, and signaling that the manager’s judgment supersedes the team’s. The managers whose teams produce excellent work are often the ones who contribute less in group settings and create more space for the people they manage.
Not managing up. Operating as if the management relationship only flows downward. Waiting passively for guidance, not proactively surfacing problems, not asking for what they need. This results in a manager who is well-regarded by their team but invisible to their own leadership — which doesn’t serve anyone.
FAQ
How do I give critical feedback without damaging my relationship with a team member?
Feedback damages relationships when it’s delivered late, vague, or in front of others — not when it’s honest. Give feedback close to the event, be specific about what you observed and what you need instead, and deliver it privately. “In the client presentation yesterday, the slide on competitive positioning wasn’t supported by data. Going forward, every claim on that slide needs a source cited” is direct, actionable, and respectful. The vague version — “your presentations could be stronger” — is what actually damages trust, because the person can’t act on it and eventually realizes you’ve been holding a concern without sharing it clearly.
My team members are asking me to do things I used to do as an individual contributor. How do I stop taking over their work?
This is the most common first-time manager failure, and it’s hard because doing the work yourself is faster in the short run. The discipline is to separate your role from theirs clearly: your job is to define what good looks like, give them the resources and context to do it, and review the output — not produce it. When the urge to take over arises, ask yourself whether you’re solving a capability problem (they don’t know how to do it yet, and coaching is the answer) or an impatience problem (you could do it faster, but that’s not actually your job). Capability problems get coaching. Impatience problems get managed — in yourself.
How do I manage someone who is significantly older and more experienced than me?
Directly and respectfully, same as anyone else. The mistake new managers make with more experienced reports is either deferring to them on everything (which abdicates the management role) or over-asserting authority to prove a point (which creates unnecessary friction). Neither works. Be genuinely curious about their experience, make decisions clearly and explain your reasoning, and be willing to be wrong when they’re right. Experienced people respect leaders who can synthesize their input and decide. They lose respect for leaders who either ignore them or can’t make a decision without their approval.
How many direct reports is too many for a first-time manager?
More than four or five direct reports is a significant challenge for a first-time manager, particularly in creative and strategic marketing work where managing well requires genuine engagement with each person’s thinking and development. Effective management takes real time — time for 1:1s, for reviewing work, for giving feedback, for having the harder conversations when they’re needed. A first-time manager with eight direct reports will almost certainly underserve most of them. If you’re being given a large team as your first management role, it’s worth raising explicitly with your own manager.
What’s the biggest mistake first-time marketing managers make?
Trying to be liked rather than trying to be effective. The two aren’t mutually exclusive, but when they conflict, new managers consistently choose likability — avoiding hard conversations, softening feedback until it’s useless, tolerating underperformance rather than addressing it. The managers people remember and respect are almost always the ones who were direct, fair, and genuinely invested in their development — not the ones who avoided difficult conversations to keep the relationship comfortable. Ironically, the pursuit of likability is what erodes it over time.
The Bottom Line
Becoming a manager is a genuine career transition, not an extension of your individual contributor role with additional responsibilities. The skills that made you excellent as a marketer are partly relevant and partly a liability — the execution quality, the creative judgment, the attention to detail are still useful; the tendency to do the work yourself rather than enable others to do it is the thing that will hold you and your team back.
The adjustment takes time. Most first-time managers spend a full year figuring out what the job actually is before they start doing it consistently well. The ones who close that gap faster are the ones who get clear early about the job description — your job is to build a team that produces excellent marketing, not to personally produce excellent marketing — and who build the habits around feedback, accountability, and 1:1 conversations that make managing well a repeatable practice rather than an improvised one.
If you’re building or scaling a marketing team and want to think through the organizational design and people leadership questions that come with growth, let’s talk.





