One box called Calibrate
An auditor at a torque-wrench calibration lab asks for the readings behind last quarter's certificates. For 37 wrenches there are none, because nobody tested them. The certificates are real records in the lab's software, saved with the values each wrench was supposed to hit. The software was built from a flowchart with a single step between booking a wrench in and closing the job, a Process called Calibrate, and the developers read that box as a step the system runs. On a busy day, pressing the button was enough.
That one box hid three different things: work only a person can do, data that has to outlast the job, and something a person needs to see. Classic flowcharts mark how a step happens, not just that it does, and they have a symbol for each. Redrawn, Calibrate becomes five steps.
The step that waits for a person
Manual Operation is a step only a person can perform. Here the technician clamps the wrench in a torque tester and pulls it, and no software in this lab can do that part. So the flow stops at this step until a person has finished, which may take ten minutes or, if the tester is booked, until tomorrow. A Process box hides that wait. A Manual Operation flags a step the system cannot complete alone, and since it still connects one-in, one-out, it describes the kind of step, not new control flow: the software has to build the wait. It also raises the question the original diagram never asked: how does the software know the test happened?
The closest this diagram comes to an answer is Enter readings, a different symbol on purpose. A Manual Operation is work a person does, here on the physical world, while a Manual Input, the symbol Data, documents & manual input introduces, is a person typing data into the flow; collapse the two and the diagram either gives the result no way in or suggests that typing a number is the test.
The symbol says that a person is needed, not which one; Swimlanes & responsibility draws who does what. To place a Manual Operation yourself, the Expense Approval Workflow challenge has one waiting on a manager's approval.
What outlasts the job
Stored Data is the symbol for data kept to be read again, and on the Grid it sits in line as the step that reads or writes that data. Save result writes the readings and the verdict to the wrench's certificate record, which is what an auditor will ask for next year. A step that reads the old result when the wrench comes back uses the same symbol. Without it, the steps that persist state look like every other box, and a reviewer looking for what the flow remembers has to open them all.
Stored Data says the data is kept to be read later, by a later run or by someone else; Input/Output says only that it crosses the flow's boundary. Stored Data states that intent and guarantees nothing; Storage & ordering stencils separates it from Internal Storage.
The panel on the bench
Display is output shown to a person: the panel on the bench shows pass or fail. The same panel also asks for the readings, so it is tempting to draw the whole screen as one Display, but typed-in data is Manual Input, not just output. Mark both as Display and the diagram shows data going one way, with no sign of where the readings came from. A Display also promises nothing once the screen moves on: a verdict that has to be proved later belongs in Stored Data.
Finding the next Calibrate
The redrawn flow would not have stopped anyone pressing the button: the software still has to refuse a result with no readings. What changes is what the developers see when they build it, a step that waits for a person and a save that comes after the readings.
In the Data Backfill Migration challenge, mark the batch read and the batch write with Stored Data instead of a generic Process, so every read and write to persistent state shows without opening the node, and mark the progress the brief asks for with Display. Then open a flow of your own and put each Process box through three questions: does it read or write data kept for later, does it wait for work only a person can do, and does it show something to a person? A yes to any of them means the box is hiding what Calibrate hid.