 제 이름은 유순 김입니다. 지금 저는 모바일에선 전원을 제공하고 있습니다. 전원의 디자이너입니다. 그리고 스티페런입니다. 전원을 소개합니다. 오늘의 일상은 하루 종일 일상입니다. 그리고 이 아침은 키노트입니다. 네. 전원에선 전원에선 전원을 제공하고 싶습니다. 이 기간의 일상은 여러분께 brief background of itobos입니다. 제가 하늘에 있는 김에 오신 김입니다. 저는 한국에서 일하고 있습니다. 저는 한국에 있는 기술과 디자인에 오신게도 매우 강한 배경입니다. 저는 많이 많이 그려줬습니다. 그리고 자연스러움을 얻었으며 한국에서 전공 디자인 기술과 시장에 오신 것을 가치면서 오랫동안 전공 디자인의 전공 디자인을 배우게 되었습니다. 타이포그래피를 만들고, 포스터를 만들고, 로션을 만들고 전통의 미디어에 관심이 있었습니다. 그리고 많은 아티프를 만들었죠. 그리고 또는 이슬랄 기술을 만들었죠. 새로운 기술을 만들었을 때에 더 관심이 있었죠. 포헤런스, 플로이리디, 심플리시디. 전통의 미디어에 관심이 있었죠. 제가 계속 전통의 미디어에 관심이 있었죠. 왜냐하면 항상 이슬랄 기술을 만들고 싶어요. 왜냐하면 가장 중요한 데이터를 생각하고 싶어요. 그리고 모든 공간을 생각하고 싶어요. 그래서 더 쉽게 타블렛, 넥스탑, 또는 TV를 생각하고 싶어요. 그리고 또한 이 시각, 우리의 시장의 미디어에 관심을 만들었죠. 이 이슬랄은 제가 shared with you입니다. 모바일폰 팩토리에서 가장 큰 기능이 있습니다. 가장 큰 기능이 있습니다. 하지만 항상 더 디테일한 게 있습니다. 두 번째 페이지는 타블렛을 만들 수 있습니다. 액션을 만들 수 있습니다. 그리고 자리에서 자리에서 자리에서 자리에서 자리에 적용할 수 있습니다. 모바일콘 팩터가 아주 중요합니다. 그리고 같은 데이터를, 같은 데이터를 다른 레이아웃으로 어떻게 우리 레이아웃과 데이터를 옮겨야 할 수 있을까 싶어요. 그리고 또는 타블렛 디자인입니다. 두 번째 주인공은 이 주인공은 아이폰은 10년의 생방송이 되기 때문입니다. 아마 이 주인공은 동일한 플랫폼, 모바일 프로팩트, Android, 또는 Second Biggest One, 또는 outside of the States, and San Francisco, probably it is the biggest one. 그래서 제가 말씀드렸던 이유는 모바일 폰을 포함하고있을 때, probably the ratio and screen size was not that many to design for as a designer, so a lot of designers, like me started with the big ratio on the individual phone size, individual phone devices, but it's been already more than 10 years. There are so many devices, if you just think about Android, probably no exaggeration, like more than 100,000. So as a designer or to developers, we cannot design one by one. We need to think about how the experience going to be on different form factor and platform, and how it's going to scale, even bigger screens. So coherence means here is we instead of focusing on individual screens, we focus on what users would want to achieve on their form factor, what's their main task, what they're trying to do. So this really allows us to think about harmonious experience on different devices. So this is phone, and this is iPad. We give them the same experience, but similar functionality, but it's optimized for its form factor. So they can see more detailed information by just tapping it on the chart or contextual actions in this case, they can change different chart type or dive into more detail, or select and dive all those different ways. And this is the screen, actually users can even change the query. We wanted to think about how would even users want to change query, like asking questions and answering those business questions on the go, even on the mobile form factor. And third one is fluidity. So animation transition is both even getting more and more attention in the US industry, and it's huge. It's not just about giving creative pictures. In analytics, it's fundamentally hard to achieve for users to understand. So we really wanted leverage is fluidity to help them even, they don't have to try to hard to understand data. So the way we did is we want to take advantage to evoke their emotion or to delight their experience. Also the lastly, as you can see here, it's not just showing the animation per se, but this animation actually helps to users understand the data. You can throw left and right on the legend, but that is connected with the donor chart itself. So by tapping one of those, it's connected to the legend. So you can immediately see those slides if it's what those segments are on the chart. And as you can see here, each data when you change different chart type, for example this or change query, filtering dimension or measure, or data, we really wanted to connect the thread of the data while they are exploring. So they always know their contacts where they are, and how they are actually transforming. We do. So this kind of visual momentum, first of all, it looks really cool. So the sales teams loved it because it was very easy for them to demo to their customers. But for the end user perspective, it helped connect data to the same data even when the visualization changed. So this is a really, really key element of the design of the analytics tools. So if you see now in the industry, a lot of people probably, a lot of companies and product provide like this, we actually started like four years ago, but it was pretty revolutionary at that time. I'm very proud of it. This didn't exist on the phone back then. And last principle, simplicity. Again, this is mobile phone. So really want to think about what's the most important data users would want to see. And we really need one, two, three, down. And also fundamentally analytics with this chart, but by providing the most important information on the top, on their hands. Let's talk over one by one on this screen. I'm not going to go over too much details, but what I want to say on this screen is we want to show what users want to do on individual screens. The last most, first screen is the dashboard landing page. Second one is users can drill tapping into individual charts and see the more details. Third one is actually opening up those widget charts. And next one is seeing the detailed data and then following with the contextual actions. So primary actions would be probably here I want to scroll up and down to see data or double tapping on the chart or rotating the donors or tapping those segments and I see information. But while providing the primary actions and then this key point, we also want to, there is more when users want to see more data. So users can tap, shake or double tapping, wiping but we don't want to override them users by showing all these up front. That naturally progressively users naturally find it. And this is the last part. 10 minutes, I think it's okay. Then I want to talk about briefly and then I want to close this talk with our design process and in Salesforce how we innovate and create this amazing product. So service innovation is always understanding our user's needs, what their current pain points, what their experience is like. So we collaborate with researchers a lot like Steve to understand their current pain points and then having like a really deeper empathy. And do you want to talk about? Yeah, a couple of things that we observed. So the mobile research teams do a lot of work observationally. So that means is in some cases we might actually bring mobile users into the office or into a lab and observe how they use the product. That gives us some of that gestural and facial information. More valuable is watching how they work in the field. And especially from a sales use case, what we noticed is that sales people, especially sales people who do their work on their mobile device aren't just tethered to the mobile device. They have multiple other devices. They also have paper that they use in their car or in their vehicles. So one of the things that we learned through doing observational study was that things like findability were really critical. If a person is driving, ideally stopped maybe on the side of the road, maybe not actually driving, it's really critical for them to be able to find the right sales metrics right before they visit with a key client. Another thing that we do is we do interviews. And through the interview process, you probably know if you've heard me talk before, we know that asking users what they want isn't the best way to get information because users are just reacting to their current challenges. But we want to understand what problems are they experiencing. So through interviews and through observations, we learned things like, well, I really wish I had landscape mode so I could see this. Right now, the product does not support landscape mode as far as I understand, right? Not on mobile. Okay, yeah, so the mobile is still portrait only. And when we talked about why did they need that, the ultimate goal was, I need to be able to see this number in context with these other numbers. So maybe landscape mode is absolutely the right way to go, but there might be other more elegant design solutions that also satisfy other uncovered problems that we would go for. The last area of needs is coming through feedback that we'd get primarily through our various listening posts. So any kinds of instrumentation in the product or any kinds of surveys that come in. We basically hear the kinds of feedback that people give us as they're interacting with the product, either in aggregate or individually. This is a great way for us to find evidence of bugs if it's a shipping product or evidence of unmet needs. And we'll talk more about that in a moment. That's the fourth stage and next stage is creating concepts. We have this amazing culture generating ideas. We collaborate a lot of stakeholders, researchers, other PMs, even other designers. And this is the time we often call it like design thinking. There's no boundaries constraints. Don't think about the technology for feasibility. How it can help users to improve their daily tasks or make it efficient and effective. How it can help, they don't have to stay in their office and they enjoy their life more. So yeah, this is the time we draw a lot of sketches and post-node time and generating idea like you did in the workshop, like crazy ideas, the folding paper. Crazy eights. Yeah. And the next stage as a designer, I think about how I am gathering all those information and then this is down and then creating flow and trend flow and make a wireframe. And this stage probably not every time, but we a lot of times also talk to customers sort of like a validating concept. And next stage is code solution. This is the time we actually collaborating with developers and product type, our designs. And creating high fidelity prototype and also get usability test out of it. Last stage is releasing product. We have a three release product in sales worth per year. Three release per year. But mobile is not necessarily following this release cycle because we need to submit to store, app store, or Google Play. And we have a feedback channel we are still getting from users. There is a section feedback. And users keep continuously giving us feedback. What's right, what's wrong, and what's not working and how we need to, how they want us to improve their experience. And the reason also we are releasing more than three times a year is like there is a platform we are supporting besides Salesforce. Like iOS platform, Android or Windows. And they always have every year new OS. And then we need to keep up with it and make it work perfectly on both platforms. And also tons of other bugs. So there's a bug patch to be released soon. Not tons, not tons of bugs. Just some bugs. That's mine about bugs. You want to make? That's true. Yeah, so I will say probably if I say the top size is three releases per year, we probably mobile probably once every other month or even open then. So yeah, this is the feedback channel. I don't know if you want to. Yeah, I just mentioned we have a three-phase feedback channel process. We have listening posts embedded in the product. So analytics usage data shows up so that we can understand what users are using in aggregate. It also lets us know what features are being adopted and the velocity of that adoption as well as what features aren't being used which allows us to do qualitative research to understand why is this feature not being used. Maybe it's not needed or maybe it's not discoverable or maybe it's not usable. And then the last listening posts are as a user interacts with the product, the product does the thing that most of us don't find super exciting. It says how do you like it? And if they say oh I like it, we'll say oh would you please consider writing us a review and also giving feedback. If they say I don't like it, we'll say we really want to hear your feedback and we have an embedded feedback survey in the product. There's also a feedback survey that people can use at any time. And when they click that, it provides us the ability to identify first of all whether or not there might be a bug or a defect every time iOS or Android changes their platform, maybe that broke something. So we get early warnings about that. And then second of all we hear the wish list items. Customers say I really wish I could do X. That gives the research team a great opportunity to do additional research and the design team opportunities to start ideating and creating new concepts. So this is the brief of our design process. And as you guys know obviously every step is very iterative and there's no like it's not a linear process. So take away, we talked about briefly user centered design and for design principles use cases target audiences. And but wait, there's more. There's more. I want to guys download an experience. We have on Apple App Store, Google Play Store and if you guys downloaded there is a record sample data. So you guys don't have to process the test for license because of the way we did. Yeah, there's sample data sets that you can use. You can use it on your device right now. I'd recommend please don't fill out the feedback survey unless you find a real problem or you just want to say hi. All feedback goes directly to me as well as the mobile analytics team. That's it. Thank you.