Engineering teams fall into two categories as companies scale: back-office teams that serve internal developers with tools and infrastructure, and glue teams that work on cross-cutting product features like authentication and billing that directly impact users. Back-office teams should be delayed as long as possible since they create distance from customers, while glue teams should be formed earlier to maintain product quality in shared areas. The key is maintaining direct connection to user value rather than optimizing for internal convenience.
Table of contents
Two types of teamsResist the calls for nice-to-havesAddress must-have gapsThe bottom line🧠 Good reads for people who build cool stuffSort: