2 min lesson
Build it once, reuse it everywhere
Put this idea into your own words: "Build a reusable curriculum and self-serve assets you can tailor per stack."
Step 1 of 3
Build it once, reuse it everywhereyou serve many accounts
You're one SA across multiple strategic accounts, so artisanal one-off sessions don't scale. Build a reusable curriculum and self-serve assets you can tailor per stack: a session outline, a Rules starter kit, a short recorded walkthrough and a one-page 'first week with Cursor' for new joiners.
'40 people attended' is an awareness metric, not an enablement metric. The real question is whether workflows changed: did weekly-active and Agent depth rise in the trained cohort in the two weeks after the session? Attendance with flat usage means the enablement failed, however full the room was.
Learn more
Full explanation
Catch the post-training drop-off
Catch the post-training drop-off
- Recurring office hours where engineers bring a real task and leave with it solved in Cursor.
- An async support channel staffed fast enough that a stuck engineer gets unstuck before they revert to their old editor.
- A one-week and four-week check-in on the trained cohort's depth metrics, so you see the drop-off forming and intervene.
If asked to design enablement, refuse the generic-demo framing out loud and anchor on three things: their repo, the four high-impact habits and a post-session depth metric. Cite the pattern that mentorship and office hours, not one-time training, are what lift sustained usage.
Said out loud: “I wouldn't run a generic demo. I'd run the session on your monorepo, drill context curation through verify-before-merge, and I'd judge it two weeks later on whether Agent depth moved in that cohort - not on how the room felt on the day.”
Learn more
Optional practice