Yes. A list of tactics tells you what to do this week, and a strategy tells you why those tasks exist and which tasks do not. If your plan is only marketing strategy vs tactics in the sense that everything got collapsed into one busy list, split the documents. Tactics are the posts, the ads, and the emails. Strategy is why those exist and which ones do not. A list of tactics with no ignore-list will fill the week and not the pipeline.
Takeaways
- Keep the decision and the task list as two documents.
- Let tactics exist only when the decision names them.
- An ignore list is what stops the task list from eating the week.
- Write the decision if all you have is things to try.
What Tactics Are
Tactics are the moves. A post. An ad. An email. A page edit. A conversation with a partner. They are concrete, and that is their virtue. You can finish a tactic. You can assign it. You can tell whether it happened. A business that only respects tactics will get a lot of happening. Happening is not the same as a path. The path needs a reason the move exists, and a reason some other move does not.
Your plan is a list of things to try because trying feels responsible. Each try is a tactic looking for permission. Give permission in a separate place, or the list will grant it to itself. Self-granting lists grow. They do not choose. By Friday the team is tired and the enquiry looks the same as Monday, only with more drafts in the folder.
None of this insults the drafts. Drafts are how work ships. The insult is asking a draft list to do a decision's job. It cannot refuse. Refusal is the decision. Keep the drafts. Move the refusal somewhere they have to look.
What Strategy Adds That a List Does Not
Strategy adds the enquiry, the offer, the page, and the channels that are out of bounds. It answers why a post exists. It answers why an email does not. A list of tactics can sit underneath that page as the tasks for the channels that remain. The list is allowed to be ordinary. Ordinary tasks in service of a named page beat clever tasks that each invent a new offer.
If you only write one document this month, and you already have a crowded task list, write the decision. The task list will still be there. It might get shorter, which will feel like loss and function as relief. You will know which document to write by noticing which one cannot say no. That one is incomplete. The decision is the document that says no.
- Open the task list and group each item under the enquiry it serves.
- If an item serves no enquiry, move it to a parking line.
- Write the offer and the page the surviving items must use.
- Write the ignore list from the parking line, with reasons.
- Leave the task list as tasks only. Do not let it reabsorb the decision.
How a Busy Week Hides an Empty Path
A busy week is the list winning. Posts go out. Ads are tinkered with. Emails leave because the calendar said so. None of them had to agree with each other. The path, which is a stranger meeting one offer on one page and getting a follow-up that remembers them, never had to be true. You can be exhausted and unstrategic. The exhaustion is often the clue. Strategy should make some of the exhaustion unnecessary.
The pipeline the gain mentions is not a number you should invent. It is the line of real enquiries. A week of tactics that does not touch that line has filled time. Look at whether a real enquiry would recognize your posts, your ads, and your emails as the same offer. If they would not, the list is several strategies pretending to be productivity.
Use the table when someone defends the list as flexible. Flexible without a refusal is porous. Porous weeks do not fill a path.
| Document | It can | It cannot |
|---|---|---|
| Task list | Say what will be drafted or sent | Decide what the business is refusing |
| Strategy page | Name the enquiry, the offer, the page, and the ignore list | Replace the tasks once the decision exists |
| A single mixed doc | Feel complete in a meeting | Stop a new tactic from joining without a decision |
| Ignore list | Give a no that survives Thursday | Motivate anyone by itself. It needs the enquiry beside it |
Which Document to Write
Write the strategy page if the tasks already exist. Write the task list only after the page exists and only for the channels it allows. Marketing Strategy is the page. Digital Marketing is the path those tasks must serve. A task that does not touch the path is a hobby the business is funding with attention.
The tasks have homes when they are real. A task about defining the enquiry belongs with Lead Generation. A task about one friction on the named page belongs with Conversion Rate Optimization. A task about a send belongs with Email Marketing, and only for people who asked. A task about a rule belongs with Marketing Automation, and the rule has to be readable. If the task list is those things in disguise, good. Give each one the decision's permission or park it.
You will know which document to write when you try to explain the week to a new person. If you hand them tasks, they will do tasks. If you hand them the decision, they will know which task to refuse. Refusal is the skill the list cannot teach. Write the document that teaches it.
How to Keep the Two From Collapsing
Put them in different places. The decision is one page, slow to change, owned by the person who can say not yet. The task list is a working note, fast, owned by the people who ship. Once a week, the shipping note is checked against the page. Items that grew overnight get a verdict. Allowed, because they serve the enquiry and the page. Parked, because they do not. The verdict is recorded on the ignore list if it is a whole channel, or simply deleted if it was a stray idea.
Collapsing happens when the same note holds both, because the tasks are more satisfying to type. Split them the day you notice. You do not need a workshop. You need a cut and a heading. The heading on the decision is the enquiry. The heading on the tasks is this week's allowed work. If a sentence could sit under either heading, it is still mixed. Rewrite it until it is clearly a refusal or clearly a chore.
The promise of the split is a week that can be finished. Finished means the allowed tasks were done and the refused ones were not secretly done. Secret work is how the list eats the decision. Say the secret work out loud, then park it. The path gets the week. The wish list does not.
If a tactic is already running and the decision would refuse it, stop it or rewrite the decision on purpose. Letting it run as an exception teaches the team that the decision is decorative. Decorative decisions do not survive the next idea.
Name the pipeline as the enquiries you decided to count, not as a feeling of momentum. Momentum is the busy week. The enquiries are the point the tactics were supposed to serve.
A weekly check that takes longer than a short meeting has become another tactic. Keep the check to a verdict on stray items. Verdicts are yes, no, or not yet. Essays belong somewhere else.
When you park an idea, write the condition that would unpark it. Usually the condition is that the named page and the offer agree. A park with no condition is a graveyard, and graveyards get raided when someone is bored.
Do not let a tool's default folders become the two documents. Defaults mix drafts and decisions. Make the split obvious even if the tool would prefer one board.
If ads are in the task list, the strategy page should say which page they land on and which audiences you are not buying. An ad without that sentence is a tactic hiring itself.
Emails on the task list need the same treatment. Who asked, and what reason this send serves. If the strategy did not allow a newsletter, a newsletter task is a collapse in progress.
Show a new hire the decision on the first day and the task list on the second. The order teaches priority. The reverse teaches them that motion is the culture.
Once a quarter, delete parked ideas that the condition never met. A permanent parking lot becomes a second wish list. Deletion is a kindness to the next meeting.
The test of the split is a Thursday idea. If Thursday can ship without touching the decision page, the documents have collapsed again. Re-cut them. The cut is small and worth repeating.
When the task list is empty and the decision is clear, that emptiness can be correct. An empty allowed list means the page and the offer still need to agree. Do not invent chores to soothe the emptiness. Soothe it by finishing the handoff the decision already named.
Label the two documents in plain speech the team already uses. Decision page. This week's chores. Fancy names get ignored. Plain names get opened. Opening is the whole point of the split.
Questions
Are Ads and Posts Always Tactics?
Yes. They are moves. They become legitimate when a strategy names the enquiry and the page they serve, and when they were not on the ignore list. A clever post with no page behind it is still only a move.
Can One Person Write Both Documents?
Yes, if they change hats. Write the decision first, including the nos. Then write tasks that survive those nos. Doing it in one sitting without the change of hat is how the documents collapse back into a list.
What If the Task List Is How We Think?
Then keep thinking there, and copy the refusals out onto their own page before the day ends. Thinking in tasks is normal. Leaving the decision inside the tasks is how nos disappear. The copy is the whole reform.
Does the Strategy Need a Long Rationale?
No. The enquiry, the offer, the page, and the ignore list are the rationale. A long story usually postpones the refusal. If you love the story, put it in an appendix the task list is not required to read.
When Should You Rewrite Rather Than Add?
Rewrite when a new task would require a new offer or a new page. Adding is for chores that fit the decision you have. A new offer is a new strategy, not a line on this week's list.
Conclusion
Separate the decision from the chores. Tactics are the posts, the ads, and the emails. Strategy is why those exist and which ones do not. A list of tactics with no ignore-list will fill the week and not the pipeline. The promise was that you would know which document to write, and you write the one that can say no.
When you want help separating the decision from the tasks, Speak With Us.
