agentsclimarketplace

Aipom adoption impact scorecard

Skill deanpeters/ai-product-operating-model-skills/skills/aipom-adoption-impact-scorecard

Evidence-based skills for designing and improving AI product operating models

Install
npx -y skills add deanpeters/ai-product-operating-model-skills --skill aipom-adoption-impact-scorecard

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

3 things to look at

  • 20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 3 stars3 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.

What its author says it does

Copied from the file, not written here

Measure whether AI operating practices change behavior, decisions, workflows, reuse, outcomes, burden, and risk rather than merely increasing activity.

SKILL.md

4.5 KB, as published. Nobody here has run it

AIPOM Adoption Impact Scorecard

What Is It

Measure the chain from access and participation through applied behavior, workflow change, decision quality, reuse, product or business outcomes, burden, and risk. Attach each measure to a decision about reinforcement, revision, scale, or retirement.

Why Use It

Licenses, logins, prompts, attendance, and generated artifacts show activity. They do not show whether people use a practice responsibly, make better decisions, improve outcomes, or create hidden review and support costs.

When to Use It

Use before launching a capability or adoption program so baselines exist, and during recurring reviews. Scope measures to a named practice, role, workflow, and outcome.

What It Produces

  • Adoption-to-impact causal chain
  • Leading, behavioral, workflow, outcome, burden, risk, and reuse measures
  • Baselines, segments, evidence quality, and attribution notes
  • Reinforce, revise, scale, constrain, or retire decision rules

Who Should Participate

Include the practice owner, Product Operations, practitioners, workflow and outcome owners, analytics or finance, enablement, managers, and governance partners.

Evidence to Bring

Bring target behaviors, competency and workflow baselines, usage with context, work artifacts, decisions, outcomes, support burden, review labor, incidents, reuse, comparison groups or periods, and participant feedback.

How to Do It

  1. Name the practice, roles, workflow, outcome, owner, and decision horizon.
  2. Map the causal chain from availability to use, competent behavior, workflow change, and outcome.
  3. Choose the few measures that test each consequential link.
  4. Establish baselines, segments, comparison, cadence, and data limitations.
  5. Include quality, decision, outcome, burden, risk, and reuse countermeasures.
  6. Distinguish exposure, adoption, proficiency, consistency, and impact.
  7. Record attribution confidence and alternative explanations.
  8. Define reinforce, revise, scale, constrain, or retire thresholds.
  9. Assign collection, interpretation, decision, and improvement ownership.

Key Concepts

  • Use is not competence; competence is not impact.
  • Countermeasures reveal displaced work and hidden harm.
  • Attribution should match the evidence design.
  • A scorecard is complete only when results change a decision.

Organizational Applications

Use for learning systems, workflow playbooks, agent adoption, context practices, evaluation routines, governance controls, communities, and reusable skill libraries.

Common Pitfalls

  • Reporting logins as adoption
  • Measuring only enthusiasts
  • Omitting review and support burden
  • Claiming causality from a before-and-after chart
  • Combining unlike roles or workflows
  • Keeping a program because participation is high

Combine With

Use aipom-learning-system-designer to change capability, aipom-production-evidence-review for product behavior, and aipom-operating-model-retrospective for cross-system learning.

Assets and Templates

Sources

This skill is an original AIPOM synthesis of behavior change, workflow measurement, causal product metrics, adoption, and evaluation practice.

Keep looking

Skills are one crate of 328,083. 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.