Might be worth considering that in a specific example or context this may make sense, but zoom out further you will find that goals are solutions and solutions are goals.
It's a hierarchy, as Paul referred to as a "tree".
Each node in the acyclic graph is connected to a "why" node above it (goal) and a "how" node below it (solution).
OKRs reflect this in an organization.
People make decisions based on their values hierarchy, implicit or explicit.
If this isn't easy to follow maybe an example will help...
Let's say I have a goal of "provide reliable shelter for my family", the solution may be to "buy a house". Buying a house is also a goal, which maybe is slightly out of reach. So my solution is to "save a large portion of my income" and "secure a high paying job", these are also goals. The solution to saving may be a fintech app, discipline, good communication with my spouse, etc.. every solution is a goal with its own solutions and you can follow this tree down until you get into really specific motor tasks like taking a credit card out of a wallet or opening a door or turning the key to start a car.
