Ways to use Tellshift

You have the material. Give it a useful next step.

A release note, a decision, a customer question. Start with something that happened, then shape a message people can understand and respond to.

Fictional examples · manually selected sources · you review the message

01

Product teams · builders

Make a release understandable.

The release notes say what changed. Your audience needs to know why it matters to their work.

Start simply

Paste the relevant release note and choose the reader.

Read the worked guideFor builders

The material

Change
A failed CSV import now identifies the row that needs attention.
Reader
An operations lead importing their first file.
Evidence
A reviewed release note and a screenshot using test data.
Limit
Bulk editing is still being explored.

Preparation with Tellshift

A draft that connects the problem, the released change and its limits, with the source alongside it.

Your decision

Confirm the change is public, the screenshot is permitted and the wording matches what shipped.

A useful next step

Give the right reader a reason to try the change or explain what still gets in their way.

Example message · fictional project

When you need more control

Optional choices for this workflow. Keep the first pass simple.

Audience
Separate a customer explanation from a technical changelog.
Review
Name the person who can confirm the release and any permitted image.
Follow-through
Choose the question or product action you want to learn from.

Product direction · proposed

Observe selected release sources and suggest a new capture when an accepted change is worth explaining.

02

Founder-led companies

Explain the choice behind the work.

You have a point of view, but turning each decision into a post takes time you do not have.

Start simply

Write down the decision, its reason and what you do not know yet.

Read the worked guideFor founder-led companies

The material

Decision
Remove the optional dashboard from first setup.
Reason
Keep the first session focused on completing one import.
Tradeoff
People discover the dashboard later.
Unknown
Whether this will make setup easier in practice.

Preparation with Tellshift

A first-person draft that preserves the reasoning and distinguishes an intended benefit from a measured result.

Your decision

Check that it sounds like you and that the tradeoff is one you want to discuss publicly.

A useful next step

Make your priorities recognizable and invite a useful response to the decision.

Example message · fictional project

When you need more control

Optional choices for this workflow. Keep the first pass simple.

Voice
Keep a separate writing sample for style; it is not factual evidence.
Rhythm
Choose a realistic review window instead of committing to daily posts.
Boundaries
Decide which company details and unresolved questions stay private.

Product direction · proposed

Reuse reviewed company context and connect a new decision to earlier updates without repeating a long brief.

03

Founders · customer-facing teams

Turn one question into a useful answer.

A question in a conversation may also be holding back people who have never asked it.

Start simply

Select an approved or anonymized question and add a checked answer.

Read the worked guideFor founder-led companies

The material

Question
Does previewing an import change the live record?
Checked answer
The preview is separate; saving requires an explicit action.
Source
A selected question and a product explanation confirmed by its owner.
Privacy
Remove names, account details and any unapproved quotation.

Preparation with Tellshift

A clear answer grounded in the checked explanation, with an angle for a personal or company voice.

Your decision

Verify the product behavior and choose whether the original wording or only the general question may be shared.

A useful next step

Help someone understand the product and reveal the next point of confusion.

Example message · fictional project

When you need more control

Optional choices for this workflow. Keep the first pass simple.

Audience
Choose existing customers, people evaluating the product or internal colleagues.
Attribution
Use a general question unless you have permission for the exact quote and credit.
Learning
Record an actual follow-up question separately from your hypothesis about its meaning.

Product direction · proposed

Surface recurring questions from explicitly selected, permitted sources for review. Broad inbox or public-topic monitoring is not implied.

04

Company teams · around 100 people

Let expertise surface between launches.

Useful work happens across the company, while communication depends on a few people remembering to share it.

Start simply

Ask one contributor for a concrete change in how they work.

Read the worked guideFor company teams

The material

Situation
A handover left the next action unclear.
Action
The team added one owner, one next step and a date to its checklist.
Firsthand source
The contributor who made the change confirms the account.
Claim boundary
No time-saving or customer-impact figure has been measured.

Preparation with Tellshift

A draft that makes one person’s practical lesson understandable, with their evidence and voice kept distinct.

Your decision

The contributor checks the facts; the responsible reviewer confirms attribution and the intended destination.

A useful next step

Make the team’s expertise visible without asking everyone to become a daily content creator.

Example message · fictional project

When you need more control

Optional choices for this workflow. Keep the first pass simple.

Scope
Begin with one contributor and one story. Coordinate additional contributors as separate reviewed inputs.
Roles
Agree who confirms facts, who reviews the message and who authorizes sharing.
Company voice
A second angle may explain the wider lesson without pretending the company had the firsthand experience.

Product direction · proposed

Offer a shared observation queue and timely prompts so relevant work can surface with less coordination.

05

Hackathon participants · 1–3 people

Keep the story moving while you build.

The plan changes quickly. By demo time, the most useful decisions are easy to forget.

Start simply

Capture one change at a natural break, then return to building.

Read the worked guideFor hackathon builders

The material

Goal
Test an onboarding flow during a 48-hour hackathon.
Change
At hour 18, the team could not use the live integration.
Decision
Use test data to explore the complete flow.
Demo boundary
A prototype with test data; the live integration still needs work.

Preparation with Tellshift

A short progress update or thread that explains what changed and keeps the prototype’s limits visible.

Your decision

Confirm what the demo actually shows and whether now is a useful moment to share it.

A useful next step

Give people a reason to follow the experiment and a concrete next step after the event.

Example message · fictional project

When you need more control

Optional choices for this workflow. Keep the first pass simple.

Timing
Choose a check-in window and a quiet working period. Skipping a post is a valid choice.
Context
Keep the initial goal, changed decision and unresolved work together in your source notes.
After the event
Choose one follow-up experiment; do not turn the deadline into an invented launch.

Product direction · proposed

Connect before, during and after in a project timeline, with pace-aware suggestions and reusable context.

06

Organizers · communities · partners

Give the event a story beyond demo day.

The event has energy and interesting projects. A useful recap needs verified facts and contributions teams chose to share.

Start simply

Bring the official event brief and one team-approved contribution.

Manual partner pilot

Read the worked guideFor event organizers

The material

Event facts
Common Ground, a fictional 48-hour hackathon, has reached demo day.
Team contribution
A team approves an excerpt about testing an onboarding flow with sample data.
Permission
Confirm exact wording, project credit, allowed destination and any image separately.
Next step
The team intends to test a live integration after the event.

Preparation with Tellshift

In a manual pilot, shape the official facts and permitted contribution into an event highlight or recap.

Your decision

The team approves its contribution; the organizer separately reviews the complete event message and its publication.

A useful next step

Help people discover the event’s projects and keep a useful conversation going afterward.

Example message · fictional project

When you need more control

Optional choices for this workflow. Keep the first pass simple.

Contribution scope
Choose the exact excerpt, attribution, destination and reuse window with the team.
Event goal
Decide whether the message should introduce projects, invite feedback or explain the event.
Follow-up
Invite a voluntary update. No response does not prove that a project stopped.

Product direction · proposed

A scoped contribution queue and continuing event story, with withdrawal and permission checks. Event registration alone never grants reuse.

Material, without another reporting ritual

Start from the work. Keep its context.

These examples begin with material you deliberately select. An observation is a reason to look closer, not an automatic instruction to publish.

Start from the work. Keep its context.
What you haveA simple starting pointWhat stays explicit
Notes, documents or release changesPaste the useful text and keep its source reference.A saved URL is a reference; it does not fetch a repository, document or meeting.
A question, reply or reported resultAdd the selected passage or result and review its meaning.Keep attribution, privacy and missing evidence visible. A manual observation is not ongoing monitoring.
A contributor’s practical experienceAsk for the situation, action and observed outcome.Confirm firsthand facts separately from a writing sample used only for style.
An event contributionUse the exact excerpt and credit the team approved.Permission belongs to the contribution and its use; joining the event is not permission to reuse private work.

Choose one piece of work to explain.

The guides give you the method, the example and the review questions. You can use them before opening a project.

Explore the guide library

Try the workspace

See what was prepared, published and learned.

Explore a populated fictional history, its observations and the evidence for the next decision. These example results do not come from connected accounts.

Interactive example · no account required

Start in the full studio ↗

Preview edits are not transferred to the full studio. Imported files remain on this device.

Example workspaces contain fictional projects and results. Changes stay in this browser; no account is connected and nothing is published.

The workspace interface is currently in English. Content can be prepared in English or French.

Start in the full studio