2025-10-02 · Team
Run a weekly demo day your team actually looks forward to
Small ritual, big payoff: showing unfinished work beats reporting status any day.
Introduction
How we structure a 30-minute demo, why half-finished features are explicitly welcome, and what the habit did to cross-team visibility and motivation.
Why this keeps coming up
Every Team conversation eventually lands on the same tension: what is comfortable for the team today versus what the project will need in a year. Neither side wins by argument alone.
A way to think about it
- Defaults outlive intentions — design them deliberately.
- Decisions are cheap to make and expensive to communicate; budget for the second part.
- Disagreement is data. Write down what would change your mind.
What I would do
Start smaller than feels useful, write the reasoning in the commit or the RFC, and revisit it on a calendar date rather than a feeling.
Closing thoughts
Taste in Team is mostly memory. Collect yours on purpose.