Adopting a developer tool within an organization is not just a technical task, but a socio-technical challenge. The key to successful adoption lies beyond the tool itself; it’s about intentionally engaging engineers and leveraging their surrounding ecosystem for effective adoption. One of the most critical factors to getting a tool off the ground is building simultaneously: organic, real and true support from your own engineers, whilst also building a few compelling real-life use-cases. It's usually important you build this foundation before widely inviting your engineering organization to use the developer tool that you’re adopting. The steps to champion building for a developer tool look something like this: Identify internal champions, Build one or two compelling use cases, and Expand and scale.