Downloaded 15 times
![The metrics
Google Analytics
[ data image removed]](https://image.slidesharecdn.com/talk-webbeyond-121002053423-phpapp02/75/The-Web-and-Beyond-Chrissy-Welsh-19-2048.jpg)
![The metrics
Our own server
[ data image removed]](https://image.slidesharecdn.com/talk-webbeyond-121002053423-phpapp02/75/The-Web-and-Beyond-Chrissy-Welsh-21-2048.jpg)
Uploaded byChrissy Welsh
The Web and Beyond - Chrissy Welsh
This document provides a quick start guide to Lean UX. It outlines organizing hypotheses, aligning ideas with brand goals through wireframes, rapidly building rough prototypes, and using metrics to determine if ideas should be developed further or discarded to allow for failing fast. The goal is to get ideas in front of users quickly to learn what works best and focus efforts accordingly.
More Related Content
![[DevDay 2017] Productive Programmer - Speaker: Dung V. Nguyen - Developer at ...](https://cdn.slidesharecdn.com/ss_thumbnails/dungvnguyenproductiveprogrammer-170420093355-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to The Web and Beyond - Chrissy Welsh
![Intro to Lean UX: How to do it quick & dirty - Workshop [6h]](https://cdn.slidesharecdn.com/ss_thumbnails/leanuxworkshopjun27slideshare-150627135940-lva1-app6892-thumbnail.jpg?width=640&height=640&fit=bounds)
The Web and Beyond - Chrissy Welsh
- 1. Failing fast forQuick Wins The Lean UX Quick Start *Not a definitive guide (& never take yourself seriously) just a place to get started.
- 2. Failing fast forQuick Wins The Lean UX Quick Start *Not a definitive guide (& never take yourself seriously) just a place to get started.
- 3. Failing fast forQuick Wins The Lean UX Quick Start *Not a definitive guide (& never take yourself seriously) just a place to get started.
- 4. Failing fast forQuick Wins The Lean UX Quick Start Chrissy Welsh Senior UX/UI Designer Cloud9 IDE *Not a definitive guide (& never take yourself seriously) just a place to get started.
- 5. The calm beforethe storm Organise Write out your hypothesis as a collection of ideas •These can be big ideas or small change it doesn't matter •Invite your peers to also contribute to the document •Keep it simple
- 6. The calm beforethe storm Organise
- 7. The calm beforethe storm Organise
- 8. The calm beforethe storm Organise
- 9. Alignment check Compatible with your brand Spend some time with your product manager/CEO •Decide what is important for the companies goals •Those hypothesis that align with those goals are floated to the top •This becomes your work list
- 10. Alignment check Compatible withyour brand
- 11. Alignment check Compatible withyour brand
- 12. Wireframe your logic Check its possible Speed is important, go for low-fidelity •Whiteboards •Paper •Balsamiq •Invisionapp
- 13. Wireframe your logic Whiteboard
- 14. Wireframe your logic Paper
- 15. Wireframe your logic Balsamiq
- 16. Wireframe your logic Invisionapp
- 17. Build time Think rough and ready Its now time to get it out the door •Speed is still important •Build what you can yourself •If you can’t? Make your developer your best friend •Good build tool? Adobe Creative suite, Sublime, Cloud9 IDE
- 18. The metrics Keep it or ditch it? Metrics and measurements •Web changes - google analytics •Behavioral changes - clicktale •In app changes - our own server •10%+ your on a winner, develop it further
- 19. The metrics Google Analytics [data image removed]
- 20. The metrics Clicktale
- 21. The metrics Our ownserver [ data image removed]
- 22. No Fear Sometimes you gotta let go! Do not fear failure, failing fast means you can move on •If it didn't work - let it go •Do not be tempted to continue
- 23. No Fear Sometimes you gotta let go! Do not fear failure, failing fast means you can move on •If it didn't work - let it go •Do not be tempted to continue 80% of results are seen in the first 20% of effort/work. Only small gains are made there after
- 24. The recap What was all that again? •Organize & Hypothesize •Align check your brand & its goals •Wireframe your logic •Build it rough and ready •Keep it or ditch it •No fear - you can and should let go sometimes
- 25. The software What can you use? •Hypothesis- Google doc spreadsheet •Wireframing - Whiteboard, Paper, Balsamiq •Prototyping - Invisionapp •Building - Cloud9 IDE, Sublime, Adobe Creative Suite •Metrics - Google Analytics, Clicktale, Our own engine
- 26. Any Questions? The Lean UX Quick Start
- 27. Any Questions? The Lean UX Quick Start Chrissy Welsh Senior UX/UI Designer Cloud9 IDE
Editor's Notes
- #2 Hello... what an attractive bunch you are!\n\n… and this is me (weird face picture on slide)... or more accurately me.\n\nI don't think you need 1 more person telling you what Lean UX is (or what it isn't for that matter), you can find that out by a quick google yourself. This talk is for the doers, this talk is a\nbout getting stuck in, and its about getting started. So if you like to roll your sleeves up and get dirty - you my friend are in the right place.\n
- #3 Hello... what an attractive bunch you are!\n\n… and this is me (weird face picture on slide)... or more accurately me.\n\nI don't think you need 1 more person telling you what Lean UX is (or what it isn't for that matter), you can find that out by a quick google yourself. This talk is for the doers, this talk is a\nbout getting stuck in, and its about getting started. So if you like to roll your sleeves up and get dirty - you my friend are in the right place.\n
- #4 Hello... what an attractive bunch you are!\n\n… and this is me (weird face picture on slide)... or more accurately me.\n\nI don't think you need 1 more person telling you what Lean UX is (or what it isn't for that matter), you can find that out by a quick google yourself. This talk is for the doers, this talk is a\nbout getting stuck in, and its about getting started. So if you like to roll your sleeves up and get dirty - you my friend are in the right place.\n
- #5 Hello... what an attractive bunch you are!\n\n… and this is me (weird face picture on slide)... or more accurately me.\n\nI don't think you need 1 more person telling you what Lean UX is (or what it isn't for that matter), you can find that out by a quick google yourself. This talk is for the doers, this talk is a\nbout getting stuck in, and its about getting started. So if you like to roll your sleeves up and get dirty - you my friend are in the right place.\n
- #6 Hello... what an attractive bunch you are!\n\n… and this is me (weird face picture on slide)... or more accurately me.\n\nI don't think you need 1 more person telling you what Lean UX is (or what it isn't for that matter), you can find that out by a quick google yourself. This talk is for the doers, this talk is a\nbout getting stuck in, and its about getting started. So if you like to roll your sleeves up and get dirty - you my friend are in the right place.\n
- #7 Organise - now although i just told you to get stuck in you have to know what your getting stuck into. This is the part where you write out your hypothesis. It does not have to be pretty it just has to be understood as a collection of ideas. This is going to be where you (and anyone you invite, ideally your team) will put your ideas into the 1 place. Some of them\n
- #8 Not pretty is it. This is where Lean UX really shines, Doesn't have to be. It just has to work.\n\n(simplicity is key - only 4 columns (what it is you want to change, expected impact, whos doing it, actual impact)\n1st fill out 2 columns 'what it is' and 'expected outcome'.\neg: what it is you want to change: add a sample demo project for new users into the IDE -expected outcome = lowers the 30% of users who never come back.\n
- #9 Not pretty is it. This is where Lean UX really shines, Doesn't have to be. It just has to work.\n\n(simplicity is key - only 4 columns (what it is you want to change, expected impact, whos doing it, actual impact)\n1st fill out 2 columns 'what it is' and 'expected outcome'.\neg: what it is you want to change: add a sample demo project for new users into the IDE -expected outcome = lowers the 30% of users who never come back.\n
- #10 After its written you spend a bit of time with 'the man' - or woman in charge (in our case thats the CEO or product manager) they decide what goals are important for the company... retention, revenue, customers... this naturally floats those relevant ideas to the top and this becomes your new work list. Easy so far, right?\n
- #11 Staff them put their name against an item at the top of the list and NOW you get stuck in - you own a task and you have to show whether the outcome is what you expect or not.  \n
- #12 Speed is important in these tasks, because that list you saw is mammoth. So as much as possible and indeed as much as you can stand it - for get high fidelity wireframes and prototypes. \nLow fidelity protoypes that are fast and work well - and remember these are for you you dont have to show them to anyone.\n
- #13 Whiteboard\n - this is actually my whiteboard at the moment, no-one but me and my lead ux (who's brilliant face is in this audience understands it...  and thats ok)\n
- #14 Paper\n - Ahhh the humble paper. Easy, fast, portable... the ipad of the victorian times. Also your best friend. Another hour with a pencil helps fully set out your vision. Remeber at these stages your looking for pitfalls and logic breakdowns... fastestway to do that is paper prototyping.\n
- #15 Balsamiq (I find this the quickest but omnigraffle and invision app work just as well)\n- If you do have to show something or detail work to a developer  then this is the way to go.\n
- #16 Invisionapp\nIf it is a big change and you need buy in for above - then protoype it using invision app. It is also worth it in some instances to see just how the interactions work but always check how long this takes you.\n
- #17 Build what you can yourself as fast as you can. It depends largely on what you build to how you build it. The best advice at this stage if you can't do it yourself... make friends with your developer. Go to his/her desk with a coffee and talk. Ask about how it is going and see where on the priority list your tasks are. \nThis seems more like people management but trust me it works. In a Lean environment even the devs will pick the tasks they think will make the biggest impact so as a uxer its also your job to get their buy in to help. (this works both ways too)\n
- #18 This is always the fun stage for me. Because it means metrics and mesurement. This is where Lean usually falls down because metrics can be hard to implement and analyse but trust me when done right it is worth it.\n
- #19 For web changes we use google analytics and their goal measurements.\n
- #20 For behavioural changes we use clicktale and the mouse recordings\n
- #21 For in app changes we have to use our own engine. But I also believe clicktale can be used inside applications too, I have yet to get buy-in from a dev to implement this for me...\n\nSo at this point i want you to look at what you change succeeded in doing?  Based on your measurements and check against your hypothesis to see if it worked. If it shows more than a 10% change you should develop it further, if it is less than this you may want to leave the implementation as it is. If it had an adverse effect rip it out.\n
- #22 Never be afraid to let go. A good motto for life and UX in general.\nIf it didnt show good enough results let it go. Do not be tempted to continue to work on it. Your attention needs to move onto the next task at hand.\n\nOur own projects can feel like our children in some ways but 80% of the results are seen in the first 20% of the work. You are not gaining big returns by continuing to tweak an average design.\n
- #23 \n
- #24 \n
- #25 \n
- #26 \n