Weekly meetings: your team rhythm in Asana
How to run a weekly team meeting that removes blockers in 30–45 minutes, using your Asana project list as the agenda backbone. Companion to Working in Asana: how to collaborate transparently .
Small teams lose hours to meetings that drift into discussion. Without a fixed structure, the weekly sync becomes a round of status monologues, and the actual blockers surface in the last five minutes — or not at all. A tactical meeting fixes this: it exists to remove blockers and sync on what changed, nothing more.
The pattern
Run one weekly tactical meeting per team, 30–45 minutes for teams up to 10 people. Your Asana project list is the agenda: projects that live in Asana get discussed, projects that don't, don't exist.
Standard agenda:
Check-in — one sentence per person.
Checklist review — recurring items: done or not done?
Metrics review — key numbers: any concerns?
Project updates — walk the Asana project list. Share only what changed. Nothing changed? Say "no update."
Agenda building — facilitator collects topics, 2–3 words each.
Triage agenda items — process each item with one question: "What do you need?"
Check-out — brief closing.
Example of Moral Fabric's own internal weekly meeting board in Asana
Do:
- Keep updates to what changed since last week.
- State clear asks: "I need X from role Y."
- Add agenda items only if they need the whole group.
Don't:
- Give monologues or status reports.
- Discuss topics that involve only 2 people — take it offline.
- Seek consensus on decisions you already have authority to make.
The facilitator's job: keep it moving. Interrupt when updates turn into discussions, when people seek buy-in instead of deciding, or when items drift. Rotate the facilitator monthly so the skill spreads.
This structure comes from Holacracy's tactical meeting format ( overview at Holacracy.org ), but works whether or not you run Holacracy.
What to do in Asana
Create one Asana project per team as the meeting backbone (e.g. "Projects — [Team name]"). Every active project gets a task there, named in the present perfect ("Chosen new CRM"), assigned to the accountable person — see Working in Asana for the full setup.
Add Priority and Progress custom fields as described in Asana: getting started, step 5 . Update Progress before the meeting, not during it.
Screen-share the project board during step 4 and walk it top to bottom. This keeps updates anchored to real work and kills the "anything else?" drift.
Capture outcomes as Asana comments or tasks during the meeting, not in separate meeting notes. The record lives where the work lives.
What's mandatory regardless
Nothing here is legally required. But if your team is remote or part-time, the weekly tactical is close to mandatory in practice: it's the one moment everyone syncs.
Your variation
Record for your organization:
- Cadence and length — weekly 30 min is the default; adjust per team size.
- Facilitator rotation — fixed or rotating, and how often.
- Your checklist and metrics — which recurring items and numbers you review in steps 2–3.
- Governance topics — where role and policy changes go if not in this meeting (a separate governance meeting is the common pattern).