1) The overall size of a workflow is important for complex designs or where a server is processing volume. The colour of the disc could be based on the code size of the action and the average CPU/memory cost of that action weighted by e.g. number of branches. This theoretically could also roll up to an overall workflow cost weighting and possibly provide recommendations i.e. split to UDA or secondary workflow etc.

2) Since we know there are two execution stacks it would be useful to see the actual execution order within the design dynamically

3) When asking someone to review or assisting someone designing a complex workflow it can often be difficult to locate the issue by description alone, adding a unique reference to each action would help here e.g. please refer to action 1.4 or block 2.0 onwards