How do (we) programmers deal with complexity in the systems we analyse  ? We use tools (or maybe these are strategies) such as:

• generalisation and specialisation;
• information hiding, encapsulation;
• aggregation, composition;
• separation of concerns;
• modularisation;
• levels of detail.

Apply some systems / software thinking to the problem of organising your goals.

The root problem of your question is dealing with complexity. It might help to see how a other domains (beside PM) try to handle complexity.

How do (we) programmers deal with complexity in the systems we analyse? We use tools (or maybe these are strategies). Be aware that there might be two sides to deal with complexity, what is shown in my bullet list. It might be worth to google for some of those techniques or principles.

• generalisation and specialisation;
• information hiding, encapsulation;
• aggregation, composition;
• separation of concerns;
• modularisation;
• levels of detail.

On an abstract level it's always about

1. Highlight the goals speciality in order to define a clear scope
2. Summarising associated goals