The builder's plain-English draft, then editing what it produced.
Describing what you want
Adding a new workflow offers a choice: an empty canvas, or a description. Describe the process the way you would to a new starter. Say who reviews, in what order, what happens when someone rejects, and where a threshold changes the path. The more specific the description, the less editing afterwards.
What comes back
A complete draft on the canvas: trigger, decisions in the order you described, outcomes, a reject path, notifications, and an End block. It is a starting point rather than an answer, and it is usually right about the shape and vague about the details.
Editing after
Two things are always worth checking. Assignment, because a draft cannot know your people and will have guessed; prefer a permission or a field over a name. And the reject path, because the useful version loops back into review rather than simply ending the run.
When to use it
It earns its place when you are converting an existing written procedure, or building the fifth variant of a process you already understand. Starting from an empty canvas is still the better way to learn what the blocks do, which is why it came first in this course.