The Tuning Fork Silent Read
Don't ask what people think — put something concrete in front of them and force a live, in-room read.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 90%
Asking a team for their opinion produces silence; giving them something concrete to react against produces signal — the tuning fork. Kevin Yien pairs that with the silent read: rather than dropping a doc in Slack and hoping for comments, book 20 minutes, put everyone in a room or Zoom, and have them read and comment while you respond to their comments in real time. It is moving slower to move faster — collapsing the latency between question and author response.
Origin
Kevin Yien describes the silent-read meeting as a Square-ism, likely adopted from Amazon's well-known silent document-reading meeting culture. He pairs it with his own 'tuning fork' framing of feedback.
Core principles
- 01The best way to get feedback is not to ask what people think, but to put something concrete in front of them to react to.
- 02Async doc reviews decay: 'I'll get to it in 24 hours' usually means never, and the few comments you get are shallow.
- 03The real cost in a doc review is latency between a comment and the author's follow-up — collapse it to zero by being in the room.
- 04Meetings that are actual work getting done are the good kind of meeting.
- 05Moving one clock speed faster is mostly about shortening the gap between feedback and iteration.
How to run it
- 1
Produce something concrete first
Never open with 'what do you all think?' Write the doc, sketch the flow, mock the ugly version — give people an artifact to push against.
Pro tip A deliberately rough or ugly design is often the fastest way to activate a designer, who cannot stand to leave it that way.
- 2
Book 20 minutes of focused reading time
Instead of sending the doc to Slack with 'please feedback', schedule a short meeting whose entire purpose is reading and commenting on the doc together.
Pro tip Frame it explicitly: 'I need 20 minutes of focused time to interrogate something I've done.'
Watch out People will resist another meeting. This one is different — it is actual work getting done, not a status update.
- 3
Run it silently, cameras off
Nobody talks. Everyone reads and comments on the doc. The only expectation is thoughtful engagement with the artifact.
Pro tip The silence is the feature — we rarely give people space in any meeting to actually think, and thoughts get crisper when they do.
- 4
Respond to comments live
As comments land, the author replies in real time. This is where the compounding happens: the back-and-forth resolves ambiguity that would otherwise take days of async ping-pong.
- 5
Reserve the last minutes for the one real discussion
Carve out a couple of minutes at the end for the single most important discussion topic that surfaced, then take the input away for a substantial revision.
Pro tip You should exit with enough input for one big rev, not a list of nits.
In the wild
A PM posts a doc into Slack asking for feedback. Everyone is busy. One or two people chime in with surface-level comments; most never open it. The PM waits days and ships on weak input.
→ Replacing it with a 20-minute silent-read meeting produces enough high-quality input in one sitting to do a full revision and move to the next stage.
Rather than asking designers what direction they'd take, put a deliberately rough or ugly draft in front of them.
→ Designers react immediately and forcefully — 'let me make that better' — producing far more signal than an open-ended request for opinions.
Common mistakes
Asking for open-ended opinions
'What do you think?' gives people nothing to hit. Concrete artifacts create reactions; abstract questions create silence and hedging.
Defaulting to async because meetings are bad
Async review inserts hours or days between every comment and every author reply. The latency is the real cost, and it silently doubles or triples cycle time.
Letting people opt out with 'I'll get to it'
Most people won't, and even those who do lose the real-time interaction that makes the review valuable. Yien urges you to make them come to the meeting.
Is it for you?
Best for
PMs and leads who write strategy docs or PRDs and struggle to get substantive feedback from busy cross-functional partners.
Not ideal for
Fully asynchronous, deeply distributed teams across incompatible timezones, or reviews where one highly-trusted reader is the only reviewer needed.
From the transcript
“I need 20 minutes of focused time to interrogate something that I've done and we're not going to talk I'm literally going to force us…”
“the latency between a comment or question and a quick followup from the author just pushes that cycle speed really long in a way that…”
“I don't think we give enough space in any type of meeting for people to actually think”
From the episode
Unorthodox PM wisdom: Automating user insights, unselling job candidates, logging every decision, more
Kevin Yien (Stripe, Square, Mutiny)