Good morning to everyone. You are here for the tableau essentials, dashboards, and delivery. I'm really excited to be leading this session with you guys today. So let's go ahead and get started. First, I wanna give a quick little intro about inner works. If it's your first time being with us on an inner works webinar, welcome. Thanks for joining us, and we're glad that you're here. Interworks is an analytics consultancy, and we're global. I'm talking to you guys today from Chicago. Rachel, you're from Raleigh. Correct? Yes. I am. Yeah. She's talking to us from Raleigh. And we also have consultants in Europe and Australia, so just about anywhere across the globe. We specialize in helping people and teams succeed with tech. Tablelo is a great example in what we're gonna be talking about today. We've been a long time partner, and they've built a great analytics product that we love, and we'll be showing you today. But InterWorks does alongside our partners and customers is we help build strategies and problem solving solutions to help succeed with the technology that you have invested in. We can help with all kinds of different things Whether it's just general analytics, data preparation, data management, enablement, or maybe administration. Today, we're gonna be talking about Tableau essentials. But I also recommend that you visit the Interworks blog, where you're gonna find a whole lot more content about the tech that we support. We're gonna have webinars much like this one, and Also, follow us on LinkedIn. We're gonna be pushing out whenever we have sessions much like this one coming up in the near future. Just a few reminders, we're gonna be recording this session and it'll be on our website in a few days. We'll also send you an email if you registered and all of you did since you're listening to us right now. You'll get you'll get an email that is also going to have a link to the recording, and also we're gonna have a survey at the end of this session as well. To see how you liked it, and also if you need any follow-up. During this session, if you guys do have questions, feel free to use the q and a function. Rachel's gonna be monitoring that, and he's gonna politely or non politely interrupt me if you guys do have any questions. And we'd be more than happy to try and answer those today. So with that said, let's go ahead and do some introductions. You guys heard a lot about me. I am from Chicago. My name is Maxwell Croft. I am a membership enablement lead at Interworks, and I am here to help you guys succeed. So with that said, I'll go ahead and let Rachel introduce herself. Hi. I'm Rachel. I'm an analytics architect, like you said, based in Raleigh, which is in North Carolina, we're right in the middle of the East Coast, and I kinda work with the entire life cycle of data when I clients with everything from data preparation, data visualization, and data science models as well. Real quick before I move on from that, we got a question we both went to Tableau Conference, and I am not I did not go to Tableau Conference, and Maxwell can't remember if you did. I didn't. Not this year. We did not. We did have a whole bunch of us who were there. Just Maxwell and I were not able to go this year. So if you went, I hope you had a great time. I heard good things about it. Yeah. Same here. Rachel, thank you, and I am so glad to have you as my cohost today. I'm excited to talk about this fun topic. So today, we are gonna be discussing Tableau essentials and its dashboards and beyond. So first, we're just gonna do a little refresher of what is Tableau. Why are we here using this Visual Analytics software? And my assumption on this call is gonna be that some of you have touched the tool before. You've opened it? You've maybe built some worksheets, built your first dashboard, and you might be thinking what's next, or maybe you need some tips and tricks on how to make your dashboard better. We're gonna discuss that. We're also gonna go through a design checklist to think about what are the things that you missed. For myself, I definitely did not come from an analytics background. My background is in chemical engineering. So whenever I heard a Tableau, I was like, What is this cool tool? And I had to learn all these things much like you guys. So I've been in your seat before, and I'm really thankful for webinars much like this one. We're also gonna finish up talking about once we finish building that dashboard, it looks great. We then wanna publish this to server. And we're also gonna look at something that's called embedded analytics, which some of you might have heard of today, some of you might not have. So with that said, let's go ahead and jump into things. And I wanna start off by taking a quick poll. And I wanna know what is your experience with Tableau? I'm gonna let Rachel go ahead and open that up for us, and we have three levels, beginner, intermediate, and expert. So We're gonna give that a second to let everyone answer. And a lot of responses fairly quickly, you guys are paying attention. Ready at the trigger. I love it. This is great. I love the live polling feature because it lets you guys be interactive, and it also lets us learn who our audience is. Seems like we're kinda coming to a point, so I think I'm just gonna end the poll and share results. Yeah. So it looks like the bulk of you on this call are intermediate, which is great. That means that you've opened up the tool you've built a few dashboards and hopefully you know what you're doing in the tool. We also have thirty nine percent better beginners. Don't worry, we're not going to be doing anything too crazy that is going to be beyond a beginner level in this workshop. So You guys are in the right session. And a few experts, maybe I should be asking you guys to lead this session instead of me. Well, thank you very much. Gonna get some tips and tricks. From us as well. Something -- Yeah. -- with some fresh eyes to look at. Well, guys, thank you for taking this poll for from us. I'm gonna go ahead and click out of this, and we'll continue on here. So Again, today's topic is gonna be about Tableau, and Tableau is a visual analytics software. So we're wanting to connect to some kind of dataset and kinda tell a story with it. We wanna be able to analyze and visualize what's happening with that data. Are we trending up? Are we trending down? Is there something that our stakeholders or whatever need to know? And then we wanna be able to share those insights. We can develop these dashboards and workbooks on our local computers, but at some point, we're gonna need to share this to server or maybe somewhere like curator to let others see what we're building how we're doing. Tablo has a ton of different data connections available. Salesforce, Excel, SQL, PDF, you name it, it's probably located right in there. Now where we all need to start is with the data, and what I will say is we do need to have clean data to start building dashboard. So We're not gonna dive into that to that today, but know that data preparation is key. And I know Rachel can definitely agree with me on that. So the tool that we're looking at is really nice because it's fast, iterative, and it has this drag and drop functionality built into it. We're not just looking at some flat file like PowerPoint. PowerPoint is what you see is what you get. Tableau allows us to explore data through visualization. We can look at trends. We can find the insights to the questions we're asking And again, we're telling a story with Visual Analytics. On a dashboard, if I open it up and I quickly see something highlighted in red, I'm gonna think, oh, something's bad here, and it's gonna want it's gonna trigger me to wanna dig in for more details. And that's what I really like about this tool and the functionality it gives us. Now The Tableau workspace has a few things included. One, a worksheet. I know most of you are familiar with this. This is where we're gonna be building those bar charts line graphs cross tabs. Then we're gonna be putting those worksheets into a dashboard. A dashboard is a collection of worksheets. And then on top of that, we're gonna have the overall workbook, where the workbook is a collection of worksheets and dashboards that we're gonna be publishing to the server environment. Today's focus is gonna be looking at a series of completed dashboards, but we're gonna see how these different components go into the overall workspace of Tableau. I wanna start off today talking about some dashboard best practices. And it was really nice seeing that poll because a lot of you have had experience with the tool and most likely building a lot of dashboards on your own. Now, whenever I start building a dashboard, I always think about what is the overall story of the data A lot of times I'll tell a client to open up their dataset, investigate the columns and figure out what columns are you gonna go to first. Meaning that a lot of times, we wanna build a high level summary of the dataset so people can understand how the data is trending, how things are doing. So this is creating a maybe a high level KPI dashboard. What that'll do is it'll allow us to at a glance see how we're doing and then drill down to details as needed. Now upon doing that, building and creating that overview dashboard, we're gonna have to think about what different personas are gonna be looking and navigating through this visualization. Just like on this call, I have some beginners and I have some experts. If the experts were to open up these dashboards, they're probably gonna quickly navigate through the view and get to exactly what they need. But if I have a lot of beginners that are looking at these visualization, they might be confused. They might not know how to navigate, click, filter, and find those insights that they need. It's important that we add in instructions, in context from the data, and how to use these visualizations overall. Now To me, this is sorry. I just interrupted you. Go ahead. That is probably one of the biggest things for me that I had to learn when I first started getting more into building these kind of workbooks is giving the instructions in context. Because as you're building it, right? You're so in it. You know exactly what you're doing. It makes complete sense to be able to see something and be like, oh, well obviously you would use this filter to do this or whatever it might be. But allowing others to not assume that others are gonna be thinking the exact same way you are and giving instructions almost to the point of over explaining how someone can use it, then that would be probably one of the biggest things that I had to learn how to do. Yeah, I totally agree with you. You know, you and I probably spent forty hours developing a dashboard before, and after we complete it, we're like, that's it. But After spending forty hours, your eyes are glazed over, you can't see if it's good, if it's bad, if others are actually going to be able to utilize it. And I definitely had to learn that as a young consultant at Interworks, how to upscale this, how to make sure that this is reusable by other end users. So, Rachel, thank you for adding in that tidbit. Also, we're gonna see that on a dashboard, real estate is precious. We don't have all the space in the world to share everything. So we wanna make sure that we keep it clean. White space is a good thing on a dashboard, but also intuitive. So if you're finding that you need to add a lot of instructions, you need to add details about the data. You can always add in an info button where users can hover, and have a tool tip open up and list all those details if needed. So it's more on demand for people. So let's go ahead and take another poll. We've talked about dashboards and Rachel and I's experience with it. Where do your current dashboards fall short? So we're gonna have a few answers here. Is it bad data? Maybe you just need training on how to build these, standardized formatting or low engagement. You all aren't able to see the results yet, but it's feeling it's seeming pretty divided. Everyone feels like it's pretty pretty easy. I think I know what my answer would be of those. I think just like being on the data prep side bad data, right, data in, data out, kind of thing where if you have bad data, then it's going to be problem when you're trying to visualize it. You know, I should have added in one of the responses to be all the above because I'm not sure. Exactly. I'm sorry about that as well. We'll rate them if we can go ahead and share this. Alright. Yeah. I think we've got a a fair amount of people, and then we'll share the results. So again, I asked where do your current dashboards fall short, and it is a tie between standardized formatting and training needed. I think that Rachel and I have both been in that seat. One being the trainers of how to instruct people of how to use Tableau how to build these dashboards, but also being on the client side thinking, do we need a style guide? Do we need to tell people how to start building this within the company? Because It's not one size fits all. It's very specific to your data, to your infrastructure, and all those things. So I think that both of those answers are great. And then low engagement and bad data. Low engagement, I think, is a big one too, because you might have spent all this time building and curating this perfect dashboard that you thought of, push it out the server, and then no one's touching it. Why is that? Is it because you didn't add instructions? Is it because maybe there's too many things in the visualization in the dashboard and people are overwhelmed, or is it because it's slow? Maybe it's a performance issue, and people go to use it and it takes more than ten seconds. Most likely someone's going to press exit and say, no, I don't want to use that dashboard. So, I think that all these are cool answers and what we expect in. Rachel, do you have any comments towards that? No. That seemed to be what I would assume to be it. And I'm sure, like you said, a lot of the answers were they chose one of the reasons I'm sure a lot of them will be like multiple things, right? It might be bad data and training needed or something along those lines. So this feels like it fit about exactly what I was thinking. Yeah. Same here. Alright. That's great. So today I want to navigate one between looking at some best tips and for you guys, but also looking at a sample dashboard. I've built this dashboard using a data set called sample Superstore. And for those of you that have used Tableau before, I'm assuming you've used this dataset. You can kinda think about it or think think of an Amazon store. We're selling different products, and we're trying to see how much money we're making from those products. This dashboard that we see here is pretty clean and crisp. I can see that it's a regional analysis. I'm looking at different regions across the US and how my cells are doing. I can see how they've been trending over time. My different categories that I might be selling in, technology, furniture, and office supplies. And also some different products here. Now, I did say that this is a nine nice clean crisp dashboard. But, Rachel, what's missing here? Well, I mean, instructions. Right? Like, there's there's a whole bunch. I wouldn't be able to look at this and know outside of I mean, I see select the date range, which is very instructive for it. But I wouldn't know how else to interact with it, like that's giving me total sales, but I don't know when. Right, like just a little bit more help to understand would be helpful. Yeah. I I totally agree with you. So know that you can create something that's nice, clean, and crisp, but, again, we need to ensure that we're adding context and we tell users how to utilize this dashboard. Mhmm. So I purposely took a screenshot of the dashboard without obstructions, but this is something that we're wanting to look for. I can see again that this is a regional analysis. I can come up here and hover over one of these KPIs, and highlight information in the view. I'm pulling forward the central region to know what states are included, how those different cells were in the categories down at the bottom, and maybe what products I was selling down there in the scatter plot. So again, think about who's landing on this and the story that's being told. You're gonna hear me bring up the story a lot because, again, we're on a data journey. We're connecting to some kind of data set and we need to think about what persona, what user, whether it's a c level executive or an analyst that are utilizing this view, and what they're going to be searching for. Let's say I was an executive, and I was looking at this view. I can quickly see that the West has the highest sales. I say great. Maybe I'm looking at the south. It's a little lower, only one million. Maybe I want to figure out why that is. Now I see that there's this highlight function put in, but also I'm gonna notice that maybe some of these filters and different items are missing. So what's gonna be next is adding in that interactivity and make sure that it makes sense. Now why is this important? Why should we be using interactivity? Again, I mentioned that this isn't a flat file like PowerPoint. We have the ability to allow our end users to come in and explore and control the data visualization. It's gonna give us that customization that we desire because each person is gonna want a little different flavor of that dashboard, and it's gonna allow for that self-service. Which is a really nice thing. So coming back to the dashboard, how can I add those in? If I was looking at this KPI up here at the top, I probably wanna make this a quick filter to where if I click on the south, it's gonna filter everything in the view. I can simply do turn on a quick filter by selecting the sheet, and you're gonna see this little funnel in the menu bar of that worksheet. If I turn it on, it's gonna allow me to filter this dashboard just for the south. So again, let's act like I'm the the account executive at the southern region. I'm clicking on the south because I see that my cells are lower compared to the others. Now I wanna keep on looking for more and more details. Maybe I'm curious about, I don't know, how is Kentucky doing? It's actually originally where I'm from. You can see that Kentucky has sales of ninety three thousand, and maybe I wanna be able to click on it and filter for more details. So I see I'm getting more and more specific as to the story or the answers that I'm trying to get to. So now I see just Kentucky cells down here in the bottom sheets, and maybe I'm curious about this outlier, way over here in the scatter plot. Global deluxe high back manager's chair. That sounds fancy. So And comfy? No. Ben comfy. Yeah. I'd love to be seen in right now. I I don't know about you guys. But, again, I'm able to click and manipulate this view to find this specific product. Now, we both said that this is comfy. What if we are curious about more information about this product? This is where we're gonna wanna keep on going down that rabbit hole or creating that narrative for our users. Maybe I wanna be able to click on this point and look at some product details. Already created another dash board that actually list out all the product details that we have in the dataset, how many items were purchased, discount, sales, whatever. We can also create filter links. I'm gonna come up to the top to dashboard and actions. And I'm gonna quickly add in a filter here. I'm gonna say click to view, product details about, And I'm gonna insert the product name, so it's going to update to whatever product I'm looking at. Or whatever product I select. I'm gonna ensure that I only select the scatter plot in this u, And the target sheet is going to be that last dashboard that I have, product detail dashboard. Now I know we're all curious what this high back manager chair is gonna look like. So now if I click on that point, I'm gonna see a hyperlink that shows up that allows me to see the details for this specific product. It's gonna drill me to that detailed dashboard and I can see that I sold thirty seven chairs. I gave no discount, and I made a profit of three thousand dollars here. So I this is really cool about tableau. Again, it's this nice interface to where I can click filter and manipulate the view to answer my specific needs. Now I'm gonna come back to this view really quick. I showed how we could manipulate this singular view to answer a very specific question about a manager's high back chair. What if I was curious about how a specific state is doing in details? Instead of looking at one single one singular product. I have another dashboard here that is a detailed view of a specific state. Just like I did for that product detail dashboard, I can also create another filter action for this state sales dashboard. I'm gonna do the exact same thing that I did for the product detail. I'm gonna add another filter action here. One of the great things while he's doing that. One of the great things of being able to do this is so that you aren't creating a dashboard that has all of this information in one spot. Right? I think Maxwell touched on that already, where you can have your high level information, but you can also have the detail in later on dashboards that they can dive into. That way you're not giving, you know, like, too much information for them to try to see all of it on a single dashboard, which is definitely something we've found with working with clients, right? They want the one dashboard to rule them all. But it ends up that we end up having to break it into a couple where there's interactivity between them. Yeah. And where we the last poll question where I was asking where your dashboards fall short, and we set low engagement. If you have a dashboard that has a ton of different worksheets, People are gonna look at it and they're gonna feel overwhelmed. It's called the cognitive overload, and they're not gonna know where to start, where to finish, anything. They're just gonna honestly clip off of it and avoid it. Yeah. So And we had one more point in the chat that someone said this also addresses a performance issue, which it can. Right? You don't have a single spot that has, you know, fifty worksheets on it, a single dashboard, those fifty worksheets. Every time you go to that dashboard, it has to render all of those images, all of those views. So that's a very good point on it as well. Absolutely. So now that I've set up this other action, I'm talking to you guys from Chicago. What if I wanted to see more details about this specific state? Just like with that product, I can click on Illinois. I see a hyperlink to see more details about Illinois. And now I have a state specific dashboard. I see that here me in Chicago, we're not doing so hot. We have a negative profit I see that I'm losing money in a lot of my categories, tables, finders, and that's a big issue. Shares even though I have some high sales in here. So if I was an account executive, I'd be like, what is happening? Am I giving to a high of a discount? I'm unsure. But what's really cool here is, again, we get to keep on digging into more and more details as we see fit. Now I could add in these actions all day, but I think you guys get the point here. Make sure that you think about the overall story. What are the different pathways that people are gonna need to go to and what views do you need to curate to answer those specific questions. You're not going to answer all of them at first. It's not going to happen. Dashboarding is a very iterative process. You're going to start, you're going to push something to server, someone's going to say, hey, I'm missing this specific sheet, or I'm missing that. You're gonna add as you go on. Rachel, before I navigate back to our slide deck, do you have any more points to make? Don't think on this one. No. I think you kinda covered all of it. Perfect. So let's say that we, again, have made this overview dashboard. Thought about our users. Now, what's next is we need to then get this business ready. Ensure that it's ready for an executive or an analyst to view this in the server environment. This is where we're gonna be going beyond dashboarding. We're thinking about how can we implement best practices to showcase this showcase our views. But before we do, I wanna see what is your comfort level with dashboard design best practices? So we're gonna have a low. I would like to learn more to get better. Decents, I have a good grasp grasp and I input what I know into practice. Hi. You're a pro with UX UI design. Maybe you should be again fixing this for me. Or other. Let us know your thoughts in the chat. We're more than happy to listen to that feedback. Mhmm. Those are you or hi. Please teach me some things. Yeah. Same. Absolutely. I'm always I'm always impressed. We use a lot of our we have a design team that is helpful for us as well. I would probably, as much as I love this, I'd say I'm decent, but our design team is what makes it. A lot better for sure. I totally agree to Rachel. I feel like I divert back to being an engineer, and I become very technical and I wanna technically answer everything. But whenever it comes to making things look pretty, I do need that little nudge and a little help once in a while. We need to remind that that color is nice. Right? Exactly. Alright. It seems like we've kinda come to a consensus at this point. So and the pull and share the results? So it looks like a lot of you say low. I would like to learn more and get better. And Rachel and I both, as we were just talking about ourselves, we've been in that seat and at some point we still are. I started using Tableau six years ago, and before that, I had never even heard of it or knew even how to pronounce it correctly. And you know, once you start using this tool over a few months, over a few years, it becomes more now flow, and you could become a lot better at it. And also under that, a lot of you said that you're decent. So what we're gonna go through next is a UI checklist. So let's say that you've answered low, you've answered decent. How can you ensure that you're mentally gonna ensure that this dashboard looks good before you push it out without having to try and consult a coworker or someone else. So I'm gonna click off these results really quick. And we're gonna look at this checklist. This is actually on our blog. I know that we're gonna put this into the chat as well. Feel free to go to this, download the PDF. This is super, super useful. And actually whenever I create a dashboard, I go through these exact same steps. So let's say that we're a new consultant or we're new to dashboarding, and we have to build a dashboard. I'm sure a lot of us have built of you much like this one. I know I can say for myself and see Rachel shaking her head. She says, yep, I've built one that looks like this too. This dashboard is fine. Is it good? Yeah. It's it's okay. It's not terrible, but it's not great. If I really wanted to impress someone I don't think this is the dashboard that I wanna put forward. So how can we improve this? How can we go through some steps to make sure that this is gonna shine whenever I push this to server. You're gonna see on the right hand side, there's a lot of different things that we can call out. I'm gonna go through a few of these, but not all of them. Just know that that checklist that we put into the chat, you can link to it and follow all those design steps. So the first thing that I start with is I think about what are the things that I need to talk about in this dashboard? Again, I always start with what is the data story, and we need to define the different aspects, the different parts of the dashboard. And it's defining our titles in those different spacing. Once I do, then it gives me ability to call out important information. Here I can see I'm talking about asset classes. I see a few KPIs of bonds, equities, and foreign exchange. I have another two areas place for industry performance, and asset performance. So now I've created this nice, neat, organized view for people to look at. You have to think a lot of us I'm talking to you guys from the US. We read in a z pattern. Start at the left and go from left to right, and then back down. A lot of times people need to design their dashboard in the same way, so it's natural for people to look at. Something else we need to consider is also our tech size. We need to make our views automatic for people to interpret. Think about your favorite website, whether it's something social media, whether it's, I don't know, some golf website or whatever it is, these companies will spend lots and lots of money on their design to make you enjoy the experience, and a lot of that is through text and design aspects like this. We wanna implement those same practices here. For our text hierarchy, we wanna make sure that it's simple and about three different weight sizes. Maybe some of you have seen the slide that I'm about to show you next, but You will read this first, and then you will read this, then this one, and you'll read this one last. I always like showing this because This makes it apparent that text is so important. Your titles should be the biggest and boldest. Then your sub headers after that, tell people what they're looking at, and then following that, give them instructions. We're gonna do a little experiment with our text hierarchy. I can see I have three main things that most likely you're gonna be using in the dashboard. A title, a chart title, and some body information. I'm gonna quickly click through these, but you can see throughout time as we start to transform change different weight sizes, add in some coloring, start to break up this text, and make sure that it's obvious, what text belongs where, we can make this very clear as this is as to the story that we're trying to tell. I'm using the same typeface, different weights, and different shades of color to help break up all this information. This looks a hundred times better from just the plain text being shown on your screen. So try and break up your information in the same way. Now it doesn't have to look all fancy like this, but I think you guys get the point that I'm trying to make here. Also, with this text and instructions, make sure that your charts follow a logical placement as well. Again, we wanna make this very clean and crisp and easy for people to understand. TYplets can be really useful. One of the polls that I talked about earlier was standardizing, dashboarding across the company. Kemplates can be a great solution for that. Maybe you have a KPI dashboard that everyone needs to land on in an overview, boxes much like this one can really help show placement of what's important, and then allow people to drill down if they need to. Make this more of a on demand thing. And from those high level to lower level views, Again, keeping that same look and feel so it all looks natural, and it's easy to understand. We also wanna make sure that our dashboards are accessible to everyone. We have a good amount of people on this webinar today, and I'm really happy about it. But if I had to guess, someone on this call is color blind. Mhmm. I don't know it. And most of the other people that are joining this call don't know it either. But if the entire dashboard was built in red and green, The people that are color blind aren't gonna be able to see the differences like people that aren't. So we need to make sure that we keep that in mind. Also limit the number of colors you're using in your dashboard. You don't wanna open up a view, and it look like a circus. I have definitely seen a lot of those dashboards and Rachel. I know you have to, and it might seem cool, but it's not enjoyable to look at day in and day out. So just be aware and make sure that we try and avoid those things. There's a lot of websites. Again, these will be linked in the blog if you guys wanna review it. After you've thought about all these different UI design tips, ask people what they think. Watch them use your dashboard and lean towards simple. Because, again, I could create something that I think looks amazing. Rachel can go and use it, and she might be lost confused by something, and I wanna know that feedback so I can help improve it so no one else does or feels the same way. We can spend a ton of time trying to curate something that we think looks great. Much like this nice beautiful paved sidewalk with a lovely little bench where you can sit, people are always gonna look for the fastest and easiest route possible, much like these lovely two muddy pathways. So again, think about the people. Ask them to use it and watch them use it. Much like this one here. Right? This was me running to chemistry class whenever I was in college. Now I was late and they had to put up a gate so then I would try and avoid it. Well, if people still like jumped over the gate apparently, in that picture. They were like, no. Don't care. Jump it over it anyway. Exactly. We can build something that we think looks really cool, much like this dashboard. It's not useful. Even some KPIs, there's too much text on this screen. We wanna try and avoid some of these pitfalls. You can have a really complex dashboard. As long as it's organized, people can follow it, they're gonna be able to utilize it and understand the story being told. So iterating's important. We started here. We were able to correct this dashboard, implement some of these best practices, and make this have a great look and feel. You'll have different flavors of it. Maybe you have a dark background. I'm not one to make anything dark, but I do like the light background. But think about this as we're designing. There's a starting point, but once you do this, some of these design best practices, you're gonna help elevate your dashboard for your end users. And maybe you wanna put this into a web portal, which we'll talk about here in just a minute as well. So I'm gonna come back to our dashboard really quick. And I just wanna make a few little statements. We've added in our our instructions here. We've kept the same text and weight across all of use. I'll say, go and check your the numbers that you have in the view. Is its currency adding dollar signs? Just like here. My total sales, do I really need to have five million twenty nine thousand seven hundred and forty five? Probably not. My professor in college would be kicking me saying that's those significant figures are not correct. Go and make those changes. Come here and I don't know why they give me that. Change this to where you're just seeing a custom currency, maybe put units in millions. Show that high level information. So again, this is clean and crisp and easy for people to look at. It doesn't take that long for you to analyze that checklist and make sure that your dashboard looks great, and you're ready to show this off to anyone. Now the last part here is after I built this view, I'm ready to push this to server. I'm ready to share this with others. Once I do, you know, you can click through the views, make sure that everything looks good, that you're happy with the look and feel. But then I'd wanna come up to server, and I did see I do have one little issue here. I need to fix one of my dashboard actions before I publish it. My action of my state filter, I said show all values after I leave. But I do wanna keep that dashboard just filtered for one specific state. So once I click on Illinois and I filter for Illinois, now my KPI, and my map look good. Perfect. Now once this is done, and I'm ready to share this with others, You wanna go up to server on your top menu bar. You'll need to ensure that you're signed in to your specific server at your company. I'm already signed in to our POC at Interwork. And then I just wanna simply publish the workbook. I'm not sure why I'm getting an error code. Of course, this is showing up in our workshop. Perfectly fine. I've already published this server. Just for this specific reason. So here I can see that I have my dashboard published. This is what your view is going to look like. And what's great is you're going to have all the same interactions available to you that you did in desktop. I can hover over the KPIs, and it's going to filter for those specific views. I can click and even look at just a central region. I can drill down to that specific state. Maybe I wanna know how Illinois is doing. So I drill down to the state, I see again how Chicago's not doing so great. I also wanna make sure that we add in buttons so we can navigate back to the overview. Because different people are gonna wanna look at different areas. So this is allowing me to navigate click and answer those questions as I need. I'm gonna pause here. Rachel, do you have any comments about server or what I just showed here before we go to looking at embedded analytics? No. I don't think so. I think a server is very helpful on actually trying to share it. I think a lot of times we've gone to clients before they had server, and I think the majority of you all have server. But clients have had that before there. Just passing workbooks around, right? And there's no real version control or being able to know what's the most up to date one and all of that information and server is just helpful in trying to actually share and have some engagement in your dashboards knowing that people are actually utilizing it the way it should be used or just utilizing it at all for whatever purposes they have. So just love server. Yeah. They Same here. I don't wanna have to create something in desktop and be like, Rachel, I'm done. I'm gonna email this to you, or I'm gonna put it on the box, and then I want you to download it, and I want you to go and look at it. And then you might have a few comments, and they need to be updated. And we're -- Mhmm. -- constantly doing this file share. Server, this is gonna be our source of truth. We're gonna be able to land here, know how we're doing and then log off and be happy with it. Mhmm. Yeah. Now I wanna display something else and this is, again, in that beyond dashboarding topic. And I wanna talk about the overall analytics journey. So we're gonna have a data layer. So we're building we're using some kind of database, that's where all of our data lies, whether it's in Snowflake, or it's SQL whatever it may be. Then we're gonna have an analytics layer. In this use case, we're using Tableau. To build those dashboards to show how we're doing. And then we have a presentation layer. So how are we showing this to everyone? Are we sending this to server? We're possibly at our company, do we have different platforms that we're using? Maybe you're using another BI reporting platform, or you're using some other tool? What if you're having to even flip between multiple servers and your end users are like, I'm confused. Where do I go to see all these different views? At Interwix, we do have a product called the curator. That puts all these different viewing platforms into one. So let's say that we had Tableau along with another platform, you can log in to curator and have the same look and feel between all the different platforms and views that you're building. You can create standardized logos, formatting, and even filters to use across all the different views. So again, your landing pages are gonna look the same, and your end users aren't going to be confused. And Honestly, this is how you can make your dashboard look really slick. I actually took in one last comment. No coding acquired here, they can be launched in under a week, and you do get some port from experts, from InterWorks, from everything from working with the data all the way up trying to display that in curator itself. Now we saw that view in server. It looks very similar to what we saw on desktop except we have it in an Internet browser. Now in curator, our view would also look very similar. So I can land on my curator page, and I'm just gonna refresh it really quick. You can also have a custom load screen, which is really cool. We we have a lot of different iterations here. But a user can land on this page and have that standardized look and feel. I have all the same functionality that I did in server. I can come and look at my map. I can click on a specific state. I can filter for more details and navigate back and forth. Now in this dashboard, I created navigation buttons in the view. You can also add in that navigation into the curator portal as well. So it makes this nice, clean, and crisp. And again, just making this more uniform for our users because we want people to use the visualizations that we build, and we don't want to confuse them. And this is a really cool product to help us streamline this, and also make us as the creators of these views look great. With the story that we're trying to tell. So I wanna take a one last poll here. And I'm curious where are you with embedded at analytics? We're not gonna share the results here. This is this for us being curious, I'm currently using embedded an embedded solution. No. I'm not currently. You're not currently utilizing, but you'd like to explore it, or you're not sure that you're ready for embedded yet. So take just a minute, answer this. Actually, curious myself to see where a lot of people are. While that's happening, we did have one question that came in through Q and A that I just wanna kinda like touch on real quick. It was asking about how do you display your dashboard centered on the server. Right when you were showing your dashboards up on server, it was nice and in the center. And sometimes I have seen it where it's been more left aligned and it is a little bit frustrating to do that. I always thought that it was just kinda like the luck of server sometimes, but it seems in doing some research that if you have any of them, any of your dashboards set to automatic sizing instead of a fixed size, then it will left align them automatic left line everything, even if you have even if you have some of those, some dashboards that are fixed and some that are automatic. If any of them are automatic, then it will, it'll left align it. So if you wanna show Maxwell what we're talking about there by automatic versus fixed, that might be helpful. Yeah. So back in the dashboard view, on the left hand side, you're gonna see an option of size. And we always recommend a fixed size. One, if you select automatic, you're gonna see some issues much like Rachel was talking about. As you publish this to server, things might move around, and they might not be centered or in the the exact location that we're wanting. Also, if you're publishing dashboards automatic to the server, You're going to slow down the server, because Tableau is then having to think about every single device that's loading on. We need to rerender the dashboard to make sure that it's going to fit whenever you pull it down from server. So a fixed size is going to fit most laptops, most computers that are logging into the server and needing to look at that visualization. At a company, I I don't expect that you're using a hundred different types of laptops. Most likely you're using some standard flavor, and you can publish up your workbooks. With those sizes in mind. Great question, Rachel. Thank you for bringing that up. We're getting towards the end here, and I we do want to give a little more time for q and a. I just want to say a few follow-up things. So one, after you after we do end our session today, you're gonna get a little pop up survey in your browser. Take just twenty seconds to answer questions for us. We really want to know what's this useful to you, and a few more follow-up things. Also, I showed you curator here at the end, really cool product, great for our end users. There's a fourteen day free trial. If you guys wanna scan your QR code, feel free to take advantage of that. Also, follow us on LinkedIn and look at the inner works blog. We're gonna be posting a recap or replay to this specific webinar, and also look for our upcoming workshops that we have. We're actually going to host this workshop next month So if any of your coworkers or anyone else that missed out, come and listen to Rachel and I again. We might not talk about pizza next month, but we'll definitely have a few interesting tips and tricks for everyone. So Maybe ramen. Right? Yeah. Maybe ramen. Who We'll talk about ramen next month. Who knows? I'll just do a different food every month. We had one question in q and a that I also just wanted to kinda touch on live and that was a question about if we were planning to do any data cleaning webinars or how does set up a dashboard from already clean data. As Maxwell said, and I think that we've been we've posted in the chat and we'll post again, look at that website for our upcoming events, we are constantly adding. I do not think that there is one on the books, but we are constantly adding more and more events onto there, so just kind of keep an eye on that as well as your email for any kind of thing coming through saying, hey, we're going to have a nice data cleaning webinar coming forward. So, All that to say, we are constantly adding new events, so keep an eye out for those. And thank you for the input on what you are interested in seeing in the future. Yeah. And we wanna thank you guys. It's fun that I get to present with Rachel. So, Rachel, thank you so much. And we'll sit here and answer any other questions that you guys may have. Otherwise, we hope that you have a wonderful rest of your Wednesday. And so I do see there was a question up there. Yes, we have a couple. Where does data structure supporting the curator dashboards reside? If someone has to use them, what is some going to be the data lift for this. So the curator is a nice, like, visual wrapper for server. So it's if you have your data up on server and that's where it's living, that's where it is for curator as well. Curator isn't taking the data away from server. It's just giving you a nice visualization, as well as a nice wrapper around it to make it a little bit more specific to your company, as well as making the interactivity with it a little bit better. So hopefully that answers the question that we had about the data behind curator. If it did not, feel free to ask a follow-up question. It seems, yeah, I think a lot of they're answering a lot of questions. I'm glad that you all have been enjoying this. Yeah. And if we don't get to all your questions, know that we will follow-up and answer those specifically for you. I'm just trying to scroll through myself in see if there's any that I can answer quickly on the call. I did see some on some formatting. Absolutely. Keep formatting consistent. Mine might not have been absolutely perfect, but I hope you guys get the point as to ensure that you examine that and update that as you push out your different views. And look at that UI checklist. Super super helpful. Mhmm. I definitely use that UI checklist. Sometimes even now, even years years later. Right? He gave up to do that. So, like, wait. What was I doing? And because you, like, looked at a dashboard for so long, and you're like, what am I looking at? I have no idea. You forget you forget. But yeah, I think we've we've caught everything in as Maxwell said, we have this chat, we keep this chat, so we'll be able to kinda parse through that and see if there's any specific questions that we missed that made its way through. We were not intentionally ignoring you. We should be able to get back to you. Well, Rachel, I think that we have hit the end and a lot of thank you. So, again, Rachel, thank you for joining me to all of our guests that joined this week. We are very thankful for your questions and your time. Again, we'll host this again next month. So if you guys want to come back and get a refresher or know anyone else, tell them to sign up. Otherwise, we'll see you at the next Interworks webinar. So thank you so much, and we'll see you soon.