Most marketing plans fail in one of two ways: they are too vague to guide the next decision, or too rigid to survive contact with real business conditions.
A Growth Move is our way of keeping strategy practical. It is one focused improvement selected from a Planned Growth Roadmap, completed with a clear purpose, measured, and used to decide what comes next.
A Growth Move is smaller than a campaign—and more useful than a task.
A task describes activity. A campaign groups activity. A Growth Move connects the work to a specific bottleneck or opportunity in the larger system.
For example, “write a blog post” is a task. A Growth Move might be: create the comparison article prospects need before they book, connect it to the right service page, and review whether it produces more qualified conversations.
The four-part rhythm
1. Choose
Select the next improvement from the roadmap based on the current goal, the strongest constraint, and what must be true before the next larger investment makes sense.
2. Build
Complete the work with a clear scope. That could be a service-page revision, a conversion path, a CRM connection, a campaign test, or a lightweight automation.
3. Launch
Put the improvement into the real system. A Growth Move is not finished when the draft is approved; it is finished when customers or the team can actually use it.
4. Learn
Review the signal. The result may support the next planned move, reveal a new constraint, or show that the roadmap should change.
Examples of roadmap-ready Growth Moves
- Improve one high-priority service page
- Publish a useful article tied to a sales question
- Connect a website form to the right CRM pipeline
- Tighten conversion tracking before increasing ad spend
- Automate a simple notification or follow-up step
When a move becomes an add-on
Some opportunities are too large to fit responsibly inside the monthly Growth Foundation. Custom software, mobile applications, complex advertising programs, large migrations, high-volume content, and advanced automation need their own scope.
That distinction is healthy. The roadmap still helps us decide why the add-on matters and what should happen before or after it, while the separate scope gives the larger work the strategy and production it deserves.
The goal is momentum with memory
A Growth Move should not disappear into a list of completed tickets. Each move changes the system, creates information, and makes the next decision better. Over time, that is how a managed website becomes a compounding growth asset instead of a project that slowly goes stale.
Leave a Reply