How to Manage Capacity in SmartSuite for Project Management

All right, we are getting started. Hopefully you can see and hear as we're just getting ready to go behind the scenes here. We'll be starting on the hour. Looks like we've got some connection puzzles on Facebook, but we'll be working those out and we'll be seeing y' all soon. While we are here, just say hello in the chat. Let me know if you're able to see and hear. Okay, we'll be starting on the hour. Sam, we'll be getting started on the hour with our SmartSuite for managing workload and capacity. If you are joining us here, get cozy, post something in the chat, get your SmartSuite account open and let us know if you can see and hear okay in the chat. We'll be starting here momentarily. All right, do not be shy. Let me know if you are joining us here. And hello and welcome back to one of our hopefully lovely live streams here on the channel. Whether you're joining us here on Facebook or YouTube or LinkedIn, please do drop a little something in the chat to let me know if it's coming through. Okay? If you don't do that, then I'm starting to think if I'm just talking to a camera in a quiet room. Today, what we're going to be doing is going through the build out of SmartSuite for capacity and project management. Now, this wouldn't be a process driven video if we didn't also talk about the process side of things. So just know we're going to do a little blend of both a tutorial and a little bit of theory today because I think it's going to be the most useful combo for you guys. I'm going to get our agenda opened up over here inside our SmartSuite account and as we dig in, I'd love to hear what you guys have top of mind. So if you're joining us here, is there any particular question that you would like to see answered around capacity management or project management in general in terms of your processes or inside of SmartSuite, let me know in the chat to the side and we will dig in. Our agenda for today as we get into this live stream is as follows. Using the lovely sub Items feature in SmartSuite to do this. Here we go. Hopefully I have successfully accomplished our first piece of welcome you, if not welcome, welcome, welcome. Now you're welcomed. Good. Let me go over what our plan is. The first thing we have to share is just a quick announcement around a suite deal thanks to our sponsor, SmartSuite. So if you are someone who is interested in clicking along with us today and you do not already have a SmartSuite account, this is your opportunity to fix that. SmartSuite not only has provided us with an affiliate link, which is a great way for you to support this channel at no cost to you, but they also have kind of given an extra bonus to these followers of this channel. And if you sign up using our affiliate link and contact SmartSuite, like, do it now, who knows how long this will last? You will save 10% on your SmartSuite purchase, which is really, really cool and a huge savings, particularly for those of you with larger teams. So keep that in mind. That's our first little reminder as we dig in here. We're going to be first covering how to build out our smartsuite structure. Our task manager, Manage Manager. Wow, that was a word. Our task management template. We're going to build out kind of our project management flow in SmartSuite. We're going to be building on what we covered in last week's live stream. Then we're going to take a quick theoretical aside and talk about what is capacity, right? Like what are we even talking about today and how do we conceptualize this from a process perspective? Then we're going to flip back to SmartSuite and figure out ways to not just manage our tasks, which is part of the capacity and project management puzzle, but also how can we forecast and report on that capacity using dashboards and charts in SmartSuite as we go through. If you need any additional support, if you have questions, utilize that live chat. If you're here with us live because, hey, newsflash, this is live because I want to hear from you. And if you are not joining us live and you're watching on the replay, drop a comment below or check out the description where you can find out more resources for how we can help with that. Let's dive in to our tutorial today and let's start by building out our SmartSuite structure using a task manager template in SmartSuite. So moving into this, I just want to get a quick check on the chat. Those of you guys who are here with us live, do you have your SmartSuite set up yet? Give me a yes or no in the chat. Let me know where you're at on that systemization journey. Are you just getting started? Are you beginning. Are you somewhere in there? Are you kind of just having your account set up, but not quite having your task management set up? How far along are you? I see some of the comments are coming in on the different platforms, but not showing up on my end here. But thankfully we've got lovely Carly behind the scenes who will help DJ that and bring it in so we can make sure we see it. Good to see LinkedIn, though. LinkedIn's in the house and coming in strong. Hey, David. All right. So cool. I see some of the Comments here on YouTube are coming in that, hey, Charlie manages capacity and is trying to manage that capacity when processes vary wildly. Sheena is yes, starting on her SmartSuite setup journey. Shane is thumbs up starting that piece. And good to know we've got the audio and sound coming through. Sweet. Perfect, Perfect. David is signing up for SmartSuite right now. Awesome. When you do, David, make sure you let them know we sent you via a support chat. They've got a little sweetheart deal for us, which is amazing and a huge support to our audience. Thank you guys, smartsuite for being so kind. All right, so depending on where you're at in your journey, you may or may not have your task set up, but what we're going to do today is assume you have a blank slate. You just finished our last tutorial last week. You have your account set up, your personal account set up and your workspace calibrated. Now we need to add our task management structure on a very basic level. To do that, what we're going to do is go back to the home of SmartSuite, and together we're just going to build out a basic task management system, one that you've probably heard me talk about on this channel that we've used in other platforms that we're going to Translate into the SmartSuite universe. Okay? To make this happen, we are going to use a SmartSuite template as our jumping off point. As with all the templates we talk about on this channel, templates are a jumping off point. SmartSuite's templates are better than just about every tool in the industry in terms of how real world their templates are. But even still, a template is not a replacement for you adjusting things to match your workflow. So as we go in today, we're going to use this as our beginning point, but not our ending. From the Add a new solution button inside your SmartSuite account, which hopefully, like David, you have used and set up using our affiliate link, we're going to start with the template called Task Manager. Task Manager still with me, hopefully. So once we see this template, we can preview it from the preview available view here. But really we want to use this to incorporate this into our SmartSuite account to start giving us this space with which to start organizing our to DOS our tasks and our projects. The default setup of this particular template is what I'm going to show you here. It is a solution called Task Manager. Yours probably will not have a one on it because you might not have a million copies of this like I do. You have several views here that help you organize your tasks by different criteria based on how you like to see things. And you have just one app, meaning just one database of information that you're pulling from called tasks. And from the get go, this is actually a pretty nice beginning, right? If you're just looking to get basic tasks organized, this is going to get the job done and is a good, let's just say like trello to do list alternative at just this basic level from the get go. But for most of us here, we want to go a bit further and just having our tasks is kind of a little too basic for our preferences. So what can we do? Well, the first thing I want to do is do the baseline template modifications that we do for every template we load in Smart SmartSuite. Starting at the top, we want to review the core information. We always want to check. We want to check the solution name. Does this make sense? For me personally, I follow a philosophy that we teach here at ProcessDriven called Capacity Defense. And that Capacity Defense system is implemented through what I'm about to show you here. So I'm going to rename this area Capacity Defense. Below that we have solution color and icon, which again, we want to change to suit our preferences and how we like to view things. Below that, we have our solution guide. Now, by default, this solution guide is going to tell you how to set up the template. But because we are process driven oriented people here, we probably want to rework this particular template guide to match our own workflows. So just from the get go, I'm going to suggest we edit this guide and actually delete it and then replace it with our own best practices as we fill this baby out. So just saving this year, we'll leave it there. Below that we have permissions in every tool. When we are creating something new, a new structure for our team, we want to make sure we are quarantining. I'm loath to use that word, but you know what I mean, separating the stuff that's in construction from the stuff that's in production. We had a question come up in the weekly review inside the ProcessDriven membership. Just this past week about this topic of you know, I've installed all these templates into my account but now they're everywhere and I can't find my actual work. We want to avoid that. So with this particular template we want to practice what we preach and change the solution permissions just for now to be limited to the people who are our creators, the people who should see the messy behind the scenes stuff. Here's where we could adjust that. Restricting things by only teams, certain members or advanced permissions. Sorry, all members or certain permissions. So adjust your permissions here to make sure we're not distracting other team members in terms of automations, whether integrated into the tool or third party, we can pretty much hold off on for now and skip these remaining sections. However, once we are done we are going to want to delete this demo data, but we can pass on that for now. Beyond Capacity Defense, the overall solution settings, we want to look at the app. The app is our database by default. With SmartSuite we have just the one database here, but we know we can add so many more to have different structures, different apps all tucked inside. I know many of you here might be familiar with other platforms. I know we've talked about ClickUp in the past and one of the things that we had to do in ClickUp and in other tools is we always had to create different lists or in Trello different boards, or in Asana, different projects or teams in order to organize things like Capacity Defense. Something unique about how SmartSuite works is that because the views are so powerful, we can actually get away with fewer databases that collect more of our information with fewer silos. And so despite the fact that we are going to be making a pretty complex and scalable Capacity defense system, I'm actually suggesting that for today guys, we do not expand beyond this tasks area. We are going to track everything we have to do related to our work and tasks in this one app. Why we're doing that is to give us a basic starting off point. So I'm going to call this Action Tasks for now. That's just a terminology I like to use. You can rename this to whatever you want. And because I'm me, I'm also going to add a little emoji in here because I think that is a nice touch. I guess just to get ahead of it. We usually get a question at this point saying what how did you add emojis, Windows key and period command shift space. If you're Mac, you can use the Emoji toolbar that is Inside your computer. Once we have this going, we are ready to get down to the views level. Now, what These views in SmartSuite allow us to do is view our information in different ways. We've got this one database for all of our action tasks. How do we want to see them? Do we want to see them by due date in an overall year view? Do we want to see them in more of a traditional spreadsheet view, or will we prefer to see it in a Kanban? And SmartSuite out of the gate gives you a lot of options here, so you can quickly see what you want to see without having to do a lot of manual work. But in practice, it's going to be helpful for us to pick one or two that matches our way of working and eliminate some of the rest. So we're not having that overwhelm of oh my gosh, there are so many views to click on. So how do we decide what kind of views we need? Well, determining our structure and our way of seeing data is going to be based on what our data actually is. So we're going to go one layer deeper first and review what our records actually contain inside of SmartSuite. So what we have here is our task information up at the top. So for anyone who doesn't know what we're looking at right now is a record. So this is smartsuite language for kind of like the row in the spreadsheet or the task or the item or the page, depending on what your tool you're coming from. When we open this baby up, we can see all the information stored inside this unit of stuff inside our database. And the fields that we have here are entirely customizable. This is a standout feature of why SmartSuite is considered a little bit more on the database side. Every field here we could require, we could delete, we could auto generate for some of them, we could have them auto applied. And we want to adjust these to match the way that we want to view our task management. So what is that? The first field we have here is our task name. And because we are dealing with things and they are going to be tasks, I'm actually okay with that here, but I'm going to clarify this to be the task name or task title. Just so that way it's a little bit clearer when I'm looking at it. As we go through and build out this capacity defense system, we are going to start defining different Grady grades, I guess, of tasks. And so just know that this is going to become a little bit More nuanced as we go. For now, we're going to keep this as a manual input. We're going to require unique entry and strangely we're not going to require an entry in this field. That is something that's just a personal preference. I find that I can sometimes think of maybe notes before I think of the task name. And so I like to keep things a bit more flexible. So I'm going to leave that. So when we move on past the task title here, we have the status field. Now, you guys all know what a status field is, right? It's just different conditions or states that something can be in. If we modify this field though, I'd like us to adjust this to be a little bit more process oriented. The default statuses are quite structured, but I kind of want to take it a notch further. Okay. When it comes to tasks and the things that we do, there really are three different stages to them. There's thinking of the idea, there is realizing we need to do the idea, and then there's doing the idea or task. At that point, the name kind of changes, but it's the same thing. It's the art of getting things done. When it comes to most task management tools, we are forced to think in terms of tasks. Everything's a task, everything's equal, it's all in there. But when we're trying to think about capacity, defense, defending our ability and our oomph and our power and our energy, it can be more meaningful to think about tasks as a spectrum. There are tasks that we could do, there are tasks that we should do, and there are tasks that we need to do. And so I want our processes here, our overall statuses, to reflect that kind of layers of gradation, the separation between potential tasks and tasks. We're committing to current language uses, backlog and process and so on. I'm going to just simplify these a little bit based on my preferences and I'd suggest that you do the same for me. I'm going to do this as new. We'll just do this as idea Shortlist to do in progress, complete. I'm also going to go ahead and do a blocked oops. Okay, so what these are, are, I mean, the same number of statuses, but each of these has a different meaning. Idea is where we're going to put tasks that are something we could do. We've got no commitment to do them, but there's something that is possible. Right? Idea. A shortlist idea is an idea that not only could we do it, but it's seems like a pretty good idea. If we have time, we should do that. Normally people will clump two of these things together in what's called a backlog. But because backlogs can be hard to sift through and it tends to carry some connotations from the tech industry that not everyone relates to, I prefer kind of a more nuanced idea. So this could be shortlist idea, potential task, whatever you want to call this, make sure it works, works for your brain. Below, potential task we have to do. I think we all know what that means and we want to pick a color that represents, hey, this is something that is ready for us. And I'm going to choose gray. Next step we've got in progress. This is something we're working on. I'm going to choose purple. Blocked means something that we can't move forward on for some reason. I'm going to choose a pinkish color. And then we have complete. These are going to be our six different stages of moving something from something we could potentially do to something we are going to do to something that we are doing and then is eventually done. Notice the colors I have in place here too. I like to keep all of my kind of planning stuff in one color palette and all of my active work in a more active color palette. So what I mean by passive is things that involve planning, organizing, prioritizing. I like to keep them as a boring color. You notice how these are all gray? Yeah. Because what this allows us to do is to say, hey, this planning time, don't become addicted to it. Layla and others out there who might be Procrusta planners, this is just a reminder to work through the planning section as one chunk and then move on to the active work. What's the active work, Layla? Well, the active work, these three ones down here, is where things come to life. This is where you're actually doing what you said you were going to do. It's very important to me, at least in the clients I've worked with, to see a clear separation between the planning and the doing. If we're constantly going back and forth between plan land and do land, all of a sudden we end up overwhelmed, distracted, with a lot of half finished projects. So having the color distinction is helpful to me to help keep this going and is just a little pro tip I thought I'd sprinkle in there. Moving through here, you'll notice some other kind of elements coming in from the smartsuite side of things of the mark as complete button. This is where we can choose what's considered done in the SmartSuite universe because again, everything's customizable. I'm going to keep it with complete. I am going to require an entry in this field, meaning it cannot be blank. Just carrying over from that kind of basic task management angle. And I'm going to set a default value as idea. So that way if I don't fill this out for a particular task, in this case, it's always going to default to that idea value. Finally, I might want to take a moment here to fill in some help text and explain what each of those values means. I can do that here and I can also add these details into particular fields if that's helpful. Okay, so quick check on the chat here. I know I can't see all of it, so I'm going to be relying on a few tabs switching here on my end. Is this making sense? Is this where we're going? Perfect. Looks like we are making sense so far. All right, got it. So now we are picking up where we left off. We've got this task template structured. We've removed the pieces we do not need. Now it's time to start focusing in on how we can start measuring this particular template and creating more of a capacity defense flow. For that, we need to have a shared definition of what capacity defense is all about. And for that, I'm going to take us back in to our lovely little whiteboard that you might remember from last week. When it comes to managing capacity in SmartSuite, we need to have a measure of what capacity actually is. So I like to think of capacity as oomph. And oomph is a word that is probably not the clinical definition, but oomph is just how much energy, power, brain power, time, resources you have to accomplish anything. And if capacity is how much oomph we can handle, we need to have a more meaningful way to measure what that oomph is. So if I just scroll down here, I want to highlight some of the common ways of measuring out what capacity looks like. There's three common ones, there's many more and more nuanced ones. But here's the main three points. Time and number of tasks. Okay, I'm going to talk through each of these briefly and then we're going to apply these into our SmartSuite template so we can start building out some kind of overviews and forecasts. Points is referring to utilizing kind of a sprint point T shirt size estimation method of estimating how much effort a given task will take based on relative size. So let's say we've got five things we need to do. Human beings are generally not very good at estimating precise. Just looking at number four and seeing how big that is, how long that'll take, for some reason our brains just aren't very good at that. So the idea of points is to make things not so much absolute where you're looking at number four and thinking how long will that take me? But instead to make things relative. Human beings are bad at figuring out how long number four takes, but are thought to be more accurate and more capable of doing relative sizing. Basically saying, hey, number four is bigger or smaller than number five and number two and kind of putting everything into a prioritized order and, and distributing out these things called points based on where people fall in that spectrum. You'll hear this a lot of times in kind of like the Sprint agile methodology world where you'll see Sprint points being used. But just know you do not have to practice pure agile in order to practice this. In some elements, points are often used in things like productized services. I know many agencies operate on a point based deliverable system. You can adopt this to your flow. The benefits of points are that they can be more accurate in theory if they're executed properly, which is rare, but they're challenging. And because they're challenging to implement correctly, that may hurt the overall accuracy. The other common unit of capacity is by number of things, right? So if we were working in our capacity management system, that could be the number of tasks that are complete, the number of videos that are filmed, the number of widgets that are whatevered, the number of paints that you have canned. I don't know, I'm stretching now. That's our other measure of capacity. That's one of the easiest ways to measure capacity. And when we're thinking about factory line worker kind of mentality, it seems to be the easiest to do. The problem is most of the time when we're actually working in our businesses as small teams, people don't have such clear jobs. You know, it's not like we can just say hey, Carly is productive based on how many banners she has appear inside the live stream. If so, I mean, she could just go ahead, flip through all of them right now. But I don't think that is really, oh, there we go, revenge. But I don't think that's actually a measure of productivity. And because people do so many different things and a lot of things are qualitative instead of quantitative, the number of tasks or Number of things can sometimes fall short of actually providing a meaningful metric of output or how much someone can handle. So that brings us to the middle of the road, which is time, everyone's loved and hated. Favorite in the capacity management space, which is using the unit of time. This looks like time estimates and time tracking. Again, everyone's favorite subject. The reason time can work really well is because it's fairly standardized. Whether you are sealing paint cans or you are having banners show up on a video or you're working on a YouTube video, time is something we all have in common. It's also relatively easy to measure and easy to quantify regardless of what you're doing. Plus, because time is time, and you know, I think we've pretty much agreed on what time is by this point in human development. There's not as much challenge when it comes to implementing it as there is with things like program points. So why am I talking about units of capacity? What the heck does this have to do with anything? Well, if we want to figure out where we are on the metaphoric ruler that is our capacity management, if we want to know if we are fully at capacity, meaning we are doing all that we can, we are tapped out, we are getting to the zero in our gas tank every day, or whether we are at the bottom of that metaphoric ruler, I realize, is parallel. Whatever. Maybe we aren't working hard enough. Maybe we don't have enough work to do to do any of that. We need to have a shared unit. This unit needs to be one that we can measure for both how much we do and how much we can do. And we need the same unit on both sides of the equation in order to do the math. What math, you say? This is like a weird conversation with myself. Yes, because the math is really what we're talking about when it's capacity management. Capacity available versus capacity spent or used determines our excess capacity. And if I can select the right one, we got this going. Excess capacity right here. So if we just add a little divider line here inside of our lovely whiteboard for today. Capacity available minus how much we've used determines our excess capacity, which tells us how much more we can take on. What could we do? Can we do that new product? Can we offer that new service? Can we redesign our website this week? Week. When we get this math wrong and we don't have enough available, we end up in a deficit. Here we have negative capacity, negative 100. That's where burnout happens, where we feel like we're panicked, where we can't deliver on our client promises. When we end up with too much excess capacity, that's when we get into twiddle our thumbs land. We get into having way too many costs versus the revenue that's coming in and so on. So capacity management is about making sure that the cost you have available and how much you're using feels good. We're not running the tank fully empty, but we're also not underutilizing resources. So given that for today, we are going to move forward with the kind of traditional choice of time tracked, slash estimated and we're going to work that into our capacity system inside of SmartSuite in order to make sure we can forecast this more generally. So going back inside our task structure, the records we have here, whatever pieces are in place, we need to add two pieces of information capacity. Right? We need something to track capacity estimated and something to track capacity used. Now, if we're talking about time, let's just go into the fields available inside of SmartSuite here, add a new field, search for the word time. And what do we have come up? First one that we want to pay attention to here is the time tracking log. This is going to become our measure of the capacity used again, if time is going to be our measure when we add this field in, I'm going to change this to be called time tracked and give it a color that works for my brain. And this is going to be our way for tracking how many resources this particular item is using. Going to add that field here. Now that's handled one side of the equation right? We've added this field. We can now go in here and easily have our timer start ticking and track how much time we're spending, as in this case, myself, with a little note saying, hi Mom. We can also have a duration tracked here by using again the time tracking log. Add something like four hours were tracked today because I was prepping for live. Add that time and we can also add a time range which is where we click the plus, go up to range and say what times things were happening and on which day. Now, while all of that is great, it's only one side of the equation. What do we need to do next? We need to figure out how much time is budgeted or available for a given task. This is only going to be necessary if you want to track capacity on a task by task basis and roll it up if you're more concerned about, hey, my team can work 40 hours. Do they have 40 hours of work? You do not need to Include this additional step. Okay, now say that one more time. What we're going to add here is a new field called duration that we are going to call time estimated. Adding this in here, we're going to just go with minutes and hours because we're not that ocd, right? We are going to choose the compact view because I just think it looks a little nicer and we are going to add that field. However, to repeat what I said before, if you are somebody, Sorry, that was a little small to see. Just to go back in there just so you can see the settings, this is what it looks like. But if you are someone that does not need to have capacity tracked on a per item, a per task, a per record basis, you can choose to skip the second field. You can just track time and then sum up your people's availability in other methods. So moving on here and no worries, David, enjoy your meeting. Thanks for joining us here. Moving on here. Now we have the requirements. We need to start reporting on these and this is what's going to take us into our next portion of the agenda. Now I want to do a quick check once again on the chat to see how things are going. Are you guys still with me? Is this making sense? Is this too much review? I know we have a little overlap from last week, but now we're building onto it and hopefully the steps are building and you're not feeling like you're being thrown to the wolves. If you are, well, sorry. And we'll try to correct that here. Moving on, going back to our agenda here, we've got what is capacity? I think we've successfully covered that and now we're going to talk about forecasting. Quick check on the chat. I'm sorry, I got to toggle between tabs to see all of you here. Sheena says, yes, it makes sense. Rahul says, hey, no, still with us. Makes sense. Okay, great. Carly, I'm going to ask that you get some of the questions in in the chat and just put them in the banner so we can pull them up on the screen for later on. Fabulous. Sweet. So Carly says, or Carly says, Rick says. Might be covering this today, but would be cool to look at how to view capacity across solutions. Okay, well that's gonna be a perfect segue. We planned this, you and I. Let's talk about how to forecast capacity in one solution and then let's broaden this out, Rick, because it's a little funny right now in full transparency. So what we're going to do is head back into our Solution over in this land. We're going to locate our our overall zone where we've got time estimated, time tracked. Click save. We're going to finish the cleanup we may or may not have done already, which would be deleting the views we do not need and making sure that everything matches our expectations by removing fields. And then ultimately what we're going to do is delete the demo data. Case closed. Moving on now, fast forward. Let's just imagine we did all that. I have this other view ready here for you to show you some of the ways we can summarize and report on this information. The way we're going to do this is to make sure that our fields have the things we need again, like the duration and time estimated. But now we want to add some separate views that track what that information is telling us. So by this point in time, you've probably deleted all of the views you have here that do not suit your style. So maybe I only want to have Kanban views. So all of these board views, I'm just going to kick them out. But we want to add new views for the summation of all these records. To do that, we're going to click on the plus button right here and we are going to choose a chart view. Now, it's a little confusing, or at least it was confusing to me not to like smart people, but for myself and maybe some of you, it's a little confusing at first. When you're in SmartSuite figuring out whether you need a chart or a dashboard view for what we're going to do today, for various reasons, I'm actually suggesting that we start everything we build with a chart view. A chart view is smartsuite's chart builder where you can create a name, make it private or not, and start to create tables and reports and so on on the data that you've tracked elsewhere inside of SmartSuite. So what we want to do is start to create charts that summarize the values that we have tracked on both sides of the equation. Time estimated and time tracked. Luckily, I've started some of those here for us so we can save you a bit of time. The first one we're going to look at is one we're going to call time estimated distribution. Donut. What this is is a donut chart that shows us how much work is distributed based on the actual who's assigned to it. So let's just go through, make sure everything's here to remove that little piece. Let's do all time there we go. It's weird with demo data that sometimes it blanks out. So let's go through how to build this out inside your account. To create this view, what you're going to do is go into your Views area, click plus and add a chart just like shown. First setting you're going to want to adjust is our chart type. In this case, we're going to choose a donut. If you prefer a pie over donut, you know, whatever more to you, I'm going to go team Donut on this one. Below the donut chart preference, which is just telling you what visual look you're aiming for. We want to determine the values. Basically, what are the things that we are counting up to make up the full donut or full pie. In this case, we want to look at time estimated. So that might be your field called time estimated. In this case, duration estimated. To find the name of this field, you can always head back into the records that we've created elsewhere. Click on one and locate the name of your fields here. Okay, so time tracking, log duration estimated. Those are the two I'm going to be using for you. It'll be whatever your fields are called. Heading back into our lovely donut once we have our values in here to show us that that's what we're summing up. We want to make sure we have some selected because we want to get a picture of the total allocated resources as of right now. And so we want to sum these up, not anything else below that we need to group. And this is where we're going to basically say, how do we determine what slices of the pie there are? Do we want to break it up by maybe the status? Maybe we want to break it up by whether there's a tag or not, whether it's completed or not, or so on. But for us, I think what's going to be more meaningful is seeing how workload is distributed by person in a moment in time. So. So just select assign to right here. Below that we have the option to set what the total of the chart is, in this case its duration. Not really serving a huge purpose for that one. Finally, we have the option to add a dynamic filter. Now, if I can hold my mouse in one position. There we go. You can see that a dynamic filter is basically this guy over here. It determines when you're in the view mode of the chart, like getting rid of settings, what toggles appear over here to quickly allow you to sort and segment the settings data. So if I change this to six months, you See how the chart kind of changes because looking at things based on that time window, there's different data than if I look at all time work distribution. So that's kind of what we've got going on. This is being based on the due date of the task. There are multiple ways we could go about doing this. Maybe we have a field for something else. Like we could have this based on the person, the priority, the whatever to see maybe how high priority tasks are being distributed amongst the team. Not that interesting, but I think for this case we're going to go ahead with due dates so we can filter based on different windows of time. In this case, what this is showing us is that that Melissa person is doing way too much of the work, at least in our projections now. And we can also, I should say you can see how the charts in SmartSuite are interactive. So we could choose to remove certain values here if we want to just focus in that is our time estimate distribution. What that's telling us is how evenly our projected workload is distributed. This is going to be more meaningful for smaller teams moving on projected workload by quarter. Let's say you're in a situation where you want to use this capacity planning stuff and you don't want to just focus on okay, in this moment, is Melissa doing more or is Carly doing more? Maybe that's like you're like, I got a project manager for that. I don't need to worry about it. Maybe you're thinking about a layer up the capacity tree and you're thinking about okay, in terms of my company as a whole, can my agency take on one new client in February or should I wait to onboard them in March? Do we have capacity as an overall team based on what we've estimated to take on this new client and deliver stellar service for people who are looking for that next level up in capacity management. This next chart is for you. I should be pointing this way. This next chart is for you. Not a very good Vanna White. So in here we've got another chart view. By now you know the drill. Our chart views are allowing us to sum up information. We're going to create a chart and we are choosing the line chart. Back to the original question earlier on in the day asking about multi solution charts. Right now, just know that these are reporting on one particular solution. So this chart is summarizing this data right in the One app just for clarity. Okay. So once we have our line chart, our values for this one is once again duration estimated. This is basically saying hey, how long we expect this to take is going to determine how much volume we have. I should say, in order for this chart to be something you can trust, you need to make sure you are using duration estimates consistently. Can't tell you how many times. Particularly agencies, we've worked with them and they're just so excited to get their capacity forecasted and you know, they're like, ah, I just can't wait to know exactly what's going to be coming up next. But then they don't execute, they don't take the time, which I get it, it's painful, but they don't take the time to do this stuff of making sure that all of their fields are filled in when they're creating their new templates. They're not filling in these values or they're not using the default fields here to set a default value, such as always defaulting to four hours. And so so many of their tasks are blank and missing that unit of capacity that it's no longer helpful and it's not informative and it can't be trusted. For all of this stuff I'm talking about here, forecasting, imagined capacity, and really all data in general, your forecasting is only going to be as accurate as your data input at the onset. So fill in the data that you want to report on, particularly if it's important to you. So make sure that stuff's filled in. All right, moving back into what we were actually talking about. Sorry for the moving there. We were talking about this one, which I wrote, bar chart, but it's actually a line chart. No problem, I promise. I know what charts are moving on. Our values here is duration estimated. We are grouping by due date. So here's a little bit of a smart sweet ism just for all of you who may notice this group by in SmartSuite land and it comes to these charts, view is referring to the horizontal axis. So I'm choosing again, due date as our benchmark because I want to know when tasks need to be done and how long they're going to take. And that's determining where they show up. Something's not due until Q4. I don't want it to be showing up in the Q2 numbers. This is something that's kind of neat about SmartSuite is that we can adjust this either by day, by month, by week, by year and so on. Clearly this demo account is pretty ambitious with their due dates, but this is a way that we can kind of zoom in at various timescales to see this Information either in a line chart or a bar chart or any other kind of view. From here. Something that would be a nice addition for say, people who either don't want to use time estimates with full accuracy or have kind of like a best practice in mind, we would take one additional step and say per quarter, add a benchmark line. What's a benchmark line? Well, it's the thing that my face is pretty much blocking, but besides that, it's also kind of the line we can set for ourselves as our goal value. So goal workload or target workload? Oops, I promise I can spell target it. There we go. This could be our opportunity to specify where we want our capacity to be. What I like about this is it makes the capacity planning thing way more visual. I wish I could reference the quote, but there's a great line talking about team motivation that basically said your team needs to know if they're winning or losing very easily. Like red, yellow, green. Works for a reason, people. And when it comes to these kinds of charts around capacity, how nice would it be for your project manager to see? Ah, okay, we are definitely above capacity here by having that target clearly defined for a period of time. And that's kind of what we're getting at with this benchmark view. Plus you can also add multiple benchmarks. So you could have a high, a medium, a low and so on. That way you know in what criteria you should start worrying. So maybe when we are in the 15 it's a little low, when we're at 60 it's good. And when we're at oops, wrong number, this is also bad. And when we're at 25, which I can type, we are good. This is also good for like, good, better, best kind of situations. Gives you that range of acceptability. This is all using the benchmarking tool that you could not see because my big old head was in the way. But there you go. Just using these benchmarks and assigning colors to them. Below that we have another option for a dynamic filter. If we want to narrow things down by maybe a tag. So if we tag by context or by department, maybe we want to just see, oh, you know, how ahead is the alpha project, how ahead is the guru project. Whatever fields you have added to your task management system, you could review those here. One thing I haven't said throughout this time, but I should also highlight here, is up at the very top of the screen you'll notice that there are filters, in this case, most of the charts, because this is a demo Data area, I have it forced to only look at things that are on or after 2020 because there's old data in here. However, you could also use these kinds of filters to narrow your chart down to specific teams, specific avenues. So for example, if we built out both our ideas, our potential tasks, and our tasks inside the same area, we may not care if our ideas and the time estimated on those ideas are really high. One month. Because who cares, right? So maybe we would want to have something where it says we don't want to include ones that is where there is no due date, so we only want to include them when they're not empty. Or maybe we want to add a filter that says when the status is in in process, that's the only time we care about it. Whatever the situation is, you can narrow this down further using the same filters that you know and love from other views inside a space. SmartSuite if you're not familiar with how filters work or what the options are, just know that they're just different ways to narrow or filter down your viewable data that's informing the particular view that doesn't damage the underlying information. So even if I filter all this stuff down just like it shows here, despite the fact that it doesn't quite make sense, that's not going to affect my other views on this particular field. It's not altering the data, it's just filtering how we see things in a particular moment and saving it to that particular view. Good. To move on to the next example. Just checking in on you guys. It's like the tab wars here in the chat. Makes sense. Waiting on a smartsuite course. Yeah, we hear you. Okay, cool, cool, cool. Keep coming. Charlie. Michael asks. Or Charlie and Michael. Charlie Michael. It's so weird that we have to retype these. How do I manage capacity when my processes vary wildly between customers? One customer step made me may take 10 minutes. The same step with another customer may take an hour. Oh, I love this. So Charlie, what I would say is two options. One, narrow your customer avatar. That's just an option. Unpopular opinion here. But when we see wildly different experiences across the customer base, it's generally because your customer base is really broad. And if you prefer one reality versus the other, it can be sometimes nice to cater your service to that avatar. So cater it to the quick decision makers or cater it to the people who prefer a high touch experience. That way your default becomes what you want and you price and offer your service based on the service you want to deliver. Unpopular opinion but just Putting that out there. The second option is to have a more active project management step. So what I showed you in here really encourages you to add time estimates and these are things in my view that should be added into your kind of templates or your default master structures when you're adding in a new client. We have a video that we will link up above but we can't do it now because it's live. So we'll just put it in the description afterwards where we talk about the different ways to set up projects inside of SmartSuite. Whether you're a VA, a contractor, some other example. There's three different examples and depending on where in the hierarchy you're building out your client projects, you'll template things in different ways. But for you Charlie, what I would say is default all of your values in your template or your master copy or your default values or your automations to the normal and then in your actual projects. Let's just go in here, let's say let's go back to one of these guys that we had up at the top because I can probably, oh gosh, there were so many different examples of that. Here we go. This is, this is one of the examples from that video. Let's say this is your situation and you've got one overall solution per project. You might want to take the time to have a task or a step in your process for each element. So maybe the fire pit, maybe the outdoor kitchen to have a sub activity for actually reviewing the duration. This would be on a per item basis if you're this far up the hierarchy or maybe for the overall project if you're lowering the hierarchy. So this would be review time, duration, time estimate, estimate for the project. And this would be a task that you would assign to the project manager. So that case going to be this Layla person and have it do when the project kicks off. Your project manager should know your customer or your account manager should know your customer and be able to kind of assess that on a as needed basis. If this is something that becomes quite time consuming. You can also streamline this a bit further if you really want to go intense by having three different versions of your service template. One for the high touch client, one for the easy client and one for the average client. Again you start to make your life harder by having multiple avatars. But that's one way to streamline this piece or automate on it. But that's a little bit more intense. Any other questions coming in on the chat? Perfect E asks, I'd like To hear more about how you handle forecasting capacity weeks or months ahead if you're not entering time estimates on your tasks. Crying no. So if we go into SmartSuite here and we're back into our overall task manager view, if we want to forecast capacity, meaning forecast how much we can do and we do not want to track things on a per task basis, we need to revisit that conversation of how we measure capacity. So my suggestion here is to pick one measure and use it for both capacity available and capacity used. But if we don't want to do it on a per record or per task or per project basis, the alternative way to do this to handle in this case it sounds like the availability think yeah, availability would be to just look at the hours people have available to them. So how would that look? Let's go back to our other example here. Okay. Task manager. Everyone else find it kind of strange that the search is over there. I always go to the wrong spot. I think I'm just like not with it yet. So let's go back into this area. If we wanted to follow ease situation here and not track time duration on the tasks itself. So maybe we just have something like time log but we do not want to take the time to put the duration on each one when we create our dashboards for that particular experience. So say we've got four hours tracked here. The way we would go about tracking how full we are and have the kind of the. The top end of that equation will be creating a chart where we use the benchmark system. So let's just say capacity, utilization, whatever you want to call it buzzwords here. Here we could have a column chart probably seems the easiest choice. We will do the logged time field so how much time people have actually tracked and then we will use a benchmark to say the available capacity. So let's just say 40 capacity. I could work 40 hours a week. So far this week I have worked four. I've got excess capacity. Say I've only got three hours a week, then I'm over my capacity. We would set that maximum based on people's work schedules that are fixed. Just averaging it out over the entire year and not worry about it on a per task basis. Um, if you do it that way you may. Since you can't forecast because time track doesn't happen in the future until the future is here, you may want to change your unit of measurement for the this piece to not be time either. Maybe do something like number of tasks instead. So in that case we'd go back to this view. When we have the values, we would change this to be just do. I guess we'll do tasks and we'll do the count. Actually, tasks are the name of the subtask in this particular one. We'll just do count here. So here we go. One task assigned to Layla. My capacity is on gen, on average, 30 tasks a week. Looking at my available time and how many tasks I've completed in the past. And that's how I can benchmark it without having to track things on a per task basis. Okay, I think we're gonna move on here. If there's any other questions, please just ask them in the chat. I love the rabbit holes. We're going to move on to our next chart. Our next chart here is one that is time estimated versus tracked. So that's two of these actually are going to be in the same ballpark. This chart is for those of you who maybe you're new to forecasting or maybe you just don't trust yourself, which who really should. And you want to figure out ways to see how accurate your time estimates are. Are again, can't tell you how many times. We'll have folks be like, I am so into time tracking. And then we'll ask, so what do you do with the time tracking? And they say, oh, it's tracked, that's great. But if you're not tracking your time or if you're not reviewing your time tracked and you're not billing on it or anything like that, that seems kind of like a waste of data. You're storing all that information but not utilizing it. Likewise, if you're starting to do time estimates and you're so excited about being able to forecast your capacity like in those other charts, but you're never taking the time to revisit how accurate your time tracking and time estimating is, well then you're just going to end up with kind of just an exercise in pointlessness. So these two charts are about making sure that our time estimates and our time tracked are fairly consistent. The way we're going to do this is a column chart and this is where we're going to be having columns going this way for each period of time. The values in this case the two different bars that we've got doing their thing is the time tracking, meaning how much time is tracked, summed up and the time estimated. So this is going to be the sum of how much time is expected to be utilized. You can see here we've got time tracking. Oop, there we go and time estimated, the group by field once again is just the x axis inside of SmartSuite. And in this case we're going again, go by the due dates. You can group by anything you want. So, for example, if you find that certain people tend to over. If you find that certain people over or underestimate, regularly, grouping by assigned to might be interesting as well. So in this case, we can see that time tracked and time estimated is generally pretty on par for this Layla person. But Melissa, oh my gosh, I don't know how, but she's getting tasks done so much faster than our estimate. Why is that? That's what that group by can tell us. But we're going to keep it at due date and currently it's just by day. But we're going to change that to quarter. And notice that there are some gaps in our quarter because this is a data set that is incomplete. So Q4, 20, 21 is not here because there's nothing there in our data set. For yours, this will be a little bit more informative, but adjust that to whatever timescale you want and look at your comparable consistency here. We also have over on the side, another dynamic filter where we can narrow down just how it has worked for each person based on the timescale we have. So let's just go ahead and for the sake of things, make it by week and look at Melissa by week. In the two weeks that we have had tasks assigned to her in this case, she's beat her due dates. But if we flip it to that other person, Layla, yikes, she's all over the place. Sometimes she's way over, sometimes she's under. Layla might have a little bit of some difficulty with estimating her workload. Okay, next up is a scatter plot kind of showing us the same data but in a different way. If we have our time tracking and our time estimates being super on par with each other, we're almost always at the same point where we estimate an hour, we spend an hour as a copy company with a scatter plot, we should be able to see that correlation. Basically, we should see a line this way, there we go this way up the chart saying when one happens on the estimate, one happens on the utilization or the time tracked. However, when we scatter plot out this particular workflow, we see that there's not really a lot of predictability on this small sample size. And this scatter plot would be another way for more of the Big Picture Manager to see how well people are reviewing and analyzing their work. So if I track everyone's data here, we do see a roughly straight line with just the three points of data. But if you had hundreds of tasks in here, hundreds of people tracking them, you could narrow this down and say, who has the straightest line, the straightest view when it comes to the correlation between time they've tracked and time they've estimated. For all of these kind of time estimated, time tracked, review style tasks, it would probably be a best practice to make sure that you're comparing tasks that are all in the same stage at the same time. So as it stands right here in this chart, we're just kind of showing everything because this is a demo area and, you know, it's just showing you how this works. But if we were to use this to make meaningful observations about our company, it might be helpful to make sure that we are only looking at things that are finished so they're not still in progress. And we also want to look at things that maybe have been done for a little while. Because I don't know about you, but I find that sometimes there are tasks that were technically finished yesterday, but then something comes up and so I end up doing a little bit of work on them today, even though they're technically closed. So I might do something like the due date is, let's say in the last 45 days. So we've got a rolling average, or maybe we say it is not today or is not yesterday, different things like that. So I hope this is kind of a helpful way to talk about kind of reviewing your predictions of your time estimate and time tracked versus your actual. As we look at these, we've got a bunch of different charts available to us here that we can then combine into a dashboard in SmartSuite if we want to get a more big picture perspective. So the last view I just want to show you guys here is a dashboard view. A dashboard view is one you can create in SmartSuite by clicking Dashboard here. When you create from scratch, you give it a name just like always, and you get this beautiful blank slate where you can add new widgets to serve the purposes that you need to have in your particular workflows. We're going to be going over widgets in a lot more detail in the sales reporting I want to say is the name of it. But the sales reporting live stream that's happening later this month, we can probably grab the link and put it somewhere in the chat. If not, you'll find it. We'll be, we'll be shouting from the rooftops about it, but we'll be going through more of these widgets in detail for that sales CRM example. But for now I've mocked up a quick workload dashboard in case you would like to implement something like this inside your account. The first element of this workload dashboard is a textblock widget and currently I just have it saying some self aggrandizing information and arbitrarily adding a bunch of formatting so you can see how cool it can look. But if this was your workload dashboard, what you'd want to do is give some guidelines here to explain what this dashboard is for, how someone can use it, and what information they should be looking for in each particular piece. So for example, you might add a note in here by editing that particular text block widget to say look for is capacity equally distributed. My economics teacher would be mad at me for saying that equitably difference between equity and equality is capacity equitably distributed. Meaning does it make sense how many people have each thing and we can add other things to look for in a quick reference chart. In this text block widget we can also choose to add these kinds of details inside the description of the dashboard. If there's stuff that's big picture like why do we have this dashboard, who sees this and so on which can add some clarity to this. And we can also add some of this into the title of each of the widgets. But I think a text block widget is a nice place to add images, hyperlinks, maybe a video tour to break things down for your operations manager. To the right we have a current assigned to distribution. This is the widget that I showed you guys earlier, but now we have it embedded all into one view for ease of reference. Below that we've got our time estimated and tracked by due date. Look familiar? Hope so, because that's what we talked about earlier. Then we have an embedded task list here. The way we did this is by going into this, clicking on embeds and adding in. Is it not embeds? Yes we did. So this is adding in the grid view inside of SmartSuite. Sorry that I thought this was under embeds. My bad, it's under the SmartSuite Views category. We just added the grid view to show a list of all of the active tasks inside this area in one preview. Inside this widget we have chosen to select the view that we have inside our tasks area, choosing a grid view and we've disabled some of the editing options to make it look a bit Cleaner save work. Over to the bottom right here we have tasks by priority, we have time zones Breakdown, which is a widget inside SmartSuite to just show us. Hey, where's our team at? Who can I expect to hear from today? And then we have a comparison widget going into here that just shows me how our workload is year over year or period over period in a quick visual resource. So in this case, hey, we have seven tasks in demo versus last year. Woohoo. Please note that for each of these widgets you see here, we actually have two options for how to add them into our universe. So if I search for chart inside these widgets, we have the option to embed a chart view that we created elsewhere, which is what we did in the whole beginning of this presentation. And we also have the option to build charts from scratch, which can be confusing. It was for me at least. Again, maybe you guys, you're like quick on the draw. Took me a second. So in case anyone is confused by the difference here, the chart views we created earlier are fully featured chart creators. And then when it comes to the dashboards, all we're doing is taking them and embedding them into the app. So we can choose our reports from anywhere, pick the particular chart we want to embed and have it embedded. That allows us to have the setup in one spot and the visual in another. Whereas these ones bar chart and so on is creating things from scratch and we have all the same settings we have elsewhere. When I first started with SmartSuite, I will admit my bias took me into creating my charts right in the dashboard. I have later learned how that's actually not the most efficient way with how SmartSuite is created. Instead, what we did here of creating chart views and then embedding them in dashboards is more sustainable because it allows us to create charts once and embed them in a bajillion other places without having to manually recreate them one by one. So that's my little pro tip. When it comes to the question that came up at the halftime of this show about how to have a dashboard that reports on multiple different areas. This is your answer. What you'd want to do for yourself is at each solution that you have, create a chart like the ones I've shown you here to report on that particular solution. Then create one dashboard that combines and embeds all of those charts from all of those different places. In this case, you might have one chart from another app, one chart from this app, add all of your apps together and Add those into your dashboard to give you a broader report. That would be one way that you could go about it, to give you a bigger overall visual. It's not the perfect full workspace summary. That's something that, from what I've seen at least, is still in the works and being developed by SmartSuite and I think we'll have some cool developments on that soon. But for now that's kind of the way it goes. You have to select your solution report on your thingy, Bob, and just in plug, plop those widgets side by side to give you that overview. But there's not a great way right now to combine multiple apps into one particular report or one multiple solutions into one chart. Did I lose you? Does that make sense? So you create the widgets side by side, make them all parallel and that's how you can get that overview level. Okay, I'm going to do a quick check in on the chat again or maybe Carly can help me out. Perfect. Does SmartSuite not have any functionality along the lines of portfolios in Asana or workload in ClickUp? The closest thing we have right now is. Let's just go into this and this is an area that I've seen a lot of movement on. SmartSuite's at that really fun stage of software where things are being developed so quickly that by the time I'm saying this, it's probably outdated. But our most common options around availability right now are our availability status, our work hours, which is a workspace setting we talked about last time where you can set like hey, we work eight to four or whatever. And these kinds of charts that I showed you here, there's not a pre baked like time estimated versus how much time they have in a day view that I know of yet. But I have seen so many things in the kind of work in progress area related to that that I am loathe to say anything definitive because I imagine it's going to change almost as soon as I say it. If you guys aren't following right now, the, the canny SmartSuite board, that would be where I would check, check the progress on these because there is a lot of stuff in the works that kind of touches on this particular feature. I will say from a data perspective, SmartSuite has a lot of information they're tracking in, I mean kind of a creepy way, but mostly a really good way around how people are working. And from the features I've been seeing roll out, they're starting, they're just starting to leverage that data and for a tool that's this new, even what we have is cool. But they're tracking so much about how people utilize the platform that if SmartSuite doesn't develop best in class gamification and workload and capacity utilization, I would be absolutely shocked because they've created. They've had a much bigger bias towards people management in the work management space than pretty much any software out there. The out of the box features they have for managing people. It would be very natural to see a best in class feature around this element. But I don't have a go to resource at this time. Check back though, because I imagine either I'll learn something new, maybe it's in here and I'm just missing it, or we'll see something come out pretty soon. Anything else Gimquy asks Can you create or download templates like notion? Yes. So SmartSuite has a template database thingy mobabi that I showed at the top of the show here where we actually have their particular templates. But you can also take the things you create inside of SmartSuite, such as this particular beauty I have here and we can choose to share solutions and allow users to make copies. So you have the option to not only have kind of templates internally but also externally and you have the ability to restrict with a passcode, which is a rare and convenient add on that I don't think we often see in terms of templating features. If you're someone who still offers templates via Google Files, this is going to be a big upgrade for you. So yes, you. You definitely can. Yeah. And it's via a link so you don't even have to download E Asks ideas for workaround on the charts to consider both start and due dates where tasks show. Say there's a task that you'll be working on for four weeks and you want to look at capacity by each week. Yeah. So right now SmartSuite is a little biased towards records, which makes sense. It's like the center of their universe. So when you want the most accurate reporting on anything, I would be biased towards making it its own record. What does that mean? That means in this case, probably right. Sizing your records so that way your record equates to one work session. That can be weird for people, but I think there's a tendency to want to make a record. Think of it as Excel. One record is a giant project and you assign it to John and you're like good luck. Having something so large is not only hard to estimate but it's hard for these kinds of reasons where you're going to be working on it steadily. So what I'd suggest is, if possible, break that project down into pieces that are bite sized. Session size a session for a busy mom, a work session could be 15 minutes because you know, it's in between juggling a million things. Someone for. For whom deep work is kind of their bias. A session might be three hours. But I would try to make sure that your records are the size of a typical work session. You can do that by either going inside of SmartSuite and having your base records be that small, or my preferred method, which I actually showed in that video, is to have, let's just add it here, add a linked record field and actually connect out. So rather than using sub items or checklists, which are great but not as good for this estimating piece, I would have little tasks, subtasks, whatever you want to call them. And I would use linked records and have one database for your projects, like the overall containers and one database, AKA an app for your chunk by chunk, bit by bit, actions you need to do. And it's on these little tasks that are the size of one work session that I would be putting my time estimates. I would then be using a roll up field. This is getting geeky, guys. I hope you're with me to roll up based on that relationship to say, hey, of all of those little tasks, what is the total time estimate or what is the total whatever? So I could still see it at both levels. Anything else on this one? Good. Okay, awesome. Well, thank you guys so much for joining us here on the live stream that we've got talking about capacity management. I'll get my little slides up here to wrap it up. If you guys have any questions you'd like to see answered for next week, please do let me know. We'll be back here next week to talk about how you can use SmartSuite to build out a CRM. How I'm saying that, thinking, yes, that is next week, right? Yes. Okay. And so if you would like to have any questions answered around how you can actually build a CRM inside of SmartSuite, if you've got any questions about how to go deeper on a particular use case, or if you just want to see how we can bring all of this to life inside of an account like yours, please do let us know. Just going to confirm here. Yes. Okay. February 15th, how to build CRM in SmartSuite. That is the thing. Dates are hard for me, people. Thank you. Guys. So much for joining us, though. And until next time, enjoy the process. Bye, everybody.