Patterns

Pattern	What happens
The 40% trap	The later steps in a workflow absorb the time AI saves on one step.
Authority as the bottleneck	Once AI does the thinking work quickly, the wait moves to whoever has to give permission.
Build the ontology from shadow IT	The spreadsheets people keep for themselves list the categories they work with. Use those categories as the system's vocabulary.
The magic wand question	Ask, "If you had an infinitely capable intern, how would you instruct them to achieve this outcome?" The answer gives you the goal to design new steps around.
Zero-based workflow design	Start from a blank page and design the shortest sequence of steps current AI can support.
Seamful handoffs	Put deliberate friction where AI hands work to a person, so the person reviews it before approving it.
The portfolio trap	Hiring forward deployed designers on screen polish tends to bring in people who struggle with embedded work.
Ask for the demo	Ask to use the software yourself. Whether the team lets you shows how much it trusts the software.