Welcome to ClickUp Weekly episode 6. My name is Greg McKenzie. I'm the founder of Zenpilot and your host for ClickUp Weekly. We've got a great show for you today. As always, we'll be digging into what is new in ClickUp from this week. We'll take a look back in our ClickUp Rewind section. Um we'll talk through our ClickUp wish list and some things that we wish were out there. We'll talk about ClickUp in the wild. And we're going to spend time today on ClickUp statuses. Everything you need to know about uh kind of the simplest version of statuses to much more complex use cases of statuses and why you would want to move uh from originally starting in a less mature organization with fewer statuses to potentially more statuses or multiple sets of statuses um as you mature and why you would not want to invert that and start where most people start, which is way too many statuses and then uh you know progressively get simpler as you go. So, I'd rather see you move on the curve the other way. We'll talk through all of that and more here in this week's episode. Uh, as we get started, disclaimer, ClickUp Weekly is, uh, fully my fault. Um, this is presented by Zen Pilot and it is exclusive to Zen Pilot. It's neither sponsored nor endorsed by ClickUp. They want to make sure that I let you know that. And with that disclaimer out of the way, let's dive in. Um, if you've got comments along the way, make sure that you leave them here on YouTube or however you're watching this. And, uh, if you've not yet subscribed, please go ahead and subscribe to the show as well to get future updates. Okay, ClickUp release notes. We're going to start here with what's new in the platform. Nothing new in ClickUp's official change log this week, but there's three things that I want to call out. Uh, the first one is we got u beta access here at ZMPLET to the org chart feature that's coming out. So, inside your Teams hub, um you'll be able to use that. Now, I'm not sure if I pull up I think I'm recording only a window on my screen that won't show. Uh I'm going to pull this up anyways just in case you can see it. Um I'll just talk through it in my ClickUp window here, which is probably not recorded um as I'm going through. I think I I hit tab instead of uh remembering to do a component of my screen. But basically, I can see um you know, the org hierarchy from top to bottom. I can click and expand um or move stuff along. And as I'm clicking on individual users, I'm able to do a couple, you know, kind of standard things that you would anticipate being able to do. Um edit managers being there, changing permissions, but one of the helpful things is getting an AI update. So when I click get an AI update, it pops up in the right sidebar and I'm able to easily see, hey, what give me give me an overview of what this person's worked on and completed over the past week. Um, so anyways, just an FYI that that is out there and it is kind of handy. Like I thought, you know, why do we need this? Like this takes, you know, a minute or two to spin up in whiteboards. Um, I think it's going to be handy, especially if you're in a large organization or just to keep track of, hey, where are we truly um across the team? Uh, second one is not a new feature or any progress on a feature. It's just an update on AI billing per user. So, let's pull this open here. Um, and we got an update uh 18 hours ago as I'm recording this saying, hey, the peruser seat model that has been requested as we covered a couple weeks ago here on ClickUp Weekly uh is not on the near-term roadmap, but they're working on something that's going to shift a lot of these AI features to, again, we talked about this a couple weeks ago, usagebased billing. And I think that's going to be the way that this um entire industry, which is really all industries, uh but this segment of the economy is going to continue to move uh towards more usage-based uh billing. So I think that that for some people that's going to address the core pain point. For other people, they're going to say, "No, I want to pay for fewer users, but the users I do have, I want them absolutely using the heck out of this product and sharing login." And so, you know, there's no way you're going to please everybody. which totally makes sense. Okay, I just wanted to call that out because um there is an update about it and so it's worth worth noting that stuff um and knowing, hey, don't hold your breath for per user uh AI features. You're not going to have the option to toggle it on for five people and leave it off for 45 people here in the super near future inside ClickUp. Track assigned comments. What the heck is this? We've not covered assigned comments uh yet on ClickUp Weekly in any sort of detail. So, assign comments. Let's just go into ClickUp real quickly and let's leave a comment. Um, at Zenpilot. Um, so I'm going to leave this comment. Um, but I have the opportunity if I wanted to to say, hey, I want to actually assign this to that person. And so, it's now assigned to Zen Pilot. I could pull up, you know, whoever I wanted to see and, you know, I could see their profile and see what stuff they have to take care of and deal with. Um, but what there wasn't was an easy way to see um, hey, what are I I'm able to easily go see all the comments that are assigned to me and deal with those. there wasn't a super easy way to see if I assign something to another user. Uh, how can I see that that all of I could go user by user, but if I want to see I've assigned, you know, 17 different comments out to eight different people. Um, how do I go see the progress on those 17? There wasn't an easy way to see that. Well, that is what this uh solve is solving for. So, this was called out a while ago. This has actually been live here um for a bit, but uh ClickUp just marked this as completed this weekend or uh here at the end of the week. And so, um, I just want to call this out that the assigned comments page. Um, so if we go into our home, pull click up back up here and go to home. Expand this. Go to more. We can go to assigned comments. And now we can see this tab that has delegated by me. And I can see when that comment gets done or not done. Um, and obviously I could filter down through and see what are ones that have already been completed. it's going to only show me open ones by default. Worth calling out if you didn't know that that was around. Um it's worth knowing that hey that exists. There are real reasons not to use assigned comments and you just want to be careful about how do we use assigned comments versus like the easiest way to hide workload things that should be reflected as tasks should be tracked as real work should show up on dashboards where assigned comments are not going to show up like your tasks or like somebody's tasks. um is to to build these out as actual tasks. But there are use cases and at some point we'll do a whole segment and we'll talk through where is it okay to use assigned comments and where do we really need to say wait a second that should actually be a task. And so I'm as I'm creating that instead of just leaving that as a comment here. What I actually should have done is I should have said hey create a task and you know plug in or I've got a template already built. Um there's a couple different ways that we could tackle that. Okay. So, I want to call that out. Um, that's going to bleed into our ClickUp Rewind segment, which is our total time in status click app. So, if you're not familiar with click apps already, click apps are functionality inside ClickUp that are optional. You can toggle them on or off. Some of those are on by default, some of those are not. I just hit command K on my keyboard here to and started typing for click apps. And so, here you can see all the different options. You know, there's a million different uh click apps that you can have turned on or off. The beauty of this um is that if there's a feature set that would be super helpful for one team's workflow, but it doesn't fit yours, you could leave it turned off, or in some cases, you can change the settings of the Click app itself, so it works better for you. That is amazing for making it simpler for your specific workflow to work super well. The downside to this is, well, then we've got to think through the options, like, do I want that turned on? Do I not want that turned on? And this is really hard to kind of prescribe out of the box for every single user. Um, so things like time tracking, you know, maybe your team tracks time and you need all of that stuff uh tracked or you estimate time and you need time estimates built for everything because that's how you do your workload and your resource management. Well, you need those turned on, but teams who don't do not need that turned on. So, um that's kind of a simple example, but um this is, you know, thinking through if if you're brand new to ClickUp and you're thinking through what Click apps do I want turned on or turned off, um this takes a little bit of work. Okay, that's a a Click app. Let's talk about the total time and status feature that ClickUp has built as a Click app here. And I'll pull this up just so you can see the documentation as we're uh as we're walking through it and talking through it. The most common times that you'd want to be able to see time and status um are things like an SLA or service level agreement uh that you need to do SLA tracking for and reporting. In a CRM use case, you want to know how long did a deal stay in this specific stage. You know, what's our average like deal velocity is a super important metric to to know and to measure. So, how do we get that set up in a CRM type use case? There's a bunch of other other common like real world use cases that that pop up all the time. Um, but automations is another place like as an automation trigger. Hey, when something sits in client review for more than three business days or more than four days, then I want to trigger a comment to make sure that or I want to trigger, you know, a follow-up task uh for that specific uh person. It might be an external notification to someone who's a guest user in the workspace or it might be an internal notification. In some cases, uh I don't know if we've talked about this on this show at all, um but an auto approve clause is something that a lot of service providers have added in, especially if they're producing content for clients. Hey, you've got three business days to give feedback. We'll make sure you get the notifications. You've got a dashboard. You can see all that stuff. U they set this expectation at the beginning of the relationship. uh if you haven't replied after three business days, then on the fourth business day, that's auto approved and we've got the green light to post it so that we're not hamstringing your own success by your inability to follow up and reply to us. Um just having that um agreement in place substantially accelerates how quickly most clients will reply and will give feedback and follow up knowing, oh, this is going live automatically. the automatic the default behavior is basically yes publish not you know sit on your hands and and don't do anything and when the default behavior changes then the behavior around it also changes which is cool okay anyways uh time and status click app this is one thing to know about some click apps some of them are not available on every single plan u and so this is available on the business plan and above if you have any questions on clickup pricing you can reach out to us um at support zenpot and we can help you out on that Okay. So, you can see it in a couple different places then this time and status. So, let's go into ClickUp and I'll just take you through a couple of these um just so I want to make sure that you're aware. Hey, this exists and this works. So, I can see it here on an individual task. I can see, hey, this specific world's best boss parent task, which is a milestone task type in this case, has been sitting here for 514 days. So, I could see it in an individual task level. Uh we could go to actually we'll pull this back up and we'll go to just the the list view uh version of it. So I could add it as a new column here. So I'm going to add time and status by default with time and status. And this tells you a little bit about um what it's built for. I think by default this defaults I've already added this uh in in this case for someone who I was showing this to earlier this week. Um I think by default this defaults to hours. I could be wrong about that. Um, and that gives you a little insight. Anytime you see something like that, uh, sometimes our our natural reaction is like, "Oh, it's so annoying. I only would want to see this in days." It's kind of fun just to be curious and be like, "Well, why' that be the case?" Well, in the SLA, uh, setting, like hours is huge. Um, so this is generally going to be hours, even though for your specific use case, uh, that's not necessarily the case. So, uh, just be aware sometimes when you're playing around with features and you're like, "That makes zero sense." It does make sense. The use case is just a different use case than the the more common use case is not the use case that you're encountering. Um, and you could also look at this and say, "Hey, what was the date that this was last updated, but in this case, we'll move it to to days." U, so we can see it here. And um you know [clears throat] ClickUp's documentation talks about seeing that in list view. Uh we can see it in individual tasks and then we can see it on dashboards um in cards as well. Uh exporting this information. Um you can export this from the actual list level. So anyways, want to make you aware that is there. There's a bunch of examples. Uh, I think Nate on the Zenpilot YouTube channel just published a great walkthrough of our CRM setup. U, you can see some deal velocity stuff there where we're grabbing uh, time and status. There's a lot of different ways and and times and situations where this might be helpful. What's the requirement for this? The requirement for this is that what you're trying to measure is reflected as a status. In other words, I can't say um I want a different drop-down field and tell me how long something was in the inbound work category versus the branding work category. Does that make sense? So, there's a limitation to this feature in that it only does what it says it does, which is it only measures time and status. It doesn't measure uh time a specific dropdown or a specific property was attached. And you so you can't pick like, hey, I want to measure 17 different customizable properties um and pull those in. And that's going to um jump us right into our wish list section where [snorts] I want to talk about um like what would you like to see in ClickUp? Um is that something that you'd want to see is the ability to measure specific stages? I'm going to talk about statuses here in just a moment. And then the other item on the wish list for this week is uh ClickUp Brain and Ask AI is using GPT 4.1 right now. Um, hey, can we please get this upgrade updated to uh GPT5 or above? Um, there's some other options as well here. Uh, but ClickUp just shared an update here in the past uh week that this is under development for both Ask AI and Brain inside ClickUp. So, I just want to shout out that this one is coming. This has been a while. I actually just had a text exchange yesterday morning uh with someone saying the same thing and they've kind of moved to using the Claude uh the ClickUp MCP through Claude um for some of the stuff that they were trying to do previously um because of model control and and faster model upgrades. So that's coming. Let's dig into ClickUp in the wild and let's talk about ClickUp statuses. I've got a couple things that I want to share. The first thing, let's just cover a quick framework here on click of statuses. There's three three ways I would think about this primarily. So simplicity is one. How simple can we make it for users? And I don't know if I've got a good example in ClickUp already. Let's go to let's see if tools have this. Um let's pull up actually let's go to our tech stack. So here I've got a list. These are all specific tools. Um they're actually set up just as records. And so there's a tool. There's who primarily owns it. Blah blah blah. All that, you know, all that information. And there's only two statuses for it. It's either open or closed. You can see a custom task type for record here. And the statuses are custom messages have two. That's as simple as you can get. So when we talk about simplicity in statuses, this is the very easiest you can do. To-do or open and closed. What's cool about that from here on the task screen, if I click on this, it just instantly closes and the task is done. So, I'll undo that here versus let's go back here. We'll go to world world's best boss. We'll jump out to list view. If I go to try and close this out, it's going to give me a drop down. So, it's one more click to go, you know, to the place that I want to go. Does that make sense? Okay. So, that is and we'll jump back to our to our text stack here. That's the first place is simplicity. But then management precision is the second consideration. There's if I thought about this for more than 10 seconds, I'm sure we'd come up with a simpler way to say this. It's basically like visibility. Visibility doesn't quite do it all because being able to visualize something and not do anything about it is not that useful. So like how precisely can we manage something? There is a too far like we could super precisely manage things and waste all kinds of times doing it. So there should be some layer of abstraction and the further removed you are in terms of managing a process like the more abstracted it gets that's fine but for work uh you know we're rebuilding the Zen pilot website um seeing to-do and done is not that useful for knowing hey where does this sit like is there any work that is there is anybody blocked with anything um you know are things flowing smoothly are they not flowing smoothly um Like that's, you know, this might be a much longer process. And so for a simple task that you're going to either like not have done or have done, hey, flip this light switch on or off. Yeah. To do and done obviously makes sense. Um for stuff that's um spread across a team and or it might be one person's work, but it's going to take them three weeks to get it done or three months to get it done. Uh being more precise about where specifically are we in the process is extremely useful. So that's the second big consideration. And that's going to pull us like the natural pull is simplicity. How do I make this as easy as possible for users to just click a button and it's done. There's no guessing. Uh there's this natural tension and that's a healthy thing and a good thing to hey how can I have full visibility into exactly where this process you know where this where this what what's our progress on this specific deliverable or on this specific task. The third consideration that I don't think gets um considered a lot like we fix a ton and and see on a weekly basis dozens of workspaces um where folks have gone in and set it up themselves or they worked with somebody you know they found some other contract they worked with somebody else. We see dozens of them and every single week and we get to fix, you know, a third of those um over time who are actually going to work with us. We get to get in and start fixing those. Um, and this ClickUp functionality, like thinking about that gets missed a ton. Things like time and status. Um, it'd be really nice to abstract some of this information and push it down to, you know, a different custom field or something else. But and and often that's the right situ that's the right uh conclusion to get to. But sometimes, hey, we are going to need to measure time and status and show that reliably and easily. Well, then we've got to be aware that hey, this may be a reason or a situation to deviate um from a standard set of ClickUp statuses. Okay, hopefully that's helpful. Let's get let's go into ClickUp and just kind of walk through a couple examples. In this case, we are using a record to represent a tool here. And this is a custom task. I remember when I'm saying record like they're still tasks, but they're representing what tools have we subscribed to, who's responsible for it, you know, what status are we at, why why are we using it, how much does it cost, where do we go to log in, u we probably have like who's the tool champion for this, uh what are instructions for using it, all that kind of all that kind of information, you know, here's a getting started guide, like all that all that kind of information. In this case, this is purely a reminder for whoever the the assigne is. Um, and this is kind of an older version of this text stack, so I wouldn't set it up the exact same way today. We've got an updated version in the uh Zen Pilot um ClickUp install, uh, which by the way is available for purchase. So, if you want kind of a holistic install, um, tons of templates, features, like really well thoughtout stuff, um, you should, uh, reach out to us and, uh, we should see whether that would be a fit for for your situation or not. Um, [clears throat] but in this case, this is just a reminder. Hey, go in update. You we probably have links to like what users are using that tool, how many licenses do we have? Like, this is just a reminder for you to to do it. So, you're going to look at it. You're going to look at the users. You're say, "Hey, do we still need that tool? Yes, we do. All right, it's done." Like, no problem. Um, and we can move through it. [sighs] So, that makes a ton of sense in that case versus, hey, here's live work that's going on and now I want to know some information. So, these are for most of you, I would recommend these seven statuses as your starting point. Well, so I'll just kind of quickly take you through each of them. to-do. I don't care whether you call it to-do or open uh or if you've got another another um you know, if you've got other vernacular that you like to use, that's that's totally okay to do it. Some people will say not started. I don't think that that's quite uh enough because you can see we have two different statuses in this grouping of not started. The other one is planning and that means something different to us. To-do means it's scheduled. It's assigned. we know who's going to do this work. Um like those decisions we already have the the subtasks planned out. Um that's what to-do means in the Zen pilot ecosystem. Um planning means, hey, we're still figuring out some of the details. The client may or may not want to do it. Um or we internally may or may not want to do this. Uh we don't know who's going to do it. We don't know when it's going to happen. It could be all or um any of those variables aren't figured out yet. we're going to treat those planning tasks slightly different from a management perspective than we will uh to-do tasks. So, in other words, if a planning task um you know, we want to find our ClickUp Champion is going to go in and flag any tasks that don't have an assigne, don't have a due date, don't have a time estimate, but there's no way we would have a time estimate on it if we're just considering it as an idea. If it's in the planning stage, we wouldn't have assignees assigned to it if we don't know when we're going to do it or who we're going to be working with. We might not have due dates. We certainly won't have due dates set on it if we don't know when we're going to do it or for sure if we're going to do it. So, we'll treat those differently if they're in the planning status. Hopefully, that makes sense. Then you get to work on something. So, I pull this up. I [clears throat] start working on the first subtask. I'm updating this to in progress. And now, boom, everybody knows, hey, this isn't just to-do anymore. Now, we started working on it. Um, blocked. This is probably pretty self-explanatory, but it's blocked for a specific reason other than these next two statuses. Um, so blocked might be uh there's a technical limitation on this. I've had an obstacle I cannot overcome. This is not just kind of the normal flow. So blocked will not be used that frequently. Uh should not be used that frequently. Um, but it should be used as frequently as it's appropriate. Um, and we've got in the Zenpilot training center, all of this stuff's documented with with full definition. I'm kind of giving you the the super high level scoop on this uh internal review. Hey, somebody on our internal team needs to see this. If it's client work, in this case, we're working with Trader Joe's. Um, this is in their review. Again, this is might be a situation where you use those automations. Hey, this has been four days in client review. Um, we're going to automatically move it. Leave a comment. uh we'll send a message to them and we're going to move it back to in progress and then closed. Ultimately, this has been closed. Now, there are cases where moving from this set might make sense. So, my big caution here, why I bring up these three considerations is when you explain that to your team and say, "Hey, these are the seven I want to go with. This makes sense. Uh Zenpilot walked me through it and like this totally makes sense." Um there's going to be some people who say, "Yeah, it was great." And then I added another closed status for published because that makes sense when I'm doing these um blog posts or these social posts or you know this like I've got another one for sent for emails. Um, and we start adding all of these different statuses and without enough justification that hey, we need it for management precision or clickup functionality, we get away from our simplicity. And maybe the easiest way to help you visualize what this would look like is if we went to we're just going to add another view here and pull up a board view. By default, this is group by status. And sometimes this is super helpful. Well, imagine zooming up to the all tasks level and seeing a board view. Uh, so let's go ahead and grab just like a a dummy board view and we'll pull it up here. And now we've got open, we've got to-do, we've got not started. Why are there three different statuses here? Then we've got planning, we've got active, which is apparently different than in process, which is also apparently different than in progress. Um, now we've got update needed. You can see inclient review versus client review. This is what happens when you don't have a clean workspace. So in in this case, maybe it's excusable because we're in a demo workspace and we've pulled in and messed with all kinds of different things in here, but this would drive me absolutely crazy that we've got completed and complete. And now when you try to pull any type of meaningful reporting, just imagine this in a pie chart on a dashboard and you're seeing, you know, four different shades of green and somehow closed, paid, complete, completed all mean something different. And reviewed in this case is also a done status. It's showing up in this section, but client review, but it's it's blue or purple, and that's matching up with this. Someone's going to laugh at me for saying that was blue. Uh, that was my first instinct was that it was blue. Come on, guys. It's bluish purple. Um, you know, it's it's showing up as a color like this, but it's going to mean something like it's just going to be so confusing. And so, um, that's the argument for simplicity is keep this as consistent and simple as possible because when you go to you when you go to pull reporting and now you're aggregating from different areas of the app. I get that it totally makes sense to have a sent and a published and a delivered and all these different status ideas. when you're on a oneto one, you know, you're just you're down in the weeds of working on something, it makes sense to complicate it. When you zoom out, it makes sense to simplify. So, I will always opt for simpler statuses that give enough clarity to be able to manage it uh versus more complex ones and then take that next level of detail and we can move it into a dropdown. Um, so the status could be our final status here. It could be closed, but the publishing stage or some type of stage custom field. In fact, let's see if we have any Yeah. deal stage or a client stage or a life cycle stage or something else. Could be uh you know, sent uh closed one. So, it could still be a closed status, could be closed one, closed, lost, deal stage. Does that make sense? Um hopefully that's a [clears throat] helpful overview of statuses. Um, there's so much that goes into this and there's use cases where I say, uh, yeah, it totally makes sense in the CRM or in this SLA reason to make statuses a little bit more complex. And now we need to be thinking about, well, where else are we going to pull reporting and how do we consistently exclude those from the reporting or show them differently so that it doesn't mess up everything else. It's all possible in there. It's just a matter of thinking through it. All right, I want to spend some time on that. That's come up. Um, I've had probably four or five different conversations in the last two weeks, a couple on LinkedIn and a couple on on live calls where I've been walking through where there's just been so much confusion about statuses and kind of like, "Hey, could you please walk us through uh some of that?" So, we'll do it here at scale. Uh, I'll remind you, I shouted this out before. There's a uh email that went out this week u to any workspace administrators reminding them again on February 20 27th, your workspace, if you've not yet upgraded to Click of 4.0, is going to automatically switch to 4.0. You'll be able to revert that switch if you want to for uh up to a month until March 27th, which is the mandatory migration timeline. Um, but that [clears throat] is going to happen. So, if you've not yet switched or if you have switched and you've got questions and you're not sure if it makes sense or not, um we have a ClickUp 4.0 U optimization. So, how do we migrate [clears throat] and then how do we get the most out of this tool set in 4.0. Some of that might involve some status stuff. Uh we have a service specifically for that and you can either uh book a call on the site at zenpilot.comcall um or reach out to us at supportzenpilot.com and we can help you out with that. That's a lot to cover. Let's get into trivia time. It's trivia time. Last week's trivia. You ready for this one? Without looking it up. What does the word buteraceious mean? Does it mean A relating to or resembling butter? B having an unpleasant rancid smell, C thick skinned or tough in texture, or d excessively flattering or smooth talking. I shared the story last week that this is the word uh and I I don't think I said this. I have told the story this way before. Here's my here's confession time when I've said it before unintentionally. I've said this is the word that kept me from going to uh Washington DC for the national spelling bee. It's actually not. I probably would have lost at some point anyways. Um, but this was uh the final word spelled in uh in our spelling be in 8th grade to get there. I had no idea what it meant. Uh, the answer, if you guessed a relating to or resembling butter, you are correct. That definition didn't help me spell it correctly at the time. Um, but now in retrospect, I've never forgotten it. So buteracious. You've got a new vocabulary word to use when somebody says uh something relating to or resembling butter. You can pull out buteraceious. You ready? On on that note, let's go to trivia time. I mentioned I was down in Florida um [clears throat] this week for time away with my wife. Uh we've got baby number five coming on the way. And so this is our little uh getaway, just the two of us to do a couple different things. um one get away and just enjoy time together before the baby comes. Uh but two, we're homeschooling our kids. And so this was also kind of planning out um hey, what are the the educational plans here as we're finishing up um the 2025 to 2026 school year? Um and so kind of just like some of some of the natural rhythms that that go with that stuff. Uh we had a great time down in and around Fort Lauderdale and South Florida. And so I've got three questions for you. I probably should have that collapsed, right? And I should have have these spaced out so you're not seeing all the questions at the same time. What is Fort Lauderdale's official nickname that actually appears on the city seal? That's right. Turn question number one. What is Fort Lauderdale's official nickname that actually appears on the city seal? Is it A, the yaching capital of the world, B Venice of America, C gateway to the Caribbean, or D America's tropical tropical paradise? Uh, I was like saying Caribbean, by the way. Uh, Caribbean, Caribbean. You've got people who feel strong on both sides. That was your first question for trivia time. I've got three questions for you this week. Question number two on ClickUp Weekly Trivia Time. Studies show that the average office worker is actually productive for how much of an eight hour workday is it? A an hour 39 minutes, B two hours and 53 minutes, C four hours and 15 minutes, or D 6 hours and 11 minutes. Submit your guesses, leave a comment here, and we'll pick a winner for next week's uh on next week's Click ClickUp Weekly. And question three of trivia time on ClickUp Weekly, which of these is botanically classified as a true berry? Is it A strawberries, b raspberries, c bananas, or d blackberries? This one is probably, if I had to guess, I think this one, if you've never been, is probably like a eight out of 10 difficulty level. If you've been, it's like a one out of 10. Uh, this one's probably like a five out of 10 difficulty level, and this is probably two out of 10 difficulty level. That's my ratings for this week's trivia time. U hey, it's fun to fun to share this stuff. Uh this has led to some funny conversations internally at Zen Pilot. I feel like I do this selfishly just for the people who I interact with uh the most. Probably 90% of people are like, "What are we doing?" I came here to learn about ClickUp. Uh these trivia questions will have to do with ClickUp uh from time to time as well. Um, but I love having some random stuff and it's fun just to put it out there and then have the conversations internally, have the conversations with uh clients and with a bunch of my friends in this ecosystem. So, apologies if that goes if that trivia time is not for you. That's okay. It's not all going to be for you. What is for you are some other ways to get involved. So, please subscribe to the show uh here on YouTube. uh email showpilot.com if you'd like to be involved and then make sure you've subscribed to First Class Operations for any insider tips that we've got there and there are a bunch of our ClickUp 4.0 resources continue to go out there and you can sign up at zenpalot.comnewsletter. All right, that's it for this week's episode of ClickUp Weekly. Thanks for joining me here on episode 6 and we'll see you next week for episode