Run a weekly marketing meeting that ends in decisions

Decide what the meeting is for

A weekly marketing meeting can consume an hour while changing nothing. Everyone reports activity, the founder suggests new ideas and the team leaves with more work than it arrived with.

Separate visibility from decisions. A short written update can show what shipped, what is underway and what is blocked. The conversation should focus on interpretation and choices that benefit from the people in the room.

The agenda below is a starting point. Adjust the duration to the complexity of the business rather than treating a particular meeting length as a performance standard.

Before the meeting

Ask each owner to provide a concise update: expected outcome, current evidence, important change and decision needed. Link to the underlying work rather than pasting a large dashboard into the update.

Use the same definitions each week. A qualified enquiry cannot mean one thing in the campaign report and another in the sales discussion. Note data delays and incomplete cohorts so the team does not overreact to a number that has not matured.

The founder should read the update in advance. If the meeting starts with everyone narrating material nobody has read, it will struggle to reach the decisions.

Begin with what changed

Review the few business measures relevant to the current plan. Ask whether the change is meaningful, explainable and connected to work the team controls.

A single quiet week may reflect timing rather than a failing strategy. An increase in enquiries may hide a drop in customer fit. Avoid responding to direction alone; inspect the composition and context of the change.

Then ask what customers or sales taught the team that the numbers did not. One repeated objection can be more useful than a large movement in an unrelated metric.

Spend the middle on the constraint

Choose the most important issue blocking the agreed outcome. Review the evidence, plausible explanations and available responses.

For a hypothetical startup with strong demo attendance but stalled proposals, the discussion might focus on which stakeholder is missing from the buying process. Launching a new social channel would be a separate decision, not the automatic response to a slow revenue week.

Give the relevant owner room to recommend a course of action. The founder's role is to add business context, resolve tradeoffs and approve decisions at the right level, not to rewrite every task.

End with a decision log

Record the following for each decision:

• What will change, and why.
• Who owns the next action.
• What support or approval they need.
• When the team will review it.
• What evidence would change the decision.
• Which existing work is being stopped or deferred to make room.

Read the list back before ending. If an action has no owner, it is still a suggestion. If new work has no capacity assigned, it is an unresolved tradeoff.

Protect decisions from reopening casually

Keep a record of the reasoning so the team can distinguish new evidence from a new preference. A founder seeing a competitor's campaign on Wednesday should not automatically overturn a channel decision made on Monday.

Revisit decisions when the underlying assumptions change, a test reaches its review point or an important risk appears. Consistency should support learning without turning the plan into a rigid commitment.

The meeting is working when fewer decisions remain stuck, priorities stay understandable and the team can explain what it learned. First 10's fractional leadership includes this operating rhythm because strategy only matters when it shapes the work that happens next.

Apply this to your business

End the next meeting with a decision log: observation, interpretation, owner, action and review date. If there is no decision, ask what evidence is missing.