Purpose
This pulse is meant to be a short weekly check, not a full survey.
Administration notes
- target completion time:
2-3 minutes - cadence: weekly during the pilot
- default reporting mode: confidential and aggregated
- use it to spot friction, rework, and support needs early
Form build notes
- keep this short enough that weekly completion is realistic
- use a controlled workflow list if the pilot scope is narrow
- review results the same week they are collected, or do not run the pulse
Recommended form fields
| Field | Type | Required? | Notes |
|---|---|---|---|
| Most-used target workflow this week | single select or short text | yes | controlled list preferred |
| Overall effect this week | single select | yes | keep to one directional question |
| Verification confidence | scale 1-5 |
yes | core weekly confidence signal |
| Rework or near-miss severity | single select | yes | none / minor / moderate / major |
| Short note on what happened | short text | no | only if something notable happened |
| Most useful support next week | single select | yes | keep response options stable |
Weekly pulse questions
1. Which target workflow did you use most with AI this week?
Free text or controlled list.
2. In that workflow, how did AI affect your work this week?
- helped clearly
- helped somewhat
- no meaningful effect
- made work harder
- did not use AI in a target workflow this week
3. How confident are you that your verification was sufficient for that workflow?
Scale 1-5
1: not confident5: very confident
4. Did AI create any meaningful rework, confusion, or near misses this week?
- none
- minor
- moderate
- major
Optional note:
- what happened
5. What support would help most next week?
- example or demo
- office hours
- manager guidance
- peer review support
- clearer guardrails
- workflow-specific coaching
- no extra support needed
Optional rotating retrieval check
Use one short rotating question after major learning events.
Examples:
- When should this workflow stay in learning mode?
- What is one verification step you would not skip here?
- What would make this task higher risk than it first appears?
Optional manager or technical-lead add-on
If the pilot wants a second viewpoint without creating a separate instrument, add 2-3 optional weekly questions for managers or technical leads:
- Where did something feel heavier, riskier, or less trustworthy than the dashboard suggests?
- Which workflow most needs support or inspection next week?
- Did you notice hidden cleanup or review burden this week?
Suggested action triggers
moderateormajorrework reports should be reviewed the same week- low verification confidence on a high-risk workflow should trigger follow-up
- repeated requests for the same support type usually indicate a workflow or enablement gap, not just an individual need