View flowcharts for 4 usecase scenarios.
PDF format, 145 KB.

”Routing” is the process of obtaining mandated permissions before releasing to publication. While at Bayer, one of my assignments was to design a "routing" module for ”BayerTracker,” a web application for collaborating on publishing projects.

Routing was a classic "messy process":

• 8 required Approvers plus any number of optional Approvers.
• Some "optional" Approvers could actually stop publication; others might be involved only as a courtesy.
• Some Approvers would use the system only occasionally, placing a heavy burden on usability.
• A project could exit routing with one of 3 statuses:
1. Approved; ready to publish.
2. Not approved until edited and re-routed; an approver demanded changes and wanted to see them implemented before releasing the project.
3. Not approved until edited, but re-routing NOT required;* an approver demanded changes but did not need to review them before release.

To define and clarify the process, I created this series of flowcharts that color-coded the path determined by each of those statuses.

* Terminology created another complication. Bayerites habitually described the third status as "Approved with changes." I felt it was better understood as a "NOT approved" state because it too sends the work back to Design. These charts were a valuable tool in establishing that understanding.