agentsclimarketplace
Sign in

Enablement program design

Skill nthnclrk/enablement-skills/skills/enablement-program-design

Diagnose an unclear field-performance problem or design the cross-functional wrapper for a multi-intervention revenue enablement initiative, including charter, capacity, pilot, governance, rollout, and measurement. Use when several workstreams must operate as one program. Route standalone launch readiness to product-launch-enablement, recurring coaching rhythm to manager-coaching-cadence, formal readiness standards to certification-program-builder, new-hire curriculum to onboarding-program-builder, and quarter-level prioritization to quarterly-enablement-planner.From its SKILL.md

Install
npx -y skills add nthnclrk/enablement-skills --skill enablement-program-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.8 KB, as published. Nobody here has run it

Enablement program design

Design a program that changes observable field behavior and gives managers something to inspect. If it reads like a kickoff deck, rewrite it.

A program is one performance problem, one target behavior, and one inspection. Content calendars, completion dashboards, and "journeys" are not a program.

Program. "AEs will ask one inspectable qualification question before they book SE time. Managers check two calls a week. We stop if inspected calls do not show the question by week 4."

Kickoff. "A four-week enablement journey with kickoff, certification, office hours, and a dashboard of completions."

If a manager cannot tell from a live artifact whether the behavior happened, it is not done.

Confirm Inputs First

Ask only for the inputs that change the design:

  1. The performance problem, the evidence, and the outcome at risk
  2. The current behavior, the target behavior, and where it must show up
  3. Sponsor, accountable owner, and who can approve scope
  4. Real delivery and manager capacity
  5. What is already running this quarter

If the problem, owner, audience, or decision authority is unknown, return a discovery brief. Do not invent capacity, baselines, or dates.

Read The Right Reference

Read references/program-charter-template.md for the kickoff-deck tell, diagnosis rules, and the charter shape. Skip it if they already diagnosed the barrier and only want the wrapper filled in.

Default Workflow

  1. Diagnose the performance problem. Separate evidence from interpretation. Skill and knowledge are not the same as process, product, incentive, capacity, territory, or management. Done when you can name the cause, the confidence, and what remains unknown. If enablement is not a material response, stop and name the owner who should take it.
  2. Define the target change. Role, workflow moment, current behavior, target behavior, the evidence that it occurred. List what this program will not solve. Done when a manager can inspect the behavior in the workflow, not in a quiz.
  3. Design the minimum viable program. Match each intervention to a diagnosed barrier. Keep only the assets, practice, manager inspection, and workflow support that produce the target behavior. Cut anything that does not earn its place.
  4. Set the capacity envelope. Audience volume, facilitator time, manager time, content effort. Reduce scope or sequence cohorts when the plan exceeds capacity. Do not invent hours to make it fit.
  5. Build the pilot. Cohort, entry, duration, evidence, and the rule to continue, adjust, or stop. Done when week-N evidence can kill the program.
  6. Establish governance and measurement. Decision rights, approval gates, one primary behavior metric, one primary business outcome. Record definitions, sources, baseline status, and limitations. Do not invent baselines or targets.
  7. Produce the charter. Make unresolved decisions and next approvals visible. Label it a draft until hard-stop decisions are resolved.

For a standalone launch kit use product-launch-enablement. For a coaching rhythm use manager-coaching-cadence. For pass/fail standards use certification-program-builder. For new-hire ramp use onboarding-program-builder. For what will not happen this quarter use quarterly-enablement-planner.

Output Contract

Return a charter a first-time owner can run:

  • Decision brief: problem, evidence, target behavior, outcome, and open decisions
  • Exclusions: adjacent problems this program will not solve
  • Intervention map: barrier, response, manager inspection, owner
  • Capacity decision and the scope cut it forced
  • Pilot with continue / adjust / stop
  • Measurement with sources, baseline status, and limitations
  • Risks and approvals

Do not add a quarter stack or a launch kit unless asked. Do not enroll anyone or publish materials.

Quality Bar

  • A manager can inspect the target behavior in the workflow.
  • The charter refused to be a kickoff deck.
  • Every intervention ties to a diagnosed barrier.
  • Scope fits named capacity, or the conflict is visible.
  • The pilot can stop the program.
  • Facts, interpretations, assumptions, and unknowns stay distinct.
  • No invented capacity, baselines, or dates.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.