Continuous Annoyment: Bringing More Zen to a Hectic Writing Environment
summary
A documentation team adopts a one‑word framing and a time management regimen to survive a continuous development product rollout, publishes content as data for a knowledge base, and uses Cisco Spark as both the product and the collaboration platform. The experiment pairs David Allen’s Getting Things Done workflow with explicit prioritization and saying no, reduces emergency firefighting, keeps coverage current through CI driven docs, and preserves team morale during rapid releases.
AI-written summary · about
chapters (7)
- 0:00Introduction and energy
- 3:15Introducing Tina and the problem
- 5:44From continuous annoyance to Zen
- 7:34Continuous complexity and prioritization
- 10:26Zen is complex but evolving
- 11:51Rest and reframing the cycle
- 14:00Tools and conclusion
related talks
41mContinuous Learning, Teaching and the Art of Improving Yourself
52mMaximizing Productivity
45mDeveloper Joy – How great teams get s% t done
31mHow Great Tech Teams Build a Productivity Culture that Scales
49mFrom Busy To Effective Developer
50mThe Effective Developer - Work Smarter, Not Harder
43mThe Joys of Managing Engineering Teams
47mUnleashing Your Super-dev-powers