Recognize the problem?
Useful work. An unclear message.
A weekly update can become a task list or an opinion detached from the work. Neither explains why your company makes its choices. A useful update connects a decision, its reason and the uncertainty that remains.
What you will make
You will have a founder note, a shorter company version and a reusable decision record. A weekly review rhythm does not require publishing every week.
What you need
- A decision you made or can explain firsthand, with notes you are permitted to use.
- One reader you want to help: a prospective customer, collaborator, candidate or peer.
- An observable next question; a strong opinion alone is not evidence of a result.
Step 01
Pick the decision, not the busiest week
Choose something you postponed, simplified, changed or stopped, and explain the pressure behind it. If nothing changed, explore an unresolved question or skip the update. Readers learn from the judgment inside the activity, not how busy the week was.
“We had customer calls” becomes “We paused the broad dashboard to test whether one handover workflow is useful on its own.”
Step 02
Keep the evidence close
Name what informed the decision: a permitted conversation note, a product observation or a constraint. Describe what it supports and what it does not. A customer expressing interest supports a question worth investigating; it does not establish willingness to pay or prove that the solution works.
Step 03
Explain the tradeoff in your own words
Write the option you chose, the option you left aside and the cost of that choice. Use language you would use in a real conversation. A point of view becomes recognizable through specific judgments, not through adding forceful adjectives to an ordinary announcement.
“We chose a narrower first version. That lets us inspect one handover, but it will not show the whole project portfolio.”
Step 04
Separate personal judgment from company commitment
The founder can explain their reasoning and what might change their mind. The company version should make the current direction and reader relevance clear. Check that a personal exploration has not become a delivery promise when written as “we will.” Review both versions before either is shared.
Step 05
Leave a question you can act on
Ask the reader about a comparable situation or invite a specific walkthrough if one is available. Keep a small reply log: what was said, how you interpret it, and the next action. At the next review, decide whether that response changes the product, the explanation or neither.
Fictional worked example
The facts stay. The perspective changes.
The starting material
Fictional founder note: “Discovery conversations keep returning to unclear handovers. We paused a multi-project dashboard and are testing a single handover checklist. No adoption or time-saving result yet. Customer names and quotations are not cleared for publication.” Before: “Busy week. Great conversations. Exciting things coming.”
The company or project voice
The personal perspective
Make it your own
The founder decision note
Copy this into the tool you already use. Fill in what you know and leave unknowns visible.
Reader: The situation this week: The decision: The evidence or constraint behind it: The alternative we left aside: What this costs or leaves unresolved: My point of view: What the company can commit to now: What would change my mind: One useful question or next action:
Stay faithful to the work
The boundaries to keep.
- The scenario is fictional; its conversations and proposed test are not Tellshift customer results.
- Removing a customer’s name may not remove identifying context. Use an invented example when you cannot safely explain a real one.
- A founder’s public exploration should not quietly create a contractual or delivery commitment for the company.
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 workspaceFounder-led companies