Before scoping the rebuild I read three years of public complaints about Diagram View: ServiceNow Community threads, support portal posts and technical write-ups, from 2023 to June 2026. Twenty-eight distinct findings, each recorded with how often it came up and how badly it hurt. This is what turned a rebuild into a scope.
Each bar is one theme, split by how severe its findings are. Sorted by the number of high-severity findings, not by size.
Bar length is the number of findings in that theme.
Feature limitations is the biggest pile and the softest: eight findings, none of them high severity, half of them mentioned once. It is the pile that looks like a roadmap and behaves like a wish list.
Cognitive load is the opposite. Four findings, and every one of them high severity: large flows unreadable, debugging slow, the mental model mismatched, the visual complexity itself. Nobody is asking for a feature there. They are asking to be able to read the thing they already have.
That is the argument for spending V1 on organising the canvas rather than extending it, which is what the eight scoped items are.
Everything else degrades the experience. These stop it starting.
Frequency is the number of independent sources raising it. Severity is my judgement, recorded so it can be argued with.
| Finding | Theme | Severity | Sources | ||
|---|---|---|---|---|---|
| 1.1 | Flow Stages Blocking Diagram View | Compatibility | High | 5 | blocker |
| 1.2 | Plugin Availability and Enablement Friction | Compatibility | Medium | 4 | blocker |
| 1.3 | Dependency and Installation Issues | Compatibility | Medium | 2 | blocker |
| 2.1 | Cannot Display Diagram in Form/Workspace | Feature limitations | Medium | 2 | |
| 2.2 | Performance Issues with Large Diagrams | Feature limitations | Medium | 2 | |
| 2.3 | Limited Advanced Visualization Features | Feature limitations | Medium | 3 | |
| 2.4 | Auto-Arrange Insufficient for Large Flows | Feature limitations | Medium | 3 | |
| 2.5 | Feature Parity Gaps with Classic Workflow | Workflow gaps | High | 3 | |
| 3.1 | Large Flows Become Visually Cluttered | Cognitive load | High | 5 | |
| 3.2 | Debugging Complex Flows Cumbersome | Cognitive load | High | 2 | |
| 3.3 | Mental Model Mismatch: Monolithic vs. Modular | Cognitive load | High | 3 | |
| 3.4 | Cognitive Load of Visual Complexity | Cognitive load | High | 4 | |
| 3.5 | Limited Visual Organization Tools | Canvas and layout | Medium | 3 | |
| 3.6 | Canvas Navigation Friction | Canvas and layout | Medium | 2 | |
| 4.1 | Steep Learning Curve from Classic Workflow | Usability and learning | High | 5 | |
| 4.2 | Limited Advanced Documentation | Usability and learning | Medium | 3 | |
| 4.3 | Terminology and Conceptual Confusion | Usability and learning | Medium | 3 | |
| 4.4 | Non-Intuitive Interface for Beginners | Usability and learning | Medium | 2 | |
| 5.1 | Cannot Convert Workflows to Flow Designer | Workflow gaps | Medium | 2 | |
| 5.2 | Limited Error Handling Patterns | Workflow gaps | Medium | 2 | |
| 5.3 | Advanced Integration Scenarios Still Easier in Workflow | Workflow gaps | Medium | 2 | |
| 6.1 | Visual Layout for Wide Flows | Canvas and layout | Low | 2 | |
| 6.2 | Minimap Limitations | Canvas and layout | Low | 1 | |
| 6.3 | Zoom and Pan Controls Friction | Canvas and layout | Low | 1 | |
| 6.4 | No Comment / Annotation Layers | Feature limitations | Low | 1 | |
| 6.5 | No Diagram Export / Sharing | Feature limitations | Low | 1 | |
| 6.6 | No Undo/Redo in Diagram View | Feature limitations | Low | 1 | |
| 6.7 | Test Mode Limitations | Feature limitations | Low | 1 |
Method and limits: this is secondary research. It is public posts, not interviews and not telemetry. Frequency counts how many separate sources raised a thing, which measures what people write about rather than what they experience. Severity is my call. Both are recorded per finding so someone who disagrees can say where.