Use cases / 02 Documents

Improve an onboarding proposal

Discuss the paragraph that needs work, with the supporting files close at hand.

A proposal becomes easier to review when the decision and its supporting evidence are in one place. This onboarding proposal asks new users to invite teammates before they have experienced anything useful themselves.

Read the proposal

Open the rendered Markdown and scan the first-session sequence. The file list keeps the supporting research nearby, so you can check what happened in user sessions while evaluating the proposed flow.

Read the proposal alongside its supporting research. Read the proposal alongside its supporting research.
Read the proposal alongside its supporting research.

Challenge a step

Point to the sequence and ask for a first win without involving anyone else. That gives the agent a clear revision to make: move invitations after the user has something worth sharing.

Question the invitation step in the first-session sequence. Question the invitation step in the first-session sequence.
Question the invitation step in the first-session sequence.

Inspect the revision

Follow the agent’s fix link to the new version. Project creation, a first milestone, and a useful dashboard now come before invitations. The original proposal and discussion remain available if you need to revisit the reasoning.

The revision lets new users reach a useful dashboard alone. The revision lets new users reach a useful dashboard alone.
The revision lets new users reach a useful dashboard alone.

Try this example →

Real r3 screens. Fictional data and scripted replies.

View Markdown