Recognize the problem?
Useful work. An unclear message.
A useful question, decision or delivery is already recorded. Scattered across tools, it is easy to miss or repeat without explaining why it matters.
What you will make
Finish with a checked story brief, two drafts and a useful question. Work in a plain document; no Tellshift account is required.
What you need
- A few excerpts about one project or event that you are permitted to reuse.
- The original source, date and owner for each excerpt.
- One intended reader and someone who can confirm what actually changed.
Step 01
Choose a small slice of work
Choose one project and ask: what changed that a reader would care about? Select a few excerpts yourself. A meeting note, chat message and release entry may suffice. Keep source links for verification; leave unrelated conversation behind.
Step 02
Find the decision, lesson, question or delivery
Label each excerpt’s contribution. A decision explains a choice; a lesson changes an assumption; a question suggests an explanation; delivery establishes available behavior. Prefer a connected moment over a task list.
“Added an owner field” becomes “A handover needs to show who acts next, not just what happened.”
Step 03
Reconcile the sources before counting the evidence
Group excerpts about the same event. A meeting note copied into chat is the same observation, not more customer evidence. Separate facts, plans and interpretations; resolve disagreements with the owner. A merged change does not prove release: check the release entry and availability.
Fact: the field is released. Plan: reminders. Interpretation to test: a visible owner may make the handover clearer.
Step 04
Give each voice a useful job
The company explains the reader’s problem and the available change. The person explains a firsthand decision or lesson. Keep drafts beside the evidence, remove unsupported claims, then ask the author and reviewer to check the wording.
Step 05
Choose the next conversation
Ask a question that could improve the next decision. Keep relevant replies with the brief: do they clarify the problem or challenge your interpretation? Revisit this selection at a useful project moment. More collection does not automatically improve the story.
Fictional worked example
The facts stay. The perspective changes.
The starting material
Fictional source bundle for a request-tracking tool. Monday, Maya’s meeting note: “Our handover explains the task but leaves the next owner unclear. I assumed a role label was enough. We chose an explicit next-owner field.” Tuesday, team chat repeats that decision; it adds no new user observation. Wednesday, the decision document lists reminders as future work. Thursday, release 1.4: “Next-owner field available in all existing workspaces. Reminders are not included.” The release owner confirms that status. No effect on missed handovers has been measured. These excerpts are approved for this fictional exercise.
The company or project voice
The personal perspective
Make it your own
Work signals → story brief
Copy this into the tool you already use. Fill in what you know and leave unknowns visible.
Project and intended reader: Question worth explaining: Source / date / owner / permitted use: Exact useful excerpt: Decision, lesson, question or delivery: Same event as another source? Which? Confirmed fact and evidence: Planned, not available: Interpretation to test: What remains unknown: Company: reader problem → checked change: Personal: my decision → what I learned: Reviewer and chosen destination: Useful next question: Reply or follow-up to revisit:
Stay faithful to the work
The boundaries to keep.
- The project, source bundle and drafts are fictional; they establish no product or customer results.
- This is selected-context work. Recurring connections and observation from these source families are proposed Tellshift capabilities, not live adapters.
- Access to a source alone does not authorize every public use. Keep the agreed scope and attribution with the brief.
A concrete next step
Try it with your own update.
Set up an empty workspace, add your material and prepare your content in the public studio.
No sign-in required. Progress stays in this browser; nothing is submitted or published. The guided workspace currently uses English. You can prepare content in English or French.
Set up my workspaceCompany teams