1 min lesson
Lower the activation barrier with shared assets
Match each case in "Lower the activation barrier with shared assets" to the signal and response that fit it.
Step 1 of 2
Lower the activation barrier with shared assetsmake the right setup the default
Every engineer who has to figure out good configuration alone is a chance for the habit to die. Build the assets once, centrally, so a new team inherits a setup that already works.
A shared project rules setup (.cursor/rules) encoding the team's stack, conventions and dos and don'ts.
New joiners inherit good context for free.
A wiki of prompts and agent recipes that worked on this codebase.
Turns one person's discovery into everyone's default.
A Slack channel and a quickstart page owned by the champions.
A place to ask, brag and unblock without going through you.
When a team ships a hard thing fast with Cursor, get that story into the channel the whole org reads, with the engineer's name on it. Public early wins create social proof and pull. People adopt because a peer they respect bragged about it, not because the vendor sent a deck.
Learn more
Full explanation
Pull the four adoption levers, in order
Pull the four adoption levers, in orderchampions are one lever of four
Champions are the engine, but they don't fire on their own. The orgs that get real adoption pull four levers together, and a champion program with no executive sponsorship or aligned incentives stalls the moment the novelty fades. Name the levers explicitly so the buyer can see where their rollout is thin.
Tie Cursor use to a customer or business outcome the org already cares about - faster delivery on a roadmap commitment, lower time-to-first-PR, fewer escaped defects.
"Adopt the AI tool" is not a why. "Ship the migration a quarter earlier" is.
Leaders model the tool, they don't just mandate it. An eng director who builds an internal dashboard or a small tool with Cursor and shows it carries more weight than any all-hands slide.
A mandate without a leader who uses it reads as theater.
Empower the early adopters early - give them access, status and air cover before the broad rollout, not after.
They are the catalysts who convert peers faster than you can.
Align the durable incentives - HR, performance reviews, recruiting - so using the tool well is part of how good work is recognized and who gets hired.
Culture is what holds adoption after the launch energy is gone.
The levers compound in sequence. A clear why gives leaders something real to model; a leader who models it gives champions cover; champions who win in public give HR and recruiting a reason to bake the habit into the culture. Skip a lever and the ones after it work harder for less.
When asked how you'd drive adoption across a large org, lead with the champion model, not your own activities. Then make the behavior-change point explicit: "developer adoption is a culture change, so I engage resistance directly and let peers carry the proof." If you can name all four levers - define the why, leaders modeling it, champions, and evolving HR and performance incentives - you signal you've run a culture change, not just a training calendar. That separates you from a CSM who only counts sessions delivered.