Describe the job, not the software
Write it as you would explain it to a new colleague: what starts it, what has to happen and what good looks like. For example: when a delivery is going to be late, tell the customer before they ask, with the new date, and let customer service check it first.
Make the choices that matter
Choose the tools it may use, who approves, how sensitive the data is and your working hours. A person always approves before anything leaves the business or touches money; you can ask for two approvers on money.
Read it, then try a dry run
Every step, branch and approval is shown. The dry run walks the workflow with sample data and says what each step would do, without reading, changing or sending anything.
Start in shadow
After you approve it, run it for two weeks with a person approving every step that acts. When approvers rarely change what it proposes, let it run under your normal approval settings.