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.
Why this can grow a startup
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.
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.
Source-reported evidence
Source: Microsoft Learn: Tabs in Microsoft Teams
Teams defaults to pinning the static tab first when both static and configurable tabs exist in a scope.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Onboarding, Brand Trust, Product is relevant to teams apps, tabs, first-run UX and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Onboarding and Brand Trust, using evidence from Microsoft Learn: Tabs in Microsoft Teams as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.