developer-adoption-program

name	developer-adoption-program
description	Plan and measure a developer adoption initiative using target personas, activation behavior, enablement assets, channels, feedback, and downstream usage.

Developer Adoption Program

Use when this procedure is the primary professional method needed for the assignment.

Procedure

1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using developer personas, SDK/product telemetry, channel access, content inventory, and support capacity. Do not fill material gaps with assumptions when they can change the result.
3. Define the developer segment and first-value action, coordinate assets and outreach, instrument adoption, and compare activation/retention with baseline.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

Quality gate

The program demonstrates whether developers reached meaningful product value, not merely whether content was viewed.