Challenge    I am a product designer of an M&A product company. We are building an extra tool to help tender  users to manage their projects and manage all submissions from bidders.     The users currently using our Data Room system to manage their tender projects. Our hypothesis is  to create a new tool to support the users manage their tender project easier.    So, we get to start to research how do the users manage their tender project by using the current  system and what is the information they really want to prepare for the tender project.    Our challenge is to make sure our hypothesis is correct and validate if this new tool can help them to  manage their tender project better.    Selection  Our team was thinking about trying the ​Visualize​ and ​Learning Launch​ tools for building a simple  tool that helps enough for the first MVP instead of building the whole process of the tender process  tool.      Application    The team included sale people and product people talked to the real user to understand the whole  user journey of how to manage a tender project.    Our product team collects the data in our system to understand how is the current way the project  team and bidder collaborate together.    In order to visualize our user journey, our team including product, designer, engineers doing some  workshop to understand user journey and​ create some hypothesis, finding pain points that they  may get while using the current system.    Workshops:

● The customer journey: ​Visualize customer journey into steps and activities for each step.

● Product team workshop: ​By the same time, we were doing the workshop with the internal  team such as developers and testers to sharing understanding and put them to the role of  the customer's empathy.

By this way, the team understands the business well, create more hypothesis.

● UI flows​: Specific user flow for each role by a simple mockup

● Job to be done & sitemap​: Define use cases that the users need to complete and the  structure of information.

● Low-fidelity prototype​: That describes the detail of the content of each screen and able to  click through between screens.

Then, we do some interviews with the real customers to validate if the hypothesis flow and prototype  that matched with the way of the real flow of their project and validate the prototype if they can use it  easily and the content is exactly what they need.      Insight    After validating with our real customers, we were finding that almost our hypothesis are matched  with their needs and we can improve quickly our prototypes.    This helps us to improve our product early and don't waste the time of developing. We updated the  mockups base on the real customer's feedbacks and going to prepare for the design.    This is a good start going to the next step.    Approach    With this approach, we are building the very MVP tool that helps enough their need then we can  launch and test very early, keep it simple but can be useful, then test and learn.    While we know the real usage of this tool we can move forward to the next improvement or not.    Next time, we are keep using this Learning Launch tool and trying the Storytelling tool in the future  for sharing this product to the other stakeholders.

