Reflection – Visualization     Challenge & Selection    I am a software engineer, I and my group of friends tend to work on different ideas from time to

time but always fail as the product isn’t up to the mark or it fails completely, as we have nothing

but an idea that we thought or the description of the product which was provided by a company.

The major shortcomings are that we tend not to think about the long term effects if the product is

created or not. The tool that we needed was the tool of Visualization. Through visualization i.e

planned seminars and schedule boards, we doubled down on the tests we need to run before

presenting the new product to the investors. Over the course of 2 weeks, we identified and

replaced the problems with temporary solutions for the time being. This created a better insight

into what we were doing and this brought closer to the ideal state of the workflow. We shared

our learnings, gave more focus on creating different prototypes I used this approach and

visualized the needs, and presented it to the general public our actual customers which may be

a teenager or an older person.    Application    I start the process by checking if we have the members who meet the required expertise to

meet the product needs. Through design thinking I’ve learned that we need to dig deeper into

the relationship of the product to the customer, combined efforts are made by the team to

understand the environment. Most of the time we don’t need extra apparatus other than our

computers to create a product. We spend most of the time doing our research and minimize the

time wastages and meet deadends If an appropriate solution arrives we add it else we table it

for the future.    In this para, I will explain how we used the concept to “journey mapping” along with

brainstorming, using journey mapping as a tool to understand the needs of the customers from

analyzing their experiences. ​this tool tracks the journey of the customers so that their goals can

be accomplished. Further, I learned about the rule of brainstorming which includes all the

aspects i.e. mindset, challenges, people, empathy, facilitation, and much more.    As we are a bunch of software engineers we picked up two brainstorming techniques which are

helpful for the group and the product as well. The first one I want to talk about is reverse

brainstorming, ​ordinary brainstorming asks participants to solve problems. Reverse

brainstorming asks participants to come up with great ways to cause a problem. Start with the

problem and I ask “how could we cause this?” Once we shortlist all the ways to create problems,

we start solving them.    The second one is SWOT analysis this one is popular amongst IT companies to analyze

strengths, weaknesses, opportunities, and threats. This makes us look at the product from every

angle. Through these two approaches, we gain insights into our project.

Insight & Approach    Through these experiments, I have learned is that creativity and engagement amongst my

colleagues and the customers can be increased, instead of just following the book we started to

think about the ways we could improve and came up with several ideas most of them were bad

but we have tabled good ones for future updates or for the new projects.    We are new Incorporating new ways to produce the product instead of relying on the old

rudimentary methods. Dividing the project into different points and looking at them carefully so

that the released product is free of any flaws and finally we produce something that customers

actually need.


Reflection – Visualization Challenge & Selection I am a software engineer , I and my group of friends tend to work on different ideas from time to time but always fail as the product is n’t up to the mark or it fails completely , as we have nothing but an idea that we thought or the description of the product which was provided by a company . The major shortcomings are that we tend not to think about the long term effects if the product is created or not . The tool that we needed was the tool of Visualization . Through visualization i.e planned seminars and schedule boards , we doubled down on the tests we need to run before presenting the new product to the investors . Over the course of 2 weeks , we identified and replaced the problems with temporary solutions for the time being . This created a better insight into what we were doing and this brought closer to the ideal state of the workflow . We shared our learnings , gave more focus on creating different prototypes I used this approach and visualized the needs , and presented it to the general public our actual customers which may be a teenager or an older person . Application I start the process by checking if we have the members who meet the required expertise to meet the product needs . Through design thinking I ’ve learned that we need to dig deeper into the relationship of the product to the customer , combined efforts are made by the team to understand the environment . Most of the time we do n’t need extra apparatus other than our computers to create a product . We spend most of the time doing our research and minimize the time wastages and meet deadends If an appropriate solution arrives we add it else we table it for the future . In this para , I will explain how we used the concept to “ journey mapping ” along with brainstorming , using journey mapping as a tool to understand the needs of the customers from analyzing their experiences . ​this tool tracks the journey of the customers so that their goals can be accomplished . Further , I learned about the rule of brainstorming which includes all the aspects i.e. mindset , challenges , people , empathy , facilitation , and much more . As we are a bunch of software engineers we picked up two brainstorming techniques which are helpful for the group and the product as well . The first one I want to talk about is reverse brainstorming , ​ordinary brainstorming asks participants to solve problems . Reverse brainstorming asks participants to come up with great ways to cause a problem . Start with the problem and I ask “ how could we cause this ? ” Once we shortlist all the ways to create problems , we start solving them . The second one is SWOT analysis this one is popular amongst IT companies to analyze strengths , weaknesses , opportunities , and threats . This makes us look at the product from every angle . Through these two approaches , we gain insights into our project . Insight & Approach Through these experiments , I have learned is that creativity and engagement amongst my colleagues and the customers can be increased , instead of just following the book we started to think about the ways we could improve and came up with several ideas most of them were bad but we have tabled good ones for future updates or for the new projects . We are new Incorporating new ways to produce the product instead of relying on the old rudimentary methods . Dividing the project into different points and looking at them carefully so that the released product is free of any flaws and finally we produce something that customers actually need .