惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

P
Proofpoint News Feed
V
V2EX
WordPress大学
WordPress大学
Google DeepMind News
Google DeepMind News
Martin Fowler
Martin Fowler
小众软件
小众软件
Blog — PlanetScale
Blog — PlanetScale
月光博客
月光博客
The Cloudflare Blog
T
Tailwind CSS Blog
H
Help Net Security
腾讯CDC
爱范儿
爱范儿
人人都是产品经理
人人都是产品经理
H
Hackread – Cybersecurity News, Data Breaches, AI and More
The GitHub Blog
The GitHub Blog
Microsoft Security Blog
Microsoft Security Blog
Stack Overflow Blog
Stack Overflow Blog
D
DataBreaches.Net
C
Check Point Blog
量子位
酷 壳 – CoolShell
酷 壳 – CoolShell
美团技术团队
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I Investigated 986,317 retro cards. Teams aren't as negat...
Kelly Lewand · 2026-05-22 · via DEV Community

Every retro I've ever run starts the same way. Screen shared, columns loaded, and a long quiet second where everyone waits for someone else to drop the first card.

So I got curious about what actually lands on those boards. We host a lot of retrospectives on Kollabe, so I pulled the aggregate: 79,868 retros, 986,317 cards. Anonymised, counted, nothing fancy.

The thing that surprised me most: retros have a reputation as a place to air what's broken, and the data says the opposite.

Teams write almost twice as much about what's going right. The "What Went Well" column collects 5.4 cards on average. Its "What we want to improve" neighbour barely clears 3. "Glad" beats "Mad" by more than two to one. Whatever the format, the positive side fills up first.

And the loneliest column in agile? "Stop." At 1.5 cards on average, it's the one teams reach for least. Starting new things is easy. Admitting you should stop doing something, apparently, is not.

columns

The textbook format isn't the popular one. Start, Stop, Continue is the one everyone learns. But the single most-used format is the plainer What Went Well / What Went Wrong / What We Want to Improve, ahead of Start/Stop/Continue and Glad/Sad/Mad. We don't pre-select a format for anyone, so that's a real preference rather than a default nudge.

Friday is retro day. Measured by when a board actually gets filled in (not when it was created the day before), Friday is the most popular day to run a retro, just ahead of Tuesday. Teams reflect at the end of the sprint and the end of the week.

Action items are where good intentions go to rest. A typical retro produces about three of them. Only around one in eight ever gets marked done. I'd love to say my own team's board looks better than that. It does not.

There's more in the full breakdown, with charts for formats, columns, timing, kudos and reactions: Retrospective Statistics 2026.

Popular formats

A rule of thumb I've started using: if your retros only ever fill the "what's broken" column, you're probably running a complaints session, not a retrospective. The good stuff is a signal too. It tells you what to protect when the next reorg or deadline comes for it.

The honest caveat: this is data from teams who chose Kollabe, so it skews toward teams who like running structured retros in the first place. Your mileage will vary. But a million cards is a lot of cards, and the positivity gap holds across every format we looked at.

If you want to run one this week, Kollabe retros are free to start. Or grab whatever board you already use, add a real "Stop" column, and watch how empty it stays.