# Teams Store icon parity with 32px name legibility

> Keep the color icon, outline icon, marketplace icon, and abbreviated mark aligned so the brand still reads at Teams' smallest size.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/teams-store-icon-parity-with-32px-name-legibility/
- Source: [learn.microsoft.com](https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/design/design-teams-app-icon-store-appbar)
- GrowthDex source hub: [Microsoft Learn: Teams app icon for Teams Store and app bar](/sources/microsoft-learn-teams-app-icon-for-teams-store-and-app-bar-learn-microso/)
- Last checked: 2026-06-05T09:16:00Z
- Rarity: rare
- Budget: low
- Channels: Marketplaces, Brand, Trust
- Stages: teams store, icon system, brand consistency, small-screen readability


## Why this can grow

Store branding fails when the small assets stop matching the product memory. Microsoft makes the rule concrete. The color and outline icon must match, the marketplace icon must match the color icon in the package, and long words should be abbreviated so the mark stays readable when resized to 32 by 32. That matters because enterprise buyers often scan a grid before they read a paragraph. If the small mark is inconsistent or illegible, the listing looks less trustworthy before the copy gets a chance to help.

## 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 store icon parity with 32px name legibility can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Brand 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 Teams Store icon guidance says the listing must include matching color and outline PNG icons, the marketplace icon in Partner Center must match the package icon, and long app names should be abbreviated so the icon stays readable at 32 by 32.

## Adjacent tactics in the same lane

- [VS Code extension README and CHANGELOG finish the detail page](/growth-ideas/vs-code-extension-readme-and-changelog-finish-the-detail-page/) - 3 shared channels
- [Teams Store first-run account with preloaded proof](/growth-ideas/teams-store-first-run-account-with-preloaded-proof/) - 2 shared channels, 1 shared stage
- [monday marketplace partner page with installs, ratings, and support](/growth-ideas/monday-marketplace-partner-page-with-installs-ratings-and-support/) - 3 shared channels
- [Teams Store publisher verification and attestation before promo](/growth-ideas/teams-store-publisher-verification-and-attestation-before-promo/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The Teams Store page should survive the first admin review](/blog/the-teams-store-page-should-survive-the-first-admin-review/) - marketplaces, brand trust, SEO

## Advisory

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