Skip to main content

Preventing diagram overload as projects grow

  • January 22, 2026
  • 0 replies
  • 3 views

Seth Dillingham

I just ran into this question internally at my company. I do a lot of very large, multi-app workflow diagrams as part of creating tech designs.

The only sensible solution I’ve come up with is to do overview diagrams first that fuzz out a lot of the details, and then separate diagrams that give details on a particular area or sub-flow. In the most complicated cases (like the one I’m working on now...) I’ll zoom in “part way” to show more details but still fuzz some of it out, before finally doing the most details level of particular elements.

I think Lucid supports internal links between tabs, but I haven’t started using it yet. I’m hoping to find that there’s a robust feature set that makes it easy to “feel” like you’re navigating a single, very complex “picture” of the design.