The reading list
Essays, tech notes, and the in-between.
- Product·3 min read
Mad Tea: Nine Sentence Stems Before a Migration Nobody Wanted to Question
Moving every customer onto the new test-runner infrastructure had been decided months earlier and reviewed to death. Twelve minutes of rotating pairs found the two things the review had missed.
- Product·3 min read
Mad Tea: Reading the Room in Twelve Minutes Flat
Before committing a quarter to a mobile rewrite, I wanted to know what the team actually thought — not what they'd say in a planning meeting. Nine sentence stems, thirty seconds each, two moving circles.
- Product·3 min read
What I Need From You: A Submission Deadline and Nowhere Left to Hide
Nine days from a theme-store submission cutoff, four functions were each waiting on the other three. Banning every answer except yes, no, I'll try, and it's unclear got us to a real plan in thirty-five minutes.
- Product·3 min read
What I Need From You: Four Functions, Two Asks Each, One-Word Answers
Launching live cohort sessions needed four teams to depend on each other, and every dependency lived in someone's head as an assumption. WINFY forces the ask into the open — and permits exactly four replies.
- Product·3 min read
Fishbowl: When Engineering Needs to Hear Sales Calls Without Being in Them
Every enterprise deal was stalling on self-hosted test runners, and engineering thought sales was inventing the requirement. Putting two account executives, a solutions engineer, and the head of sales in a circle — with engineering listening — settled it in half an hour.
- Product·3 min read
Fishbowl: Letting the Whole Team Overhear the Argument
Four people had been fighting about half-day accrual rounding in a private thread for months. Putting them in a circle with fifteen colleagues silently listening around them ended the argument in fifty minutes.
- Product·3 min read
Heard Seen Respected: Repairing a Handoff Nobody Wanted to Talk About
Two designers had spent a quarter watching their work get reinterpreted in code with no conversation, and had gone quiet about it. Twenty minutes of paired listening — where the only allowed response is silence — got the conversation started.
- Product·3 min read
Heard Seen Respected: The Retro That Had to Happen Before the Retro
A theme update wiped custom CSS for two hundred merchants, and support had warned us it would. Before anyone could talk process, the two teams needed a structure where the only permitted response to a story was silence.
- Product·3 min read
Conversation Cafe: What to Do With a Decision the Team Didn't Get to Make
Leave Balance was moving to per-employee pricing and the decision was final. The support team would absorb the fallout either way — so we gave them ninety minutes to think out loud about it before the emails went out.
- Product·3 min read
Conversation Cafe: Sitting With Bad News Before Trying to Fix It
We shipped a test generator that wrote four hundred wrong assertions into customer repos. The instinct was an action plan by lunch. What the team needed first was a talking piece and four rounds of nobody being allowed to interrupt.