What makes a chart look finished when it is not?
Even spacing and a title. Neither one tells you whether a step was skipped. A chart can be tidy and still hide a decision inside a rectangle that says Review. Review is a diamond if it can go two ways.
Color is the other disguise. A legend nobody remembers is not a control. FlowSimp can color a shape. Use that for one meaning, such as a waiting step, and write the meaning in a label too.
How long should a label be?
Short enough to read in the export at the size you will actually send. If you need a sentence, the shape is two steps or the sentence belongs in the procedure next to the picture.
Questions end with a question mark. Actions do not. That single habit stops people from drawing an arrow out of a statement that was really a choice.
Ready to draw?
No signup. Opens instantly in your browser.
How do you review without a workshop?
Send the PNG or the read-only link and ask one question: where do you hesitate? Collect those points. Do not add every suggestion as a shape. A suggestion that does not change the next step is a comment, not a box.
Then look at the diamonds. Each one should still have two answers after the review. Reviews like to add a third arrow called Sometimes. Sometimes is a missing question.
What are the steps?
- Limit the scope. One trigger and one ending. A second trigger is a second chart.
- Shorten the labels. A verb and an object. Email the policy. Not a paragraph about the policy.
- Check every diamond. One question. Two labeled answers. If both answers go to the same place, delete the diamond.
- Test with a stranger. Ask them to say the next step out loud. Do not help. Fix the shape where they stop.