Weekly meetings: your team rhythm in Asana C Copy title and link

The pattern

Default agenda items explained step by step

• What needs to be said in able to be fully present in this meeting? Keep it short.

• Walk the Asana project list (shared on the screen).
• Keep updates only to what changed since last week. Nothing changed? Say "no update".
• Only clarifying questions, no discussions. If a project update leads to a tension, add it to the agenda.

• What changed since last meeting?
• Discuss KPI's, and OKRs if you have any.

• Facilitator collects topics, 2–3 words each.
• Add agenda items only if they need the whole group. Don’t discuss topics that involve only two people: a shared agenda costs everyone in the room their attention. The bar for putting something on it: the whole team genuinely needs to hear it or weigh in. If not, take it offline with the relevant roles.
• Don't seek consensus on decisions you already have authority to make.

• Facilitator: process each item with one question: "What do you need?"
• Participants: state clear asks: "I need X from role Y."
• There are 4 valid answers to the question "What do you need?":
• 1. Someone to take action: Clarify which role the ask belongs to. Check the rolesin Moral Fabric if needed. The facilitator asks: "Can we expect this from you, given your purpose or accountabilities?" ⟶ Capture as an action item or project.
• 2. Information or input: The tension-holder wants information from one or more roles, or wants to give input on a decision. Watch the shift from asking for input to asking for permission; those are different things. Ask: "Which role is responsible for this?" ⟶ Capture as an action item.
• 3. Sharing information: The tension-holder wants to share something with the group. Watch for hidden asks: "Did sharing this give you what you needed? Or do you want reactions, or someone to act on it?" ⟶ No capture needed, unless a follow-up ask emerges.
• 4. Making an agreement: The tension-holder wants to set a lasting expectation: about roles and accountabilities, or about behavior.
• On roles and accountabilities: Make a governance proposal, in the governance meeting or asynchronously in Asana.
• On general norms and behavior: Ask the relevant people to make a working agreement, which they may accept or decline.

• Brief closing.

What to do in Asana

1. 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.
2. Add Priority and Progress custom fields as described in Asana: getting started, step 5⁠. Update Progress before the meeting, not during it.
3. 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.
4. 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

Your variation

• Cadence and length: weekly 30 min is the default; adjust per team size.
• Facilitator rotation: fixed or rotating, and how often.
• Your metrics: which recurring items and numbers you review in step 3.
• Governance topics: where role and policy changes go if not in this meeting (a separate governance meeting is the common pattern).