Chapter 15
Organizational Navigation
A senior engineering lead at a growth-stage company is responsible for code review on a major product. The reviews typically take one day, sometimes less. The product team, under pressure to deliver features before a funding round, begins treating the reviews as a bottleneck. Stakeholders start bypassing the lead by messaging junior engineers directly, asking them to merge changes without review. The lead raises the concern: reviews are how the team catches architectural regressions, and skipping them during a migration to a new design system is precisely the moment when the risk is highest. The product team hears an engineer who is slowing them down. The lead knows, with the confidence of someone who has ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access