Sustainable operating model

Problem

The connector dashboard pack catalog is a living product—connectors change their schemas, Fivetran adds new connector features, user expectations evolve, and packs need updating. Currently, there is no documented operating model for who maintains packs, how support tickets are triaged, what the release cadence is for pack updates, or how new connector packs are prioritized. Without a sustainable operating model, maintenance will fall to whoever happens to be available, support requests will go unrouted, and the release process will be ad hoc. This leads to stale packs, inconsistent update quality, and unsustainable load on the engineering team.

Context

Possible Solutions

Plan

Implementation Progress

Review Feedback

• Review cleared