Growth idea action plan
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.
Why this can grow a startup
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
- Define one narrow startup segment where fewer teams first before workspace sprawl can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Product and Operations channel.
- Use the evidence from linear.app to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- 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.
Source: Linear (linear.app)
GrowthDex source hub: Linear
Last checked: 2026-05-26
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Shared language guide before org-wide rollout same source · 2 shared channels · 2 shared stages
- Read-only shutdown note after cutover same source · 2 shared channels · 2 shared stages
- Hidden-work audit from switch pilot same source · 2 shared channels · 1 shared stage
- Integration cutover checklist before tracker switch same source · 2 shared channels · 1 shared stage
Related GrowthDex essays
- The switch feels real when the old habits have nowhere to hide switching, product operations, brand trust
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory