The testing habit that separates demand gen managers who advance from ones who plateau is simple: they run tests continuously, whether leadership asks them to or not. They're always running a small experiment on the side. Channel tests. Creative tests. Audience tests. Timing tests. By the time they get promoted, they have institutional knowledge about what works that their peers have to learn from scratch.
This doesn't mean running undisciplined experiments. It means having one slot in your team's capacity where something is always getting tested. That slot runs every week. Some weeks the test is small. Some weeks you run something bigger. But the habit is consistent. You get comfortable with the pace. You get fast at designing tests that actually answer questions.
How to run a 30-day channel experiment that produces a clear answer, not more questions, requires discipline in the design. You decide: what is the success criteria? What's the minimum viable signal that tells me to continue versus the signal that tells me to kill it? You write those down before the experiment starts. You commit to honoring what the data says. A real test says: "If CAC is below $500, we scale it. If it's above $750, we kill it. If it's between, we optimize for two more weeks." Those are the numbers you decide on day one.
What launch fast, learn faster actually requires in terms of setup, measurement, and reporting is rigor in the boring parts. Your tracking has to work. Your tagging has to be consistent. Your reporting has to be automated. You can't spend three weeks pulling data from different sources to figure out if your test worked. You need a dashboard that tells you on day 15 whether you're on path. Most demand gen teams are slow not because they can't move fast. They're slow because their reporting setup won't let them.
The two metrics to check every Monday are the ones that predict your week's outcome. For most demand gen channels, that's cost per lead and conversion rate to pipeline. You look at the previous week's data every Monday morning. You ask: is this channel trending the right direction? Is the cost moving? Is the conversion holding? If something looks off, you adjust Tuesday. If it looks good, you run the same thing. Small moves accumulate.
How to propose a test to your VP in a way that gets a yes faster than you expect: come with the success criteria and the exit plan already decided. You don't say, "I want to test LinkedIn for three months and see what happens." You say, "I want to test LinkedIn for four weeks with $5K spend. If CAC is below $400, we scale it to $20K. If it's above $600, we kill it." Your VP can say yes to that because there's no ambiguity about what happens at the end. Most managers don't propose tests this way because they're afraid of hard numbers. That fear is what makes them slower than they need to be.
The managers who get promoted are the ones who get comfortable with speed and clarity. They test constantly. They kill constantly. They scale constantly. Their team learns to move faster because they practice moving faster.
Speed is a skill. Train for it like everything else.
Scott.