January 2016 Event: UX Strategy & Simplification
Download as PPTX, PDF1 like525 views
The document explores how user experience designers simplify complex systems for organizations, discussing the importance of collaboration, user research, and maintaining scope. It highlights the challenges faced in large enterprises, such as the growth of teams and the influence of various voices, while advocating for strategies to advocate for simplicity and adaptability. The presenters emphasize the need for effective communication, building relationships, and continuous learning to enhance UX processes.
January 2016 Event: UX Strategy & Simplification
- 1. How User Experience Designers Take Hugely Complicated Systems and Make Them Less Complicated For The People That The Organization Serves. Starring James Schmittler & Tim Leisio 01.14.16
- 2. UX Simplification & Strategy Starring James Schmittler & Tim Leisio 01.14.16
- 12. Tim Leisio User Experience Architect Twitter & Medium: @timleisio Linkedin: linkedin.com/in/timleisio
- 13. James Schmittler User Experience Team Lead Twitter: @jamesschmittler LinkedIn: linkedin.com/jamesschmittler
- 14. Who are we? Write this down, there might be a test later.
- 15. James & Tim Experts...probably. ● Bit of experience ● Lots of ideas ● A presentation
- 16. Legal UX We stole all the whiteboards. ● 50+ people ● 40+ projects ● Design, IA, Research, CSS, Accessibility, etc...
- 17. Thomson Reuters “The Answer Company” ● Lots of segments ● Billions (with a B) in revenue ● Many employees ● Global ● Eagan is the largest
- 18. Where are we headed? I’m think a beach somewhere. Is Minnesota always this cold?
- 19. Company Shift Design thinking company
- 20. Planning the Future *Maniacal Laugh!*
- 21. Cross UX Team Collaboration Lean on me...when you need a wireframe.
- 22. Cross Company Awareness People know me. I’m...kind of a big deal.
- 23. How are we changing who we are? pain (n) 1. physical suffering or discomfort caused by illness or injury 2. careful effort; great care or trouble.
- 26. 3 Years Ago... So, what’d we actually make?
- 27. 2 Years Ago... Can I haz juice box too?
- 28. 1 Year Ago... We need more coffee.
- 29. Why is all of this important? So we’ve grown up. Good for us. Why do you care?
- 30. Context The environment and situation people are experiencing. ● Growing team ● Large enterprise company ● UX only one of many voices ● Takes time to build relationships ● Change is slow
- 31. Context The environment and situation people are experiencing. ● Growing team ● Large enterprise company ● UX only one of many voices ● Takes time to build relationships ● Slow to change ● We have complex products ● Ever growing scope
- 32. Context The environment and situation people are experiencing. ● Growing team ● Large enterprise company ● UX only one of many voices ● Takes time to build relationships ● Slow to change ● We have complex products ● Ever growing (potential for) scope
- 33. What happens if we lose control of scope? The first step is admitting you have a problem.
- 34. It Doesn’t Fit You can try all day lady, but that couch isn’t going in that car.
- 35. Why is it so damn hard to maintain scope?Go home scope, you’re drunk...
- 36. Mind Your Surroundings Or fall through the ice like a ninja.
- 37. Short on UX Knowledge Can you make it a blue button!?
- 38. Attitude Bias Evidence We build what they say they want. https://www.nngroup.com/articles/which-ux-research-methods/
- 39. People for Research Or just empty seats?
- 40. Funding the Unknown Not quite as epic as exploring strange new worlds.
- 41. Role Ratio Disparities When you have 1:100 ux-to-not ux skill sets on your product team.
- 42. Focus on Features I heard the abominable market wants a spoon.
- 43. Fear of Damaging Relationships No. And here’s why...
- 44. Dogma of “The” Technology When competition isn’t good.
- 45. Reliance on 3rd Party The world changes. Change with it.
- 46. UX Debt I thought there was only technical debt... http://nform.com/blog/2013/05/user-experience-debt/
- 47. Are We Done Yet? Not at all, but OK.
- 48. What do we know about scope? Well, how about an example.
- 49. We’ve Been There Wireframe hell!
- 50. Taking a Risk Jump now, worry about landing later.
- 51. Organizing the Chaos What the hell are we trying to build here anyway?
- 52. Presenting Our Ideas Have at you!
- 53. Coming to an Agreement No one sleeps until we figure this out.
- 54. Aftermath Blue skies and happy faces next 100 miles.
- 55. Customer Partnerships Everyone being super friendly.
- 56. Better Product Just in time for Spring too!
- 57. Better Product Oh, you meant Spring in Minnesota...
- 58. Why We Think Less Scope = More Hope DOWN WITH SCOPE! UP WITH HOPE! ● Sustainability ● Growth ● Market understanding ● User research
- 59. How do YOU advocate for simplicity? Can you make it simple. Like 3 a step process?
- 60. Find the Core Cut the crap, strengthen the core
- 61. Seed Possibility And maybe prototype it...
- 62. Collaborate Milk could make a Dark Side parody...
- 63. How to handle chaos & prepare for the future?Scout Motto: Be Prepared
- 64. Do Things That Make You Better Treat Yo’Self
- 65. Build Trust How to influence friends and eliminate enemies.
- 66. Be A Part of the Project Team Cowabunga!
- 67. Increase Your Skillset Change is good. Sometimes you’re an alien, sometimes you’re a pop star.
- 68. Be Strategic Without Being Asked Still waiting for that invitation?
- 70. Follow Through Even the best laid plans have flaws.
- 71. Learn From Mistakes Obviously, you wouldn’t design the same flaw twice...obviously...obviously…
- 72. Questions? Besides “Who shot first?”