Collaborate on Invoice Wording Examples for Product Management with Ease Using airSlate SignNow

Invoice wording examples for Product Management

hey yo it's khloe recently i have been doing a lot of talks with college students from all over the nation and one of the most common questions i get is hey chloe i am interested in being a product manager but what is it that you even do the product manager role is definitely one of those really buzzy and cool jobs to try to go after it is highly sought after it is well paid and it is very respectable in the world of tech so today i am here to tell you what it is that i do on a day to day as a product manager so let's get started [Music] welcome to my channel colors of chloe i am a product manager and i work in the creator space i have built features for many years now and i have worked at boeing google caffeine facebook and now at tick tock so now that's out of the way let's talk about what a product manager does the one thing that we do really is that we launch features to make our users happy our role is really at the intersection of user experience tech and business we are really involved in crafting the look and feel of the experience we have to understand what are the technical costs and what the tech debt is to help us prioritize what features to work on and then we have to be very very in tune with the roi is for the business whether that's in revenue or user growth or safety or pr we have to know how it benefits us as a business though i really like to think about product the way that todd jackson who's a vp of product at dropbox has put it pms are responsible for number one articulating what a winning product looks like number two rallying the entire cross-functional team to build it which is a really hard process and number three iterating until we get it right so how it starts off is like we really have to understand how product is broken down into features and experiences like you're not just a product manager of google you're not the product manager of airbnb you are staffed on a specific product team that owns a very particular product experience i couldn't quite understand this concept for a really long time until i started to understand how org charts are created oftentimes companies will separate different types of product teams based on like different user experiences or maybe the different buttons that exist on your platform or maybe a combination of both so if we're separating teams on different user experiences people can be staffed on product teams that own the creator experience or user growth or ads and monetization or the creator insights team or even the viewer experience team if you think about it from a buttons perspective there's pretty much a product team for every like cluster of buttons that exist like there's a team for the share button the go live button the notifications that pop up the admin settings panel the feed team the event creation flow if there's any features that you roll out as a pm that impacts other teams which often times it does you have to make sure that every team is okay with what you're launching because sometimes your feature might take away from another feature for example rolling out instagram stories probably took away from instagram posts you know there are always these product trade-offs to think through [Music] so let's pretend that we're on the creator experiences team and usually your leadership which refers to your executives on the team they set a north star that you have to aim for these are your metrics of success that you're measured against this is a really important metric to understand and to define so i read this somewhere but basically once upon a time slack used to measure their north star on the number of spaces that users created and that's not super meaningful because like what if you have a bunch of spaces that people create and nobody engages with them that's not really valuable you have to really understand what the magical moment is within the scope of your product team and the users that you're serving what is the aha moment for slack's case it's really getting to that point where you're collaborating and working with your teammates that's what slack is all about so they change their north star from raw number of spaces created to something more meaningful which is their activation milestone and that is like getting a space to have three members and 3000 messages sent and this is not random which a lot of companies do which is pretty bad but slack really did very deep analysis on what their threshold is for what spaces that exist that have really great retention and they find what correlates to that this is just like facebook's aha moment where facebook try to get as many users to reach 7 friends in 10 days this is the point where your users finally get it if you know what i mean so we as the product managers have to really understand number one who our users are what are their user personas how do they behave what are their demographics what do they like what don't they like what are their pain points and what prevents them from reaching the experience that we want them to have then the next step kind of is like putting together design workshop where you bring in all your cross-functional partners we call them xfns and we whiteboard out all the different user profiles and then we figure out which ones are most important to our team and then we analyze these specific personas and we're like can we come up with a set of people problem statements to understand their pain points then you brainstorm all that you prioritize which ones that are important for you right now and then for every single pain point for every single people problem you brainstorm all together what are all the different feature solutions that you could implement to solve their problems so let me pause right there and give you an example and this is really outdated but a people problem could be as a new facebook user i have a hard time finding friends who are already on facebook and then from that people problem you can come up with all kinds of solutions like it could be adding a suggested friends list or in the account creation process you can import emails or contacts from your phone you can also browse other profiles based on your network your school ultimately you want to come up with feature solutions that solve the root pain point that can help move the needle on your north star does that make sense and then after you have all these ideas you prioritize you ruthlessly prioritize and then you build your roadmap and then once you have your roadmap you start working on the individual features and you scope out the product with your xfns you work with uxr partnerships data product operations engineering and ux in the understand phase you really have to deep dive into every single part of this feature you build the design mocs with your designer and your copywriter or your content strategist and you simultaneously work with your data team to understand the success metrics and you put all of that into what's called a prd which is a product requirements document this is your main direct deliverable i mean your deliverable should be launching the product and making users happy but like the thing that you have to write up yourself and you own is this document but once you have that done you go through so many rounds of review it's insane you just have to make sure that this feature is a net positive in the grand ecosystem of things within your product and that takes really deep understanding of your product so it's best that you have a deep interest for the product space you're working in after your billion reviews then you hand it off to engineering to do their own technical review they figure out end time edge costs who needs to do what is a client-side server side you have to decide whether or not it needs a b testing and after you're ready to release like at least the v1 you have to go through qa testing release testing launch planning we usually don't roll out features at 100 all over the world we have to come up with a way to test it in a small environment first and then if everything's gucci then you roll it out globally and you have a launched feature you have to work with data really closely to make sure all of your events are logged so that you can come up with proper analysis and once you've launched we make sure to celebrate and then after a few weeks we come up with a report out of the results as well as a postmortem for what we could have done better and the whole process just kind of repeats so once your career progresses you kind of just work on features that are bigger and bigger and you work on like big bet features because we want to venture into like a new space and yeah that's pretty much the job if i had to break down my job um it would just be a lot of meetings and a lot of writing it's like 60 meetings 30 documentation like i have a hundred tabs on chrome that there are different documents or spreadsheets or design files it's a lot and then 10 group chats like for real especially because we're remote now i wake up to probably anywhere from 100 to like 400 messages in my group chats and not all of them are that important but it's important for me to be in a lot of these group chats and then respond back to stakeholders to get back to them when things are being released why something wasn't prioritized why something is prioritized and then just sending them the documents that i constantly pump out so that's a lot of discussion and deliberation i know that sounded like a lot but i really do enjoy being a pm out of all of the various roles that i've had in my career being a product manager has been my favorite in a future video i will share exactly why i love being a product manager so stay tuned on this channel if you liked what you saw today do join this community we welcome you with open arms to learn about all things career in tech and the creator space come by twitch for my co-working and co-studying sessions and that's it thank you for sticking around i hope you have an excellent day or evening wherever you are and i will see you next time bye [Applause] [Music] [Applause] [Music] you