# Fewer teams first before workspace sprawl

> Start the new workspace with fewer teams than you think you need, then add more only after live work shows where the boundaries belong.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/fewer-teams-first-before-workspace-sprawl/
- Source: [linear.app](https://linear.app/switch/migration-guide)
- GrowthDex source hub: [Linear](/sources/linear-linear-app/)
- Last checked: 2026-05-26
- Rarity: rare
- Budget: free
- Channels: Product, Operations, Onboarding
- Stages: switching, workspace design, team structure, adoption


## Why this can grow

New workspaces often inherit the old org chart before the team has learned the new workflow. That creates messy boundaries, duplicate labels, and avoidable routing confusion. Starting with fewer teams buys time to see which groupings hold up under real work. It keeps the structure legible for buyers and operators alike, and it makes later expansion a deliberate choice instead of a cleanup project.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where fewer teams first before workspace sprawl can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product and Operations channel.
3. Use the evidence from linear.app to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Linear's migration guide recommends starting with fewer teams and then adding more over time as necessary issues move into clearer product or feature groupings.

## Adjacent tactics in the same lane

- [Shared language guide before org-wide rollout](/growth-ideas/shared-language-guide-before-org-wide-rollout/) - same source, 2 shared channels, 2 shared stages
- [Read-only shutdown note after cutover](/growth-ideas/read-only-shutdown-note-after-cutover/) - same source, 2 shared channels, 2 shared stages
- [Hidden-work audit from switch pilot](/growth-ideas/hidden-work-audit-from-switch-pilot/) - same source, 2 shared channels, 1 shared stage
- [Integration cutover checklist before tracker switch](/growth-ideas/integration-cutover-checklist-before-tracker-switch/) - same source, 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The switch feels real when the old habits have nowhere to hide](/blog/the-switch-feels-real-when-the-old-habits-have-nowhere-to-hide/) - switching, product operations, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.