Choose a bounded use case
Prefer work with clear inputs, a measurable outcome and an existing accountable owner. Avoid beginning with high-impact automated decisions.
Define the information boundary
Decide what information may be used, where it can be processed, how long it is retained and which outputs require human review.
Measure usefulness and failure
Record accuracy, time saved, exception rates and the effort required to review outputs. A pilot should expose failure modes, not hide them behind a polished demonstration.