Assess cross-base continuity across related bases
Separate systems can signal either healthy autonomy or costly repetition.
Teams often protect local ways of working while needing continuity when work crosses boundaries.
“I don’t want one giant tracker, but I’m tired of rebuilding the same context every launch.”
Zara Chatterjee · Operations Program Manager
Coordinates company-wide launches while each functional team maintains its own operational base.
What pulls against what
- local autonomy vs. cross-team continuity
- pattern detection vs. customer intent
- strategic focus vs. reversible learning
What is at stake
A mistaken assumption could either over-centralize customers or leave recurring handoff work untouched. The task is to find a meaningful, testable customer outcome
Why Airtable
For Airtable, the distinction can matter because flexibility is valuable only when teams can still carry context where it is needed.
Written for
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.