Flowchart Tips
- Keep your audience in mind and gear the detail in your chart to them. Clear communication is a key goal of flowcharts.
- If the process you are charting involves different teams or departments, consider using a Swimlane Diagram to clearly delineate responsibilities and handoffs.
- Use on-page or off-page connectors to âeditâ your chart and make it flow logically. This can allow you to break up a chart into separate pages and still flow well.
History
Flowcharts to document business processes came into use in the 1920s and â30s. In 1921, industrial engineers Frank and Lillian Gilbreth introduced the âFlow Process Chartâ to the American Society of Mechanical Engineers (ASME).  In the early 1930s, industrial engineer Allan H. Morgensen used Gilbrethâs tools to present conferences on making work more efficient to business people at his company.  In the 1940s, two Morgensen students, Art Spinanger and Ben S. Graham, spread the methods more widely. Spinanger introduced the work simplification methods to Procter and Gamble. Graham, a director at Standard Register Industrial, adapted flow process charts to information processing. In 1947, ASME adopted a symbol system for Flow Process Charts, derived from the Gilbrethsâ original work.
Also in the late â40s, Herman Goldstine and John Van Neumann used flowcharts to develop computer programs, and diagramming soon became increasingly popular for computer programs and algorithms of all kinds. Flowcharts are still used for programming today, although pseudocode, a combination of words and coding language meant for human reading, is often used to depict deeper levels of detail and get closer to a final product.
In Japan, Kaoru Ishikawa (1915-1989), a key figure in quality initiatives in manufacturing, named flowcharts as one of the key tools of quality control, along with complementary tools such as the Histogram, Check Sheet and Cause-and-Effect Diagram, now often called the Ishikawa Diagram.
Symbols
Here are some of the common flowchart symbols. For a more comprehensive list, see our full flowchart symbols page.
| Terminal/Terminator |  |
| Process |  |
| Decision |  |
| Document |  |
| Data, or Input/Output |  |
| Stored Data |  |
| Flow Arrow |  |
| Comment or Annotation |  |
| Predefined process |  |
| On-page connector/reference |  |
| Off-page connector/reference |  |
Â
Flowcharts for computer programming/algorithms
As a visual representation of data flow, flowcharts are useful in writing a program or algorithm and explaining it to others or collaborating with them on it. You can use an algorithm flowchart to spell out the logic behind a program before ever starting to code the automated process. It can help to organize big-picture thinking and provide a guide when it comes time to code. More specifically, flowcharts can:
- Demonstrate the way code is organized.
- Visualize the execution of code within a program.
- Show the structure of a website or application.
- Understand how users navigate a website or program.
Often, programmers may write pseudocode, a combination of natural language and computer language able to be read by people. This may allow greater detail than the flowchart and serve either as a replacement for the flowchart or as a next step to actual code.
Related diagrams used in computer software include:
- Unified Modeling Language (UML): This is a general-purpose language used in software engineering for modeling.
- Nassi-Shneiderman Diagrams: Used for structured computer programming. Named after Isaac Nassi and Ben Shneiderman, who developed it in 1972 at SUNY-Stony Brook. Also called Structograms.
- DRAKON charts: DRAKON is an algorithmic visual programming language used to produce flowcharts.
