Nerd Sniping
summary
At a 100-person company a deliberate tactic called nerd sniping turns customer tickets and curious questions into autonomous projects using open questions and an experiment template (hypothesis, test, outcome in Google Docs), plus timed hack weeks and manager book clubs (Slack No Hands). Metrics are concrete: long threads of 100+ messages, lower-status engineers initiating work, and one customer feature delivered within 24 hours after a public nudge. Consent checks and timeboxes prevent burnout and keep outcomes tied to measurable customer impact.
AI-written summary · about
chapters (13)
- 0:00Nerd Sniping concept
- 1:48Autonomous teams and XKCD
- 3:37Nerd Sniping as tactic
- 5:46Fly.io examples
- 8:16Open questions
- 10:46Experiment templates
- 12:53Leadership discussions
- 15:01Maso’s motivations
- 17:08Customer impact
- 18:53Power dynamics
- 20:39Team readiness signs
- 22:32Autonomy with direction
- 23:37Two techniques
related talks
34mBecoming a team, one pixel at a time
32mDeveloper productivity 2.0
24mBottom up org change and evolution
47mDoing I.T. for SCIENCE! - Sprints, Startups and the Scientific Method
23mUsing Data to Bridge Product and Engineering Teams
19mReducing Context Switching & Unplanned Work Through Platform Engineering
11mLightning Talk: Building a Community Inside your Company
25mRethinking measurement for high-performing teams