Weekly GTM Standup
The 30 minutes that keep the quarter on track.
Workflow
Step 1Status Collection
ObjectiveGather status updates from all teams
InputInitiative progress, team accomplishments, blockers
OutputStatus summary from all teams
Key activities
Have team leads provide updates (what we accomplished, what we're working on, blockers), consolidate status
Decision points
What was accomplished? What's on track?
Tools: Status templates, meeting toolsRoles: Team leads (updates), Operations (consolidation)
Success: Status received from all teams
Quality gate: Comprehensive status collected
Why it matters
- The weekly rhythm is where execution is steered. A good standup surfaces what needs a decision before it becomes a problem.
Best practices
- Keep it to 30 minutes and on a fixed cadence.
- Focus on issues and decisions, not status.
- End with actions and owners.
- Log learnings and follow up.
Common mistakes
- An hour of reading dashboards aloud.
- No decisions, no owners.
- Skipping it when things get busy.
Key questions
- What changed this week that needs a decision?
- What is blocking the quarter's progress?
Agents that drive this
Planning Cycle
Tools we use · alternates in [ ]
Metabase[ Looker Studio, Power BI, Grafana ]Slack[ Teams, Discord ]Notion[ Confluence, Obsidian ]