Build a process as a sequence of procedures.
A process is a way of doing things, so you can often build it out of a series of procedures that must be done in a particular order.
Use a table of stages, or a flow chart, to demonstrate the sequence of procedures within the process.
If there are places where a person can one way or another, use a chart with a decision point.
If the procedures are done by different people, follow playscript format, indicating who does what in a parallel column, as in policies and procedures manuals.
A process, then, grows out of a series of actions and decisions. On the ground floor, you have a series of procedures.
Caution: Do not call a procedure a step. Sure, seen from high enough, an individual procedure is just one move forward in the process. But reserve the word "step" for a single meaningful action within a procedure.
Recognize that you can build many levels of process out of procedures, and groups of procedures.
Action can be viewed at many scales: at the lowest level, we look at a step. One level up, and we encounter an entire procedure. Then a group of procedures, which may be part of a process...and so on up the tower of Babel.
Your pattern for processes must accommodate action at several levels, building up from simple actions like flipping a switch to broad strategic processes, such as analysis and design.
