Growth Competency Stack

How Growth Competency Stack actually works in practice, plus the mistakes worth avoiding and the steps worth keeping. For strategists, marketing leaders, and growth teams.

By David Schaefer · LinkedIn · Updated · 9 min read · 3 sources cited

Key takeaways

  • Growth Competency Stack is a topic within Marketing Frameworks — a concrete choice, not a vague best practice.
  • Change one variable at a time so results are causal, not coincidental.
  • Review on a fixed cadence and write down what you changed and what moved.
  • Define the term in one sentence everyone agrees with before you measure anything.
  • A good tool on a fuzzy definition still produces a misleading dashboard.

What Growth Competency Stack covers

Growth Competency Stack is one subject within Marketing Frameworks, which covers the structured ways of thinking operators use to organize decisions, from positioning to funnels and prioritization; here it is framed as a decision, not a definition. Start there.

Begin with the decision this topic has to support. Growth Competency Stack belongs to Marketing Frameworks — the discipline of the structured ways of thinking operators use to organize decisions, from positioning to funnels and prioritization. We are after something usable in a planning meeting, not a glossary line. Most teams stumble by leaving it undefined and assuming agreement. Make it a specific decision the team can write down and re-examine.

Growth marketing requires its own competency model. The discrete skills a growth practitioner needs at each proficiency level — and how those skills evolve as the practitioner moves from IC to lead to head-of-growth.

Growth marketing is sufficiently distinct from general marketing that it warrants its own competency framework. The Reforge growth competency model[1] defines the discrete skills a growth practitioner needs at each proficiency level.

You've read the concept. Now build the skill — RGM's SEO training takes you from technical foundations to content strategy with real exercises, audits, and worked examples. Free. No signup required.

A working-level practitioner can execute experiments competently in their channel. An advanced practitioner can design the experimentation program for their channel. An expert practitioner can design the cross-channel program and connect it to business model and unit economics.

If you want primary material, start with the Strategic Choice Cascade, AARRR pirate metrics, and the RICE scoring model. Use the named sources as a map, not as an answer key. Hold onto that and the rest of the page is detail.

How Growth Competency Stack works in practice

Growth Competency Stack runs on a simple loop: change an input, read the signal, decide the next move, then improve them one at a time. That is the whole idea.

The mechanics are ordinary; the discipline to follow them is not. Cut the goal into inputs, name who owns each, and follow each input separately. In a healthy version, no one is unsure which input is theirs.

Growth Competency Stack — the parts to name and own
ElementWhat it is
LagHow long before the effect is visible.
GuardrailThe limit that stops a local win from causing a global loss.
InputsWhat you actually control week to week.
BaselineThe pre-change level you compare against.

Pick a rhythm and keep it; consistency beats intensity here. Obvious once stated, which is exactly why it is worth stating.

How to apply Growth Competency Stack

Work it as a loop: name the goal, trust the data, isolate a variable, then keep notes. Keep that distinction.

  1. Define the term out loud. Get the definition onto one line the whole team will sign. Disagreement here is the real starting issue.
  2. Instrument before you optimize. Verify the measurement before you touch the lever. If you cannot trust the number, you cannot read the result.
  3. Change one thing and test it. Change a single variable and measure against a control group. Without isolation the result is just correlation.
  4. Review on a cadence and write it down. Record what you changed, what moved, and what you will try next. The written trail stops the team relearning the same lesson.

Respect the order. The written review is the step teams drop first and miss most. In practice, that distinction does most of the work.

Grounding Growth Competency Stack in real numbers

Check the numbers against public data before treating any of them as a target. Use that as the anchor.

Treat any blended average as a compass heading, not a destination. A figure from one industry, channel, or business model rarely transfers cleanly to another. Take the number below as a sanity check, not as a goal to hit.

Claim: Nielsen and others note that a large share of marketing effect is delayed rather than immediate. Source: [Think with Google]. Context: It is why last-click reporting tends to understate upper-funnel work.

If a number below is unsourced, read it as RGM analysis: a tested observation, not a citation. It is a hypothesis to test, not a fact to cite.

Common mistakes with Growth Competency Stack

Most failures here come from skipping definition, optimizing in isolation, or ignoring a counter-metric. That part is non-negotiable.

The mistakes that quietly cost the most
  • Letting one team own the metric while another owns the lever.
  • Skipping the current-state audit before designing the fix.
  • Copying a competitor's setup without their context, constraints, or data.

They are predictable, which is exactly why naming them helps. Calling them out early is cheap insurance against an expensive quarter.

Quick answers

How should a team treat Growth Competency Stack day to day?
As a recurring decision, not a one-time setting. Name it, measure it, and revisit it on a cadence so the choice stays matched to the current goal.
Can small teams use Growth Competency Stack?
Yes. Smaller teams often apply it better because fewer handoffs mean the person who owns the lever also owns the number.
Where do RGM observations fit here?
Any pattern labelled RGM analysis comes from reviewing real accounts. It is offered as a tested hypothesis, never as a substitute for measuring your own data.

Frequently asked

What is Growth Competency Stack in simple terms?

Growth Competency Stack is a topic within Marketing Frameworks, the discipline of the structured ways of thinking operators use to organize decisions, from positioning to funnels and prioritization. In plain terms, this page treats it as a recurring decision your team can make with a shared definition instead of restarting the debate each time.

Why does Growth Competency Stack matter?

It matters because it shapes how budget, effort, and attention get allocated. When growth competency stack is defined and measured well, spend follows what works; when it is fuzzy, spend follows whoever argues hardest.

How do you measure Growth Competency Stack?

Pick one primary number, instrument it cleanly, and pair it with a counter-metric so you are not gaming the goal. Then compare against a pre-change baseline rather than an industry average.

What references help with Growth Competency Stack?

Useful reference points include the Strategic Choice Cascade, AARRR pirate metrics, and the RICE scoring model. Tools matter less than a clean definition and trustworthy measurement; a good tool on a bad definition still produces a misleading dashboard.

What is the most common mistake with Growth Competency Stack?

Optimizing it in isolation. A local improvement that ignores the downstream business effect can look like a win on the dashboard while costing money elsewhere.

How often should you review Growth Competency Stack?

Pick a rhythm and keep it; consistency beats intensity here. The point is a fixed rhythm, so slow drift gets caught before it becomes a quarter-sized problem.

Sources cited on this page

  1. HBR Strategy — hbr.org/topic/strategy
  2. Reforge — www.reforge.com/blog
  3. First Round Review — review.firstround.com