Experiment
After exhaustive research and experimentation, I have yet to come across an AI agent or SaaS platform that can arrest and visualize complex, conditionally-saturated funnels with any reliable detail or consistency while adhering to established best practices.
Experiment goals
Do flow diagramming best practices exist? If so, where are they, who defined them and which tool can I use to apply them to my work?
- Seek out flow diagramming best practices
- Challenge emerging technologies and existing SaaS platforms for their ability to execute against those best practices
- Evaluate the generated artifacts for their value-add potential
Historical context
Standing on the shoulders of giants
Did you know that humanity’s fascination with logic dates back to Socrates? From Plato, Leibniz, Boole… the investigation into human logic is a fascinating story. Those lessons and principles are still applicable to the design we do today. The essence of a best practice task flow diagram is its ability to embrace the concepts of And, Or and Not.
- This AND That
- These NOT Those
- This AND That OR Those
- IF This OR That THEN NOT Those
Best practices
Principles first approach
Before subjecting and evaluating popular SaaS platforms and emerging AI agents for their value-add potential, we should first agree on the principles and best practices to use for those evaluations.
Best practices… yes, they exist
In 2000, Jesse James Garrett introduced a set of flow-diagramming best practices that reimagined electrical schematic conventions for interaction and information design. By assigning logic-based definitions to simple geometric shapes, he transformed them into a symbolic language. These symbols, when combined correctly and consistently, allow information architects and designers to articulate complex, condition-heavy funnels with clarity and precision.
Findings: The pitfalls of today’s traditional SaaS options
After auditing three SaaS platforms, I found that each used symbology inconsistently—and none provided a clear, comprehensive definition of what each geometric shape represented or how it related to a logical operation. Simply labeling a trapezoid as a “trapezoid” offers little value to a designer (especially newbies) trying to use a trapezoid meaningfully in a diagram. Today’s SaaS platforms…
- …fail to give the geometric shapes contained in their libraries clear definition and purpose as they might relate to logical considerations
- …fail to encourage designers to consider flow diagrams as an alignment artifact versus a design artifact. If you’re adding a bunch of color to your diagrams you’re likely adding too much detail.
- …fail to establish their own internal best practices for use or embrace other established versions.