Findings only matter if a room full of people can act on them. This is a real shareout from a Lamps Plus Voice of Customer study — published as a live, navigable proposal rather than forty slides nobody reopens.
The study behind this shareout was ordinary mixed-methods work: a customer survey of 128 respondents, seven follow-up interviews, and a read of the competitive landscape. What made it land was the delivery. A loyalty program touches merchandising, ecommerce, IT, finance, and the showroom floor — five audiences who never sit in the same meeting and never need the same level of detail.
A deck forces one linear path through the argument, at one depth, for whoever happens to be in the room. A site lets the finance lead go straight to the revenue model, the merchandiser read only their segment, and the engineering lead filter benefits by build effort — from the same source of truth, without a follow-up meeting to re-explain it.
It also survives the handoff. Six weeks later the artifact is still a URL that renders on a phone, not a 40MB attachment in a thread nobody can find. That durability is the point: research that cannot be re-found cannot be re-used.
A shareout is a product.
Its users are a team about to make a decision.
The same UX thinking I bring to a product, turned on my own deliverable. The audience is a stakeholder under time pressure — design for them accordingly.
Stakeholders do not arrive curious about sample sizes. The first screen states the tension and the stakes; sample, instrument, and limitations sit where the people who audit them will look.
Each section carries a single argument and the evidence for it. If a section needs two claims, it is two sections. This is what keeps a long document readable in a 30-minute meeting.
Self-report and behavior disagree, and the disagreement is usually the finding. Showing both in one view stops the room from arguing about which number is real.
A static forecast invites a debate about the forecast. An interactive model with visible assumptions moves the debate to the assumptions — which is the conversation worth having.
The main line stays short. Journey walkthroughs, tier architecture, stacking rules, and sources live in an appendix — reachable in one click, invisible until wanted.
The closing section is a validation plan, not a victory lap. Naming the tests that could still kill the idea is what makes the recommendation credible.
Six stops, in the order the argument builds. Each one opens the live shareout at that section.
Cross-functional decisions with real money attached, where the audience is distributed, the detail requirements differ by role, and the work needs to stay referenceable for months. Anything with a model in it — letting people move the inputs themselves is faster than three rounds of "what if we assumed…".
Weekly usability readouts, single-team tactical findings, anything with a 48-hour shelf life. Those go in the channel where the team already works, as a short written summary with clips. The format follows the decision, the same way method follows question.