[Music] foreign [Music] okay we are at the top of the hour we still have some people that are trickling in but we're going to go ahead and get started so welcome to the platform analytics Academy um that we're having today uh really excited about the content that we're going to be going over today uh I have myself and of course some of the co-workers of mine that are on here so um you know hopefully this is going to be really great content for you and you know please ask all the questions that you can get my slide deck moving there we go so as usual this is always for you uh we try as hard as we can to bring fresh ideas you know what I think I'll go on camera too I seem to be outnumbered here so I might as well do the same thing oh no they're okay there's no proof no peer pressure there we go oh you're all right you're meaner than I am Tara so again as usual these are always for you we try to bring as many fresh ideas as we possibly can to you and of course better understanding and some practical guidance and I think um there'll be a lot of that today uh so this is being recorded um it will be out on the community event later on this afternoon and of course out on our YouTube as well this afternoon um and of course use the Q a please try to use the Q a we'll have other people uh that are monitoring it uh so if an answer can be uh if an answer a question can be answered it will be uh answered via type or out loud if it's something that's pertaining to a certain spot that we are and we feel like we need to stop we'll go ahead and stop and ask that question as well but please feel free to ask as many questions as you can and if you can put those in the Q a rather than the chat that would really help out um a safe harbor uh they're always that could possibly be things that are mentioned inside of these presentations so please don't make any sort of purchasing decisions uh based on that uh I don't know how much of that we'll actually have today but we always like to be safe and make sure that you all are aware um and again my name is Thomas Davis and today we have Tara and Dan that are actually going to co-present and bring some really good things around uh dashboard design strategies and then uh also Adam is here as well who always has just a wealth of knowledge so I expect him to hopefully chime in at some point as well so with that I'm going to stop talking and I'm going to give it to Dan or Tara whoever is first and we'll go against the same story first yep I'll be first okay go to Dan go to Dan okay and now that slide that's up there right now indicates a reduction with dashboard design strategies so let me share my screen thank you so it'll go over to our slide deck here yep so uh so we're talking about dashboard design strategies for some of you this might be kind of you that this might be kind of a uh a back to the basics but we do want to make sure that we cover that uh that we want to make sure that we're covering what I would consider to be some of the more basic stuff but at the same time um we talk with customers all the time who really struggle with this so I think this is a this is a topic that is something that I think a lot of customers can can use some guidance on and the other part of this is and I'm sure many of you have your own thoughts around it too so please do feel free to share your ideas that'll probably be a good use if you want to if you want to share something you might do you might mention that in the chat but if you have to ask a question put that in the Q a so but we'll definitely open to hear your ideas around this as well so we're so when we're talking about uh okay gotta make sure we have the Safe Harbor so our agenda for today is we're talking about the you know design the different perspectives of Design Within uh within a dashboard so the all right so topics we're going to cover designing with intent the organization of the content on your dashboard the do's and don'ts and just general helpful tips uh we want so we think there's some some things that we've come across and this is again where we're gonna really I think we're gonna really uh I'm interested to hear your ideas too about any other helpful helpful hints that you might have about the design so we mean by Design with intent that first part we're really talking about the content the you know the actual data that you're putting on that you're putting on a dashboard then we get into the organization we're talking more about the design of what's there you know how it's visually presented and a point that I like to make on this wherever that we really want to stress is how you present the information is just as important as what information you choose to present so and that's something that's often overlooked I I was joking with Tara a little bit earlier about this I am I consider myself to be pretty good at the content part of what content to put on a dashboard and how to get there I am probably not the best person for it to say uh I I'm gonna design it for you as well I usually like to bring in others to help with the help with the design elements I can follow the basic rules like we're going to talk about today but uh that's but I always like to give you know this is a place where I also want to get your ideas so when we're talking about dashboards I want to put in the context of this quote I I just love this quote and think of this in the concept of the dashboards that we present our customers action is achieved not when there is nothing more to add but when there is nothing left to take away and I cannot be that this is I I've thought of this message I try to find good ways to to mention talk about this message with customers on one-on-one calls all the time and I think this is a great way to put it it's not how much can I put into a dashboard it's what is the least amount that I can present on the dashboard and still get that still provide the information that my customer or that my consumer of that dashboard needs so it's it's the less is more if I have more content I need to add that should probably be a different tab or a different dashboard or maybe not on the dashboard at all so but that's it's so the idea is to when you look at a dashboard we look at the content of it is there anything I can take away from this and still provide the primary intent of this dashboard or of this tab that's the way we really want to think of it So within that really leads into the discussion of Designing with intent I'm gonna do a quick switch here I want my and bear with me for just a moment here having my own technical issues but all right no worries so but we say there's really two two primary perspectives of purpose we talk about the purpose what is the purpose of a dashboard a purpose of your dashboard should never have anything to do with my customers said they wanted to see this this data on it um always if you are if you are designing your own dashboards and you represent the customer you know you want to always keep this in mind but also a way a lot of customers work is they might have a a business analyst or even someone from I.T that's actually developing the dashboard for them that wouldn't be the ideal in most scenarios from my perspective but in some companies that's just the way it works but if you're in that ladder scenario really we really want to uh enable you really want to encourage you to push back if someone just says I need these 15 things on my dashboard uh and we can start really from these two perspectives in mind it should be that when the general users are viewing a dashboard to do one of two things they're there to either take an action so the who is my consumer of this dashboard and what actions do I expect them to take as a result of this information secondly is also just to start a conversation which in a way is an action itself but we're just saying you know so how am I trending against my goals so kpi should always always tie back to a specific goal I won't go through the whole presentation again some of you are veterans and have seen best present on this numerous times but we have lots of information on the community about like how to pick metrics and how to um but the the main the main theme of it is start with a a primary organizational objective and then work and then kind of and then analyze your way down to what the kpis are so if my organizational objective is I need to reduce costs by 10 percent then then on this dashboard maybe it's for the executive maybe it's for the executives direct reports I want to think about what are the kpis that that support that specific objective that specific goal so so it's either to take an action on it so there's something that I say I'm uh I I'm a director and I need to take action on an area that is driving up costs that my dashboard is in that is showing me I can take action on that or it starts a conversation I'm the executive and I say hey um line level manager why is the you know why are the uh um why is the average time to resolve let's say that's one of your cost factors why is that going up they're not going to drill into the details of it it's not their job to go in and say what is exactly causing it at my level at the executive level I just want to see what's the Top Line and are we getting worse or better so it starts a conversation and that's really what we're talking about here when so and then we went and that's what I mean by tying back to a specific goal so we're talking about business goals we want to make sure that when you're just when you're starting from a from dashboard content you want to understand your goals so thinking of this again from the perspective of if is it my business unit is it my my Department's dashboard that I'm presenting or am I the designer that I'm helping another department put their dashboard together but you always want to think of it from these goals perspective what are the business goals I talk with customers a lot when I used to do implementation projects I used to be on our services group and the first question I always ask is what what is your primary reason for investing in servicenow and I will tell you that many customers got a a blank look in their face because there wasn't that conversation between the executive level and the implementers to say what is it we're trying to achieve by by moving to service now what's our what's our organizational reason because that can be usually a great starting point for determining what it is that I want to put on my dashboards you know so I need to start identifying you know what is our purpose if our purpose was to reduce costs if our purpose was to increase you know increase knowledge use or whatever that purpose is so these goals are usually determined by the c-level teams so understanding those goals ask start the conversation so in a couple of examples there's a deal that reducing I.T spend by 10 increased customer satisfaction might be might be even more specific on a let's say like not just even a csat score but maybe it's a um suddenly forgetting the term the the customer index the uh thank you net promoter thank you thank you net promoter score it might be that or detaining 95 self-service workflows these are things that generally the the line level folks who are working on your in working on your incidents working on your cases working on the day-to-day task records may not have visibility to we want them to know what their top level objectives are so that they can see how the work they're doing aligns with those top objectives know your audience key part here so and we have this example of you're using that example of reducing I.T spend um so this a service owner of let's say a person who owns the desktop Support Services they have a different perspective on what data they want to see what kpis they want to see then the executive would now I want if I'm the desktop support service owner I want to know what the executive's goals are and I was but so I might want a I want to might want a main dashboard that gives me a small little number that says what their what kpis they're looking at but I want the but I want the main part of this dashboard to tell me what are the things I can do to to help improve the executive's objective scores so how can I impact trends that affect call cost and quality same thing for your Frontline workers if I have an agent level dashboard how you know put things on there that helps them understand how they can how they can work better to work towards that overall reduction of I.T costs so it's thinking of so there should never be a thought of One dashboard to rule them all we really want to look at lots of different of multiple dashboards not lots of different but multiple dashboards from multiple stakeholders and it's types of stakeholders so who are they what is their purpose so what are they trying to accomplish with that dashboard what do they do what what do they do with the data what do they do with the information so if I'm the executive do I need to report that do I need to be able to defend that number back at the at the c-level staff meetings um you know that these are the sort of things that we're talking about what is it that they need to get out of this dashboard and more and pro just as important is can you tie it all back to that top level goal so ultimately everything every all the metrics for my different for my different personas here all for my different personas all my metrics for each of these different personas should ultimately roll up to the goals at the at the executive level so we're all aligned okay understanding their Journey so find out the steps your users take before arriving to your dashboard and where they go next so what are their needs so how do where have they come from if it's an executive where they're coming from is probably a very different place than your than your customer service agents working on on CSM cases you know that they're coming right from their tasks when you move as we start moving into the workspace world with next experience that's going to become even more important because the dashboard content that you present to an agent is going to be you know is probably going to be very different in their workspace than the dashboard you present to your um to your line level managers or to your executives so and so these are all the different things to consider as the kpi actionable is the action intuitive does does the presentation does it give me data in a way that makes it clear to me as a consumer of that dashboard what I'm supposed to do with it if it just says mttr is going up what does that tell me if I'm if I'm an agent does that tell me anything because that's like I'm a golfer so it'd be like telling a golfer you know uh um you really need to get your scores down into the 90s because I'm over and I'm over 100 so uh you need to get your scores down into the 90s okay great thanks that really helps um what can I do so we helped so we put out information for the agents that might say things like um how we how well you're utilizing knowledge articles how you know the uh how you know how many reassignments are there on cases that you opened that that sort of thing but it all still rolls up to that top level goal so that's just a quick look at the at the at the content side of things and I want to stop to see I see there's some things in chat and at least one q a so do we have questions or issues that we should discuss here before we move on well we did have we did have a question come through that says I'm curious to know how prevalent PA usage is amongst servicenow customers uh any idea and oh yeah that's a great question okay go for it and I would say and because it's interesting because I would because we're actually working we've actually been working on some of those exact we've had kind of decent numbers we really all along but we've really been focusing a lot more recently on it on on those in the last six months or so I would say we probably have PA usage for those who are eligible for PA so they have like itsm pro itom pro they have one of the pro licenses so they have PA we probably see 60 to 70 percent and probably even more than that I want to say PA was probably in the mid 70s of those who are entitled to use it but when I say usage that means that can mean a lot of different things what we're saying is they've shown signs of use of use signatures that how we intend PA to be used doesn't mean they're doing anything really Advanced with it it just means they're doing some basic usage with it so that's good so that's a good question so why not just let turn PA on and let the customers go in and create dashboards that is a whole other discussion and um that around the governance piece a lot of customers will do that we'll just say you know I can you know I I can allow anyone to create a dashboard and by the way that is the default that is the default for it for a dashboard uh the default permissions is any user who has a system login can create it back by default though they can't sh that they can't share it they get you know that they're not visible to everybody and they're limited to what content they can place on that page it's not until they get like the PA power user or PA admin can they do can they do more with it and can they share it more broadly um so some companies will do that but I will do maybe a plug for a a previous Academy session we did in the white paper that goes along with it on governance that talks about the whole process of you know how we recommend based upon a lot of our customer feedback how we recommend addressing a lot of the governance issues when it comes to PA and Reporting um but because there's different perspectives you can have on that and there are different cases where you might want to handle that question differently so as I said some customers say just turn it on and let anyone do what they want to with it I wouldn't but I would be very careful with the PA power user and Pa admin I would recommend to have at least some baseline level of training and demonstration of competence um in in usage of PA before I give anyone the PA power user there's also a really good knowledge session from a couple years back that Lisa Barrymore from Walmart presented where she talked about her process of doing that no really good question ah yeah Dan I think that I think that you could probably move forward we'll oh yeah let's go ahead and move forward and paste that in there and then I think some of the other ones might be getting answered it can move forward all right so yeah let's go ahead and move forward to Tara um I am going to talk to you very briefly if organization is and then jump jump into a demo so we have a few more slides that are in the stack that kind of talk about um some of the stuff that I'd rather just demo for you oh yeah sorry never we do um so I'll just touch on these uh next couple of next couple of things pretty briefly and then jump into the demo of of some of the things we're talking about so placement when organizing dashboard content you want to think like your users um and you also want to think about one of the things that Dan touched on and that we continue to touch on is what is that high level business goal what is my objective as an organization um and as the dashboard that I've just created for you or for my user consumer what is their specific goal that ties back to that high level business goal that should be the most prevalent item on your dashboard and we recommend leveraging the Z pattern so that you have your most important information at the top left hand corner that tells you okay this is what my goal is for this dashboard that always ties back to the high level business goal I will always continue to say that um do the kpis on this dashboard contribute to the business school that's always um uh something that you should always ask yourself a lot of times users will come up to you and ask for you know I want to know how many um open cases I have you know I think Victor asked about uh support dashboards how many open cases do I have what does that tell you other than how many open cases you have doesn't give you an action it doesn't tell you if that's a good or a bad number um it doesn't give you much of anything other than information but if you think about it from a different perspective um what percentage of my open cases are sitting um you know in the queue for more than three days or Which percentage of my open cases are critical uh Which percentage of my open cases have been um haven't been closed in three months you know stuff like that is more actionable it gives you um gives you an objective it ties back to a business goal is if you're trying to increase customer satisfaction you're not closing cases for three months or you're not picking them up from the queue in three days those are things that actually tie back to a specific business is goal that are actionable by a specific user who's accessing a dashboard um they should know by looking at the analytics on the dashboard especially if you have everything in what we call above the fold which means that you don't have to scroll down to see more data as much as much actionable um relatable information to that goal is above the fold they should know exactly what action they have to take by looking at it and so placement is critical if they have to continue to scroll if they have to go to three different tabs to figure out what they need to do if there's way too many widgets on a dashboard that can also be jarring um we talk about uh working we have worked with our own designers here at servicenow and one of the things that we've found through our user research is cognitive load in your own something that actually impacts the way your brain processes information is um a huge huge thing we never thought about that design actually impacts if you think about things and you want you keep things clean and simple and not crowded um use you streamline your process uh the way the way the data is consumed will actually reduce cognitive cognitive load that's hard for me to save for some reason and allow your users to get to where they need to get a lot quicker rather than having them have to process a bunch of stuff and figure out what they need and then we also recommend high priority actionable items always at the top above the folds and any additional information could be on another tab or or below the fold and if they are um related specific to each other like for example if you have um my percentage of open backlog that is critical but you also want to show all your open backlog and and what um different states they're in at the time you can put those next to each other so that they're supporting information and you can tell okay I need to address my critical ones first but it looks like I have a lot of p4s way more p4s than I probably should have that which means that they've been sitting out there because they're a lower priority and that actually impacts customer satisfaction because it doesn't matter if it's a low priority that low hanging fruit is generally the percentage of your workload and so you need to think about um how to flush that up to the surface and so you want to make sure that you are um thinking about where you place this stuff and how you put it together go ahead Dan come on come on okay there we go okay and user error yeah very quickly I touched on Z pattern this is just a definition of what the Z pattern is right it's the it follows the way the human eye reads right left to right and so we put our most pertinent information up in the top left hand corner and then we gradually put supporting information just like we were reading a book right top row from left to right is the most critical stuff and then the next row is supporting of all of that stuff um either either it relates directly to it or supports it and shows you what actions you take and it's just um a simple um clean and concise way for users to consume data in the same way that we generally tend to read I am being a little bit ignorant in the fact that I understand other folks read from right to left but there are um in those uh countries where that is you can switch switch the design and just flip it um and and that would work just as well but it's the same concept is consuming it cognitively so that you know um how it flows in a way that tells you the story what actions to take and supports all of your goals look at my mind because I was thinking well I was going to ask are there cultural differences in that so absolutely absolutely and you you apply culturally what makes sense as long as you're applying um a design that it follows that same guidelines right it helps you support meeting your goal next slide relevance so this is another thing that I kind of touched on already um make sure you have relevant content anything that's irrelevant or supporting or informational is sticking on another tab I'm a huge fan of if you if people come to you um and you've heard many of you who have heard me talk before heard me say no is an answer if someone comes to you and says I have this analytic why why do you need it what what problem are you going to solve um is it something that your you know cxo is just asking for because it's a number that they've always had that's fine I'll give it to you but you're getting it on another tab because I am telling you this is what we need to improve our processes our workflows highlight where we're inefficient and as a uh report writer designer I need to make sure that you are getting the most out of this on the on the front page so is this data visualization needed sometimes knows the answer um what action does it drive uh can you tell me why you need it um and then can it combine can it be combined with anything else so we do have several charts out there that you can um I I'm I'm excited to see that Steven's on this call because um I'm going to show you the workbench in a little bit and um uh there's a good opera good way of combining when you have a lot of data that users are asking for that need to be consumed and your goals are specific to that there are different widgets out there where you can combine it so it simplifies um how you're consuming that data and now I am going to jump into a very quick demo now I can stop sharing I guess that's the cancer okay now close that I'm going to share my screen in just a second I'm getting all set up here um okay so let me share my screen there we go all right so some of the things that this is what the rest of the deck uh so when Thomas shares the deck out with you this is what's documented in the rest of the deck I just thought I would show you um so in this specific uh design example here our goal is to increase our customer satisfaction store score if this specific dashboard so we want to see okay in the top left hand corner what um is my customer satisfaction score if my goal is to is to improve that and then what contributes directly to that customer satisfaction score my percentage of breached slas uh ding ding ding huge um do I have changes that are coming up in the next seven days that are going to impact whether or not instances go down um customers have access to stuff that's a that's a big one as well as mean time to resolve right that's always a big uh issue of whether or not we're getting and closing our workload I believe someone asked about support what is a good support dashboard we do have this available as out of the box dashboard that you could pick up working with um some of our teams there was there's a few more tabs on this dashboard as well but you won't see it in this in this demo but we do have this available out of the box it is directly related to support and it does highlight um as a goal improving customer satisfaction um we look at our open workload and workload means uh all of what we got going on how many incidents do we have how many problems how many requests um now in this example this is what we have available out of the box I might switch some of these to be percentages of other things that are are being impacted but um as an I.T professional group this is what uh they felt were would be the most supportive to customer satisfaction and we agree that these are all supporting analytics so they all go in that same Z pattern that we talked about and everything supports this high level goal which is increasing customer satisfaction the other thing we also want to think about is uh you that cognitive load that we were talking about what draws um what pulls in pulls you in and and uh captures you whether or not you know what action to take but also are my colors calming if I have colors on here they need to be they need to be um related to whether or not you have a good like right down here you see that this is red we're down 0.9 percent I want to be drawn to that I want to know okay there's something going on here something's wrong I need to take action down here with me time to resolve our mean time to resolve has gone up that's bad too right you set that up when you create your indicators and and all that you you set up these color changes um you want those to be the colors that you're drawn to um our breached SLA is uh up that should probably should be bad though um um we'll have to look at that yeah let's demo data so yeah yeah but yeah that's those are the colors that you want to draw your eye to so if you need to use background colors border colors they should be soft and calming um if you're going to use we we recommend not having borders and either using lightly colored headers so in this example here we have lightly colored headers um one of the things that we're really really big on as well is if you have single scores on a dashboard use the same template unless you have something else you need to highlight then move it to a different row so for in this in this I'll show you that in a different example in this example here we have all the Sim template on the top row everything is left aligned everything has the exact same color header and that keeps that keeps your your cognitive load load so that you can focus on what you need to focus on and draw my attention to where I'm performing badly in where I can make those improvements and not be looking for where's the title on this one where's the title on that one why is there all these different color you know colors and all this other stuff so you want to think about that while you're designing colors are important and I've seen some pretty wild and crazy things out there so um using the same templates um not making I'll let me get into that in the next one so in on this next example what we show here is using title alignment that is most appropriate with the widget and I'll show you here rather than have headers in this example we're going to change our background to be um calming and that also makes them stand out without making them uh be aggressive and in your face and all these hard lines and stuff it just kind of gives a seamless clean way to look in the top row I have all of the same visualizations it's a left aligned single score so I made sure that my title is left aligned here we have a single score that is Center adjusted so I made sure that my titles are centered adjusted and then if I have in this example they're just all the same widgets I just wanted to show you um what it looks like when you are clean and you have the same uh widgets next to each other so it's kind of like easy to kind of jump from one to the other you don't have to figure out well why does this one look different is it telling you know it's not confusing or jarring you always want to be thinking about that because it's it is a thing to be uh worried about how your cons your consumers are um are uh absorbing this data this one's just for you Stephen I do have an example of a workbench widget um and this is a personal joke between me and Steven so I know he's laughing really hard right now but there are that we do have this workbench widget and this is a way to con combine and consolidate data when you have a lot of information um instead of putting all of this stuff on a dashboard you can use a different visualization to combine it we have lists we have breakdowns um and this is another one that I like to use because you're able to it doesn't have to be used the way it was conceived there are other ways to use it in this team specifically decided okay I want to be able to show my own open incidents because that was something that an executive asked for even though we think it's just informational but I can by showing supporting metrics in the carousel show everything that is that is critical and actionable uh based off of this score up here so for my open incidents which is an info emotional uh data point I can show what of those open incidents have percents with problems how many of those open incidents have missed SLA what percentage has not been updated in the last five days I can show all of these supporting metrics for just that one indicator um using leveraging this visualization so I really minimize how many widgets I have on a dashboard I can just use this in one Tab and simply and cleanly show a lot of supporting information in one in one visualization and I can also you apply breakdowns to it so I can look at it for specific groups um and specific subgroups within those groups so this is a good way um to absorb a lot of information in one visualization that still keeps that cognitive load down and still provides value by showing what is applicable so you could put anything in here but really you want to be thinking about okay if this is open incidents what how do I break that down to provide value into what I need to do with these open incidents and we also you show you you can do problems requests kind of like whatever this is another example of where we have a workbench um because we want to look at activity by Channel and figure out where we can make changes within our process but in addition to that we want to know what we're spending and so instead of having uh all the single scores at the top this team decided let's put them on the left hand side and let's have the let's continue to use the workbench on the right hand side so I can continue to look and see okay I'm spending 1.7 um on average cost per week which is this is just demo data so obviously that would be insane um but then we can also look at what's my cost per request what are my mean times to resolve what's past um close past the the its actual due date we can look and figure out where we can make changes to our workflow increase Automation and reduce spend at the same time and this is a good way to combine different types of widgets on the same dashboard without making it super busy and super like I have to move all over the place like we're making sure we have all of our titles aligned the same way we're using um oh another thing that I I didn't touch on was uh casing using title casing versus sentence casing pick one and stick to it right um there's there's preferences and it depends on the designer to be honest with you or the consumer or the the person who's creating it um I like title casing our design team like sentence casing we use sentence casing most of the time in the stuff that we put out uh publicly but it just kind of just pick one and stick to it there's no Golden Rule of what's going to be easier to consume it's just consistent when things are different even if it's something simple as a title people notice that in the back of their mind and then wonder is there something different about this what do I what do I need to figure out why is that different and it takes away from the message that you're telling with your dashboard design and then uh the don't sample um I was just going to show you really quick here was um you don't want a single score to take up you know a whole row that's that's crazy they're single scores they're small they're designed they're designed to give you a lot of information and at a quick glance and then move on so you don't want them taking up I mean I only have three widgets on this page um I've got this one Center aligned this one left aligned with the weird um ugly color background and then I was going to show you you also don't want to pick distracting backgrounds you know because then that is a huge impact on your cognitive load is like where do I especially red green yellow any of the stoplight colors you want to avoid because those are actually built in when you apply targets to your visualizations and that will distract you from seeing what you should be focused on um in uh when you're when you're looking and consuming a dashboard um I'm not a huge fan of uh abbreviation so I put this in here as an example of what we would recommend you don't do um but you know if your whole team knows what it is like csat's pretty obvious but um mttr or stuff like that some people actually come to me and been like what does that mean it's like oh me time to resolve yeah I see it and live it and breathe it every single day as a report writer but yeah maybe this isn't something you understand or or know and then if we get too carried away with abbreviations uh then all of a sudden you're like oh or acronyms or whatever people are spending more time figuring out what those are and less time focusing on fixing where the problem is um so again no big uh big giant scores everything could be uh similar and then this is another example where we have three different scores they're all tying back to the same goal which is csat improving csat but we have plant changes at the top reached slas on the right all everything looks like it's different and I don't know why and so I'm going to think about that even though it shouldn't be or you know it doesn't it seems like it's not a big like why would I think about that like it doesn't seem like something you should be thinking about or worrying about but um it is definitely something that we do think about and is uh something that um comes in the back of your mind and you actually do spend time uh being impacted by it even if you don't know you're being impacted by it which is which is really weird um let me make sure I touched on everything really quick hey Tara real quick um yeah are there any are there anything specific that you would from a best practice perspective to think about when using interactive filters or breakdown filters on the dashboard um I do have a slide here I was gonna yeah let me I'll go back to titles really quick um um we do have some recommendations on filters so if you have a drop down menu right avoid having a drop down menu where they can't see all the choices at once if they have to scroll maybe that's not um that's if they have to scroll through like 50 or 60 things maybe that's not a drop down that you need to be using um there are ways to break down the data so that you have everything um relevant top in or whatever it is you have to think about the way you have your data structured and the way it's going to be consumed to make it easier for the customer to get to um sometimes if they can type it in Faster than having to pull it up in a drop down list then that's the choice that you want to make for your filter um aim to have more than you know more than seven but less than 15 so that it's not this huge uh ginormous list that they have to um go through and then um you know ask yourself is this something that I could I could present with radio buttons as long as I ha I don't have that many um and and provide them all the options all at once right to see them and use checks boxes when you have a small to medium list so that if you have a multi multi um multi-filter uh did that answer the question or do you want to ask it again we'll wait to see if they ask something at this one okay but we do I mean we do recommend um as when and I don't think I actually put in this deck but one of the designers that we worked with um recommends now that we have the option with the the new experience you can actually put the filter at the top and um it can work with all of your tabs in the the experience that we have today they recommend you either put them at the top across the top if you have more than one and do and make sure you have them um use the same type same thing like we we talked about with the widgets or um have a gutter which is you have your filter either to the right or to the left and nothing wraps around it it's literally let me actually I could just show you that so I have to change this color because it's gonna drive me nuts that's my favorite color because it's so calming um but here like let's say if I were to put a filter in here I'm gonna I'm not gonna I'm just gonna pick one uh just just I don't even know if it applies to this but we're just gonna pretend just so I can show you an example so what the designer recommends um and you know it it it's not a bad idea actually is to keep it in the gutter what they call a gutter um and then have everything like move this stuff so you would make these a little bit smaller so that the filter stands alone you know what I'm saying it really stands out yeah it's it visually stands out yeah I I I I'm not no it makes sense it's all the same size and yeah move these like right now I'm just kind of on the spot here but yeah I don't know you know what I mean put them so that they're not all um so that the gut so see how it's a gutter here now and then all my visualizations would be to the right so then whatever I picked all these would change and they either recommend it on the left hand side or the right hand side either it depends on your preference but that it stands alone so this is going to look crappy right now but that it stands alone so that you can see very clearly if I had more than one filter I could have them all on the left all on the right or on the top so that that everything below it to the right or left of it changes um and it's not they're not wrapped and what they mean by wrap is let's not let's not have oh I'm trying to move it while I'm not inside it's not like um here like above it it's not buried sorry about that yeah my dog you know it's not buried it's not wrapped or hidden in here um it's not even not even have anything below it they want it by itself which I think is great advice um and I wonder with that I don't I didn't put it in the deck I just didn't think about it until that question was asked but you see what you see where I'm going with it it would take me a while to reformat these and make these the right sizes um you know what I'm saying but I get the yeah that's really good hopefully hopefully that answers that question and then uh let's see I was gonna talk really quick about I think filters was my last slide now it just wants to spin do you see it just spinning yeah so okay here we go so I was gonna talk about um widget titles so one of the other things uh we have some out of the box content packs that are out there before we had designers on staff um years and years ago that everything started with number of age of number of number of and our designers came in and said you're giving them way too much to read and process it's obvious just put what it is open instances and then look it down and see it's a number it's like pretty clear so we recommend that and as well simplify your titles uh be careful with with abbreviations like I said um if you're going to use an abbreviation like MGR for manager or you know something like that just be consistent everywhere that's fine I mean that's a pretty obvious one csat's a pretty obvious one be consistent have it everywhere um but keep things as small and to the point as possible and avoid having these live scene some dashboards with some really long sentences if you can't explain what that data is in a couple words let's rethink uh what what value it's actually bringing to the dashboard all right what other questions we got I there was one question that I that was asked that I'm going to kind of add a little additional context to it there's one question about the noting that we're presenting on the classic dashboard so I just want to talk about that okay we are normally we like to present during the academies on the most current uh General availability release we purposefully are not this time because the uh the the dashboards in next experience are not in Tokyo are not yet feature com are not yet feature complete there it's it so they're not feature parity with the classic dashboard so the sum of the content some of the types of charts you have in classic dashboards are not yet available that is a that that is an ongoing project to work towards feature parity between the two so I just want you to be aware of that same rules apply though same rules apply yeah absolutely these rules apply to anything actually any tool that you were using right any anything yeah but uh we wanted to also do go based off of the percentage of customers we have using what experience and it's also a really good point research everybody most consumers are continuing to use classic and so and we can definitely do this one again in next experience however and it's the same exact rules uh make sure you're you know using your borders and colors and using the Z pattern and making sure your your data is relevant um see Steven's question um uh content pack versions I'm gonna let Adam take that question yeah yeah um same um in classic I mean we have the solution library for some of them and some of them we don't um just modify them I mean make the changes you need to all PA I expect to be modified all the content packs I think of as starter blueprints um their ideas to get started from for you to continue on so go ahead I mean modify them and change them I'm I don't know up top my head um but Danner or Tara Thomas in next experience there are a lot less content packs because they're just built into the workspace right right so so the updates should be now like with less dashboards and more built-in analytics it's just uh we upgraded as part of the normal process that they are going to get upgraded they'll still be analytics and there'll still be some issues with these things but the things that are core to the product should just upgrade the rest of them just up just change them do it do what you need to do um you know the model I I I wish we had used the model that we used with ATF um if you're not familiar with ATF that you can't modify out of the box you copy them um you always copy them and that's that's the way I approach the the content packs either you just copy the whole thing copy what you need or go ahead and modify it um we we are working to make a better indexed experience but in the classic one we just kind of have to Brute Force through it um I I always like have my PDI to go look if there's any meaningful changes but ostensibly everybody's going to make a change to a data collector to set the user they're going to make a change to change the time you're going to have you know we only use three priorities not four priorities or or we have a different priority there's going to be something you change and a lot you're going to build so think of the content packs as starting points which you absolutely want to start with you don't want to start from scratch you want to avoid starting from scratch but but whether you take the content back use it inspiration and create everything which is might be right for you or you take content back and tweak it that's also great as well nobody has a pure out of the box instance and the content Packs work for Pure out of the box instances so everything needs to be modified um so you know I I just don't be afraid to modify the analytics up that the other data modifying modifying flows and business rules yeah that I wish they were giving a hard time but I do want you to think about it but just don't have any hesitation about changing the out of the box indicators and content backs and those things um okay so um Caro did did you did what did you need get answered because I see a couple thank yous but I'm not sure whether or not maybe okay good okay all right thank you all right so um so Victor brought up one I guess when we were right around town we were talking about the next experience he said he's going to the next experience in two weeks how do I find out which dashboards are not available well to be fair uh next experience is a user interface so your old dashboards will continue to work and exist um in this next experience the same way you would access them today uh leveraging the left hand navigation going to Performance analytics looking at your dashboards that's not going away uh for quite some time uh you will however if you you have to make the decision at some point if you're going to leverage um the next experience and start building your dashboard experience it's almost like you're going to have your foot on one side of each side of the fence for a short period of time while we um improve the next experience because there are things in next experience that you can't do in classic that are request achievement go ahead there's a lot of things you can do the next experience that you can't do in classic and and we have the Safe Harbor slide don't expect any enhancements in classic right we are putting um for a while now we have been fully invested into next experience and those data visualizations there's awesome ones um there's good stuff in Tokyo even better stuff perhaps coming out in Utah Vancouver whatever the next one is um and continuing on um the suggestion I have when you move into next experiences if we started talking about this before know your audience if your audience is using a dashboard as using a workspace then look at next experience and building a dashboard where you put in a the dashboard viewer into the workspace um and create a next experience dashboard but if they're not in in workspace when we're in Tokyo you don't want to force them to a workspace just so they can see your dashboard we'll probably stay in classic um if we're making a small tweak just on a classic dashboard stay classic they all work there's no changes to those things I mean it looks a little cleaner the user interface is better but you don't get all the functionality but go where your users go and know your audience so they're in a workspace next experience is where you need to be looking because I don't want them to jump out of the workspace to go back to the classic dashboards to help Victor hope so he hasn't responded back yet so um it was inspirational right we had another question that was around um however capacity and allocation and someone wondering and um I pushed a doc to them but I don't know that that's exactly what they were looking for so unless um any one of you three know more about doing anything around capacity allocation I kind of pushed them to ask the question inside of the community but I'll open it up to the three of you if any of you have anything that you know on that uh what was the specific um yeah the original question was we're trying to create report chart to show capacity of team to see if they're they're over or under allocated based on the agile model but can't seem to be able to get to that with basic reporting would we need to use PA and I looked in docs in the capacity planning page uh was something that I pushed to them but I don't think that that's exactly well I mean the answer there is that's really really complicated reporting um I wouldn't just go to PA there's the resource dashboard I'm assume that's the link you sent there but there is the capacity dashboard um from SPM that's what I'd be looking to use they they built some special tools for that but you get into really really weird calculations um in terms of available time about do my 40 hours or do I only have 36 hours in my week um you know if you all want to count vacations um holidays uh which support support worlds do I live in it gets really weird really quickly and the SPM team spends a lot of time focusing in on that um and so you don't want to create a basic report you want to use the stuff that's out there um I don't know the stat of as that's moving in the next experience and what changes they're making and how configurable it is it's not quite as configurable as building something from scratch but I I've worked in this area it's incredibly complicated um so unless you want to make a huge commitment to getting the logic right which you can do you want to write on the reports that are available out of the box it's it's I say reports not really a report it looks like a report but it's a customized UI with filters it's a very specialized reporting um and and I saw I saw Victor chimed in about the workspace stuff your your comments of I need to use a workspace absolutely absolutely don't I I don't think reporting can be the tip of the spear they need to buy into the team needs to buy into a workspace and build a report with them as you're going to the workspace add the new deck the dashboard with it it's a great tie the the dashboard the inline dashboard builder in Tokyo is really nice it's the things that we've been hearing about for years A lot of them are already there and more of them are coming but if they're not on a dashboard yet I just don't I don't think you can push them um you should look at it you should so that you can take advantage of all the stuff there's more carrots there but the workspace has got to drive them they need to buy into the workspace and being able to use playbooks and all the agents and stuff all the awesome stuff that comes to workspace the new visualizations are just one more we'll continue to help you in this journey and make it easier to do but um if they're not on workspace if you have nobody using workspaces yet they're always using one of the workspaces I wouldn't expect you to be releasing next experience dashboards broadly right great you know you got some time to prototype it work with it but yeah you know take this time take this time to learn about it and embrace it um don't don't try to push it down people's throats I know we're just at the top of the hour here but I I want to address artem's quick question here this is which approach of Distributing content is better so to have more widgets on one tab having several tabs in One dashboard or having several dashboards um the first thing I'd say is more widgets on one tab is generally not the way you want to go um so if there's ever a question of should I put another widget on this tab it's almost always no um but it could that's kind of based upon some of the principles Tara talked about earlier right the discussion of whether it should be a different dashboard or a different tab that is entirely based upon who is the stakeholder of that dashboard um and that's a good way to determine if you have two men if you try to do too much with One dashboard if any if there's any piece of content that is not relevant to one of your primary consumers of that dashboard but is relevant to others it shouldn't that that that first consumer should not be the target of that dashboard it should be on a new dashboard for that for that person's role um but if it is relevant then yeah other additional Tabs are the way to go if it's still relevant to the same role the same general I don't mean role as in like system rules I mean more like functional roles within your organization yeah so one of the things I didn't touch on was the tabs is the tabs should be follow the same process that we talked about uh all data should be relevant per tab so if you have to have more than one tab which um I think if you're going to have more than one tab no more than four uh really you know three three two or three to me is is probably too much but I'm a very minimal I want to know everything and I want to immediately and to the point but um if you do have to spread out over tabs then you want to make sure that every single tab is self-containing and and tells the same story so if you're switching between like if say you want a dashboard and you're you have two goals you know one is improving customer satisfaction and one's decreasing I.T spend and your cxo wants to see that then you can have two tabs that relate to that information and then a third tab with just supporting uh support kpis but that are informational and that would be okay but you also you definitely want to minimize how much your your consumer has to dig through to figure out what they need to do so keep everything related per tab um so that they know exactly um what they what they need to focus on okay great so we are a little bit over a couple minutes over so we'll go ahead and close this out real quick to respect everybody's time Dan and Tara as usual great content really appreciate the time and effort and all the questions or whatnot that you were able to put into it it's always great content it's going to be good to have this recorded on record so we can definitely Point people in the future so thank you both for um for what you've presented today really appreciate it um real quick yeah so just final you've probably seen these before but make sure that you're checking out our platform analytics Community page really great content there um and again I put this link in there earlier but it'll also be inside of the uh Community event and also on the YouTube here is where you can go and actually see future prior future and all that uh sessions that are out there um take advantage of our platform analytics Academy Pro tips you can get those on the community as well these are quick five minute videos where Dan Tara and I talk about uh different topics or whatnot and expect more of those to come in the new year um always make sure you're checking out now learning uh the easiest thing to do is to go there and just search for analytics and all and and lots of things will come back there are paid ones they're a free one free ones so make sure that you're going to checking those things out uh the PA Advanced is now on demand uh so if that's something that you wanted to take before you just couldn't get to it uh now it is on demand so uh make sure that you're checking that out there are many other Academy sessions that are part of our organization as a whole and they they're listed here so there's any other ones that you're looking for related to topic these topics you see on the screen here's the link for you to go to and those will also be inside of the community event and the YouTube link as well if you can maybe you can real quickly with your phone scan this and give us your give us some feedback on the community the community is new so we're looking for any Community that's your any feedback that you're willing to give us on that um on the community and this of course will be a part of the the slide deck will be converted to a PDF and it'll be attached to the community event as well so if you can't do it or if you haven't been able to grab been able to grab your phone real quickly you'll be able to do that via there so again any feedback that you can give us there we'd greatly appreciate it and with that thank you as usual and we will see everybody in two weeks to close out the year with our last session so we look forward to seeing you then thank you everybody who came