Start with the work, then choose the agent.
Define the task and the decision it supports before selecting a model or orchestration framework. Identify the inputs, the expected output, and the conditions under which the workflow should ask a person for help.
Give every workflow a boundary.
An agent should have only the tools and information its task needs. Separate low-impact preparation from actions that change customer data, release money, or publish content. Make ownership and review points explicit in the product design.
Make quality observable.
Capture representative examples of the work and agree what a useful result looks like. Include incomplete information and failure cases. A production workflow needs a way to surface uncertainty, recover from errors, and support the person responsible for the outcome.
Keep people in the architecture.
Human review is a product interaction, not a label added at the end. The reviewer needs the right context, a clear decision, and a way to correct the result. Design that handoff with the same care as the automated steps.