Challenge and Selection     Recently, I had the opportunity to apply the Visualization tool, or Visual Thinking. I mentored a  session with the aim of helping to prioritize a set of initiatives to be used throughout the project.  It was the first session with this profile that I was responsible for developing. It was a great  personal learning experience, where I identified points to evolve, also generated great results  for the project's stakeholders.     Application     The process was carried out completely online with a smaller group of people, as a pilot  initiative. Mural online tool was used to apply the methodology, the board interface was design  before the session begins. The first step during the session was to align expectations and explain  a little about how the workshop would be applied, also a discussion wheel with some  explanations about the project initiatives.      I applied the MSCW's Methodology to prioritize the importance and value of the project  initiatives, with 3 remote votes sessions which allowed to separate the four classifications of the  method. Following the capacity, the second stage consisted of the complexity evaluation of each  initiative, for this step, prioritization was applied using Fibonacci sequence, since the member  had a technical background.     When concluding the first two steps, that is, the value for the business and the technical  complexity were prioritized, the initiatives were "plotted" in a graph with axes of complexity and  value, and initiatives with low complexity and high value were selected " Champions "and  adopted a higher development priority, being followed by other initiatives until arriving next to  the high complexity and low value initiatives, which would be reevaluated if necessary.     Approach    Some learnings of the application were, even do the voting session is a concentration moment,  the silence id bad for the workshop, is time to share ideas and opinions. Also, during the session  there were about 20 initiatives to be prioritized, is also necessary to reduce this number, to 15  maybe 10. The team said it was confusing to prioritize so many things at once.

