 Thanks. Hi everyone. How are you today? Good. I hope you enjoy the bizzars. Okay, so innovation, I believe you work for different company start-up, right? How many of you work for start-up? Okay, maybe bigger companies, no start-up anymore. Corporate, okay. So when I talk to people from different companies, because I try to meet people and learn from them, one of the things that I observe from almost everyone is how we can innovate, how we can change things, having new ideas, improve your product, move fast. So today I'm going to talk a little bit about innovation cultures, but with different angle, which is start with design. Anyone heard about this before? And the idea of starting with designs for innovation. Okay, so that's good. I'm going to talk about that in a little bit. Just interesting about myself. My name is Jian Yuan. I'm from Vigo. I'm a city of Vigo. So what I like to do, I enjoy a lot is traveling, coding, but what I want to do is I want to make an impact by solving the problem. Anyone knew Vigo before for your travel booking? That's good. So today you know where we go and you can start using it. So just a quick introduction about my company. Vigo is a travel meta-search platform. We connect to allies, OTA is a travel agency, and hotels, like thousands of them. So when you search on Vigo, we search across like thousands of them and bring to you the best results, best option you can book with. Vigo founded in Singapore, I think 12 years ago in 2005, 13 years ago. And today we are the number one in terms of traffic compared to other travel meta-search in Middle East region. We also have a significant traffic from different South Asia and a few other markets as well, but our market is many in Middle East. That's why we have office in Dubai, Iran, a few Middle East countries. Our tech team is very in Singapore, many. We also have a team in Jakarta and India as well. So you can see here, when you search, you can see a lot of results coming from different hotels and travel agents. So why design? Why design matters? So you can design different things. You can design your product by having new ideas, new features with better designs, do A.B. testing and whatever you can improve your products and user experience, right? You can design your product. And the result of that is how much love user gives to your product. So user loves your product and they are going to use your product more often. You can also design your system, which is system design. So you design your services, data, infrastructure, whatever. So the system designs. You can also design your team as well. So what are the team structures? What is the process? How people work together? And the result of a good system design and a team design is innovation, in my opinion. Of course you can also design your life. So you have a very clear purpose. So you know what you want to do. You know what you want to achieve and you have good plans for that to achieve those goals and purpose, which make you happy. So just a different thing you can design. And when you have a good system, good team, you can also be happy as well, right? So everything we need to each other. So today I'm going to talk a bit about system and team design because it can result to better innovation. So system design and team design, there are many things in common because my background is from the software engineer. I was a software engineer initially and then I work on different things like backend, fountain, DevOps, data, almost everything because I believe that when you understand everything, you can solve the problem faster and I want to solve problem. So I understand that system design and team design, there are many things in common. So right now I'm leading the team of engineers in Singapore, in Jakarta, in India. So how we can design a team in which we can innovate and move really fast. So I understand that designing the team and the system, there's many things in common. For example, you need to make sure that your system is reusable, for example. Then in the team design, you also need to make sure there shouldn't be two teams working on the same thing at the same time. Or it should be very self-contained, less dependencies. So in the system, you shouldn't depend on so many different external services or system. Same for the team design, you need to make sure that your team is self-contained so you will be able to move really fast within the team without waiting for other team. So when I talk to a few different companies, they have a DevOps team. So every time someone needs to deploy something, they have to talk to DevOps team, send a ticket and then wait for response. It can be in a while in order to deploy something even though you are ready to deploy. So there shouldn't be a lot of dependencies in the team as far as the system. So I'm not going to talk many different details about team design and system design. I'm going to talk a bit about the principles. So for system design and team design, I believe that ownership is important. So your team should take the responsibility, they should own the system and constantly improve the system. That's ownership. And they keep inventing, keep trying new things with a very simple solution. So you shouldn't introduce something which is super complicated for Jammu to solve small problems. And one of the things that I think is very different when you design a team is there's something like trust, respect and empathy. You can design a very good structure, well structured with a good process. But the core of that is trust, respect and empathy. So as a team member, we should trust each other, we should really respect each other and really care about others. So as we go, what we do is for others. So when we come to work, we solve a problem. We actually try to solve that problem with others. So to make sure that if someone has some problem, then someone else, they should be willing to give help to solve that problem. So that's the empathy we really need to take care of each other as a team. So everything together creates an environment where we move really fast. And the whole thing should go in the same direction. Which means we need to define a common goal. So what's the common goal for us? It's about people. It's about people. What do I mean by people? So when you work really hard, right? So you keep learning working hard for whom? Maybe for your family, those people in your family, right? Or it can be someone in your team. Like I said, we try to help each other in the team to roll together. So you help people in your team. And it can be people not in your team, not in your family. It's our users who use the products. So you work really hard, innovate, and try out new things just to improve your products. So your user can benefit from. That's the common goal I'm talking about. It's about people. So that's all about the culture I just mentioned. I'm going to talk a little bit about the architecture, which is part of that system design. So how we can come up with the architecture where we can move really fast. This is a very high-level overview of our architecture. So we based on microservices architecture. With this architecture, we have different services for different teams, like hotels for hotels, relatives, or flights. Meta-search is a search platform on user service of many others, but I didn't mention here. So with these architectures, we can be freely to use different, say, language for different services. It depends on, say, the performance, right? It depends on the purpose we want to achieve, which means we are not constrained by language or technologies. So in each service here, we can scale it differently as well. It depends on the traffic to the service. So we have different teams to take care of different services. They constantly improve the service and focus on that service, thinking of the way to improve the service in terms of performance scaling. That's right. Yeah, so since we are going to talk about data, this service produce a huge amount of data. So API Gateway is the gateway of all the traffic coming in our system. From our API Gateway, we capture all the traffic data. From that, we can do bot detection. So after capturing all the data, we build a system where we analyze data and detect which traffic coming from bot and which traffic coming from real user so that we can define some rules to filter out the bot traffic, for example. So from different services, we also lock all the data, say the pricing data. When you search hotel or flight, you see the results, right? We say different from different allies with different pricing. We capture all of them and we do the price prediction. With the price prediction, we can predict when is a good time for you to travel so that you can get a better deal, right? Say you want to travel to Bangkok, but you don't know when yet maybe a timing is very flexible for you. Then we base on the pricing data we can suggest you when is a good time to travel, when you should book it, for example. And we also capture all the user behavior data. Say you click something, you go to, you search something and you capture all of them into our data platform, right? So let's all, as I'm going to talk in more detail about our data platform, technically in detail, right? So you can ask him about question, how we decide it, what is the challenge when we decide a data platform. Later on. But here's the overview, architectures. What I want to talk to you guys here is with this micro-services architecture we can move really fast. So after we capture all data, how we can make use of data with the data-driven culture. So I think this is something that's very commonly used now, but I would want to emphasize that how to build a truly data-driven culture is different. For example, not only the data team use data, but in our company, people from marketing, from sales, engineers also use data. That's the truly data-driven culture that we build in our companies. So for example, our engineer team not only building the product feature, not only writing code, but they can think of the way to capture data to detect errors in our system, for example. That's the data-driven for engineers. So how we can move fast and build all of this, we need to automate everything. We cannot just manually build up some service or a set of something. We need to automate everything. That's why we invest a lot of effort on DevOps, especially the infrastructure as code. So we write code for everything. From creating servers or increase the size of servers, every single thing, we write code for that and we have a code review process for everything. So this is a DevOps... I would say that this is a DevOps culture. Why is it a culture? Because everyone in my team, in our team, can do DevOps. So everyone can create a server. They can create a new stack if they want to. So they don't have to wait for some DevOps team, people, to help them with that. They can design a service and then deploy a service, create the whole infrastructure for their service. That allows us to move really fast and innovate much more. Yeah, so those are a few things I wanted to say with you guys about our innovation culture and how we can enable it. Thank you. I'm going to take any questions if you guys have. Otherwise, I will give to Asan. Anyone have any questions? Okay. Me? Yeah. Okay. So the question is, am I in the following team that we go? No, I'm not. So I... My question is related to that. Yeah. This one's... Okay. In a very small size... Exactly. How do you innovate at that time? Yeah, so different, okay. So your question was with a small size team, how you can innovate, right? So... Day to day. Exactly. Day to day. Okay. So really depends on the focus of the companies each period of time. I guess for your start-up small team, what you focus on is how you can move really fast and using best practice so you don't have to make the same mistake that other people make mistakes, right? So you need to move really fast using best practice. So I think learning the best practice for your team is more important than having a real structure and with a decent size like my team. So yeah, depends on your focus and what you want to achieve during that time. For us right now, our team size is... We have 35 engineers, not very huge team, but we are able to deliver a lot compared to maybe similar companies because of this culture and designs. Yeah. I hope it answered your question. It's something worth. Any other people? Okay. Okay, thanks. So...