Feature - Persona Use Cases.

Best for: Settling "who uses this" early in a product introduction, putting use cases per segment on a single slide, separating which features belong to which role in onboarding material, and showing investors the makeup of the user base together with what each type gains

Use: Use it when the product has to be explained through its users instead of a feature list. Three to four user types stand as columns, each stacking account share, role, the job to be done, the features used, and the outcome gained. It fits the opening of a product introduction where the audience should find themselves, a one-slide compression of per-segment scenarios, onboarding material that shows each role a different screen, and investor material pairing the makeup of the user base with the value each type takes away. Carrying the account share is what makes the slide useful: a bare list of types makes them all look equally important, while the share reveals which one is actually holding the product up.

Avoid: Use team-grid or team-intro when the subjects are real people rather than role types, and company-clients for a roster of customers. When the axis is the feature rather than the person use feature-pillars or dark-feature-grid, use feature-benefit-ledger for a one-to-one mapping of feature to benefit, and feature-single-deep-dive to show one feature in depth with its screen. Go to diagram-customer-journey-map for the ordered stages a user passes through, content-case-study-results for one customer’s success, diagram-market-sizing-rings for a market split by size, and pricing-plans for what each type pays. Past five types the columns run out of width and the role lines wrap to three, so split across two slides or roll them up. If the account shares have never been counted, do not invent them, use a role-only layout instead.