Start with a job, not a list of features
Choose a recurring responsibility your team can describe clearly. What starts the work? What information is needed? Where does the work happen? What would count as a useful result? These questions make a more concrete starting point than a general wish to add AI.
Map the handoffs
List the tools and people involved in the job. Note where information is copied, where work waits, and where judgment is required. The employee should be designed around those real relationships.
Define the moments for review
Decide which actions an employee can take and which require your team. A draft, an approval request, and a completed task are different outcomes. Make those differences part of the design from the beginning.