# A small product launch: document and canvas exercise

Illustrative sample prepared by the AFFiNE editorial team on 2026-10-16.
All names, deadlines and project details below are fictional. This is a reusable
work sample, not a customer case study, product benchmark or verified import result.

## Goal

Help a small team decide what to include in a first public release of a reading-list app.

## Success condition

A new user can save a link, add a note, and find the link again. The team can explain
which requests were deferred and who owns the next action.

## Inputs for the discussion

- Request A: Save a URL and a short note.
- Request B: Browse a personal reading list by topic.
- Request C: Share a public collection with another person.
- Constraint: There is one designer and one developer in this fictional team.
- Open question: Does sharing require an account for the reader?

## Suggested canvas groups

1. Scope: saving a URL, writing a note, finding a saved item.
2. Delivery: interface design, implementation, a short onboarding guide.
3. Risks: broken links, confusing sharing permissions, unclear export behavior.

Connect the sharing request to the permission question. Connect export behavior
to the question of how a user can retrieve saved material if they leave the app.
These are editorial layout instructions, not a saved proprietary canvas file.

## Example decision log

| Decision | Reason | Owner | Next action | Review trigger |
|---|---|---|---|---|
| Include private saving and topic browsing first | These complete the basic reading workflow | Designer | Draft save and find screens | A walkthrough reveals a missing step |
| Defer public collection sharing | Account and permission behavior remains undecided | Developer | Document two sharing options | The team approves the access model |

## Handoff brief

The first release supports a private reading list. The designer will show how to
save a link and find it by topic. The developer will document sharing options for
a later decision. Public sharing is outside this example's first release scope.

## Run the same exercise in each candidate tool

- Create a written brief with the goal, inputs and open question.
- Arrange the inputs visually if a canvas is part of the tool.
- Check whether the written output still explains the reasoning in a useful order.
- Record owners in text or a supported table. Do not assume this creates task notifications.
- Try the intended sharing arrangement with non-sensitive sample content.
- Export a copy in a supported format and inspect what is included.

Record actual results in the accompanying pilot checklist. Do not replace a
"not tested" entry with a claim based only on a product's marketing page.
