CEO's 'fun ideas' are killing my actual marketing strategy

storyweaver

Solo marketing at a mid-size nonprofit. Perpetually fried but smiling because the job market is a dumpster fire and this gig beats my last three.

CEO's a nice guy. Enthusiastic to a fault. Slacks me at 7 PM: "Hey, what if we did a TikTok dance for Giving Tuesday?" or "I saw this cool video style, can you replicate it by Friday?" Half the time it's stuff already on my list - just buried under the work that actually pays the bills.

Exec team piles on too. "Fun little project!" - three days of filming and editing. Cool. Cool cool cool.

I'm not saying no to the CEO. But I'm also not cloning myself. Currently juggling a rebrand, donor retention campaigns, and grant reporting while someone's dreaming up a podcast series.

How do you redirect the enthusiasm without looking like the office grump?

pixelperfect

The terrible advice in this thread is going to get people fired, and honestly reading it stressed me out.

Don't ignore your CEO's requests. Do what they ask. They dictate what your job is, and your priority at work should be making your CEO happy. That's how you keep your job in this economy and get promoted.

bigcoffee

Someone here nailed it: make leadership feel heard while protecting your team. My version of that playbook:

Always say yes, but frame the "if" around their own constraints. They want a big launch? Great. Ask for the budget, timeline, and success metrics upfront. That shifts the conversation from "why can't we" to "here's what's possible with what you've given us."
Translate their vision into operational reality. If the ask is a major event next week with $1k, you're not saying no. You're presenting two clear options: Option A (what we can do with these resources) vs. Option B (what we could do with more time/budget). Let them choose.
Document everything. This protects your team from scope creep and gives you a clear audit trail if expectations weren't managed. A simple shared doc works.
This approach prevents the real churn: burning out your team on impossible asks and losing executive trust when you inevitably "fail." It's a retention strategy for internal relationships, too.

The key is making the "if" part of their decision, not your objection. Works every time.

dailygrind

My CEO throws an idea my way, first question out of my mouth: "What's the expected outcome - new logo or expansion revenue?" If she can't map it to CAC payback or net revenue retention inside thirty seconds, it goes straight to the parking lot.

Running a two-person growth function means every sprint has to earn its keep. My filter looks like this:

Does it move qualified pipeline or reduce churn?
Can we measure it in GA4 / HubSpot / Amplitude without building a custom dashboard?
What's the opportunity cost versus the next SEO cluster or lifecycle flow?

If the answer to any of those is "I don't know," the ticket stays in Backlog until someone does the homework. Harsh? Maybe. But I've watched too many quarters evaporate on "strategic initiatives" that nobody can tie to a number.

reddit-organic-growth

The reality is most of us never hear directly from the CEO. In a larger org, that request trickles down through the VP, who actually has the power to reshuffle priorities. My VP will straight up tell me "park that other thing for a week, we'll circle back" - and that flexibility is everything.

They also act as the filter. Pushback sounds like "team isn't positioned for that" or "we tried this two years ago and it flopped, sure you want to rerun it?" That cover lets the team stay focused.

If you don't have that layer, you have to be your own VP. "Taking on XYZ means Project ABC slips - cool with that tradeoff?" Forces the conversation into business terms instead of yes/no.

Small company, harder to say no. But honest question: at that stage, is the CEO actually a CEO or just an operator with a fancy title?

metricsmuse

Here's the thing, wanting to focus on projects that drive revenue puts you exactly on the same page as your CEO, not against them. if they're reasonable, walk them through how you prioritize and show what actually moves the needle. If they're a narcissist? Smile, nod, do the task, and quietly update that résumé. Life's too short to win battles that don't matter

dailygrind

Hard no. Learned that lesson the hard way at my last startup.

The CEO's job is setting the north star - revenue targets, market position, that sort of thing. Our job is filtering the firehose of "wouldn't it be cool if" ideas through the reality of CAC payback periods, engineering capacity, and whether the math actually works.

Built a simple scoring framework for this:

Strategic fit - does it move our core KPIs?
Resource cost - eng weeks, design, support burden
Revenue impact - modeled lift vs. baseline
Speed to signal - can we validate in 2 weeks or 6 months?

Anything scoring below threshold gets parked in a "revisit quarterly" doc. CEO stays happy because ideas are heard, team stays focused because we're not building features three customers asked for.

Saved us from two major distractions last quarter alone - a white-label request that would've eaten a sprint and a marketplace integration with zero TAM.

pixelperfect

that sinking feeling when an exec drops a "quick idea" on you? worth listening to. Just saying yes to everything is how you end up buried in work that burns time and money without moving anything forward.

Instead of shutting them down, get curious about what they're actually asking for. sometimes there's a way to fold it into your existing plan, or park it for a campaign next year tied to a date that matters to your community.

Quick stuff, like a social post that takes ten minutes? fine, just do it. but when they start piling on video requests, that's your cue to share your workload and timelines, and walk them through the strategic lens behind your priorities. people respect a roadmap way more than a reflexive yes

funnelhacker

Who signs the checks? That's the entire answer.

Look, I've pushed back on exec ideas plenty of times, usually with campaign data to back it up. Sometimes that changes the plan. Most times it doesn't. Either way, once the CEO makes the call, my job is execution. My KPIs depend on shipping what leadership greenlit, not relitigating it in meetings for a month.

Someone in the thread said it best: you're paid to do what your boss tells you. The ROI on arguing past that point is zero.

dailygrind

push back is literally the job description. If a CEO wanted a yes-person, they'd hire an EA - not a Head of Growth.

My setup:

Quarterly OKR review - every exec idea gets scored against CAC:LTV impact, payback period, and incremental ROAS. If it doesn't move the needle on at least two, it goes to the "parking lot" sheet in Notion with a timestamp and owner.
Data wall - GSC impression trends, Ahrefs position tracking for our money keywords, and Mixpanel funnel drops all feed a single Looker dashboard. When leadership suggests "let's do TikTok," i pull the cohort retention for short-form traffic vs. organic search. numbers end the debate faster than opinions.
One-pager template - every net-new channel or campaign gets a memo: hypothesis, test budget, success metric, kill criterion. signed off by me and finance before a single dollar leaves the corporate card.
Monthly "bad idea" retro - 15 minutes, async in Slack. We log what we killed, why, and what we learned. Builds institutional memory so the same zombie ideas don't resurface every planning cycle.

The relationship works because i treat their intuition as a hypothesis, not a directive. They get cover with the board ("marketing ran a structured test, here's the data"), i get autonomy, and the budget goes to what actually compounds.

Push back isn't insubordination. It's fiduciary duty.

pixelperfect

You can give your opinion, no problem with that, but your job - the thing you're literally being paid to do and the only reason you're there - is to follow their direction.

I don't understand how this is controversial or debatable. It's the absolute most basic concept when it comes to having a job.

dailygrind

hard line, but accurate. Executive "ideas" usually arrive as unvetted feature requests with zero distribution strategy attached. marketing owns the funnel - acquisition, activation, revenue - not the product roadmap. When leadership skips discovery and hands down solutions, they're doing your job and theirs poorly. Push back with data: show the CAC impact of building something nobody searched for

pixelperfect

Honestly, no. It can sting to hear, but the job is doing what the company asks of you.