Native vs Connected
Overview
Section titled “Overview”GrowthOS always owns planning: Idea Lab conversations, PRDs, the backlog hierarchy, and AI sprint plans live in GrowthOS no matter how you execute. The choice you make is about where day-to-day task tracking happens once a sprint starts.
Native keeps sprint boards and My Tasks inside GrowthOS. Everyone on the team opens one app for planning and doing the work; status updates happen on the GrowthOS sprint board and roll straight back into reports and roadmap views.
Connected pushes issues to an external tracker, such as Linear or Jira, and reads status back into GrowthOS so reporting still works. Connected is an early-partner capability in MVP; teams that are not yet enabled see a coming-soon message instead of the connect flow.
What you can do here
Section titled “What you can do here”- Decide, at the organization level, whether a project runs Native or Connected.
- Keep planning artifacts (Idea Lab threads, PRDs, backlog) as the system of record in both modes.
- Switch a greenfield project to Connected later without rewriting existing PRDs or backlog items.
- See a clear coming-soon message if Connected is not yet enabled for your organization.
When to use
Section titled “When to use”- Choose Native for greenfield teams that want one workspace for planning and execution.
- Choose Connected when engineering already lives in an external tracker and will not switch boards.
- Revisit this decision whenever you spin up a new project; different projects can use different modes.
Prerequisites
Section titled “Prerequisites”- Owner or Admin role to change organization-level integration settings.
- For Connected: an approved design-partner slot and OAuth credentials for the target tool.
Where to find it
Section titled “Where to find it”- Organization → Integrations (
/org/integrations) shows current mode and available providers. - Per-project execution surfaces live at Sprint board and Tasks once a project is created.
Step-by-step
Section titled “Step-by-step”- Decide whether execution should stay in GrowthOS (Native) or move to an external tracker (Connected).
- Open Organization → Integrations to see which providers are enabled for your organization.
- If Connected is not yet available, note the coming-soon message; planning still works fully in Native.
- Plan the work as usual in Idea Lab, PRD Studio, and Product Backlog regardless of mode.
- Run AI sprint planning to produce a sprint scope.
- In Native, track the sprint on the GrowthOS sprint board. In Connected, push the sprint to the partner tool once enabled.
- Review progress in Team Analytics; both modes report back into the same dashboards.
What success looks like
Section titled “What success looks like”- Every teammate knows, without asking, whether to update status in GrowthOS or an external tool.
- Planning artifacts stay accurate regardless of which execution mode a project uses.
- You can explain the tradeoff to a new hire in under a minute.
Tips & best practices
Section titled “Tips & best practices”- Start Native by default; it is the fastest path to a working sprint with zero setup.
- Ask your GrowthOS contact about design-partner access if Connected is a hard requirement.
- Document per-project mode choices in the project description so new members are not confused.
Common mistakes
Section titled “Common mistakes”- Assuming Connected is available for every organization; in MVP it is limited to early partners.
- Mixing status updates between a sprint board and an external tool for the same project without a clear owner.
- Blocking a Golden path walkthrough on Connected setup when Native would unblock the team immediately.