Topic
Adoption and human work
Can people use and review the result?
The changed workflow needs to fit how people work. A review step can create a new queue, and an unfamiliar interface can send people back to the old process.
The onboarding example finds where work stops reaching the result people need. Review packets need inspectable sources, correction choices, and an overflow response. The team-coverage note names skills, available time, backups, and decision rights.
Notes in this topic
An override is a clue, not a new rule
A person changed the answer. Find out why before teaching the system to repeat it.
Read the noteThe pilot works. Can anyone else run it?
Give someone other than the builder a small change and a failure to handle. Watch where they need help.
Read the noteHuman review has a workload too
An approval step needs usable evidence and enough time to check it. Start by auditing one proposed result, then work out what happens when the queue grows.
Read the noteWhere did the saved hours go?
Saving time doesn't always reduce spending. Check whether the hours went into more useful work, lower overtime, or free capacity, and count each hour once.
Read the noteWhy do people keep working around the agent?
People may avoid an agent because it adds copying, searching, or uncertainty. Watch someone try to finish the job before prescribing more training.
Read the noteWho needs to be in the room?
An engineer can build the draft, but who can check the figures, approve its use, and support it next month? Reserve those people's time before promising a pilot.
Read the noteThe brief is wrong. What do you do next?
Keep the original promise, show where it conflicts with the work, and ask what the team should build instead.
Read the note