← All examples

SAME INFORMATION. A DIFFERENT WAY TO SHARE IT.

Survey findings with the right denominator

A fictional navigation survey shows answered and skipped questions, overlapping themes, and a proposed follow-up without population claims.

Fictional worked example · Not a published customer artifact.

Your agent can use your own context or help you try the fictional sample. Review a draft first; nothing is published without your approval.

01 / The familiar format

You could share this as a wiki page.

A fictional wiki entry with the same underlying facts. Read it here, then compare how the HTML version presents the information.

Team wiki · Fictional example

Moss Workspace — guide-navigation survey findings

Survey method

Fielded September 1–7, 2026. Forty people submitted the voluntary in-product survey. The invitation count is unknown, so invitation response rate cannot be calculated. There was no weighting, and representativeness of all customers is not established.

Guide-navigation question

Q1 asked “How easy was it to find the guide?” with one choice: hard to find or easy to find. Of 32 answers, 20 were hard and 12 easy; eight people skipped the question. The 20/32 result is 62.5% of Q1 respondents, not all forty respondents or all customers.

Comment themes

Q2 received fifteen comments. Coding allowed multiple themes: navigation appeared in nine comments and terminology in seven. Counts overlap; they do not establish sixteen distinct respondents. The overlap count and links to Q1 answers are unavailable. No quotation text is approved; raw comments and respondent identities are excluded.

Interpretation and proposed next step

The reviewed interpretation is to ask where navigation becomes difficult. These responses do not establish population prevalence, causes or whether a redesign will solve the problem. Five follow-up conversations are proposed, not approved recruitment or a confirmed redesign. Owner, participants, consent process and dates need agreement in the research workflow. Source URLs are not supplied; actual private responses belong in their authorized system.

02 / The HTML version

Same information. See what needs your attention.

This is the complete static HTML example, not a screenshot. Scroll inside the preview to read it all. It has no live data, scripts, forms, or external resources.

Inspect the complete HTML source

This is the authored source for the example. The preview above passes through our HTML sanitizer before rendering in an isolated frame.

<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Moss Workspace · Navigation survey findings</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#faf6fa;color:#302439;font:17px/1.65 system-ui,sans-serif}main{max-width:1000px;margin:auto;padding:clamp(20px,5vw,64px)}h1,h2,h3,p{margin:0 0 18px}h1{font:500 clamp(32px,5vw,58px)/1.14 Georgia,serif;letter-spacing:-.025em;overflow-wrap:anywhere}h2{font:500 29px/1.3 Georgia,serif;overflow-wrap:anywhere}h3{font-size:19px;line-height:1.4}.label{font:700 12px/1.6 system-ui,sans-serif;letter-spacing:.08em;text-transform:uppercase}.intro{font-size:20px}.lead{background:#53355f;color:white;padding:24px;margin:28px 0}.lead p:last-child{margin:0}.grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,230px),1fr));gap:20px;margin:24px 0}.card{background:white;border:1px solid #bbc5c4;padding:24px}.metric{font:500 38px/1.2 Georgia,serif;display:block;margin-bottom:12px}section{margin:36px 0}ul,ol{padding-left:22px}li{margin-bottom:12px}.note{font-size:14px}.warning{border-left:5px solid #956118;padding-left:20px}a{color:inherit;text-underline-offset:4px}a:focus-visible,summary:focus-visible{outline:3px solid #956118;outline-offset:4px}table{width:100%;border-collapse:collapse;table-layout:fixed;font-size:15px}th,td{text-align:left;vertical-align:top;border-bottom:1px solid #bbc5c4;padding:12px 8px;overflow-wrap:anywhere}caption{text-align:left;font-weight:700;padding:12px 0}pre,code{white-space:pre-wrap;overflow-wrap:anywhere}footer{border-top:1px solid #bbc5c4;padding-top:24px;margin-top:40px;font-size:14px}@media(max-width:480px){th,td{padding:10px 4px;font-size:14px}}@media print{body{background:white}.card,.lead{break-inside:avoid}h2,h3{break-after:avoid}}
</style></head><body><main><header><p class="label">Fictional survey / September 1–7, 2026</p><h1>20 of 32 respondents found the guide hard to find.</h1><p class="intro">A signal to investigate navigation—not an estimate for all Moss Workspace customers.</p></header>
<section class="lead"><h2>Read the denominator with the finding.</h2><p>Forty people submitted the voluntary survey. Thirty-two answered the navigation question; eight skipped it.</p></section>
<section><h2>The exact question and result</h2><p>“How easy was it to find the guide?” One selection allowed.</p><div class="grid"><article class="card"><span class="metric">20 / 32</span><h3>Hard to find</h3><p>62.5% of respondents answering Q1.</p></article><article class="card"><span class="metric">12 / 32</span><h3>Easy to find</h3><p>Eight of the forty respondents did not answer Q1.</p></article></div></section>
<section class="warning"><h2>Who this sample represents is not established.</h2><p>Recruitment used a voluntary in-product invitation. The eligible invitation count is unknown, so no invitation response rate is reported. No weighting was applied.</p><p>Do not read 62.5% as a percentage of all customers or all forty respondents.</p></section>
<section><h2>Comments contain overlapping themes</h2><p>Fifteen respondents left open text. The reviewed coding method allows multiple themes per response.</p><ul><li><strong>Navigation:</strong> present in 9 comments.</li><li><strong>Terminology:</strong> present in 7 comments.</li></ul><p>These are not sixteen distinct respondents. The overlap count and links to Q1 answers were not supplied. No quotation text is approved.</p></section>
<section class="card"><p class="label">Proposed next step</p><h2>Understand where the navigation path breaks down.</h2><p>Propose five follow-up conversations. Owner, participants, consent process, and dates still need agreement.</p><p>This finding does not approve recruitment or a redesign, and does not prove that a redesign would solve the issue.</p></section>
<section><h2>Review and source boundary</h2><p>Source: the accompanying fictional survey aggregates and coding notes. No private responses or invented links are included. Record research and design decisions in the existing workflow; this page collects no responses.</p></section><footer>Fictional worked example by share/artifacts. Names, dates, figures and records are invented for demonstration. Static snapshot; no live data or automatic updates.</footer></main></body></html>

Make the next one about your work.

  1. Take the task to your agent. We provide a request with the goal, example, and checks. Copy it into the conversation where your context lives.
  2. Supply only what is missing. Use material your agent is authorized to access. Don’t substitute the example’s invented facts for your own.
  3. Review a draft before sharing. Check facts, readability, and sensitive information. Publishing and choosing who can open it are separate, explicit decisions.
Make this with my agent

No publishing connection is needed for an initial local draft. Your agent needs to be able to create an HTML file; preview and connection support vary by client.

Survey findings with the right denominator | share/artifacts