In the loop but out of the hierarchy
summary
Defines a clear playbook: master the current rule set by doing things the team’s way first, then note frictions in standups and retros and propose collaborative fixes; treat processes as engineering problems with test-driven iterations for meetings, code reviews, and testing practices; learn the company goals and the why by talking to sales/support/PMs and reading domain docs so tickets stop feeling like DoorDash orders; and block recurring 30‑minute focus time to prototype changes, iterate, and demonstrate measurable impact.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker intro
- 0:46What is a high impact engineer
- 3:12Getting in the loop explained
- 5:59Mastering current processes
- 8:47Identifying and proposing improvements
- 10:12Influencing the what and why
- 13:41Understanding company goals
- 15:45Navigating ambiguity and complexity
- 17:07Recap and next steps
- 18:10Focus blocks and practical tips
related talks
48mLess Process, more Guidance with a Team Playbook
42mHow Doing the Little Things Well Makes the Big Things Possible
51mHacking Your Processes
24mFrom Startup to Scale Up Designing for Growth from Day One
31mScaling Happy Engineering Teams
45mShift Your Leadership
26mEmbedding Discovery & Delivery in the Same Workflow
26mHow a team that communicates well collaborates well