Here's what you can expect:

• A framework for structuring Airtable across Portfolio, Program, Project, and Task layers
• How to link records across each layer so work stays connected and visible org-wide
• Guidance on when to use one base versus multiple, and how to design for growth
• What "good" looks like: connected records, clear ownership, and a structure ready for reporting
• Common setup patterns to avoid so your foundation stays clean as you scale 

Hosted by the Airtable PMO Crew: a new community for project, program, and portfolio managers using Airtable to run their work management practice.

What we won't cover:

• PMO leaders and program managers building or scaling a work management practice in Airtable
• Project managers who want their tools to reflect how work actually flows across teams
• Operations and BizOps professionals responsible for tracking and reporting on initiatives
• Airtable builders designing systems that span multiple teams or business units
• Anyone who has ever inherited a base full of disconnected tables and thought, "there has to be a better way"