A process map is a diagram of a single process, showing each step from start to finish, the order they happen in, and the decision points where the path branches. It uses standard shapes: ovals for the start and end, rectangles for steps, and diamonds for decisions. Teams use process maps to document how work flows, train new people, and find steps worth fixing.

List the steps of your process in order, then lay them out as connected shapes: an oval to start, a rectangle for each step, a diamond wherever the path branches, and an oval to end. Connect them with arrows in sequence and label any conditions. Start simple and refine with the people who actually run the process, since they'll spot the missing steps.

A process map lays out one specific business process, its steps, roles, inputs, and decision points, to analyze and improve real work. A flowchart is the broader, more general diagram that uses standard symbols to show the logic of any process or decision. In practice the terms overlap: a process map is a flowchart applied to a business process. You can build either in Whimsical's flowchart maker.

A handful of standard shapes do most of the work. An oval (the terminator) marks the start and end. A rectangle is a process step or action. A diamond is a decision point, usually with Yes and No branches. Arrows, the connectors, show the order and direction. Some maps add a parallelogram for an input or output. Those few shapes cover most everyday process maps.

A process flow diagram is another name for a process map: a visual of the steps in a process, connected in order, with decision points where the flow branches. The term shows up across operations, engineering, and software. Whatever you call it, the goal is the same: show how a process runs from start to finish so it's easy to follow, teach, and improve.