Moving Parts.
I heard from some architect friends that the most difficult architecture projects, somewhat ironically, have the least number of constraints.
Normally, a project comes with strings attached. Perhaps, it's the budget. A way they want the staircase. Or, an open-ceiling bathroom that is adjacent to the walk-in closet and has a ceiling to floor wall window
[1].
On second thought, what my friends say makes total sense.
A tight budget massively narrows down the types and amount of material available. A staircase restriction may influence how to structure the rest of the building for the sake of stability. The open-ceiling bathroom thing, well, you get the point.
Oftentimes, we get stuck because we realize how everything is interlinked. Well if you make this choice, you close these options. But if you go that other route, well, that sort of closes that door and might be bad for later on. And this isn't just about planning out massive buildings that have to adhere to complex governmental regulations while satisfying everyone involved. It's also when you try to start writing a short story. Or, when you've finally learned how to code but not sure what to try as your first project.
This is especially true for early stage startups I've mentored and seen. And, it's something I myself am also struggling with my most recent project: there's just too many moving parts! The earlier the project, the more freedom (and more links and decision trees)!
When this happens, I find it helps to artificially construct some restrictions for yourself.
Alternatively, find some core values or a "mission statement" of some sort to adhere to. Then, link every dilemma back to them when you're stuck.
__