Revisit designs and another round of testing You have a working prototype with feedback. Now it’s time to revise your designs, and analyze what worked and what didn’t. Don't be afraid to create a completely new wireframe storyboard and make a new prototype. Starting over can create a better flow than trying to move things on your earlier prototype. Try not to be too precious of it because it is just a prototype. Once you are happy with your designs you can test it again and refine it some more. In cases where the prototype didn’t hit the mark at all, well you might think the project has failed. In actual fact it hasn’t. You've likely spent less development time than if you had actually built the design and you know more bout what user's actually like. With design sprints we have a philosophy where you either win or you learn, so don’t beat yourself up too much if the idea didn't work as planned.

google / WebFundamentals

Former git repo for WebFundamentals on developers.google.com

Apache License 2.0

13.85k stars 2.56k forks source link

Revisit designs and another round of testing You have a working prototype with feedback. Now it’s time to revise your designs, and analyze what worked and what didn’t. Don't be afraid to create a completely new wireframe storyboard and make a new prototype. Starting over can create a better flow than trying to move things on your earlier prototype. Try not to be too precious of it because it is just a prototype. Once you are happy with your designs you can test it again and refine it some more. In cases where the prototype didn’t hit the mark at all, well you might think the project has failed. In actual fact it hasn’t. You've likely spent less development time than if you had actually built the design and you know more bout what user's actually like. With design sprints we have a philosophy where you either win or you learn, so don’t beat yourself up too much if the idea didn't work as planned. #9007

Open SeymurPasha opened 4 years ago

SeymurPasha commented 4 years ago

Welcome! Please use this template for reporting documentation issues on https://developers.google.com/web/.

For questions about Chrome DevTools, checkout the google-chrome-devtools tag on StackOverflow. For questions about Chrome, check the google-chrome tag. If you think you've found a Chrome bug, check out our feedback page for more details on how to file it.

Page Affected: https://developers.google.com/web/TODO

What needs to be done?

Please provide description of what's needs to be done here. Please be sure to include the link to the original page and any supporting links/data.

[x] Appropriate type-something label has been added.
[ ] Appropriate section-something label has been added.

SeymurPasha commented 4 years ago

. You've likely spent less development time than if you had actually built the design and you know more bout what user's actually like . I just noticed while reading that there is a typo in sentence above ("bout what user's..."). Seems like should be 'about' instead of 'bout'. Hope by opening this issue I helped and didn't annoy you.
Thanks

SeymurPasha commented 4 years ago

here is the link: https://developers.google.com/web/fundamentals/design-and-ux/ux-basics