# Aipom Adoption Impact Scorecard

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

- Skill: `deanpeters/aipom-adoption-impact-scorecard` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add deanpeters/aipom-adoption-impact-scorecard`
- Raw SKILL.md: https://api.skillmd.com/api/skills/deanpeters/aipom-adoption-impact-scorecard/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Dean Peters (https://skillmd.com/u/deanpeters)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/deanpeters/aipom-adoption-impact-scorecard

---


# 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

- [Adoption impact scorecard template](template.md)
- [Synthetic worked example](examples/worked-example.md)
- [Weak example](examples/weak-example.md)

## Sources

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