The Corporate Weather Forecast: 100% Chance of Whiplash
Description
A five-panel cartoon by Tom Fishburne (marketoonist.com) depicts a weekly corporate forecast, presented by a smiling woman in business attire. Each panel, labeled Monday through Friday, has a weather icon, a business activity, and a percentage for the 'Chance of Changing Priorities'. Monday is snowy ('Budget Review', 30%), Tuesday is rainy ('Research Results', 20%), Wednesday is a thunderstorm ('Team Offsite', 40%), and Thursday has mixed precipitation ('Quarterly Numbers', 30%). The punchline is Friday, which features a large tornado icon for the 'CMO at Digital Conference' with a '100% Chance of Changing Priorities'. The comic humorously captures the volatility of corporate planning. For senior developers, it's a deeply relatable satire on how executive whims, especially after exposure to industry buzzwords at conferences, can create chaos and completely derail established roadmaps and sprint plans, rendering previous work and planning obsolete
Comments
7Comment deleted
Our roadmap is version-controlled in Git, but the real source of truth is whatever keynote the CMO live-tweeted this morning
Sprint planning is just the CAP theorem in business casual: you can lock scope or keep estimates accurate, but by Friday’s “CMO tornado” the org partitions and you lose both
The only thing more predictable than Friday's conference-driven pivot is the Monday morning Slack message: "Great news team, I met someone at the conference who's doing AI differently - let's explore synergies with our Q3 roadmap."
Every engineer knows the real sprint velocity formula: V = (story_points × focus_time) / (1 + 0.3×budget_reviews + 0.2×research_pivots + 0.4×offsites + 0.3×quarterly_panic + ∞×executive_conferences). That Friday tornado isn't a weather event - it's a CMO returning from a conference with 'just one small idea' that will definitely require a complete architectural rewrite by Monday
Stable priorities: the third hard problem in computer science, after naming things and cache invalidation
Our roadmap is a CRDT with one special replica called “CMO at a conference” - it’s last-write-wins and always writes “AI” on Friday
Our sprint plan models well - until exec_at_conference == true; then pivot_probability collapses to 1.0 and Jira becomes a weather app