Skip to content

Choose what a public sample-workspace tour should teach

Handoff a screen-to-question map, proposed fictional-data labels and unresolved workflow dependencies.

Use cases

How should an editor choose what a public sample-workspace tour should teach using public evidence?

A sample workspace can look impressive while leaving a business evaluator unsure which example records are fictional and which workflow they illustrate. Decide how a public project-planning tour should introduce its sample content. Use vendor documentation and explicit demonstration labels, avoiding customer records, private workspace access or claims that the sample represents typical business outcomes.

Example onboarding review
Prepare a documentation-only brief to choose what a public sample-workspace tour should teach. Choose one published sample workflow, such as turning a planning note into a scheduled task. Include official walkthroughs and public demonstrations naming the product edition. Exclude customer screenshots with unexplained personal data. State which business decision the tour should clarify before inventorying every visible feature in the demonstration. Cite original passages, label fictional examples and return the decision handoff without creating accounts or changing records.
01 / Use cases

Define the tour outcome

Choose one published sample workflow, such as turning a planning note into a scheduled task. Include official walkthroughs and public demonstrations naming the product edition. Exclude customer screenshots with unexplained personal data. State which business decision the tour should clarify before inventorying every visible feature in the demonstration.

02 / Use cases

Build a sample ledger

Record each example record's stated role, fictional labeling, workflow stage and original source section. Distinguish a sample deliverable from a real customer outcome. If the publisher does not explain where records came from, mark provenance unclear instead of assuming the workspace is sanitized, representative or safe to reproduce.

03 / Use cases

Inspect the explanatory path

Compare the order of visible screens with the sequence the documentation describes. Identify where viewers need context about ownership or status labels before the example makes sense. Do not infer hidden automation or permission behavior from a smoothly edited transition between two screens in a promotional video.

04 / Use cases

Draft the tour script

Propose a hypothetical narrative naming the sample's purpose and explaining which actions are merely illustrated. Add context cards for unexplained status changes. Keep actual account setup and workspace mutation out of the plan; the researcher should not create records just to make the proposed tour appear complete.

05 / Use cases

Deliver the evaluator brief

Handoff a screen-to-question map, proposed fictional-data labels and unresolved workflow dependencies. The editor should be able to distinguish documented behavior from planned narration. No trial account, customer data or guaranteed productivity result is needed; the decision is how the public sample can teach its stated task honestly.

Keep the boundaries clear.

  • Business examples must use clearly fictional records.
  • Documentation evidence is not live execution proof.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage