Articles on Design Thinking and its advantageous approach to define effective product solutions, are always welcome. However, if I may opine, the optic of this article, may give the impression that Design Thinking and that process is reliant entirely on Designers, which is not an accurate statement, and is to a large extent, impossible for a single professional to tackle. Design Thinking, has always been as successful as it coalesces multiple inputs/points of view, from different participants, who help inform the solutions that are being devised. Research, with all its protocols, is fundamental, but simplifying it, its reach and breadth can warp the perception of the path a Designer and their teams are embarking on. Research (ethnographic and across a variety of other fields), is something that should be conducted with strategy, considering resources, timelines, and how that information is also going to be digested, and ultimately applied to the process itself. That’s one of the reasons, processes such as FAST UX have appeared, processes that aim to respond to questions such as: what happens when a team can’t access their users in order to gather insight, better understand the problem, the opportunities and testing concepts. I believe it’s fundamental that Designers understand their role as catalysts within the Design Thinking process, as facilitators, the ones probing and asking questions, their role as producers/partners. The sources of information, the insights, the granular information on topics such as demographics, platform performance, trends, localization, among many other topics, will have to be gathered by the teams on that shared journey. In my humble experience and opinion, Design Thinking is not only about the solution that is found, nor about the “formula” that everyone tries to apply to every single application project: it’s about the collective journey Designers and their peers/team members understand and define early on to tackle, and what they’re really trying to ultimately state.