Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
•
3 likes•1,041 views
When you order something at Coolblue a lot of things happen behind the scenes. Thank goodness there's Vanessa, our back-office software that helps colleagues get sh*t done. Started nearly 15 years ago, she's due for retirement. Let us talk you through how we're redesigning such a complex application and what we've learned along the way.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Similar to Getting sh*t done: How design is changing the way Coolblue works - Jeffrey (20)
Recently uploaded
Recently uploaded (20)
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
- 1. GETTING SH*T DONE. How design is changing the way Coolblue works as a company. By Jeffrey Simons
- 5. ?
- 7. • Jeffrey Simons. • User Experience Designer at Coolblue. • Working on the new Vanessa apps. • Also Scrum Master of a team of six developers. WHO AM I.
- 8. VANESSA.
- 9. VANESSA.
- 11. “SHE MAY NOT LOOK LIKE MUCH, BUT SHE’S GOT IT WHERE IT COUNTS”.
- 13. NEARLY 15 YEARS OLD.
- 15. WE NEED TO MAKE THIS BETTER.
- 17. IT’S A MESS.
- 18. WHY IS IT GOOD.
- 20. WHY IS IT BAD.
- 22. WHO IS THIS PRODUCT FOR.
- 23. EVERYONE.
- 27. • What do people do? • What do people need? • What do people want? WHERE DO WE BEGIN.
- 28. WHAT DO YOU DO.
- 30. IT’S ALL ABOUT TASKS.IT’S ALL ABOUT TASKS.
- 31. Section H Section G SectionF Section E Section D Section C Section B Section A 1 Task
- 33. JOBS TO BE DONE. “Focusses on a functional need.”
- 34. CAPTURING TASKS.
- 35. CAPTURING WHY’S.
- 36. WHAT DO PEOPLE WANT.
- 37. IF THEY COULD DO THEIR JOB WITHOUT, THEY COULD.
- 38. WHAT DO PEOPLE NEED.
- 39. PEOPLE NEED TO GET SH*T DONE.
- 40. JOBS TO BE DONE.
- 41. SH*T TO BE DONE.
- 42. WHAT DO YOU DO.
- 43. IT’S ALL ABOUT TASKS.IT’S ALL ABOUT TASKS.
- 44. Section H Section G SectionF Section E Section D Section C Section B Section A 1 Task
- 45. EVERYTHING YOU NEED, IN ONE PLACE. AT THE TOUCH OF THE BUTTON.
- 52. LEAN UX.
- 54. ASSUMPTIONS.
- 55. EXPERIMENTS.
- 56. PROTOTYPES.
- 57. MVP’S.
- 59. NEXT STEPS.
- 62. TAKEAWAY.
- 63. • Use a “lean” process to experiment and test assumptions • Use the ‘jobs-to-be-done’ framework to focus on needs • A great software experience is no software experience* • Continuous Discovery helps create lean products (nothing superfluous) TAKEAWAY.