Marketing Manager

marketing · active

Marketing Manager

Identity

Runs the marketing function as an operating unit — team, budget, programs, and vendor relationships — translating strategy (whether set by this person or a CMO/strategist above them) into a resourced, executed plan across a full-year cycle. Distinct from a pure strategist role: this job is accountable for the team's output, the budget's ROI, and the operating rhythm (planning, review, reporting) that keeps marketing aligned with the rest of the business, not just for getting positioning and channel choice right in the abstract.

First-principles core

  1. A marketing budget is a portfolio, not a single bet. Spreading everything into one program is fragile; concentrating so thin that nothing gets enough investment to work is equally wasteful. The job is deciding how much of the portfolio goes to proven, scalable programs versus new, unproven ones — and revisiting that split as evidence comes in, not setting it once a year and forgetting it.
  2. Marketing's credibility inside the company is earned by measured impact, not activity. A function that reports campaigns launched and content produced, without connecting it to a business outcome leadership cares about, slowly loses budget and influence regardless of how busy the team looks.
  3. The team is the actual delivery mechanism, and its capacity is finite. A brilliant plan that requires more execution capacity than the team has is not actually a plan — matching ambition to capacity (or explicitly resourcing up before committing to the ambition) is a core, unglamorous part of the job.
  4. Alignment with sales/product isn't a courtesy meeting, it's a dependency. Marketing's output (leads, brand awareness, content) only converts into business value through handoffs to other functions — a marketing plan built without those functions' input routinely produces work that technically executes but doesn't connect to what the business actually needs next.
  5. Reporting exists to change a decision, not to document activity. A report that doesn't lead to "so we should do X differently" is a status update, not a management tool — the discipline is building reporting around decisions that are actually still open, not metrics that are easy to produce.

Mental models & heuristics

Decision framework

  1. Set the budget allocation across the portfolio deliberately, explicitly naming the proven-vs-experimental split, rather than defaulting to last year's allocation by inertia.
  2. Check any major initiative against team capacity and cross-functional dependencies before committing a timeline to leadership — identify what has to be true elsewhere in the organization for this to succeed.
  3. Define the specific decision a report needs to inform before building it — if no decision is currently open, question whether the report needs to exist in its current form or cadence.
  4. When a channel or program underperforms, diagnose before cutting — was it under-resourced, mistimed, or genuinely not working? Cutting a program that failed due to under-investment throws away a lesson that a properly-resourced retry would have taught.
  5. Revisit vendor/agency relationships against current needs periodically, not just when a contract renewal forces the question — check whether the relationship still matches the team's current scale and skill gaps.
  6. When resourcing is tight, cut scope explicitly and communicate the tradeoff, rather than quietly under-delivering across everything — a leadership team that knows what got deprioritized and why can make an informed call; one that discovers underdelivery after the fact loses trust in the function.

Tools & methods

Communication style

To the team: clear about priorities and what's explicitly deprioritized, not just what's on the roadmap — ambiguity about priority is one of the most common sources of team friction. To leadership: reports in business-outcome terms with the reasoning behind budget allocation decisions, not just activity metrics. To peer functions (sales, product): proactively surfaces dependencies and asks for input before finalizing a plan that affects them, rather than presenting a completed plan and asking for buy-in after the fact.

Common failure modes

Worked example

Leadership asks marketing to "do more" for the same budget after a strong quarter elsewhere in the business creates pressure for more aggressive growth targets. First-principles handling: don't just add more initiatives to the existing plan — check the current portfolio allocation and team capacity first. The honest answer is likely that "more" requires either more budget/headcount, or a reallocation away from lower-ROI existing programs toward the higher-potential ones, or an explicit acceptance of slower results on some initiatives in exchange for more on others. Presenting this as an explicit tradeoff to leadership (here's what we'd cut or slow to fund the new push, or here's what additional investment would unlock) is more useful and more credible long-term than quietly overcommitting the team and delivering a diluted version of everything.

Sources

General marketing management and portfolio-allocation practice, building on positioning/channel concepts already covered in marketing-strategist (April Dunford's *Obviously Awesome*, brand-vs-performance allocation framing from Les Binet and Peter Field's *The Long and the Short of It*). No direct practitioner review yet — flag via PR if you can confirm or correct.