Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
GETTING SH*T DONE.
How design is changing the way Coolblue works as a company.
By Jeffrey Simons
?
• Jeffrey Simons.
• User Experience Designer at Coolblue.
• Working on the new Vanessa apps.
• Also Scrum Master of a team ...
VANESSA.
VANESSA.
“SHE MAY NOT LOOK LIKE MUCH, 

BUT SHE’S GOT IT WHERE IT COUNTS”.
NEARLY 15 YEARS OLD.
YOLO DRIVEN DESIGN.
WE NEED TO MAKE THIS BETTER.
IT’S A MESS.
WHY IS IT GOOD.
WHY IS IT BAD.
WHO IS THIS PRODUCT FOR.
EVERYONE.
• What do people do?
• What do people need?
• What do people want?
WHERE DO WE BEGIN.
WHAT DO YOU DO.
IT’S ALL ABOUT TASKS.IT’S ALL ABOUT TASKS.
Section H
Section G
SectionF
Section E
Section D
Section C
Section B
Section A
1 Task
NEEDS & MILKSHAKES.
JOBS TO BE DONE.
“Focusses on a functional need.”
CAPTURING TASKS.
CAPTURING WHY’S.
WHAT DO PEOPLE WANT.
IF THEY COULD DO THEIR JOB
WITHOUT, THEY COULD.
WHAT DO PEOPLE NEED.
PEOPLE NEED TO GET SH*T DONE.
JOBS TO BE DONE.
SH*T TO BE DONE.
WHAT DO YOU DO.
IT’S ALL ABOUT TASKS.IT’S ALL ABOUT TASKS.
Section H
Section G
SectionF
Section E
Section D
Section C
Section B
Section A
1 Task
EVERYTHING YOU NEED, IN ONE PLACE.
AT THE TOUCH OF THE BUTTON.
BUT NOTHING SUPERFLUOUS.
LEAN UX.
CONTINUOUS DISCOVERY.
ASSUMPTIONS.
EXPERIMENTS.
PROTOTYPES.
MVP’S.
Product teams
Business
NEXT STEPS.
DESIGN PRINCIPLES.
TESTING, TESTING, TESTING.
TAKEAWAY.
• Use a “lean” process to experiment and test assumptions
• Use the ‘jobs-to-be-done’ framework to focus on needs
• A grea...
QUESTIONS.
j.simons@coolblue.nl

@jeffsimons
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Getting sh*t done: How design is changing the way Coolblue works - Jeffrey
Upcoming SlideShare
Loading in …5
×

Getting sh*t done: How design is changing the way Coolblue works - Jeffrey

847 views

Published on

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.

Published in: Design
  • Be the first to comment

Getting sh*t done: How design is changing the way Coolblue works - Jeffrey

  1. 1. GETTING SH*T DONE. How design is changing the way Coolblue works as a company. By Jeffrey Simons
  2. 2. ?
  3. 3. • 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.
  4. 4. VANESSA.
  5. 5. VANESSA.
  6. 6. “SHE MAY NOT LOOK LIKE MUCH, 
 BUT SHE’S GOT IT WHERE IT COUNTS”.
  7. 7. NEARLY 15 YEARS OLD.
  8. 8. YOLO DRIVEN DESIGN.
  9. 9. WE NEED TO MAKE THIS BETTER.
  10. 10. IT’S A MESS.
  11. 11. WHY IS IT GOOD.
  12. 12. WHY IS IT BAD.
  13. 13. WHO IS THIS PRODUCT FOR.
  14. 14. EVERYONE.
  15. 15. • What do people do? • What do people need? • What do people want? WHERE DO WE BEGIN.
  16. 16. WHAT DO YOU DO.
  17. 17. IT’S ALL ABOUT TASKS.IT’S ALL ABOUT TASKS.
  18. 18. Section H Section G SectionF Section E Section D Section C Section B Section A 1 Task
  19. 19. NEEDS & MILKSHAKES.
  20. 20. JOBS TO BE DONE. “Focusses on a functional need.”
  21. 21. CAPTURING TASKS.
  22. 22. CAPTURING WHY’S.
  23. 23. WHAT DO PEOPLE WANT.
  24. 24. IF THEY COULD DO THEIR JOB WITHOUT, THEY COULD.
  25. 25. WHAT DO PEOPLE NEED.
  26. 26. PEOPLE NEED TO GET SH*T DONE.
  27. 27. JOBS TO BE DONE.
  28. 28. SH*T TO BE DONE.
  29. 29. WHAT DO YOU DO.
  30. 30. IT’S ALL ABOUT TASKS.IT’S ALL ABOUT TASKS.
  31. 31. Section H Section G SectionF Section E Section D Section C Section B Section A 1 Task
  32. 32. EVERYTHING YOU NEED, IN ONE PLACE. AT THE TOUCH OF THE BUTTON.
  33. 33. BUT NOTHING SUPERFLUOUS.
  34. 34. LEAN UX.
  35. 35. CONTINUOUS DISCOVERY.
  36. 36. ASSUMPTIONS.
  37. 37. EXPERIMENTS.
  38. 38. PROTOTYPES.
  39. 39. MVP’S.
  40. 40. Product teams Business
  41. 41. NEXT STEPS.
  42. 42. DESIGN PRINCIPLES.
  43. 43. TESTING, TESTING, TESTING.
  44. 44. TAKEAWAY.
  45. 45. • 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.
  46. 46. QUESTIONS. j.simons@coolblue.nl
 @jeffsimons

×