Lessons from Labyrinth: Designing in the world of enterprise - UX Thursday Toronto - Kimberley Peter
2 likes2,132 views
The document discusses lessons learned from designing enterprise systems, emphasizing the importance of effective collaboration across disciplines and the use of user story mapping alongside microservice architecture. It highlights the role of continuous feedback and IBM design thinking in project execution while also addressing the pressures from executives. Key takeaways include the need for holistic thinking, clear communication, and adapting methodologies to enhance productivity and engagement.
Lessons from Labyrinth: Designing in the world of enterprise - UX Thursday Toronto - Kimberley Peter
- 1. LESSONS FROM LABYRINTH Designing in the World of Enterprise Kimberley Peter IBM Rational + DevOps kpeter@ca.ibm.com @kpeter UX Thursday Toronto. Kimberley Peter . IBM ©2014
- 3. ?
- 4. Technology methodologies Team member exits + entrances Executive Project pressures scope / mission 2010 2011 2012 2013 2014 2015
- 5. Project scope / mission 1 2 2010 2011 2012 2013 2014 2015
- 6. Backcasting Learning sources: Matt Nish-Lapidus and Matthew Milan, Normative
- 10. PRESENT TIMELINE FUTURE Dec ‘16
- 11. PRESENT TIMELINE FUTURE Dec ‘14 June ‘15 Dec ‘15 June ‘16 Dec ‘16
- 12. Dec ‘14 June ‘15 Dec ‘15 June ‘16 Dec ‘16 Elements PRESENT TIMELINE FUTURE
- 13. Dec ‘14 June ‘15 Dec ‘15 June ‘16 Dec ‘16 Elements PRESENT TIMELINE FUTURE
- 14. Dec ‘14 June ‘15 Dec ‘15 June ‘16 Dec ‘16 Elements PRESENT TIMELINE FUTURE
- 15. Dec ‘14 June ‘15 Dec ‘15 June ‘16 Dec ‘16 Elements PRESENT TIMELINE FUTURE
- 16. Dec ‘14 June ‘15 Dec ‘15 June ‘16 Dec ‘16 Elements Actions PRESENT TIMELINE FUTURE
- 17. Dec ‘14 June ‘15 Dec ‘15 June ‘16 Dec ‘16 Elements Actions Indicators PRESENT TIMELINE FUTURE
- 18. Dec ‘14 June ‘15 Dec ‘15 June ‘16 Dec ‘16 Elements Actions Indicators Risks PRESENT TIMELINE FUTURE
- 19. Dec ‘14 June ‘15 Dec ‘15 June ‘16 Dec ‘16 Elements Actions Indicators Risks Opportunities PRESENT TIMELINE FUTURE
- 20. Dec ‘14 June ‘15 Dec ‘15 June ‘16 Dec ‘16 Elements Actions Indicators Risks Opportunities PRESENT TIMELINE FUTURE What can we do tomorrow to start this journey?
- 22. Technology methodologies 2010 2011 2012 2013 2014 2015
- 24. Engineering Approach — Service Maturity Model
- 25. Yeah, but …?
- 27. Business goals / user info / principles / ideas (at top) Activity Task Sub-task Time Release 1 ! Great sources for learning more: Jeff Patton and Winnipeg Agilist
- 28. IBM Rational . Advancing UX in Your Organization, Kim Peter and Adam Archer ©2014 16
- 29. IBM Rational . Advancing UX in Your Organization, Kim Peter and Adam Archer ©2014 17
- 30. IBM Rational . Advancing UX in Your Organization, Kim Peter and Adam Archer ©2014 18 Define Scope Monitor + Manage Communicate Up Get Productive
- 31. Sketching
- 32. + Audio/teleconference Screen sharing software Social software Sketching tools
- 33. Team member exits + entrances 2010 2011 2012 2013 2014 2015
- 35. + IBM Design Thinking
- 37. Executive pressures 2010 2011 2012 2013 2014 2015
- 38. Takeaways
- 39. Hack the tools
- 40. Hack the tools Engage across disciplines
- 41. Hack the tools Engage across disciplines Use relatable language
- 42. Hack the tools Engage across disciplines Use relatable language Push for holistic thinking
- 43. Hack the tools Engage across disciplines Use relatable language Push for holistic thinking ~ The medium is the message
- 44. THANKS! Now, go show ‘em how it’s done! (after lunch, of course ;) Kimberley Peter IBM Rational + DevOps kpeter@ca.ibm.com @kpeter UX Thursday Toronto. Kimberley Peter . IBM ©2014