# Product messaging brief

Richie Lin · Portfolio sample · September 2026

Illustrative sample · Fictional product

A fictional product exercise prepared for this portfolio. For the exercise only, the stand folds flat, has two fixed height settings, and supports laptops up to 15 inches. These are not claims about a Romin product.

## The brief

How would I explain a folding desk stand to someone working in a shared space?

## Worked example

Proposed feature to benefit message map

| Supplied feature | Audience hypothesis | Example copy | Proof to confirm before use |
| --- | --- | --- | --- |
| Folds flat | The same surface is used for work and other activities | “Set up for work. Fold it away when you’re done.” | Show the folding action and verify stored dimensions |
| Two fixed height settings | Users want a simple choice when arranging their setup | “Choose from two height settings.” | Confirm both positions and show the mechanism |
| Supports laptops up to 15 inches | Compatibility is a pre purchase question | “For laptops up to 15 inches.” | Validate actual model fit and load limits |

## Recommendation

Lead with the use case, then support it with a demonstrable feature.

Proposed positioning: a folding laptop stand for people whose workspace needs to clear away. This is a hypothesis to validate with customer research and verified product capabilities.

## Draft the message hierarchy

Headline: “Make room for work, and what comes after.” Support: “A folding stand with two height settings for laptops up to 15 inches.” Call to action: “See how it folds.” The copy is conditional on the exercise’s supplied features.


## Define what would change the message

If customer feedback prioritizes portability, compatibility, or setup time differently, revise the hierarchy. Avoid unsupported claims about health benefits, productivity gains, durability, or universal fit.


## Test one clear idea

Compare a shared space benefit message with a feature led message using the same audience, creative format, and destination. Choose one primary action and plan the analysis before launch.

- Track the intended next action with a consistent denominator.
- Review compatibility questions as qualitative feedback.
- Check that the message accurately describes the product.
- Share the findings with product and creative partners.

## Learning note

A product promise needs a specific customer problem and a supported capability. Test the message without adding claims the product cannot support.

## Files and sources

- Messaging matrix CSV: messaging-brief.csv


Related experience: https://richielin.com/pages/romin

View online: https://richielin.com/pages/samples/messaging-brief
