User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.
Sign up to join this community
I use process flow diagrams and find that the value they provide – the ability to scan, parse, and understand a system – starts to diminish when they become too big and unwieldy.
Can anyone suggest ways of using this diagramming style (or even entirely alternative methods) to visually represent complex systems in a way that is more likely to retain value when they systems get large?
I usually make my documentation 11"x14" (tabloid size).
Even so, some diagrams still get too large, so on the main diagram I'll show blank placeholders and diagram those subsections individually. Label each placeholder with an ID number so the subsections on the subsequent pages can be more easily found.
I've done this plenty of times, usually needing just 1-3 placeholders, but I could imagine making the overview diagram entirely from placeholders.
You could make it interactive using some simple javascript code. Check out tree diagram block on d3.js here : http://bl.ocks.org/d3noob/8375092
Interactive tree diagrams can help you hide smaller branches unless you want to see them. Hence, user navigation through large tree maps becomes easy and understandable.
One technique that's been helpful in our work is to break the processes down into successive levels of detail. Show each level with a reasonable amount of detail. Then, break down any step that doesn't have enough detail into its own diagram.
For example, mapping the process to "Get ready for school" might look like:
Even without going into any more levels of detail, we understand the process at a high level.
But, step 2 may not have enough detail for our needs. So map it out in it's own:
You'll need multiple pages and diagrams, but the goal is to keep the overall diagram sensible. Don't put too many shapes or steps on each page.
The key is to keep each page complete and have an overall meaning, not simply a continuation of a previous page with off-page references.
Reminds of this TED talk on simplifying complexity
http://www.ted.com/talks/eric_berlow_how_complexity_leads_to_simplicity?language=en
Sometimes, the complexity is a plus. You can create simplicity from it.
It depends on your goal/situation/purpose. Sometimes, you can deem information is redundant and rightfully so.
Other time, you MUST present all of the information. In those cases, find better software or prepare to make multiple drafts by hand.
