Mind the gap: Navigating the staff+ performance cliff
summary
Claim: a sharp Performance Cliff appears when engineers move to Staff+ because prior habits and metrics stop working. Concrete tactics: map stakeholders, run neawashi conversations, hold office hours and a weekly boss email to document influence. Examples and numbers: a daily 15‑minute standup with a co‑lead and a web community of 300 web engineers surface cross‑org problems to connect and solve. Measure outcomes by documented nudges and aligned org priorities, not code commits.
AI-written summary · about
chapters (9)
- 0:00The staff performance cliff
- 2:48Understanding the career shift
- 4:20Overcoming ego and resistance
- 8:10Building your professional network
- 11:01Strategies for stakeholder engagement
- 16:06Navigating organizational politics
- 19:20Business acumen and productivity
- 21:19Measuring and documenting impact
- 23:07Embracing the conductor role
related talks
44mIncrementally Improving Performance
31mCareer Ladders & Performance Management for Eng. Teams
44mBridging the Gap
44mEnhancing the Performance of Engineering Teams
47mMind the Gap: Career...
46mCracking the cadence of your software engineering 1:1s
29mStarting a new job as a Staff+
42mHow to Hit the Ground Running as a Staff + Software Engineer at a New Company