It sort of depends on what you're trying to accomplish. Based on your comment to your question I reckon that you are trying to solve a problem.
If that is the purpose, Systems Engineering (SE) has established itself as a common tool to use. Consider for example a town that observes flooding by a nearby river. As a general proceeding SE would suggest to lead with a problem that needs solving (e.g. "how do we reduce costs/damage caused by flooding?") and not with a solution (e.g. "we need to build a dam because the river floods"). This tries to ensure that a broad spectrum of possible solutions is considered.
For this example, by using a problem-oriented approach and analysing the whole system (river, rain, etc.), one might consider a variety of solutions that might be more effective than an expensive dam-construction.
- measures upstream (widening, retention)
- emergency measures at hand (mobile dams, sandbags)
- construct levee
I would suggest you read into SE, if your problem shows that it would benefit from such an analysis.