Anyone can generate this
Models now write documents, messages, and summaries. Text is cheap, and it all sounds the same.
Show rather than tell
A recording shows what a written update can only describe.
Teams that show their work understand each other
A demo culture is a habit. People show their work often, in short recordings, and the team learns from each one.
Share what you learned
Fixed something tricky? Record how you did it. The next person with the same problem finds your recording and does not need to ask you.
Teach once
Record how a task is done. New teammates watch it when they need it, at their own speed.
Show progress
A short recording each day shows what moved. Nobody waits for the status meeting.
Show the feature
Walk through the feature as a user sees it. The recording shows the intent and the result, not only the diff.
Keep remote teams close
A voice and a face convey tone. Text does not. Teams in different time zones stay connected between meetings.
Celebrate wins
A shipped feature deserves a two-minute demo. The team sees the result and the person behind it.
Faster than a write-up
You talk faster than you type. A two-minute recording replaces a twenty-minute document, and it says more.
More human than generated text
Anyone can produce text with a model now. A recording shows that a person did the work and understood it.
Fixed something tricky? Record how you did it. The next person with the same problem finds your recording and does not need to ask you.
Record how a task is done. New teammates watch it when they need it, at their own speed.
A short recording each day shows what moved. Nobody waits for the status meeting.
Walk through the feature as a user sees it. The recording shows the intent and the result, not only the diff.
A voice and a face convey tone. Text does not. Teams in different time zones stay connected between meetings.
A shipped feature deserves a two-minute demo. The team sees the result and the person behind it.
You talk faster than you type. A two-minute recording replaces a twenty-minute document, and it says more.
Anyone can produce text with a model now. A recording shows that a person did the work and understood it.
Backed by research
People understand more when they can see and hear you. Studies of learning, memory, and communication agree.
How often does tone come through in email?
In one study, people sent short messages, some sarcastic and some serious. How often did email readers tell which was which?
Pick a guess to see the answer.
105randomised trials, 7,776 students
Adding video to existing teaching gave a large learning gain.
Noetel et al., 2021 (opens in a new tab)Where recording wins
Typed updates and Shoyu updates both tell the team what happened. Only one of them keeps the context and the tone.
| Aspect | A typed update | Arecording |
|---|---|---|
| Time | TimeFifteen to thirty minutes to write and edit. | TimeTwo minutes to record. No edit needed. |
| Context | ContextLinks, file names, and screenshots that you paste by hand. | ContextApp, Browser, Code, and Terminal context attached by Shoyu. |
| Tone | ToneFlat. Readers guess the intent. | ToneYour voice makes the intent clear. |
| Trust | TrustReaders cannot tell whether a person or a model wrote it. | TrustThe viewer sees your screen and hears you. |
| Later | LaterLost in a chat thread. | LaterSearchable by what you said and which app or page was open. |
A human voice has more impact now
A recording is different
Your teammates see your screen, hear your voice, and follow your reasons. They know that a person did the work.
What the habit looks like
One team, one week. Each recording is short, and each one answers a question before somebody asks it.
Dashboard · This weekshoyu.cc
- Monday1:24
Checkout returns 500 on retry
Sam · Engineer
3 comments - Tuesday2:07
Payment flow, second pass
Mia · Designer
5 comments - Wednesday1:12
How to export your workspace
Lena · Support
1 comment - Thursday1:52
Billing page review, build 42
Priya · Product manager
4 comments - Friday0:48
Shipped: retry keeps the idempotency key
Theo · Engineer
2 comments
Decide when you will record
Make an if-then plan: when I finish an update, I record it. Across 94 tests, plans like this gave a medium-to-large boost to reaching goals.
Gollwitzer & Sheeran, 2006 (opens in a new tab)Ask for a comment
In a study of 51 work teams, people who felt safe to speak up asked more questions, asked for feedback, and talked about errors.
Edmondson, 1999 (opens in a new tab)Repeat it in the same routine
In one study, habits formed when people repeated a behaviour in the same situation. It took from 18 to 254 days, and 66 days was typical. Missing one day made little difference.
Lally et al., 2010 (opens in a new tab)
Start with one recording
- Record your next written update instead of typing it. Keep it under three minutes.
- Share the link where the team already talks.
- Ask one teammate to comment on a moment.
- Repeat each week. The habit grows from there.
