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.

Rob Gill - Minor bug fixes

146 views

Published on

It takes a lot of effort within a large organisation to get things done, especially to a really high standard. However it’s often minor tasks that will offer you the biggest rewards. This talk will take you through a journey of suggestions and tips to help improve communication, productivity and quality, whilst tying back to an overarching theme of Release Notes.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Rob Gill - Minor bug fixes

  1. 1. Minor Bug Fixes by Rob Gill
  2. 2. TL; DR too long; didn’t read Content: 
 Apps, AppStores & Release Notes 
 Topics:
 Communication, Communication Channels & Improvement
  3. 3. goal.com
  4. 4. 57.4M
 Users 585.1M
 Page Views 38 local editions 20 languages goal.com
  5. 5. Rob Gill 👋UX Manager
  6. 6. 📍
  7. 7. Business goals & priorities are changing 😫 20 different languages 🤔 Lots of different products 😅 Communication across timezones 🙁 Little time to focus on improving one feature 🙁 It can take a long
 time to do anything 😒
  8. 8. 😁 But…
 this is software
 at scale!
  9. 9. First ticket created
 29th December 2014 )* 🕸 🕸
  10. 10. ✨ First ticket created
 29th December 2014 V8.0 iOS Release
 19th May 2016 1 year,
 3 months,
 8 days later ✨ ✨ ✨ ✨)* 🕸 🕸
  11. 11. 1 year, 3 months, 8 days later 💩
  12. 12. 😍 😍😍 😍 💩
  13. 13. Nobody reads them! 😒 Not much
 point 😑 Too much
 effort 🤔 We don’t have 
 enough time 🙁 Translations
 take a long time! 🙁
  14. 14. Turns out nobody does read release notes…
  15. 15. 💩 💩
  16. 16. 📣 ----------------> 👀 your
 users 2you
  17. 17. 📣 ----------------> 👀 your
 users 2you
  18. 18. 📣 ----------------> 👀 📬 <---------------- 💌 your
 users 2you
  19. 19. 📣😍🎉
  20. 20. ! ” # $ % & ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z } { ~ D E L Ç ü é â ä à å ç ê ë è ï î ì Ä Å É æ Æ ô ö ò û ù ÿ Ö Ü ø £ Ø × ƒ á í ó ú ñ Ñ ª º ¿ ® ¬ ½ ¼ ¡ « » ░ ▒ ▓ │ ┤ Á Â À © ╣ ║ ╗ ╝ ¥ ┐ └ ┴ ┬ ├ ─ ┼ ã Ã ╚ ╔ ╩ ╦ ╠ ═ ╬ ¤ ð Ð Ê Ë È ı Í Î Ï ┘ ┌ █ ▄ ¦ Ì ▀ Ó ß Ô Ò õ Õ µ þ Þ Ú Û Ù ý Ý ¯ ´ ¬ ± ‗ ¾ ¶ § ÷ ¸ ° ¨ • ¹ ³ ² ■ ¢
  21. 21. Summarise First; Tell Later.
  22. 22. • Bullets
  23. 23. Make it easy for people to get in touch
  24. 24. Reference the last major release
  25. 25. …2 days later..
  26. 26. 🚀 Euros Section 🚀 Improved Match Pages 🚀 Bug Fix 🚀 Bug Fix
  27. 27. 🚀 Euros Section 🚀 Improved Match Pages 🚀 Bug Fix 🚀 Bug Fix
  28. 28. r 🚀 Euros Section 🚀 Improved Match Pages 🚀 Bug Fix 🚀 Bug Fix
  29. 29. 🚀 Euros Section 🚀 Improved Match Pages 🚀 Bug Fix 🚀 Bug Fix ⚽ Euro 2016 Start ⚽ Euro 2016 End
  30. 30. The perfect release note
  31. 31. The introduction. A short paragraph. Make this personal if appropriate. Eg. "Season greetings, everyone! You asked, Santa listened - this update is exactly what you ask for this Christmas." TL; DR • An extra short summary of these notes goes here. *** NEW *** • This is where you layout any new features. • Explain where abouts these features are within your app. • How do users find these new features? • Which users will this benefits, or how exactly will this benefits them?
  32. 32. The introduction. A short paragraph. Make this personal if appropriate. Eg. "Season greetings, everyone! You asked, Santa listened - this update is exactly what you ask for this Christmas." TL; DR • An extra short summary of these notes goes here. *** NEW *** • This is where you layout any new features. • Explain where abouts these features are within your app. • How do users find these new features? • Which users will this benefits, or how exactly will this benefits them? • E.g. "[Who benefits?] Apple Watch users will be particularly happy with the latest release. [Why?] We now automatically support handoff with your Mac. [Where/how?] Don’t forget to have your bluetooth turned on, you can do it]!”
  33. 33. The introduction. A short paragraph. Make this personal if appropriate. Eg. "Season greetings, everyone! You asked, Santa listened - this update is exactly what you ask for this Christmas." TL; DR • An extra short summary of these notes goes here. *** NEW *** • This is where you layout any new features. • Explain where abouts these features are within your app. • How do users find these new features? • Which users will this benefits, or how exactly will this benefits them? • E.g. "[Who benefits?] Apple Watch users will be particularly happy with the latest release. [Why?] We now automatically support handoff with your Mac. [Where/how?] Don’t forget to have your bluetooth turned on, you can do it]!” 
 *** IMPROVEMENTS *** • If improving an existing feature, rather than something that’s brand new, use the "Improvements" title instead of "New". • If you've improved something as a result of user feedback, consider a sentence like, "you asked, we listened". A great way to make your users feel valued.
  34. 34. • This is where you layout any new features. • Explain where abouts these features are within your app. • How do users find these new features? • Which users will this benefits, or how exactly will this benefits them? • E.g. "[Who benefits?] Apple Watch users will be particularly happy with the latest release. [Why?] We now automatically support handoff with your Mac. [Where/how?] Don’t forget to have your bluetooth turned on, you can do it]!” 
 *** IMPROVEMENTS *** • If improving an existing feature, rather than something that’s brand new, use the "Improvements" title instead of "New". • If you've improved something as a result of user feedback, consider a sentence like, "you asked, we listened". A great way to make your users feel valued. *** FIXED *** • List out any major bugs that might have affected many users. • If you've only addressed minor fixes, or nothing specific, use something like: • E.g. "Minor Bug fixes" • Keep the "Fixed" title if you've included other titled sections. The sign off. Similar to the introduction, this could be personalised if appropriate. You could easily have a couple of
  35. 35. 
 *** IMPROVEMENTS *** • If improving an existing feature, rather than something that’s brand new, use the "Improvements" title instead of "New". • If you've improved something as a result of user feedback, consider a sentence like, "you asked, we listened". A great way to make your users feel valued. *** FIXED *** • List out any major bugs that might have affected many users. • If you've only addressed minor fixes, or nothing specific, use something like: • E.g. "Minor Bug fixes" • Keep the "Fixed" title if you've included other titled sections. The sign off. Similar to the introduction, this could be personalised if appropriate. You could easily have a couple of variations of this in your locker. Finally Feedback. Add the feedback email address and welcome users thoughts. Eg. “Submit your suggestions for improvements to feedback@yourapp.co we value your feedback”
  36. 36. *** FIXED *** • List out any major bugs that might have affected many users. • If you've only addressed minor fixes, or nothing specific, use something like: • E.g. "Minor Bug fixes" • Keep the "Fixed" title if you've included other titled sections. The sign off. Similar to the introduction, this could be personalised if appropriate. You could easily have a couple of variations of this in your locker. Finally Feedback. Add the feedback email address and welcome users thoughts. Eg. “Submit your suggestions for improvements to feedback@yourapp.co we value your feedback”
  37. 37. Life before this template…sllbefore 😓
  38. 38. Life before this template…sllafter 😓😍
  39. 39. Issues
  40. 40. Translations take a long time 😓
  41. 41. Make it a part of your workflow…
  42. 42. 📍 📍 📍
  43. 43. What if our updates aren’t user friendly? e.g. additional ad networks integrated 😓
  44. 44. Minor bug fixes
  45. 45. “Minor bug fixes” from last 12 months 0 65 130 195 260 Total Development Time (hours) V8.6.7 V8.6.6 V8.6.5 V8.6.4 V8.6.3 V8.6.2 V8.6.1 V8.6.2 V8.5.1 V8.3.1
  46. 46. “Minor bug fixes” from last 12 months 0 65 130 195 260 Total Development Time (hours) V8.6.7 V8.6.6 V8.6.5 V8.6.4 V8.6.3 V8.6.2 V8.6.1 V8.6.2 V8.5.1 V8.3.1
  47. 47. “Minor bug fixes” from last 12 months 0 65 130 195 260 Total Development Time (hours) V8.6.7 V8.6.6 V8.6.5 V8.6.4 V8.6.3 V8.6.2 V8.6.1 V8.6.2 V8.5.1 V8.3.1
  48. 48. Before — — After
  49. 49. Minor bug fixes *** NEW *** Compact news cards - you can now see more news in on your screen *** IMPROVED *** Optimised ad experience *** FIXED *** 24 bugs fixed
  50. 50. Seems like a
 lot of effort for little reward 😓 But nobody reads
 release notes…
  51. 51. Re-use
  52. 52. Re-use
  53. 53. Proof this works
  54. 54. 📣 ------> 👀 📬 <------ 💌
  55. 55. The 2mm Rule
  56. 56. The introduction. A short paragraph. Make this personal if appropriate. Eg. "Season greetings, everyone! You asked, Santa listened - this update is exactly what you ask for this Christmas." TL; DR • An extra short summary of these notes goes here. *** NEW *** • This is where you layout any new features. • Explain where abouts these features are within your app. • How do users find these new features? • Which users will this benefits, or how exactly will this benefits them? • E.g. "[Who benefits?] Apple Watch users will be particularly happy with the latest release. [Why?] We now automatically support handoff with your Mac. [Where/how?] Don’t forget to have your bluetooth turned on, you can do it]!” 
 *** IMPROVEMENTS *** • If improving an existing feature, rather than something that’s brand new, use the "Improvements" title instead of "New". • If you've improved something as a result of user feedback, consider a sentence like, "you asked, we
  57. 57. @rob_gill_ • E.g. "Minor Bug fixes" • Keep the "Fixed" title if you've included other titled sections. The sign off. Similar to the introduction, this could be personalised if appropriate. You could easily have a couple of variations of this in your locker. Finally Feedback. Add the feedback email address and welcome users thoughts. Eg. “Submit your suggestions for improvements to feedback@yourapp.co we value your feedback”
  58. 58. @rob_gill_ • E.g. "Minor Bug fixes" • Keep the "Fixed" title if you've included other titled sections. The sign off. Similar to the introduction, this could be personalised if appropriate. You could easily have a couple of variations of this in your locker. Finally Feedback. Add the feedback email address and welcome users thoughts. Eg. “Submit your suggestions for improvements to feedback@yourapp.co we value your feedback” Thank You

×