A practical account of how a software team implemented lightweight, time-boxed process experiments to drive continuous improvement. Rather than relying on formal retrospectives or heavyweight PDCA cycles, the team adopted a simple system: write experiment ideas on stickies, discuss briefly at daily standups, set a fixed evaluation date on a timeline, and decide whether to make changes permanent. Key lessons include keeping experiments cheap and low-effort, ensuring all team members have a voice, visualizing deadlines to prevent ideas from fading, and running multiple experiments simultaneously. Concrete examples span productivity hacks, technical debt management, Kanban board evolution, testing workflows, and story decomposition. The post frames this approach through the lens of Kaizen and Taleb's optionality concept — many small low-cost experiments with unknown upside.
