# Shared language guide before org-wide rollout

> Publish a short internal guide that shows how to label work, name teams, and find daily views before the wider migration starts.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/shared-language-guide-before-org-wide-rollout/
- Source: [linear.app](https://linear.app/customers/automattic)
- GrowthDex source hub: [Linear](/sources/linear-linear-app/)
- Last checked: 2026-05-26
- Rarity: rare
- Budget: free
- Channels: Product, Documentation, Operations
- Stages: switching, language, adoption, internal docs
- Key metric: Automattic later reached 80%+ weekly employee usage and 12,000+ issues per month after the broader rollout.

## Why this can grow

A switch fails quietly when every team invents its own vocabulary. A short language guide keeps the first week from turning into translation work. It helps people route work logically, lowers the cost of asking for help, and makes the new system feel coherent to people outside the inner circle. That coherence is part of the product being sold, especially when the buyer is really choosing a new operating model.

## 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 shared language guide before org-wide rollout can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product and Documentation 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

Automattic shared a short "Linear tips and tricks" guide with examples for where to find work each day, how to label work, and how to name teams so everyone was using the same language.

## Adjacent tactics in the same lane

- [Fewer teams first before workspace sprawl](/growth-ideas/fewer-teams-first-before-workspace-sprawl/) - 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.