LeadDev Keynote Framework Situational Versatility Melissa DePuydt

Scrappy vs Scale: Leadership Versatility Diagnostic

As engineering leaders, our core job is to create clarity for those around usβ€”both in planned long-term architecture and in unplanned breaking-news ambiguity. Calibrate your team's current operating dials below.

The Keynote Insight: "Journalists and engineering leaders do the exact same job: creating clarity under ambiguity. The danger is applying heavy Scale governance to a Scrappy fire, or Scrappy shortcuts to a foundational Scale system."
1. Situational Operating Sliders Preset: Sev-1 Incident
95% Scrappy
⚑ Immediate Triage / Newsroom Bias πŸ›οΈ Multi-Stakeholder RFC / Consensus
10% Scale
πŸ”“ Direct Push / Lightweight Checklist πŸ›‘οΈ Strict Stage Gates / Formal Audits
90% Scrappy
πŸ“’ 15-min War-Room / Live Slack Broadcasts πŸ“‘ Bi-weekly Status Doc / Exec Decks
80% Scrappy
🩹 Deliberate Short-term Hack / Patch πŸ“ Zero Regression / Clean Architecture
15% Scale
🎯 Pod Level / Single DRI Authority 🌐 Enterprise Cross-Org Alignment
85% Scrappy
πŸ”₯ Fail Fast & Revert in Minutes πŸ”’ Multi-stage Canary / High Redundancy
2. Live Versatility Diagnostic Real-time Calculation
Operating Posture
Extreme Scrappy
Newsroom speed, high tolerance for tactical debt, minimal bureaucracy.
⚠️ Situational Risk & Leadership Move
  • β€’ High speed active: Ensure someone logs deferred technical debt tickets immediately.
  • β€’ Broadcast cadence is tight: Avoid meetings; use a single live Slack channel for status updates.
3. The Newsroom Simulator: Creating Clarity Under Ambiguity Hands-on Leadership Triage

Melissa DePuydt's keynote demonstrates that news reporters and engineering managers face identical challenges during live ambiguity. Test how you show up when a crisis hits.

Live Scenario
Breaking News / Peak Traffic Gateway Timeout
Your site's homepage traffic just spiked 800% due to an unannounced breaking news story. The main API gateway is returning 504 Gateway Timeouts for 40% of users. The executive team is panicking in #general.
Option A: Full Architectural RFC Scale Bias
Spin up a working group, draft an RFC for auto-scaling load balancers, and schedule an alignment sync with infrastructure leads for tomorrow.
Option B: Newsroom Triage + Feature Shedding Scrappy Versatility
Flip static caching flags, shed non-essential personalized recommendation widgets, and establish a single DRI Slack channel with 15-minute bulletin updates.
Option C: Cowboy Patch with No Tracking Reckless Scrappy
Directly SSH into production machines, edit nginx configs manually without logging changes, and tell everyone in Slack 'I fixed it'.
4. Customized Team Operating Charter Exportable Playbook

Generate an explicit contract for your team so engineers, product managers, and executives share exact expectations on when to move fast vs when to build for scale.

Copied to clipboard!
Enjoy this tool? Build your own with Super