# Looking for Organizational Suggestions

**URL:** <https://discourse.nodered.org/t/looking-for-organizational-suggestions/48927>\
**Category:** General\
**Created:** [26 July 2021 14:27 UTC](https://discourse.nodered.org/t/looking-for-organizational-suggestions/48927 "2021-07-26T14:27:17Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![meeki007](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/meeki007/32/12499_2.png) [@meeki007](https://discourse.nodered.org/u/meeki007)\
**Post date:** [26 July 2021 22:52 UTC](https://discourse.nodered.org/t/looking-for-organizational-suggestions/48927/8 "2021-07-26T22:52:17Z")

</div>

You could break things up like @MyRandomThoughts suggested but also go inception style with the sub-flows after breaking them up.

> [@Improving connection visibility](https://discourse.nodered.org/t/improving-connection-visibility/26436/6):
>
> This explanation for wire simplification will have to be picture heavy. I've started using the 'inception' (movie reference) subflow idea to manage complicated wires. So lets start at the top of the system dashboard tab. Ignore the pass word hash check stuff Just Look at the wires and how every subflow is talking to each other. Now we are going into the ethernet subflow. Here Ive used it to contain 2 subflows that need to talk to each other and the subflow above we just looked …

---

_[View the full topic](https://discourse.nodered.org/t/looking-for-organizational-suggestions/48927)._