1) What problem are we solving? 2) Who’s the target audience? 3) What are we designing for Native app or Web app? 4) Who are the competitor? 5) What are the requirements? 6) Bonus - Is there a current design systems?
Under Requirements, it's also good to know if there are any legal, industry standards, or safety requirements that might constraint your design. Also future considerations. This may be a stand alone build now, but will it have to interface with anything in the near future that might influence the design today? It's a lot easier planning for those things in the beginning than having to unravel and patch up the design later. When timeframes could be a lot tighter. And speaking of tight timelines, knowing what features you can safely removed from a project and still have a viable, though less functional produt to deliver on the deadline may also good to know, if that's an option. That way you can design with those features isolated so they can be safely and swiftly removed if you have to narrow your scope to meet a deliverable date. Then the feature can be added back in on a subsequent version.
in addition to these great discussion you've put up here, i want to ask if it's right to ask clients what their budget is for the project to see if their budget is good enough for me or if we have to negotiate about increasing their budget?
Hey mike, technical question here, how do u organize ur artboards whether in sketch/figma/xd, so other design team members could easily read the screen flow? thanks
So basically holding the stakeholder hostage for almost 2hrs and asking 30+ questions is totally unnecessary? Because I AGREE with u..lol. I believe just a few key questions are needed. Just wondering if you can expand on why long and drawn out interviews aren't necessary.
@@MikeLocke Thank you. Very helpful videos, as usual. But I think there is some difference though especially if we're designing something for a "Product Porfolio" few more aspects should be considered. But in general I agree it's the same
@@MishaRGB Are you referring to physical products? In UX, there are technically only two separate roles...1) UX Designer (aka Product Designer, Interaction Designer, UI Designer, etc.) and 2) UX Researcher
@@MikeLocke Not physical. For example, in our portfolio, we have 20+ features combined in a single product, everytime when I start working on the new features I have to keep in mind all existing features to avoid "negative crossing" (eg. Role management), or not duplicate already existing functions
1) What problem are we solving?
2) Who’s the target audience?
3) What are we designing for Native app or Web app?
4) Who are the competitor?
5) What are the requirements?
6) Bonus - Is there a current design systems?
Super helpful! Thanks for sharing
Under Requirements, it's also good to know if there are any legal, industry standards, or safety requirements that might constraint your design. Also future considerations. This may be a stand alone build now, but will it have to interface with anything in the near future that might influence the design today? It's a lot easier planning for those things in the beginning than having to unravel and patch up the design later. When timeframes could be a lot tighter.
And speaking of tight timelines, knowing what features you can safely removed from a project and still have a viable, though less functional produt to deliver on the deadline may also good to know, if that's an option. That way you can design with those features isolated so they can be safely and swiftly removed if you have to narrow your scope to meet a deliverable date. Then the feature can be added back in on a subsequent version.
🙏Thank you so much!
Awesome man, keeping it straightforward and valuable!
So helpful, Thank you, Mike !!!!!!!!!!
You continue to be amazing. Keep up the great work!
Agree with all of this 👍
Very helpful thanks Mike!
in addition to these great discussion you've put up here, i want to ask if it's right to ask clients what their budget is for the project to see if their budget is good enough for me or if we have to negotiate about increasing their budget?
Hey mike, technical question here, how do u organize ur artboards whether in sketch/figma/xd, so other design team members could easily read the screen flow? thanks
So basically holding the stakeholder hostage for almost 2hrs and asking 30+ questions is totally unnecessary? Because I AGREE with u..lol. I believe just a few key questions are needed. Just wondering if you can expand on why long and drawn out interviews aren't necessary.
What is the key difference between UX and Product designer? Your opinion. Thank you
They’re the same, just different titles. Product Designer is the more trendier term.
@@MikeLocke Thank you. Very helpful videos, as usual. But I think there is some difference though especially if we're designing something for a "Product Porfolio" few more aspects should be considered. But in general I agree it's the same
@@MishaRGB Are you referring to physical products? In UX, there are technically only two separate roles...1) UX Designer (aka Product Designer, Interaction Designer, UI Designer, etc.) and 2) UX Researcher
@@MikeLocke Not physical. For example, in our portfolio, we have 20+ features combined in a single product, everytime when I start working on the new features I have to keep in mind all existing features to avoid "negative crossing" (eg. Role management), or not duplicate already existing functions
@@MikeLocke Hey Mike I have a hard time coming up with personal projects to work on for my portfolio, any tips on how to make this easier?
Can you be my mentor. An an entry level UI UX designer