Hey, what's going on guys welcome back to another video so in this one I'm going to attempt to show you 10 product ideas that are trending, spiking massively in popularity, product ideas that you've never seen before. So these are products that are backed by the Google Trends information. I'm going to show you this for each and every product as we go through so you can see indeed that these are products that more and more people are coming into the market for. More and more people are currently looking to buy them and probably because it's well I say probably but obviously because we're coming up to Black Friday and we're coming up to Christmas time people are looking for gifts to buy their friends and family. So all of these products ideas at least in my mind make great products to jump on top of get a store built around and launch in time for the Black Friday sales as a way of testing the product is going to work so you can continue to sell it for the Christmas period. So that being said let's jump straight into product number one. Product number one is this foot massager tool. Before I go any further I want to show you that I do somewhat know what I'm talking about when it comes to massage items products whether it's neck massages foot massages that sort of thing people buy them as gifts it's just a fact you might even have seen it before in your own family somebody get your mom somebody get whoever it may be some sort of massage thing it's just I don't know why it's just one of those things people tend to buy for friends and loved ones. So this one is no different the kind of uniqueness to this product is the EMS part of it so it's a different technology and what's really good about it is you can as this video plays you can kind of line your feet up and choose where you want the massage to happen and different parts of your feet are linked to different parts of your body so perhaps if you have a sore back or sore arm or sore shoulder then this diagram on the mat will direct you to where you need to be massaging or using a technology in order to release the pain in that area. If you're wondering what platform I'm using this is called sell the trend we can see there's been kind of like a slow and steady increase in order numbers since sort of a middle of the year which is a great sign it's quite a cheap product only $7.41 recommended selling price is $23 which leaves a fairly tight margin of $14, $15. However coming into Q4 then I think you could probably get away with slightly tighter margins because your conversion rate should be higher as long as you do everything right of course you have a really good store really good ad creative and you put it in front of the right people then I truly do believe that your profit margins will be better and your conversion rate will be better if we flick through then the last few years kind of like for the search term a foot massager we can see October November December spikes massively in popularity during these months so history in theory should repeat itself and this year should be no different let's move on to product number two then we've got a lot to get through we have this sonic smile so basically it's a sonic dental floss tool again before you think what the hell nobody buys these things let's jump on to the water flosser search term which is essentially what this is and we can see this is a relatively new technology like since 2019 it was pretty much non-existent but again this is the sort of thing that people love to buy as gifts I myself have actually received one of these as a gift perhaps it's kind of like one of those gifts that maybe I don't know people obviously want to take care of their teeth for the right reasons and it's just again one of those things toothbrushes as well electric toothbrushes another really really kind of common and popular gift it's the sort of thing that you don't want to spend your own money on but you know it's important and you would like one so you would ask a family or friend to get you one instead the other thing as well is that 4.4 million dollars should not go without being noticed and without being mentioned it's obviously a technology it's obviously a tool that people are interested in order numbers aren't the be all and end all on aliexpress because obviously the majority of their business goes direct to the consumer it's not dropshipping orders but it's a proof of concept if people are ordering this through aliexpress then there's obviously a demand for the product so again if you can do everything correctly really nice looking brand perhaps a private labeled product really nice you you see your ad creative i see absolutely no reason why you couldn't make this work for yourself coming into black friday weekend and of course the christmas period let's move swiftly into product number three then is this shower head so i'm just going to play this video so you can see the different features and functions of it so it has that kind of like rubber bristle so you can use it as kind of like a scrubby motion and i think where this would be absolutely perfect is not only just to pretty much everybody who has a shower that's a pretty cool feature as well that you can pop it off and use it's kind of like a jet but i believe this would make a great shower head for anybody who wants to wash their dog as well so you could do your own research into this perhaps speak to the supplier see if you could get an attachment for an outdoor hose there is a company that you should go and check out if you're interested in this product called pup jet they are seven figure business selling an outdoor attachment for your water hose and it's basically a jet like a car foam jet that you use to wash your dog with and this is brilliant because it has the bristles so you can use that to like get all the mud in that off your dog and it has obviously all the different functions and features to then clean your dog down has the jet function that it's a pretty cool product plus there is that other shower head which has kind of died off now but again that was a proven seven figure product it's the one you may have seen it with all the i think they were copper balls that the water would be filtered through to create not only like a really powerful shower head but also i'm not sure i think like ionized the water or it had some kind of claim to the health benefit that it was making but it was a seven figure product and it was a shower head so i don't see why this one can't replicate that same sort of level of success just to kind of prove it as well we can see that more and more people are like customizing their own shower heads or changing their shower heads for whatever reason maybe more and more people are getting showers but the numbers don't lie i really like to kind of back up my product choices with numbers and if the numbers are there then they cannot they're very black and white and can't be argued with and as we can see since 2004 it's just been an increase and slow and steady which is great because it's not a volatile market it's just going to continue to grow in popularity which is the kind of business that everybody wants to be invested in we have product number four very self-explanatory i'm not going to spend too much time on this i think it's a really nice touch it's obviously the time of year families getting together they're cooking they want to involve their kids i see like nowadays there's a lot of separation between parents and kids when it comes to doing things together because everybody's really busy christmas is the perfect time an excuse because nobody has anything to do but spend time with each other um typically cooking would be left to the adults so having these kind of christmas aprons that you can be matching with your kids can help encourage them get involved in christmas dinner i think it's just really a perfect impulse purchase making it the perfect product to be advertising on social media platforms and as we can see as well more and more people look for aprons as we come into the q4 period because it's typically when people cook more as well and whether and whether isn't as nice and people tend to stay in and cook rather than go out in the cold and rain so um in my opinion definitely a product to consider there's lots and lots as well of other christmas product ideas that you could build an entire Shopify store around before we move on to the next product just 20 seconds of your time if you're enjoying the video so far then i really think you will enjoy this this is a pdf completely free 100 free instant download it's 127 trending product ideas for 2023 and into 2024 product ideas that are essentially working right now it's split across 12 months so whether you pick it up now three months time six months time you will basically have the next 12 months supply of products all ready to go in one handy pdf for free there's no like upsell on the next page or no dodgy stuff like that i mean you put your name in put your email address in and the pdf will be in your inbox within 30 seconds so if that sounds good to you make sure you grab a copy of that it's the top link in the description down below let's jump into one of my favorite products then because i actually have a pair of these not these exact ones but a branded equivalent so the ones i have are called aftershocks these work based on the same technology what i really like about them is number one is their super versatile so like they're like impossible to break number two is their waterproof so you can wear them for swimming as well and excuse me number three is they work on bone conduction so this is actually really poor video but basically what they do is rather than go in your earbuds they go unlike the bony part of your ear so and it uses the vibration so it's when it's the base on them is really crap for that reason but uses the vibrations to i don't i don't know the technology but it doesn't cover your ear um canal so when you're running when you're cycling whatever it is you can still hear pretty much what's going on around you so if you are on busy roads that sort of thing um they're really good for having that kind of like awareness of what you're surrounding so doing a brilliant brilliant product like i said one that i use every week myself again the sales don't lie at 1.8 million dollars and if we actually jump on to the search volumes as well again it's a popular gift idea for the q4 period meaning not only is it getting more and more popular it solves a real kind of pain point for anybody exercising it's going to be a great product into the January period as well typically when more and more people vow to lose weight and start exercising more so one of the better ones i would say in this video for sure and if it's something that you're interested in perhaps you exercise yourself definitely worth a product a product worth sorry ordering yourself and creating some content and building a business and brand around moving on to the next products then and we can see consistent increase in orders over time 77 000 in sales dog beds are pretty much like a win-win this time of year um you need to go with one though that has some sort of usp to it this one being it's obviously a big poor which is obviously matching to the type of animal that uses it um so it's not just your regular dog bed it does have that kind of added cuteness effect to it i suppose um and if we actually jump on to google trends information we can see again as we come into the winter period it's a time of year where more and more people are buying dog beds move on to the next products we have these headlamps now the reason i wanted to feature these is i know they're pretty generic products but there's a genuine use case for these especially this time of year and there's so many different use cases as well so as somebody who stupidly has recently signed up to a triathlon um i have quite a busy lifestyle as well so it's inevitable this time of year i end up cycling and running in the dark and i don't want to carry a torch i don't want anything that's too heavy and annoying um and going to get in the way of what my focus is to complete the run or the cycle whatever it is so any kind of really sleek compact high-tech headlamp that is going to keep you safe be able to mean you can see where you're going um and it's going to allow people to exercise in the dark safely there's a like i said there's a genuine use case for that product and there's tons and tons of other products as well which fit this same niche of keeping people safe while set outdoors so it could be whilst you're hiking running cycling and commuting in one way or form you could be fishing camping whatever it is you're doing there's so many different applications to this it gives you so many different ideas of bringing it to market and marketing angles and again it's pretty self explanatory coming into the q4 things this makes another really popular gift and it's not just the sort of product that's only going to sell well up until christmas it's going to sell well into the new year as well as long as the nights are long um then this is a product and people are commuting people exercising before or after work um then this sort of products that is always going to sell in my opinion moving on to the next one then a portable mini self-propelled electric bike pump 3.7 million sales um is not to be ignored i should have got one with a video but basically it's like you charge it up it's rechargeable so lithium battery so super powerful um it lasts a long time and again it's just perfect it's a nice little gift it's not a cheap product as well um it's quite a compact and luxurious and expensive and heavy and well put together item um that feels quite expensive it's also like a nice price point as well and anybody you know who's into cycling it would make a really really nice gift and obviously because it has that kind of specific application when it comes to targeting on your social media platforms in your marketing there's a clear kind of target market that you can go after if we jump onto the google trends as well we can see that it kind of spikes or peaks sorry um in april may time and we're actually kind of towards the very bottom end but at this bottom end is when it starts coming back up again so this is the product to kind of get ready for now and it's going to be a great great seller over the course of the next six months moving on to this one of the finer products not the finer one just yet um before you leave the video thinking this is a cheap crappy product it is but coming into q4 it's the sort of cheap crappy product that people would buy friends or family members who have cats but don't really know what to get them it doesn't have to be this exact product it just just cat toys in general it's more of a niche recommendation than a specific product however i do believe there is a market for this um exact products and when it comes to advertising as well like content is super super easy because people love to watch animals having a nice time being stupid being silly and naturally they want to see their own animals do that same thing so that would beg the question in their minds where can i can i get this same toy so that i can have this same experience if we jump onto google trends as well we can see again it's the sort of time where more and more people are looking for cat toys as gift ideas people buy their own pets christmas gifts as well i said that like people who are crazy do that i do that for my dog i buy my dog christmas gifts even though he has no idea it's any different to any other day so it is the time of year where people are looking for these cheap silly products that aren't going to break the bank um but it's enough for them to open and have a bit of fun with on the special day and like i just mentioned people are looking for gift ideas for their dogs for the cats and they're also looking for gift ideas for their dogs so here's another just kind of stupid silly product idea um that they can watch their dog open they can set up um i just have a bit of fun and include the dog on the special day having fun and being silly that sort of thing it's a cheap product as well so it's not one that people are going to be worried about spending too much money they obviously don't want to spend too much on their dogs um definitely fits that kind of impulse buy range and i can confirm the kind of increase in demand very similar to cat toys as we can see october november december with a massive spike or peak i should say i'm in popularity in the December months that was it for the product ideas i think there was 10 plus different ideas there i hope you enjoyed the video before you leave if you've stayed with me this far then i have a gift for you and only you because you stayed this far so most people leave my videos after two or three minutes those are the people who jump from shiny thing to shiny thing and they're not serious about this business people who watch my videos all the way through i like to think are serious about this business about starting a real dropshipping business that is actually going to provide them with a life-changing income for the foreseeable if that is you and that is your goal then i have something that i want to show you so what i want you to do is below this video so i'll use this exist in one as an example come down into the video description and click this more button at the bottom here you'll see this so this is a secret link i've called it and if you click that link it's going to take you to this page here and basically excuse me what this page is is it lets you book in a call with me there's a few different questions to go through so i can learn a bit about you but ultimately i want to know what your experience is with dropshipping and what you want to achieve in the next three to six months so it allows you to book a time and date that suits you for me and you to jump on a call have a casual have casual chat like i said about where you want to be in three to six months time and see if i can be the person to help you get there and we can work one to one together it's completely free cool absolutely no obligation and it's a win-win for you because at the very least you'll come away with a strategy growth plan a step-by-step plan that you can go up and implement for yourself on how to grow your business everybody gets that who walks away from this so if that's the sort of thing that sounds good to you and you like the idea of working one to one with me and make sure you go check out that link now thanks for watching guys i'll see you in the next video next week cheers


Devakar and this is Bharath here from HP. So we don't have Kiran who has done some parts of this work or most part of this work. So we'll take the time to actually talk on this behalf and walk you through this. So if you really look at this, we are trying to look at how OpenStack is actually having. What are the values that OpenStack has? And what are the values that we spear environment gives? For the sake of simplicity, we have just highlighted few of these values which OpenStack gives you and few of these values. And this is not exhaustive. So the list actually has what does OpenStack mean, which could be seamless API interface, portability across different forms of clouds and all that. And an easy way of accessibility and a seamless way of accessibility for any cloud user. And that's what OpenStack gives. And if you look at VMware, it basically gives you a lot of features and it's most proven inside the data center. It gives you a lot of functionality which is elastic cloud and it's the most adopted one.  So our intent in this demo is to how to bring these two values together and see how one can leverage the other. That's the intent of the demo. And we have a certain set of blueprints which is implemented and waiting for submission to Havana. And based on those constructs, we'll try and show you some samples of use cases which is actually using this model. And that will be our main aim of looking at the use cases. So mainly here, we see that OpenStack is good today. And vSphere, it's good in its form. And what we are trying to bring together and make it better. And we can have a better cloud built on top of this vSphere and in the OpenStack. So in the interest of the previous discussion regarding intent of why we are trying to do this, we have the following blueprints here which we are trying to implement as part of this Havana. And these are some of the blueprints which we have put and which we have discussed in the design sessions. And I'll just quickly go through each one of them and not take much time on explaining each of them. So here, main intent here for the first one is to have multiple vCenters managed through one compute, including multiple clusters and the resource pools that is in the next one here. So the third one is mainly about vCenter compute driver and schedule announcements to publish the cloud capacity which is required mainly when we implement a compute managing multiple clusters and resource pools. Today, what happens in the existing vC driver which is out there as part of the grizzly, you can manage one cluster using one compute and the cluster is the capacity what it currently gives today is mainly taking the first resource pool capacity in the default resource pool capacity and this is enhancing that feature. So the fourth one here is mainly related to, currently today you need to have a glance image wherein you will upload a VMDK image to deploy an instance into the vCenter or in the ESX. Here, what we are talking about is having a glance, having a VMware template to be used as an image and use the glance as only the metadata repository wherein you can just maintain the metadata of the template that you have available in the vCenter and when you do the actual scheduling, have the vC driver that we write to take care of the, taking the template to deploy the images, deploy the new instance onto the ESX server. So the next one is, so here we are talking about the compute driver NAS meant to support our HP Cinder 3-Power driver. Mainly here, we are talking about having Cinder volume which is carved out from HP 3-Power array and providing the support for attaching that 3-Power volume into an instance. So it's not only, yeah, it's a fiber channel support and the second thing is in this whole model we have actually the OpenStack compute is modeled as a vCenter cluster. So vCenter cluster has multiple hosts and the visibility to the volume needs to be set not to the only host which is usually the KVM model but needs to be set to all the hosts in the cluster so that a VM which is live migratable within the cluster whether it's a data disk or the boot disk should be able to move and that's one of the features which is needed because the target needs to be cluster aware and it should have the visibility. Okay, so that's the other part which is also changed. No, no, in this model we are not trying to do it through vCenter. It's provisioned through OpenStack and every API is done through NOVA and the driver which is actually talking to vCenter which is the vCenter driver will proxy it and do all the work which is needed and while it does that from NOVA so this is about getting the best of both worlds and one of the world is OpenStack and you create a VM and then how do you stitch the data disk through Cinder to a VM which is actually stitched through OpenStack and using a vCenter driver and matching these two. It's the best of both worlds marriage and in this part the only thing which we had in Cinder Cinder basically tries to do a host model with multi-initiators, it's also possible but in this particular case it's all about setting the visibility for all the hosts which are out there in the cluster and it's the volume share across all the hosts. The Cinder driver is also done for FC and it's a data structure change and that blueprint is also submitted. This is the NOVA blueprint. There is also Cinder blueprint which was also submitted and it is approved. So if we can follow through and wait for the questions that'll be great because if I run out of time then you would not see the demo so we'll go fast and then finish and probably take about 10, 15 minutes for the questions. Yeah and the last one here is we have a Health and Mon module which is introduced into the OpenStack and which is currently in Stackforge. We are trying to get the data out of the ESX servers into this Health and Mon and we will show what is available as part of this Health and Mon. So when we consider the current Grizzly model of either the ESX or the managing the ESX server through the cluster. So this is the model what we see. If you take a KVM host, you will compute into KVM host and that will reflect into a compute entry into the compute node table and you will have a queue which is created for compute one whenever a request goes into the queue. Automatically that is served by this compute here. So similar to that one when you have n number of computes you will end up with the n number of entries or into the computes and you will see the n number of computes. So when we compare the same with the vSphere vCenter driver which is existing in Grizzly. So you are modeling the cluster as a compute. So for each of the computes you will see the entry in the compute table. So this is what is currently available and NOAA scheduler uses the queue which is created to pass on the request of a particular compute and that's how it gets the instance created on a particular compute. So when we compare that with the NOAA proxy compute driver that what we are proposing, here there will not be any change in the KVM driver. So here we are talking about having a proxy compute which can be deployed either in a VM or it can be in a physical server anywhere you would like, you can have that one. Which can manage a number of clusters. It can be a number of clusters, resource pools, grouped together. So we are having one compute managing n number of clusters, resource pools and we give a feeling that you have n number of computes so that you will not have any, you don't have to enhance any other stuff which is all the features which are available as part of NOAA and it will continue to work as is today, we will see what we mean by that. So all the requests will go to this queue. So NOAA scheduler, it uses that queue to if any provisioning that needs to be done to this particular cluster. So here, what do you want to talk? You can. Okay. Here we are talking about HP three power center volume attached for an instance which is already existing in a cluster. So what we are doing here is, there are two parts to the story here. One is the change that we need to implement as part of the Cinder wherein a request to attach a volume to a compute that goes into the compute and that will be forwarded to the Cinder to create the volume and as part of this one and the storage array, it will create that volume and when it returns the, today in Cinder, what it returns is only a name value pair that of the WWN of the storage or the volume that is created and it presents it to the particular host. But in this case, what we need is since we are managing a cluster, we need that volume to be presented across all the hosts in the cluster. So that's the change what we are doing here is we are getting a list of WWNs and WPNs for hosts and accordingly all the hosts will see the, will have the visibility to that volume and it gets attached to a particular instance. So the forward, forward, the step two also passes all the initiators from the host. So Cinder needs to know what are all the initiators which are there in the host and you first give Cinder saying that these are all the hosts to which you need to present this target to and post-presenting those target it actually gives those results of how it presented and then you go do a re-scan on the first, today just does the first one and there are ways and means where we can improve things and picking and choosing which path, what we want to do all that. But basically this is about collaborating for a cluster and actually making all of the target's volumes to be visible on all the basic hosts within the cluster. So with that one we are going to talk about a demo wherein we will show some of the use cases that are possible with the implementation that we have with the managing multiple clusters and our resource pools. So our demo setup would be something like this. So you have an open-sac controller. So we have two v-senders, you sender one A and B where you have a cluster called cluster high availability and cluster FC attached. So we are going to use these clusters to depict the use cases that we're talking about. So you have another cluster tenant one where you have resource pool and resource pool two. You have an array here. So you have this two proxies which are managing this v-center proxy A, it's managing the cluster clusters which are available as part of this v-center A and v-center proxy B, which is managing virtual center B. So you have the, I initially talked about the health and monitoring component and this is the word proxy which gets deployed onto this node here which manages the v-center A and v-center B. And so we will drill down into the use case one wherein we are trying to provision highly available VM as part of the cluster which is where you have enabled DRS and HA for the cluster.  So the request goes from the controller to the compute which is the v-center proxy here. So that request gets forwarded to this v-center and we use the v SDKs to make calls to, remote calls to the v-center. So that in turn creates the VM which is a highly available VM. Now you can see that there are two clusters here and as part of, since the flavor that we have is selected is HA and image what we selected is HA image. So because of the affinity it goes into this cluster high availability. It's just an image. No, that's the name. Here just the name of the image, that's all right. So there is also a metadata which is trying to say that this particular cluster, this particular compute is aggregated and it's actually a HA enabled setup, okay? So you're trying and taking the VMware values which it could be FT enabled VM, it's a HA enabled VM, any of those. And these are things which OpenStack doesn't understand but you've tagged it in such a way that this particular cluster is actually tagged as a HA compute and the names are set that way so that we are meaning it in words and it's a HA compute and it's actually aggregated with a HA host aggregate which is actually a HA aggregate and then the flavor defines that if HA is true then provision onto this and that's how the scheduler understands all of this and provisions onto that. And in this, all of this, you have only meta tagged the flavors and stuff like that and the native OpenStack kind of provisions onto the HA enabled VM. That's the basis of actually having the values of VMware using it in the context of OpenStack and all you have done is few tags. So likewise, any number of VMs that can be provisioned into this cluster. So the next use case here is about processing a highly available instance with the FC volume attached. We talked about attaching a Cinder volume to an instance. So how that happens with the vCenter proxy here. So you have an image over here. You have an host aggregate called a three-part FC which is created in the controller. You have the three-part FC tiny as the flavor type and there is a FC compute which is basically representing this particular cluster which is managed by the vCenter proxy driver here. And at the same time, we are showing another functionality here where you have a VM template which is an image which is out there on this vCenter which will use it for deploying the new instance. So the request here, it goes to array to create a volume like I told you about how it starts with sending a message to the array to create the volume so that volume gets presented to the host through the Cinder and the request here goes from controller to the proxy driver proxy. From the proxy, it gets to the cluster here through the vCenter and it uses the VM template which creates the VM and attaches the volume. So we will show this demo as part of the demo. And the interesting thing is if one host goes down and the VM migrates, it you will see that within the cluster, all any VM which is actually as the VM migrates, it will have the visibility to the Cinder. Yeah, since this is a highly available cluster, so if the host C goes down and as part of that DRS and HA configuration, it will move the VM to the host B. So even at that time, you will have this data disk which you attached as a Cinder volume there. It will be still be available because of the enhancement that we are doing where you can see the visibility of that volume across the host. Two questions. Yes, that's correct, that's correct, yeah. It's still within the compute called FC compute and to its knowledge, it's in FC compute and it's within the FC compute, the live migration or whichever migration happened. The interesting thing is if the Cinder volume was not presented this way, the migration couldn't have happened because it's not visible, the data disk part. Yes, yes, yeah. Otherwise, we center would not even allow the migration and it would get stopped there. It's not a destructive model, but for it to really perform, that's where this enablement gets the VM to live migrate and all of that and so that the VM is still having the data disk visible to it. So moving on. There was one more question. So the network part today is pre-configured, so that's how it goes, okay? So that's a part which we need to answer and probably Sean who's sitting here, we'll see some answers in the next, you know, time coming soon and that's where the vCenter one, a network is unsolved mystery for now, it's pre-carved and hope that works and you will not have to stay with that model for too long, I hope, okay? So for now, it's answer which is it's pre-carved, okay? That's a, at least for the vCenter driver, that's the truth. Let's be clear on that, okay? So the other use case is possible with this one is the tenant-based provisioning where you can set the affinity to a particular cluster or a resource pool wherein you want to allocate one resource pool to a tenant and you always want that new instance to be created in that particular resource pool. So this is the setup of what we have, let's concentrate on this cluster A here, where you have RP1 and RP2, these are the two resource pools which are out there in the cluster tenant and you also have a highly available cluster. So what we are trying to do here is we have created a host aggregate called tenant1 where we will set the affinity to go into, whenever you create a new instance to go into this resource pool one or resource pool two by the host aggregate set metadata that you will set here. So there again, this request goes to the proxy and from the proxy it goes to the vCenter. You have a tenant1 template, that's how you link this host aggregate. When the scheduler, it picks up the number of hosts, it goes to the host aggregate and from the host aggregate, it will pick up, okay, I have, it has a metadata to say, okay, looking for a highly available cluster with resource pool one. So that's where the VM ends in this resource pool one. Similar to that, it will deploy the resource onto resource pool two. Yeah. Yeah, single VM template. Single VM, vCenter based template, single VM. So finally, we need, whenever we configure and deploy some of the instances, we need to have monitoring and this is the monitoring solution we have where we have the component called helpmon, which can, which manages the clusters. It manages the clusters, it manages the resource pool available there. So as of today, I would have seen that from the open stack construct, we have open, open stack compute and the instances. Here, we get the underlying details about the cluster and the resource pools. All the way up to the physical. All the way up to the physical layer and also it manages the VMs. So with that one, I will move on to the demo part of the session. So here, we are trying to deploy new instance into a highly available cluster. So you launch an instance, you select image. So we showed that we have a high label image there and the flavor type. So this is the pre-carved network that we have. Yeah, I guess. Yes, yes. I'm sorry. No, we directly created it on the horizon. So. What, guest customization? No, not yet. So here, okay. We just launched this highly available VM. So here, we are trying to power on that VM. So this cluster, which is available here, it's a fully automated cluster and which is a DRS and HE-enabled cluster. No, just for showing you that it is highly available cluster and the properties out here, we are showing the vCenter, otherwise, you don't. So it's more for a demo sake? Yeah. That it's really happening and the proof is actually what you see, right? So that's the reason why you're showing it. Well, I could always say that that's all happened, but where's the proof? That's the proof. So you see that this IP address is assigned when we started this VM. So it's still pinging. So you log into this VM and show the IP address which is assigned to this VM. Sorry, I could not get your question. Yeah. Mainly, what we are doing with bringing in this functionality into the open stack is we are doing the cloud enablement of the same features that you would have seen in the vCenter and make it available as part of open stack where you get the benefits of the cloud. No, we are not. This is one way of working. Let's put it that way. So if in a brown field somebody wants to try out, they already have their VMs and they want to try out a cloud, that's the way we should talk of it. Yes. No, you should be able to. Okay, I'll move on to the next demo wherein we show the FC attached volume to an instance. Here you are selecting the volume here. So you do a volume attached to that instance. So it started the job. So you can see that it's attaching that volume to the instance which is created. Yeah. On the fly, it creates that volume on the. Create. Yeah. Yeah, yeah. Already it's presented to that host and it's available there. Yes. So when you re-scan, when you pick the right host and then re-scan, that's there. Today it picks the first one so we can do better maintenance. You could go beyond that. So see the demo is good but it picks the first one which is written. So the way it does it in the vCenter is reconfigure that virtual machine to attach that another disk which is it attaches that volume as an RDM volume.  Okay, so that's the model. I hope, Sean, you wanna say something about it? Okay. It's about which chunk are you giving it for OpenStack? That's always the different. You don't do an import. At least for today, there is no import. Everything is driven through OpenStack and it is initiated from OpenStack and provisioned. Okay. Yeah, the next part of the demo is to see how we can use a template to deploy a new instance through OpenStack. So here there is an image. This is the image metadata which is available as part of Glance and this is coming out of the VM template which is available in the vCenter here. Yeah, image metadata is available in Glance and when you do Nova image show, you see that there is a metadata which is added as an image property. Yeah, yeah, yeah. So when you launch an instance, you will just choose the image just like that you will choose for a default image launch. It's possible but not done today. It's not reconfigured, it's not, you know. We can always do it. So it's not that it's impossible but today it's more of a template provisioning, yeah. So you can see that it has started deploying that new instance from the template. So that's about the deployment of the new VM. HNAble VMs? Not that I'm aware of and here we are taking the capabilities of what vCenter supports and it's HNAble VM. So, yes, yes. So we will quickly move on to the next demo. It should be the last one. So here we are talking about this health and module which collects the inventory data as well as the usage and the alert, the alerting data from for the ES6 driver here. So you can see the clusters, resource pools, VM hosts, instances, network storage and all the inventory stuff that we collected from the ES6 driver. So this is the VM host data that we have for KVM and similar to that we have the information for ES6 VM host cluster and resource pool as well. No, currently we have this created only for the demo and we don't have it like a production quality code. Yeah, it's API. Yeah, yeah. It's the best way of showing a demo. So it's more for the demo, we are done with time. So here drill down into the cluster. This is the inventory data that we are showing for a cluster and similar to that we have the data for resource pool, VM hosts, instances, network storage and we have the alerting data as well. Okay, so we are pretty much run out of time and so we'll surely post it, give us a couple of days, we'll post it and it should be there, okay? Okay, until we get back to India or the flight takes us there. So that's the best, if there is a flight delay, if you have earthquake, don't blame it on us. Okay, so that's pretty much that's couple of days. Okay, it's all about the airline industry and nothing to do with us. Okay, that's great, thank you. Thank you.


Mr. President, Walter Mondale says you're not telling the truth when you say you won't raise taxes next year. He says you're going to have to do it, sir. Walter Mondale is not telling the truth. I've said it before and I will say it again and no matter how many of you try to put in a hedging line, we have no plans for nor will I allow any plans for a tax increase. Sir, the Congressional Budget Office is releasing figures today which says they think you're going to have bigger deficits than your own projections. Mr.  Second trip. Second. You missed the ride this morning. Thank you. Did you do it? Yeah. We get the stones. There it is. There it is. We're going to start horizontal and then we're going to do the vertical. Do it both ways. I'll take three of those. Okay, we'll do a test first. All right, Mr. President, could you slide a little bit to your right? That's good, right there. And Mr. Vice President, a little bit. That's good. And we'll just test one. All right. This is a test right here now. Right into the camera. Mr. Vice President, why don't you just lean against the fence a little bit more. That's good. That's good. Make me look shorter. And that's fine. Right in here. That was a test. I'm going to start to shoot. All right, we're going to start to shoot. And as I say, this is a real informal shot, but right into the camera. That's good. And right into the camera. Good, just a little further apart, just here. That's it. Right there. That's good. And right here. good smile and big smiles right into the camera good lean forward on the half a step to your left if you wish sir that's good that's fine good looking real good and if you could lean forward on the fence just a little bit more mr. president you can just lean your arm on that's it that's good that's nice good that's good right here now in that same position just looking at each other and just talking to each other that's it that's good that's good I like that and Walter good that looks real good that's nice good it's terrific is that light balance all right now I'm just gonna go for a vertical and we'll be done now this is a vertical so I need you a little tighter together this one here yeah that's that's better all right that's fine and right into the camera mr. president just a little bit to your left right that's good you that's fine big smile whatever happened to build one shot now looking at each other absolutely you are coming back are you now you're not coming I'm coming back when the president comes back no we'll do that cuz I need to talk you back you thanks all right yeah that looks fine


Hi, welcome to leading a product team through fast-paced product launches. I'm Maya Kacharowski. I'm the head of product at Talescale. Talescale is a wire grub-based mesh VPN solution. Part of Talescale, I was at GitHub working on software supply chain security and before that at Google Cloud working on Kubernetes and container security and encryption and encryption key management. Startups are different from big companies. And so today I'll be talking about how to lead a product team through fast-paced product launches, for a Talescale startup. I've got to build and scale up a team where our pace of launches is hectic at best compared to, say, GitHub and Google where you might launch things over several months. And throughout this talk, you'll hear my bias towards things that are B2B, or developer-centric, as well as security-focused, where these are the kinds of products that have really strict requirements around what you want to know about upcoming changes. So what will we cover in today's talk? First up, we'll dive into what a launch is at the minimum. That is, what is the MVPO launch? If you do nothing else, this is what you need to do. Next, we'll uncover the different kinds of launches that you'll encounter, including mainly the difference between front-end and back-end launches. But launches aren't one size fits all, so we'll also discuss how different kinds of products, whether it's B2B or B2C, require tailored approaches. And lastly, we'll discuss internal process changes that you can make to make fast launches more sustainable. So let's jump in. So first, you're probably here because you're wondering how to get your team moving more quickly. I don't have a good answer for you on that right now. That's going to be a different talk. But I'm here to talk about what happens when your engineering team is running ahead of product, when you're shipping new functionality and improvements that come faster than you can handle them. Some of you are probably thinking, this can't be real. It is real. It's often what happens at startups. Like I said in my prior work at large tech companies, I might be working with two or three edge teams and we might have a launch every few months or smaller changes every few weeks at best. Now that I'm a startup, sometimes we launch the feature that we got where our competitor is working on the same day. I think the fastest that happened was exactly that. We figured out our competitor was working on a feature on similar functionality. Myself and two of our engineers picked up the work around 9 a.m. that day and had it fully working with UI docs and a blog post by about 2 p.m. And that's fast, but I want to clarify that's not the typical speed to launch, which is probably more like two to three weeks or something smaller or one to three months for something larger. But what you're solving for is being able to react to an opportunity when it comes along and get something out the door quickly. So with that in mind, you don't want to slow down product launches or engineering, you want to keep moving. So in this scenario, my everyday reality, we want to get launches done as quickly as possible and make them as repeatable as possible.  That also means that your launches might not be as good, right? You might not have a competitive battle card or a landing page and that's okay. What's important is knowing when the launch is important enough that these things actually matter and then focusing on them then. So as I said, we can't always do everything for a launch. Let's talk about the MVP for a launch. It sounds clear to start here, but what do we actually mean by a future launch? Well, a future launch is when your product introduces new features or functionality or you make changes to your existing product or service. A launch could involve adding new features, improving existing ones, or even redesigning the user interface. And it's typically when these updates are made available to the public, though you might also launch functionality privately first to a smaller set of users. And so looking at what you actually need out of a launch, I could write a PRD for launches. This isn't that, but let's talk about this like a product. What's the MVP that we actually need? What's the minimum we need to get done to launch something? I think that there are three key requirements that need to be addressed. First, the functionality of the product must work as expected. How do we solve this? Tests. This involves writing and running tests to validate that the functionality is working as intended by conducting thorough testing any bugs or issues that can be identified and resolved before the launch get resolved so that you have a smoother user experience. Secondly, it's crucial to make sure that the user is actually aware of the launch and the new features or changes that are being introduced. Or else, why do you even bother with a launch? This could be achieved through something like a changelog, which is a document or notification that outlines any modifications or improvements made in the product. The changelog provides transparency to the users and helps set their expectations by clearly communicating what they can expect from the updated version. And lastly, it's essential to ensure that the user understands how the new feature is supported. This requires you as a PM to define clear launch phases, for example, how a feature goes from a limited release to a broader audience. Clearly defining launch phases helps manage user expectations of the feature. Let's talk about each of these a little bit more. First off, testing. Testing is a crucial aspect of ensuring the quality and reliability of a product or feature before its release. In my mind involves two main components, testing that you do before release, like quality assurance or QA, and testing that's continuous in the code and tries to capture new issues that might be introduced later, like unit tests. QA is a comprehensive process that involves testing the product as a whole to identify any issues, bugs, or unexpected behaviors with a new feature release. This could include functional testing, you know, does the feature work, usability testing, is the feature usable, and also security or performance testing. This lets you answer the question, does the feature work as intended? And especially for edge cases. Now, you might have a QA team, and they might be able to conduct these tests, but chances are if you're moving quickly with your launches, you might not have such a team, you might be much smaller, or they might not be blocking your launches, or at least not the first couple of releases you make. In that case, it's your job as a PM to effectively QA the project to yourself and test it in different scenarios and environments. On the other hand, continuous testing focuses on testing the product automatically when changes are made to ensure the proper functioning. For example, does this form submit if the user email address is invalid? This is usually testing each component or unit of code, so it's unit testing, but it might also be testing multiple units together, integration testing. These tests are written by developers in code, and they're meant to validate the behavior of specific functions or methods. They also are catching bugs, including security issues and ensuring correctness of your code base. When you hear developers talk about test coverage, they're talking about these. And more importantly, this lets you answer the question, is the new functionality that I'm introducing breaking any current functionality? There's obviously more than just testing, though, but I'm saying that testing is the MVP. So beyond testing, monitoring or metrics play a significant role in ensuring your product works as expected. Monitoring lets you respond to changes in how your product functions, by alerting your team if there's strange behavior in the product or potential issues with performance or availability. By finding and responding to these issues, you'll be able to proactively identify those problems. And metrics help you assess feature uptake so you can determine the success of a launch, but also gives you insights for future improvements. So for example, you might use Google Analytics or another tracking tool to understand where users click or what defaults they change in order to improve that user experience. All right, so that's testing. Next up, telling the user that a feature is launched. If a feature launches in the forest and no users are there to hear it, did it really launch? Your users need a way to know what's new in the product. A changelog is the equivalent of a pop-up notification or like a, you've got mail, ding. Informing users of a launch can't rely solely on marketing or something like an in-product notification. A user might read a blog post, but you can't expect every user to read every blog post. And an in-product notification could actually worsen the user experience. Plus it's something that the user can dismiss. A changelog needs to be a pull rather than a push model. The user should be able to access it at any time and see what's progressed in the product. When I joined TailsKill as the first PM, almost two years ago now, a changelog is actually one of the very first things I added. It was, you know, missing and we needed a way to tell users what was changing. So when do you actually need a changelog entry? Internally, I've written up a doc that's called do I need a changelog? And there's some extracts from it here on the slide. We add content to the changelog first if the user experience changes from what it previously was in any way. This isn't necessarily making, you know, a green button blue or moving it from the right-hand side of the page to the left-hand side, but if it significantly changes location or the user experience in the UI or the functionality is renamed, even if it's not new functionality, it needs a changelog. Another example here is if a default changes. If the default set of flags passed to the CLI change, so that the user who runs the same command tomorrow gets different results, then you need a changelog. And of course, you need a changelog if there's net new functionality. The other extract that I've included here is a warning that's in the doc. Basically, if you're changing anything user-visible and if somebody sent you this doc, then the answer is probably yes, you need a changelog. So what does a good changelog entry look like? A good changelog entry is specific. It has the specific dates the change was made or the version number where the change is available. It's not a summary of all the changes that happened this month. That's a blog post. A good changelog entry will have specific user problems that are addressed in that release rather than bug fixes. There's a bit of judgment here. You don't necessarily want to list every single bug fix. If you're not building a product for developers, your users might not be familiar with specific GitHub issues. The exception I would put for a vague statement on bug fixes is around security. You might not be able to disclose exactly what the fixes are when a release is cut. So being vague in that case is sometimes okay. And lastly, a good changelog entry has links for the user to learn more, like in documentation. In docs, the user can see how to enable, configure, use, or disable the feature. Again, there's a bit of judgment here. Maybe your product is not heavy on documentation overall. But nonetheless, you don't want the changelog to be serving itself as documentation. And a great changelog has a consistent format. A user might even be able to subscribe to it to get product updates. A common alternative to subscribing updates is something that marketing might be able to help with, like a monthly product newsletter. The last thing you really need in your launch MVP is to make it clear to the user how the feature is supported. This means defining launch phases clearly. It's a couple of things, terminology. Do you use alpha, beta, early access, invite only, or something else? Availability. At which one of those phases does the feature go public? And once you decide you need to stick to this, I feel like I struggle with this a lot. We have private alphas and public betas, but we might occasionally internally have conversations about public alphas. My pushback is, what's the reason we feel compelled to have a public alpha rather than a standard private alpha or public beta? If there's not a good reason, then deviating from the standard is just more confusing to users. Support expectations. When is the feature officially supported? This isn't just literal customer support, although it also includes that. It's about verifying that the feature works in most common scenarios, but also that it works in a bunch of edge cases like different platforms or languages or integrations, whether the feature has documentation and whether there's, yeah, customer support. For infrastructure products, which is, again, what I work on, this is often just, you know, can this be used in production? That's what the customer is really asking. And terms of service. This sounds silly, but it's a common oversight. You need to make sure that your terms of service cover features that are not generally available in any concerns that you have about sharing those features pre-release with users, like NDS. At a past job, requiring customers to sign a separate set of terms blocked me from getting sufficient users to give feedback on the product. So once you have these launch phases clearly defined, you should publish these on your website so that users know exactly what to expect at each stage of a launch. As an aside, I often see PMs mixing up launch phases with defining the minimum viable product, the actual minimum viable product I need here, not the MVP for a launch. You might hear PMs say that, you know, this is the beta scope or this is the MVP scope, but then it's not clear if there's more requirements after beta or why these requirements are tied to the beta launch phase. The standard requirements for beta or GA should be about how the product works and if it's supported across your environment, not about scope. So for example, you might always need audit logs for the feature of beta. Then if you're comfortable doing so, define generally when the MVP is expected to be completed. Say it's beta. You're saying you're not adding any other functionality from beta to GA or say it's GA. The other party that's going to have an opinion here is marketing. They'll want to know what phase to spend marketing efforts on. Again, I don't think it really matters as long as we're clear and consistent. So how do you make sure that you consistently launch products at each phase that have the same requirements? Launch checklists. These include the things that we just talked about, like tests and monitoring and engineering or integrations with other functionality of the product or whatever coverage you're committed to at each launch stage. So things like writing audit logs, adding new API methods or CLI commands. Giving a signal to the user that there is a launch in the product or in documentation including what release phase the feature is in. Documentation for the feature on how to use it, a change log entry and any other changes that you might need to your docs or website like adding the feature to a pressing page or a features page. These might not all apply at every launch phase and for every size of launch. Typically, you'll also define launch tiers with marketing so that they know where to focus their efforts, which is on the launches that matter. And to my earlier point, agree with them if you plan to spend more effort on certain launch phases like beta versus geo launches, which one is the actual big announcement that you're making? So for launch phases, there's a checklist you need with engineering of what's needed at each stage. And then depending on the importance of a launch, you'll have a separate checklist of launch artifacts that you need with marketing at each stage. And I'm saying keep the minimum for these very low, specific phases that we discussed, especially at early phases. You don't want to have a long list of things blocking you being able to get the product into customers' hands and get feedback. To make these launch checklists easy to get through in particular for the MVP requirements that you have for every launch, you need templates. Internally at TailsGal, I'm still working on some of these. Some of the templates that we have are just to remember specific items. So for example, for our blog post template, it's to get social graphics done and pick a permanent link. This isn't always important, but it becomes important when coordinating a launch with an external partner. So just doing this by default is best practice. I'd like to get some of these templates to a point where we have, you know, a poor version of a blog post in Mad Libs, so that worst case scenario, we can still use that, but we're not there yet. Right now, people are still writing every blog post, which is great. And even if you don't have templates, but you have someone who is responsible for or can help with certain parts of the product, then create intake forms for common things like change logs or feature documentation. Our change log intake form asks, you know, what is the change? When is it launching? And what component actually changes? All right, so we've talked about a launch MVP. Let's talk about when you might deviate from the MVP or need to define different processes. The first reason this happens is different kinds of launches. By different kinds of launches, I mean what's changing in the product. This is really about the surface area of your product. In the simplest case, your product might be a static web app, and the only thing that can change is the app itself. You roll out this change simultaneously to all users, or maybe you use Feature Flag, so test it with a few users or gradually roll out the change. But in a more complicated scenario, you might have a web UI, desktop or mobile applications, and backend changes to the API, your database, whatever. These all have changes, some of which might be user-visible, and all have slightly different rollouts. So my suggestion to you here as a PM is to first understand how these rollouts differ. Do you always use Feature Flags? How frequently do you release your desktop or mobile apps? How does versioning work? This matters because you might not have the ability to change the timing of some of these, like when the app's tour approves your app. And you need people to be ready to and launch and respond to changes when they occur. A change in the web UI might take you minutes, whereas a change to an app might take weeks. Then identify the standard way to roll out changes for each component, and when you want to tell a user about a change. So, for example, at Tailskill, we roll out web changes behind a Feature Flag, and we drop the Feature Flag at launch. For apps, the launch is when the change lands in the stable app release. And lastly, I'd say to ensure the engineering team understands what kinds of changes to the backend you consider user-facing and so need to be treated like a launch. For us, things like new API endpoints should get the launch treatment. The second main input to how you'll define your launch MVP is what kind of product you're dealing with. Specifically, I mean B2B versus B2C products. These have different users who have different expectations about how the product they're using changes. Consumers might be happy or even excited about a new feature, even hunting for Easter eggs, trying to see what the new UI looks like in that app. Businesses, on the other hand, just want to be told what to expect. But I don't know, that's not always true. Even consumers want to know about changes. Has your favorite pair of jeans ever changed its cut and you were surprised or annoyed to find that it was different? I bought a new jacket a few weeks ago and I was really annoyed to find that it fit differently than the last one, the exact same one from the same company. And I went online at the reviews and they all have the same complaints on the new cuts and sizing. Another special case to call out for Enterprise is regulated industries. They'll have specific expectations and may even need changes to go through review or certification processes before they can use the product. But let's talk a bit more about Enterprise, just in general, since that's what I focused on. What do enterprises need as part of a launch or as part of your product to make launches easier? You already know that the first thing I'm going to say, which is the change law, but there are other things that you might want to consider working on as well. First is the change policy. This lets the user know when you would change defaults or deprecate features and how you'll notify them of these changes. So, for example, you might tell your customers that you'll support the feature for at least another year or you'll support the last few versions of clients, including providing security updates. Automated updates. You know how you get out of supporting those old versions or need to provide security updates to those old versions, which is not necessarily a great use of your engineer's time. It's automated updates. If you make it easy for users to keep up to date with the latest versions, many of them will. For apps on the iOS or Android app stores, this is done for you automatically. I saw the other day that Docker desktop now requires you to update or upgrade if you don't want to update. That means they've made not updating an enterprise feature of the product. Clearly defined security guarantees. If you're explicit about what security you expect to have and that you can't make changes that will weaken that security, it'll help your customers decide what their risks are. When it comes to security in general, you build trust through transparency. And lastly, things like trusted testers. It's hard to get businesses to test new features as part of their work because they don't want to have any issues. They don't want to encounter any issues as part of their live production environments. So work with your users to develop test environments, or when you find users who are willing to test lots of features, involve them more deeply in something like a trusted tester program where they get early access to features, can provide feedback directly to your team, or have other perks. With all of these restrictions on how I make changes, can I even do any experimentation? And this is another area that B2B and B2C really differ. Since B2C users are more amenable to changes, they're also more amenable to experimentation.  You might have other restrictions, though. For example, you can't really test different versions of your apps if they're distributed through an app store. You can use something like TestFlight to get early access to things, but it's not different versions. That you would get from A-B testing on the web. Instead, you'll need to build new testing and feedback mechanisms. In particular, think about how to get earlier versions of the product, especially when they're still in ideation, into folks' hands for testing. So for example, working with user research on things like mockups. And lastly, we'll talk about improving your internal processes so that it means you can actually ship fast. First and foremost is communication. You need coordination and communication between PM, Eng, Design, Marketing, Docs, DevRel, and others to figure out when a launch is going out, the status of the launch, and any requirements needed for that launch. This isn't easy. This is actually the hardest thing we've been talking about today. There's no silver bullet here. But I would ensure a couple of things. You want to ensure that you made it easy for someone to know the status of a launch. There should be one place where anyone who's involved can go and see that status. That you communicate out regularly on the status of various launches, especially when something major changes. Does a contract fall through the day before the launch? Everyone needs to know as quickly as possible. And this is where the launch phases and the checklist we talked about earlier really matter. Being clear and consistent on status and on what's missing. Changing the launch phase, the MVP scope, the requirements, the name of the feature, the launch date, et cetera will all confuse folks. Some of these things will change. These changes should be material changes. They shouldn't just be you changing the definition of author requirements. And just in general, over communicate. If you think you're communicating too much, you're probably not and do it some more. Just over communicate what's going on with your launches. Second is making it easy for anyone internally to edit and contribute to things. I've worked in a few different tech companies now as a PM. In one of them, I couldn't edit documentation directly. And it drove me absolutely crazy. I had to file a ticket and it would always end up being lower priority than something else. It thankfully never delayed any launches that we had, but really frustrated me. As a PM, it's your job to unblock things and to help get things done. I've written docs, I've written blog posts, written code, given conference talks, or written in other people's conference talks, made slides for them, everything.  That doesn't mean no review process. It means not blocking on the process to get a first draft done. It also means that if you're not comfortable editing markdown, learn how to edit markdown and get in there and start editing things directly. Or move to a system that you do feel comfortable editing and more folks feel comfortable editing, including, for example, your support team. Next is building a really strong engineering foundation so that you can make rapid changes when you need to. That means building the monitoring testing that we talked about earlier to proactively identify and fix issues before they become problems. I know, I'm repeating myself, it's boring. But that also means refactoring old code to be more readable so folks can more easily jump in and contribute. If you're trying to make a very hectic last-minute change, if your engineers are spending a lot of time figuring out what's going on in the code base to begin with, it's harder for them to make that change. If you've spent a lot of time continuously editing that, keeping it up to date, it's much easier to make incremental changes to your code. You can't always move fast. Sometimes you have to go slow to be able to move fast, again, when it really matters. And lastly, pointing people at the right problems to work on. As I mentioned earlier, I'm often running behind engineering right now at TailsGal, the catch-up to new functionality we're working on and new launches that we have coming up. We don't always write a purity for every feature. What makes this easier though is pointing engineers at the top problems or issues that you're dealing with. Sharing customer conversations or notes with them, maintaining a backlog so that if somebody has extra time, they know what they could help you with if they picked up. Maintaining and sharing your backlog on a regular basis. You might also do regular issue triage to continuously address the top issues that are being reported. Go through support tickets, see what's going on. Tell folks what matters, why it matters, and help them prioritize how to spend any extra time that they have because people really do want to make your product better. They just need to know what to go work on. All right, that's it. So let's recap what we covered today. As your development team is moving quickly, you want your launches to keep up. As a PM, you need to figure out how to get the minimum set of things done for a launch to be viable. What you need to do to unblock the launch and get it up a tour in such a way that folks can just keep moving. A launch is any change that is user-facing to your product. It could be a change to existing functionality, it could be net new functionality, and you have to define that line internally for yourself exactly what that means. At minimum, launch should have tests to verify the functionality works as expected, should have a change log to notify the user of changes, and should be clear around the support expectations with defined launch phases that clarify what you'll have working and integrated at every single launch, when documentation will be available, when the support team will support a launch, that kind of thing. Launches might be different for a couple of different reasons. They might look different or happen at different speeds depending on what product surface you're dealing with, like front end versus back end changes. And different users will have different expectations around launches, like B2B versus B2C users. B2B users are much more demanding as to what a launch is or changes in their environment, and will want notification and tools to help them keep up to date with changes. And lastly, to keep people moving quickly, you need to over-communicate about upcoming launches. Tell people what's coming up, where they can get status on what's going on. Make it easy for folks to contribute to your launches, including documentation, and have a solid engineering base to work on so people can make those fast changes. Thanks for joining this talk, and I hope you learned something new about quickly moving through product launches.