# Teams panels five pinned actions before More screen sprawl

> Keep the room-device policy to five essential pinned apps or fewer, so the first-use actions stay on the Teams panel home screen instead of slipping under More.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/teams-panels-five-pinned-actions-before-more-screen-sprawl/
- Source: [learn.microsoft.com](https://learn.microsoft.com/en-us/microsoftteams/app-support-on-teams-panels)
- GrowthDex source hub: [Microsoft Learn: Microsoft Teams apps support on Teams panels](/sources/microsoft-learn-microsoft-teams-apps-support-on-teams-panels-learn-micro/)
- Last checked: 2026-06-09T06:09:26.000Z
- Rarity: rare
- Budget: low
- Channels: Product, Onboarding, Operations
- Stages: teams panels, shared devices, room UX, quick actions


## Why this can grow

Shared devices punish clutter faster than personal ones. Microsoft's Teams panels docs say that when there are more than five pinned apps or any unpinned apps, the rest move under the More screen. That means every extra pin is competing with the speed the room device is supposed to provide. The best panels setup is not a miniature app directory. It is a short list of actions the room actually needs in the moment. Once the critical actions fall behind More, the device starts behaving like a kiosk with bad navigation instead of a useful workflow tool.

## 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 panels five pinned actions before more screen sprawl can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product and Onboarding 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 says Teams panels show more than five pinned apps under the More screen and recommends a custom setup policy specifically for Teams panels.

## Adjacent tactics in the same lane

- [Teams panels static tab only before room-device pitch](/growth-ideas/teams-panels-static-tab-only-before-room-device-pitch/) - same source, 1 shared stage
- [Milestone suggestion during issue creation](/growth-ideas/milestone-suggestion-during-issue-creation/) - 3 shared channels
- [Workflow template ships with prewired form and destination](/growth-ideas/workflow-template-ships-with-prewired-form-and-destination/) - 3 shared channels
- [Dedicated onboarding team over cross-functional seams](/growth-ideas/dedicated-onboarding-team-over-cross-functional-seams/) - 3 shared channels

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The Teams rollout should survive the policy layer](/blog/the-teams-rollout-should-survive-the-policy-layer/) - enterprise rollout, distribution, product-led growth

## Advisory

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