Reflection – Visualization

Challenge

As a person from a tech background, I had the responsibility to lead the project to create an app for  my organization to manage various requests such as tickets, leaves, travel, other requests etc in my  organization. Even though I would not be personally creating the app, and will be getting it created  by an outsourced organization, ensuring that the requirements (i.e. the scope, boundaries, key  functionality, user flow etc) are accurately identified was of paramount importance. However, since I  was the most junior member of the team, it was necessary that I understand the context well, and  have it verified with the team, before approaching outsourced developers to create the app.

Selection

I chose Visualization as a tool, as there were a lot of UI Prototype/Wireframe development options  such as Proto.io which were available online to help me visualize my understanding of our  requirements, and get it validated from them.

Application

I first created a simple flowchart, highlighting the flow of use in the application, based on my  understanding from various documents, and resources available in the organization. Once this was  done, I presented the same to the steering committee members, who then vetted it, and suggested  changes. However, the best was yet to come.

Once, this was approved in principle, I put together a Project on Proto.io to visualize the app, by  dragging and dropping various app elements such as menu items, forms, login pages etc. and  creating a visual replica of the actual application we intended to build. When this was presented to  the committee, I received many inputs, which helped me improve the app design, user flows and  interactions even further, over and above what I had received in the previous step. Moreover, many  functionalities and use cases, which weren’t thought of earlier, such as internal news updates, and  many other nitty-gritties such as ensuring that the user stays logged into the app, unless otherwise  specified, password recovery via email etc, were identified and introduced.

Insight

I learned that it is difficult for humans to creatively imagine and comprehend to a large degree. Thus,  it is essential to put existing ideas on paper, and then build upon them, so that further creativity can  be added. Another insight I observed was that, even though the flow chart was approved at the first  stage, many features were identified only in the second stage when the actual User Interface  Prototype was shared. This showed me that, the more the user can identify with the visualization,  the better will be the ability of the user to innovate and think creatively.

Approach

Next time, I would like to start with Journey Mapping & Mind Mapping, before coming up with the  clusters on insights (Concept Development), and then develop the initial flow chart, in order to have  a better starting point, before the actual development.


Reflection – Visualization Challenge As a person from a tech background , I had the responsibility to lead the project to create an app for my organization to manage various requests such as tickets , leaves , travel , other requests etc in my organization . Even though I would not be personally creating the app , and will be getting it created by an outsourced organization , ensuring that the requirements ( i.e. the scope , boundaries , key functionality , user flow etc ) are accurately identified was of paramount importance . However , since I was the most junior member of the team , it was necessary that I understand the context well , and have it verified with the team , before approaching outsourced developers to create the app . Selection I chose Visualization as a tool , as there were a lot of UI Prototype / Wireframe development options such as Proto.io which were available online to help me visualize my understanding of our requirements , and get it validated from them . Application I first created a simple flowchart , highlighting the flow of use in the application , based on my understanding from various documents , and resources available in the organization . Once this was done , I presented the same to the steering committee members , who then vetted it , and suggested changes . However , the best was yet to come . Once , this was approved in principle , I put together a Project on Proto.io to visualize the app , by dragging and dropping various app elements such as menu items , forms , login pages etc . and creating a visual replica of the actual application we intended to build . When this was presented to the committee , I received many inputs , which helped me improve the app design , user flows and interactions even further , over and above what I had received in the previous step . Moreover , many functionalities and use cases , which were n’t thought of earlier , such as internal news updates , and many other nitty - gritties such as ensuring that the user stays logged into the app , unless otherwise specified , password recovery via email etc , were identified and introduced . Insight I learned that it is difficult for humans to creatively imagine and comprehend to a large degree . Thus , it is essential to put existing ideas on paper , and then build upon them , so that further creativity can be added . Another insight I observed was that , even though the flow chart was approved at the first stage , many features were identified only in the second stage when the actual User Interface Prototype was shared . This showed me that , the more the user can identify with the visualization , the better will be the ability of the user to innovate and think creatively . Approach Next time , I would like to start with Journey Mapping & Mind Mapping , before coming up with the clusters on insights ( Concept Development ) , and then develop the initial flow chart , in order to have a better starting point , before the actual development .