Recognize the problem?
Useful work. An unclear message.
The update says what shipped but gives readers little reason to care. Copying it onto a company page and a personal profile repeats that weakness. Start with the same facts, then choose what each voice can contribute.
What you will make
You will leave with a source note, two distinct drafts and a relevant invitation for each. Use any document; no Tellshift account is required.
What you need
- One project note, release entry or firsthand explanation that you are allowed to use.
- A named company audience and a named personal audience; they may overlap.
- The people who can confirm the facts and agree to each intended use.
Step 01
Extract the useful moment
Choose a decision, difficulty or discovery your audience could recognize. Record the situation, what someone did, and what was observed. Keep the original note beside this summary for review. The task is a starting point; the reader’s problem gives it meaning.
“Added a mapping preview” becomes “Supplier files use different column names, so users need to check how each field will be interpreted.”
Step 02
Separate fact, interpretation and boundary
Mark what the source establishes, what the author thinks it means, and what remains unknown. Remove identifying details before drafting. If the source contains no measured improvement, explain the design choice without adding a percentage or a time-saving claim.
Fact: the preview shows the mapping. Interpretation: this makes the decision visible. Unknown: whether it reduces import errors in everyday use.
Step 03
Give the company and the person different jobs
The company can explain whom the work helps and how its approach addresses a problem. The individual can explain the judgment behind the work, a mistaken assumption or a lesson they can own. Write each opening separately; replacing “we” with “I” is not enough.
Company question: “How do you check an unfamiliar supplier file?” Personal question: “Which assumption did I have to change while building this?”
Step 04
Review both destinations
Check factual claims with the source owner. Review authorship, client references and permissions for each destination separately. Let the person rewrite anything they would not say; a campaign must not assign them a belief.
Step 05
Invite one useful response
Ask a question the reader can answer from experience. Record a relevant reply and choose the next explanation it calls for. If the drafts repeat each other, share the stronger one first; save the other until it adds something.
Fictional worked example
The facts stay. The perspective changes.
The starting material
Fictional project note: “Supplier files label the same field differently. We added a preview of incoming columns and expected fields before import. I had assumed the column names were obvious. We have not measured error reduction. The supplier and sample records must remain private.”
The company or project voice
The personal perspective
Make it your own
One source, two voices
Copy this into the tool you already use. Fill in what you know and leave unknowns visible.
Source and owner: Situation: Action taken: Observation and supporting detail: What is unknown or private: Company reader and problem: Company opening: What this says about our approach: Useful next question: Personal reader and problem: My decision or changed assumption: What I learned firsthand: Useful next question: Reviewers and permitted destinations:
Stay faithful to the work
The boundaries to keep.
- Both drafts above are fictional examples, not customer evidence or Tellshift feature announcements.
- Permission for a company post does not automatically cover an employee’s personal account, or the reverse.
- One post can start a conversation; it cannot establish expertise, reach or commercial demand on its own.
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