Streamline project pipeline management in NDAs with airSlate SignNow

How to create outlook signature

tools and the workflows is under NDA but I saw the opportunity to share the processes and what I did in different stages of a Project Life Cycle the idea was that we already speak about the work done in the resume so I will present it visually just expanding on those bullet points and not showing the company's IP that sounds smart enough already right it's abstracting it it's showcasing something which is general which doesn't really have any IP to it so let's see exactly how AR did [Music] that and this portfolio as the others come from Design Squad Community if you're new to this or you don't know what it is make sure to join there's definitely a link Down Below in the description where people can meet like-minded designers researchers strategists product people or techies there's a lot in it and I think it's one of the biggest Discord communities for product design and research out there so why not anyhow what I'm going to review today for is a portfolio from AR deep AR deep is a product designer of management and Leadership experience he helped scale two startups currently upgrading their skills in postgrad diploma IT project management and looking for full-time roles in Canada specifically during my time with a startup I created more than 500 screens for their internal dashboards with multiple users I contributed from inception of user stories to the final mockups so let's see exactly how AR did that the project entails creating a white label SAS platform vable designed for higher higher education institutes weable serves as a Global Hub connecting students employers and institutions to unlock opportunities worldwide now I'm just going to quickly go and Google vable okay so weable is weable is actually a brand it's not necessarily a feedback for Rd but for everyone else cuz sometimes when you create a wh label tool you can Rebrand it you can literally save it this make it look different especially if there's IP you can abstract and blur things out you can Rebrand the actual product and name it something else create a new brand and just be explicit that you did it it's simply taking away from the actual brand and making it the actual project and displaying is just as a project not related to a brand specific details of the work undertaken cannot be disclosed however this case study will focus on methodologies and approach perfect except I would probably make that first thing somewhere the actual positioning or where you put that message it doesn't really matter but I at least like that you put that and made it explicit I would maybe even make it stand out more visually small thing cosmetic thing but so it cannot be missed basically you know because again hiring managers are going to be like okay okay what what is this what am I looking at uh this headline that headline what does that say connecting and mapping the details very quickly so make it easier for them so they don't miss that block out and again they're not going to read it as a book They're going to skim it and then look into the detail and and look deeper pH Health lead product designers uh I think you should just say lead product designer cuz that higher educational portal is all redundant we know exactly what it is tools irrelevant and why I say it's irrelevant because everybody is using those tools it's redundant tell me if you use any Design Systems tell me to what extent tell me how big is the design system tell me if you needed to maybe do some branding tell me something technical instead of just giving me a logo of the tool because again they don't really matter everybody knows them or should know them you might be a pro in figma but who the hell cares ux is not the tool project timeline uh contribute lead different phases of the startup I like that you you're being explicit that okay this is free blocks and that's about it fair enough not going to even question that that's great but the time frames would be interesting to know as well because this could be 4 weeks or could be 4 months or could be 2 years or could be 10 years you spend doing it that would be very interesting to understand and it's going to position the project and give context necessary to proceed and Frame It product vision vable is pioneering platform that unites students employers academic ins ution wall fostering Innovation resilience things of that nature and this is fair enough but I would want it to be expressed visually maybe could you show it in some sort of visual ways could you give a storyboard perhaps of what happens in product design and ux strategy and product strategy generally visioneering or Vision typing it unlocks so many ideas and clearly showcases exactly what's different about it because I can't still tell all of this Vision it makes sense to you or maybe weable but it doesn't make sense to me just yet I would need to kind of look at it go back and forth we could simplify it and make it easier for anyone so there's quite a few different users uh higher end admins employer students advisors mentors varable admin it doesn't give me enough but tells me about their needs in the abstracted way you know without giving me specifics at least I know that archdeep understands that they're different that segmentation was done that there is some sort of thinking of how to approach them so this is great of course I would want to know more but that's where archdeep could be like hey do you want to find out more give me a ring I would ask them in the interview of how they approach so many segments who were the primary who were the secondary to what extent what was it phasing like maybe you had some sort of goto Market strategy of where you approach certain segments first when secondary when there was some sort of strategy to that that would be very curious to learn about and I would ask especially because AR is senior I would be quizzing them as a senior you kind of need to think about those themes and give me a good informed answer kind of like of what would happen in a real project of course not giving out what's under NDA so you did research service mapping product strategy as part of that initial phase quantitive and qualitive methodologies service mapping and as you can see this is a good demo of how a hiring manager would view this you look at the balen thing okay this is what you did identification of features that align if our business goals and stakeholder needs fine that's good enough again it's so abstract so it's hard to critique but that's a good example of what NDA Cas study could look like because you know I could critique them in the actual interview or find out more there product road map and backlog after a product strategy development realistic road map for the launch of a platform prioritize product backlog things of that nature and you show the actual mockups of the things the design phas followed by information da da da and then high so all of it sounds very waterfly that would be a bit of a yellow flag to me or I would question that a lot because you kind of say okay this is so linear and I said that bullet points are great for scanning but for the story they might not be so you might want to consider how to merge it and say again I'm not going to solutionize it for you and maybe you didn't do it then that's fair enough but if you did act iterative agile approach creating wireframe testing with the users and then creating High Fidelity mockups or when back and forth you should mention that don't just say we did lowf and then high five and then we did something else it's never that static in ux projects anyways so you can be honest and say that you use different Fidelity of approaches to create wireframes and mockups by learning from the users especially because design is never that you take it away or it shouldn't be that you take it away do it in isolation and then show up with the mockups right in the prototyping and feedback you state prototypes were created for each Persona to capture maximum feedback from all users what is maximum feedback that could mean so many different things I have no idea what that means need rephrasing at a minimum can you tell me that you interviewed all the segments equally so that everything is covered and you don't miss out or on something or something along those lines like it's abstracted the wrong light in my head cuz that could mean anything it could be d for example maybe that's what could go through hiring manager mind until we know the details how could you shed a bit more light or rephrase that and then you have Handover of design which I think you could just merge into again bullet points make it easier but product reviews were undertaken with the co CTO I think you could just create a storyline for this that you closely worked with CTO and CEO and maybe this could have been the first thing as describing exactly what you worked with stakeholders and these were XY Z the Handover of design doesn't really matter now to me from someone who has hired a lot of designers when people mention Handover it usually means that it was limited contract or freelancing opportunity or was way too short cuz ux continues ux is done but done enough so you can continue and do more ux basically right so I would question that like what happens next I think you can make it a bit more Punchy of how you finish your story here give me some results weable byway for everyone is a brand right like as we saw a lot of it is available online can you talk a bit about Delta from before and after even if you cannot give me specifics what change maybe user engagement improved maybe user saw improvements and so sort of ux factors I don't know usability credibility trust something else improved on that these are General and abstracted terms but you can talk about it because it's a result of something you did for that company without giving IP so you can tweak that story a whole lot especially if you're involved in it and you deeply wear part of the team and things of that nature you can capture a lot of that and another thing to point out for AR deep is give me a call to action there's no more call to action I don't want to view more of your case studies because to be honest I see that AR is confident in their messaging and probably has the experience again it's to be see because it's NDA it's abstracted I need to talk to them but I would yeah be like let's talk I'm going to invite you for an interview let's chat basically let's find out if there's a match but view more case study isn't that and it's also I thought it's clickable but it's not so it kind of leads to next or before add a big button saying contact me now because you don't know which case study is going to make them think about talking to you make it this one make it any of them make sure that there a big call to action here which says want to find out more give me a ring or email me or contact me now or something along both lines and for everyone else I just want to call out one thing and one thing which is super important get inspired from this because there is so much good stuff in here of how to abstract it and what you could show but consider that this is n equals 1 case it's One Singular case they know exactly what they can show and what they shouldn't show don't make a mistake just copying what they shown because you need to find out exactly what you can show these are a lot of good messages at an abstracted terms level but you should always double check you could create a case study like that a draft in a PDF and send it to a product manager or that CEO or CTO and say hey could I show this on my portfolio I'm not giving away too much I'm abstracting it I'm not giving any IP is it okay with that message just asking them clearly it's always a good idea to just double check it and same applies for AR deep I would just say hey have you checked it um if you did happy days it's great and I like this approach again for abstracting and showing some things because you want to kind of invite for more conversation and actually any other case study you want to you know start conversations you want to kind of have the foot in the door so that the hiring manager would be like yeah I want to talk to them and as per usual check out my other videos on ux portfolio review I'm going to leave at least one floating somewhere here so click on it watch it it certainly helps and on that note I'll see you next time case study one thing I need to call out and give feedback to archdeep and everyone else really AR Deep's portfolio is pretty good it's clean it's effective it showcases all the different project it has a work about LinkedIn resume links and things of that nature you know it's decision to show those things and we have some information about it but here's the thing every time you go to a case study or every time you want to go back to work you're presented with this different apography being changed for no particular reason fancy but quite poor usability especially when the low time could be instant that's one ux issue with that and it's a meta issue as well of course it might not prevent you from getting interviews but if a hiring manager is considerate about accessibility or actual just general usability the loading speeds things of that nature we might kind of be like hm maybe ARP is not the right candidate keep it simple basically don't go overboard motioning everything or animating everything and a small thing on that too is navigation should really show the active thing for example the first time I looked at the portfolio itself I was like am I on work or am I on about BAS which state is active you should indicate that that's small things out of the way with a profol let's jump into the actual case study