# Teams static tab pinned before configurable detour

> Ship one strong static tab for the first read, because Teams pins the static tab by default when you also offer a configurable tab in the same scope.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/teams-static-tab-pinned-before-configurable-detour/
- Source: [learn.microsoft.com](https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/what-are-tabs)
- GrowthDex source hub: [Microsoft Learn: Tabs in Microsoft Teams](/sources/microsoft-learn-tabs-in-microsoft-teams-learn-microsoft-com/)
- Last checked: 2026-06-09T02:07:48.000Z
- Rarity: uncommon
- Budget: low
- Channels: Onboarding, Brand Trust, Product
- Stages: teams apps, tabs, first-run UX, information scent


## Why this can grow

Teams gives builders a subtle lesson about first impressions. When both a configurable tab and a static tab exist in the same scope, Teams pins the static tab by default. That means the tab most users see first should explain the job, the next step, and the proof that the app belongs there. A configuration flow can still exist, but it should not have to carry the whole introduction. The default-pinned surface is doing branding, onboarding, and qualification at once.

## 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 teams static tab pinned before configurable detour can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Onboarding and Brand Trust channel.
3. Use the evidence from learn.microsoft.com 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

Microsoft's tabs documentation says that if an app has both a configurable tab and a static tab for a scope, Teams pins the static tab by default.

## Adjacent tactics in the same lane

- [Teams message extension context matches the user moment](/growth-ideas/teams-message-extension-context-matches-the-user-moment/) - 2 shared channels, 1 shared stage
- [Teams Add pinned apps pane before rollout email](/growth-ideas/teams-add-pinned-apps-pane-before-rollout-email/) - 2 shared channels, 1 shared stage
- [Teams default install scope matches the first job](/growth-ideas/teams-default-install-scope-matches-the-first-job/) - 2 shared channels, 1 shared stage
- [Teams panels five pinned actions before More screen sprawl](/growth-ideas/teams-panels-five-pinned-actions-before-more-screen-sprawl/) - 2 shared channels

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The Teams app should meet the work before the help doc](/blog/the-teams-app-should-meet-the-work-before-the-help-doc/) - onboarding, product-led growth, brand trust

## Advisory

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