← Writing

Scaling a team: why sharing processes won't transfer results

For two years we shared every process with other teams and their results didn't change. Why a process is only a tool and what scaling a team takes.

For two years we shared absolutely everything we did with the other marketing teams in the group, and their results didn't change. Management believed that scaling a team meant taking the processes of the one that works, handing them to the others, and the numbers would follow.

Our team's numbers were visible. We hit 135% of our full-year marketing-attributed revenue target seven months into the fiscal year, and our LinkedIn campaigns converted 24% of MQLs to SQLs, against a B2B average of 13-15%. No other team reached those KPIs in that period, either in attributed revenue or in MQL-to-SQL conversion.

Everything we shared

We shared all our LinkedIn campaigns and gave the other teams a view into our accounts. They got all our graphics and every framework and procedure we kept in Asana, for every type of content and every way we generate contacts. We explained how we run events and how we invite people to them.

Everyone nodded along, said how great it was, and nothing changed on their side.

Why the results didn't transfer

The other teams got a list of activities, but what stood behind those activities couldn't be handed over. In our team I had also built a way of thinking, and that needs daily feedback, discipline and pressure on quality, none of which you can write into a template. And when the template didn't work, the blame went elsewhere: our market is different, our customers behave differently, that doesn't work here.

Event invitations show it best. We invited people to our workshops personally, by phone and through account managers, and whoever was inviting had a clear task: 30% of the audience had to be new contacts we didn't know yet (I describe it in detail in the article on the 30% rule for B2B events). One of the neighbouring markets adopted our event format but sent the invitations via LinkedIn, and was surprised that their audience looked nothing like ours. If we had invited people via LinkedIn, it wouldn't have worked for us either; we chose the route that leads best to the result, even when it took more work.

What actually drove the results

The results came from the way of managing and the discipline I pushed through in the team, which gradually became part of how people think. I cared about qualified leads, and the team knew it, because that's what we measured, decided by and gave each other feedback on. In practice it came down to four things you won't find in any shared process.

Priorities: a workshop only when we have something to show

When business or sales came up with an idea for a workshop and we had no good content on the topic, we didn't run the workshop. The condition was clear: we have to have something to talk about, we have to have something to show customers, and what we show has to be real.

Quality: content that makes sense the first time

I gave feedback on content as a matter of routine, and when a piece didn't make it clear what it was about, we rewrote it or started over.

Measurement: contacts, not impressions

I didn't care how many impressions our LinkedIn posts got. I tracked click-through on the campaigns collecting leads, because you only get clicks from an audience you've already warmed up, and for that you need the impressions. For a conversion-stage campaign to reach a decent CTR, the content had to be genuinely good; with weak content we wouldn't have got there.

So my primary measure was what has impact: how many people give us their contact details. Everything before that was a necessary condition we kept an eye on, but it wasn't the main number. How we tracked that impact all the way to revenue is in the article on B2B marketing attribution.

Consistency: being able to say no

Beyond persistence, it was above all about consistency: standing behind our strategy and what we believe in. We said no to events that didn't support our strategy, to workshops without good content, to campaigns without materials, and to campaigns on topics where we knew we wouldn't get leads because the content simply wasn't good enough.

What would work instead of sharing

If I got the same brief again, I would give the leaders of the other teams the same KPIs we had and work through with them, step by step, how to reach them, why something isn't working for them and what they need to change on their side. Scaling a team this way, though, means I have to manage them, because otherwise it won't work. You can only scale what someone manages.

A process is just a tool

Transferring processes to another team is very hard and on its own it doesn't work, because a process is just a tool. When people lack the mindset and strategic management, even the best-documented playbook is useless to them.

If you're working out how to take one team's results into other markets or offices, I'm happy to talk it through.

Frequently asked questions

Why does sharing best practices between teams often fail?

Because it hands over activities, but not the management, priorities and measurement of impact behind them. The team gets a template, and when it doesn't work, it blames a different market or different customers.

What does scaling a team need besides processes?

The same impact KPIs for every team and a leader who manages them: someone who guards priorities, sends back work that isn't good enough and can say no to activities that don't support the strategy.

How can you tell a team is copying the process but not the results?

It reports activities and impressions but has no numbers on contacts gained, leads and pipeline, and when results don't come, it explains that its market is different.

← Back to Writing

If your pipeline
isn't moving —
let's talk.

Currently open to
CMO or VP of Marketing roles at B2B consulting firms and ambitious scale-ups.
I build from scratch, I work globally, and I do not need it to be tech.

One conversation. No pitch.