Move the 8 directories under bundles/ to the repo root via git mv and remove the now-empty bundles/ directory. Replace the "bundles" entry in pyproject.toml [tool.deptry] extend_exclude with the 8 moved dir names so the moved trees stay excluded from Python dependency analysis. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
1.6 KiB
Adoption and Measurement
Technical deployment is an input to adoption, not its proof. Establish a baseline before intervention and name the intended workflow, user segment, activation event, time-to-value, support owner, and outcome decision rule.
Adoption diagnosis
When usage is weak, distinguish:
- Access: can the intended people reach and use the capability?
- Activation: do they complete the first meaningful workflow?
- Workflow fit: does it remove work or add friction compared with the current path?
- Trust and education: do users understand and trust the result?
- Support and ownership: is there help, maintenance, and a named owner?
- Incentives and authority: do policy, incentives, or manager expectations conflict?
Do not prescribe more training or more features until the evidence distinguishes these causes. A technical success with poor adoption is an unresolved outcome, not a completed engagement.
Measurement record
For each metric record definition, baseline, target or decision rule, segment, source, collection period, caveats, observed value, and interpretation. Separate observed values from inferred causes. If the metric moved, test whether the intended workflow changed and whether the change is attributable enough for the decision being made.
For AI capabilities, pair workflow measures with evaluation evidence: quality, failure and adversarial cases, safety or privacy constraints, latency/cost guardrails where relevant, human override or escalation, and production feedback that can update the evaluation set. Route statistical or instrumentation method to the named catalog specialists.