The article emphasizes the importance of labeling relationships within company operating systems. The author argues that mapping out these relationships clarifies how goals and initiatives interact. Four distinct models illustrate different perspectives on this relationship: some see goals as the strategic anchor, while others view them as outputs of initiatives or as constraints for initiatives. These variations significantly affect how strategy and execution are understood within an organization. The author presents a comparison of two "strategy-to-execution" models, revealing that each encodes different assumptions about organizational dynamics. One model assumes a stable structure where teams execute defined strategies, while the other embraces uncertainty, with strategy emerging from iterative learning. The discussion highlights the significance of understanding not just the objects (like strategies and initiatives) but also how they relate to one another. The piece transitions into an example of Amazon's operating system, noting that its complexity is found in the variety of relationships rather than a simple hierarchical structure. The author critiques the conventional project management approach, suggesting that a more nuanced network of interactions represents how work is done in reality. Lastly, the article touches on the challenges of scaling Agile practices, illustrating how organizations tried to maintain order through structured roles and groupings, ultimately sacrificing some agility for the sake of clarity and predictability.