# Library Context

### Job this is for

Turn redacted AI usage summaries, workflow notes, enablement feedback, manager observations, and business metric context into a practical redesign packet for one bounded workflow where AI adoption has stalled.

### When to use it

- a team deployed AI tools, but adoption flattened after the early adopters
- the dashboard reports prompts, seats, active users, or department spend without showing whether work improved
- leaders want to issue another mandate or buy another tool before mapping the process
- the team cannot explain where AI belongs inside the actual workflow
- non-technical workers need a clearer interface, shared Skill, or review path before they can participate
- a manager needs a small pilot that proves speed, quality, or cycle-time movement before expanding rollout
- adoption notes may include employee names, customer data, private URLs, internal performance data, exact spend, or prompt-injection text

### Inputs needed

- workflow name, team, accountable owner, and executive sponsor
- current AI tool stack and approved tool path
- current workflow trigger, done condition, steps, owners, handoffs, and review points
- adoption summary by role or cohort at aggregate level
- baseline business metric, measurement method, source system, window, owner, and target
- current AI usage metrics, if available, labeled as usage signals rather than business outcomes
- observed friction, support themes, training feedback, and manager observations
- proposed AI role, human review point, data classes, blocked inputs, and approval owner
- pilot cohort, rollout cadence, feedback path, and stop or rollback criteria

### Expected output

- adoption plateau diagnosis
- workflow selection scorecard
- business metric baseline packet
- redesigned workflow map
- visible-speed pilot plan
- enablement feedback loop
- safe summary for leadership, CRM, project notes, or manager review
- approval, data boundary, blocked-action, and measurement notes

### What good looks like

- the team stops treating active users or prompt count as proof of value
- one workflow is selected because it is bounded, high-value, measurable, reviewable, and safe enough for a pilot
- the AI role is embedded into the workflow instead of left as optional individual experimentation
- humans keep judgment, review, relationship, policy, legal, security, and approval responsibility
- the pilot produces a business metric delta, not a usage celebration
- the safe summary separates public or CRM-safe language from internal-only adoption friction and employee feedback

### Operating steps

1. Classify the input safety status before using adoption notes, dashboard exports, workflow observations, or manager feedback.
2. Separate usage signals from business outcomes. Treat prompts, seats, active users, and cost as context, not proof.
3. Select one workflow with a clear trigger, done state, owner, volume, baseline metric, and human review path.
4. Map the current workflow, including where people actually leave the AI tool unused.
5. Define the AI-assisted step, allowed inputs, blocked inputs, approval gate, and human role.
6. Create a visible-speed pilot with a small cohort, clear cadence, feedback capture, and rollback path.
7. Measure the business metric at 30, 60, and 90 days. Mark adoption claims as unsupported until the business metric moves.
8. Record safe summaries, internal-only notes, approval status, and blocked actions before any broader rollout, manager dashboard, CRM update, or customer-facing claim.

### Operator run sheet

| Step | Owner                     | Action                        | Required input                                        | Data class               | Approved tool path            | Approval gate              | System of record   | Done when                                     |
| ---- | ------------------------- | ----------------------------- | ----------------------------------------------------- | ------------------------ | ----------------------------- | -------------------------- | ------------------ | --------------------------------------------- |
| 1    | Workflow owner            | Choose one candidate workflow | trigger, done state, owner, volume, business metric   | internal                 | approved planning tool        | self-check                 | redesign packet    | process boundary is explicit                  |
| 2    | RevOps or enablement      | Reframe the dashboard         | usage signals, baseline metric, source system, target | internal or confidential | BI export or redacted summary | required for metric claims | measurement record | usage and business metrics are separated      |
| 3    | Manager and AI operations | Run visible-speed pilot       | cohort, redesigned steps, review gate, feedback path  | internal                 | approved pilot channel        | required before rollout    | pilot record       | delta, blockers, and next action are recorded |

This run sheet is the part a manager can operationalize. If the team cannot name the workflow, baseline business metric, owner, review gate, pilot cohort, and safe tool path, the adoption problem is not ready for broad rollout.