There are so many ideas, so many complex big pictures and newer business models available around as a huge novel ecosystem. When you step up the ladder of redesigning or designing a new product or an interface, you have a new "Mystery" in front of you. Something which is very indefinite, and something about which you almost know nothing but the fact that it is going to be your next hurdle. As a designer cum innovator, you would have no idea how to implement things and go about asking questions in relation to this mystery. The first step which has to be taken is to convert this low level of disclosure and a top level problem without any solvable variables into a definite solvable problem which is not only more relaxed, but also more elaborate. We would name this state as a "Puzzle". Puzzle is a stage which is physically realizable and quantitative, i.e, it outlays the constraints, the initial concrete set of challenges and problems that the whole design process would face in its cycle. There are several steps which need to be taken explicitly in order to transform a Mystery into a Puzzle. Here is a representation of those steps: 
From Mystery to Puzzle
Mystery --> Puzzle
It is evident that "Design Thinking" and "Requirements Engineering" are the most important steps and encompass almost every other step and iteration within the whole system. Through this methodology, a designer gets the problem laid out in a very concrete and absolute manner, thus thriving innovative ideas from the problem description itself. In a series of big roles for a designer, this should be the first and the foremost role which makes the following processes rewarding and less risky.