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.

Killer Specs For Product Managers (The 6 Steps Guide)

621 views

Published on

This is a 6 step guide for guiding Product Managers into a framework to write specs that will allow them to ship high quality software.

Published in: Software
  • Be the first to comment

Killer Specs For Product Managers (The 6 Steps Guide)

  1. 1. By Magdoub
  2. 2. Wuzzuf And Forasna are the Top Job Sites in Egypt Traffic > 3M / month
  3. 3. Wuzzuf And Forasna are the Top Job Sites in Egypt 90% Market Domination
  4. 4. Wuzzuf [Semi Waterfall Development] Forasna [Hardcore Agile Development]
  5. 5. Wuzzuf [Semi Waterfall Development] [Started 2010] Forasna [Hardcore Agile Development] [Started 2015]
  6. 6. Wuzzuf [Semi Waterfall Development] [Started 2010] I was Here for 3 years
  7. 7. Forasna [Hardcore Agile Development] [Started 2015] and...I was Here for 2 years
  8. 8. Here’s My Story Lessons Learned The Hard way
  9. 9. A Guideline For Making Decisions
  10. 10. A Guideline For Making Decisions Specs Come Last
  11. 11. Many Small Steps Mythical Big Launches
  12. 12. Forasna Daily Job Applications
  13. 13. Big Launch Tv Spots Radio Spots Offline Aqc. Online Ads Branding Forasna Daily Job Applications
  14. 14. Forasna Daily Applications Big Launch Tv Spots Radio Spots Offline Aqc. Online Ads Branding Forasna Daily Job Applications
  15. 15. Forasna Daily Applications The Honeymoon is Over Forasna Daily Job Applications
  16. 16. Today
  17. 17. Forasna Daily Job Applications
  18. 18. Big Launch Forasna Daily Job Applications
  19. 19. Wuzzuf Daily Job Applications since 2011
  20. 20. Forasna 400k Applications / Month Wuzzuf Daily Job Applications since 2011
  21. 21. What Took Wuzzuf 7 Years to Achieve
  22. 22. What Took Wuzzuf 7 Years to Achieve Forasna did it 1.5 years
  23. 23. OPTIMIZE FOR SHIPPING THE FASTEST And the smallest, simplest thing that will get us closer to our objective and help us learn what works.
  24. 24. Just a simple signup and Thank you
  25. 25. This Was the whole Freaking Website!
  26. 26. This Was the whole Freaking Website! Just a signup Form
  27. 27. Version #2
  28. 28. Version #3
  29. 29. REDUCE THE SCOPE In order to move faster and not spend time on things that turn out not to be important.
  30. 30. Current Applicant Tracking System
  31. 31. Current ATS Scope List Applicants Scoring In Page Screening (popup) Unlock / Shortlist / Reject Next & Previous Profiles Filters Copy Job Advanced Handpicking Mobile Friendly
  32. 32. Initial ATS Scope List Applicants
  33. 33. First Version
  34. 34. BUILDING FEATURES Daily Goals > Weekly > Monthly > Quarterly
  35. 35. BUILDING FEATURES FOCUS ON OPTIMIZING THE DAILY KPIs
  36. 36. Then Zoom Out Later
  37. 37. Daily Goals
  38. 38. Daily Goals Weekly Goals
  39. 39. Daily Goals Weekly Goals Monthly Goals
  40. 40. Daily Goals Weekly Goals Monthly Goals Quarterly Goals
  41. 41. OPTIMIZE FOR FACE TO FACE COLLABORATION Two People talking on a whiteboard much better than Long Email Threads, Complex Specs, Meetings
  42. 42. Tools are built to help us not paralyze us
  43. 43. Using software to build software is often slower than using whiteboards and Post-it notes.
  44. 44. Use the minimum number of software tools to get the job done.
  45. 45. DESIGNERS WILL DESIGN, DEVELOPERS WILL DEVELOP DATA SCIENTISTS WILL ….. and you have to stop them..
  46. 46. They had best codebase in the world They had best Design out there Products Have Failed Even though.. They had solid proof Documentation They had the best Data Scientists and the Largest/most-complicated Dashboards
  47. 47. Nobody Cares
  48. 48. The “innovative” designs that were “boundary pushing” were also practically unusable in real life.
  49. 49. “building our own framework” Because we won’t be using be using 70% of the components in Bootstrap added unneeded Complexity and slowed us down by 6 months
  50. 50. SHIP THE FREAKING PRODUCT!
  51. 51. SHORT CLEAR BROKEN-DOWN SPECS Short Specs but to the point
  52. 52. “Writing down decisions is essential” Only when one writes do the gaps appear and the inconsistencies protrude...
  53. 53. The act of writing turns out to require hundreds of mini-decision, and it is the existence of these that distinguishes clear, exact policies from fuzzy ones. F. Brooks - Mythical Man Month
  54. 54. What Problem Are We Solving and Why? Provide Context Add links to research or data points
  55. 55. How we will Measure Success? Provide Vision
  56. 56. How we will Measure Success? Provide Vision Julie Zhuo Product design VP @ Facebook.
  57. 57. How we will Measure Success? Provide Vision “We’re launching feature X because we think it will do [fill in the blank here]. We’ll invest on making it as good as we can for N months. If after that, less than Y% of people are using it daily, we’ll remove feature X”
  58. 58. Adding Scope Limitations are good It stops over Engineering (generalizing everything)
  59. 59. Visual Specs are Much Easier
  60. 60. Visual Specs are Much Easier
  61. 61. Visual Specs are Much Easier
  62. 62. Ok
  63. 63. Ok..This is Great,
  64. 64. Ok..This is Great, but
  65. 65. How Can I Make sure the Engineers & Designers Understood the Specs?
  66. 66. Make them explain the specs back at you.
  67. 67. What are we going to do with the old Data [Migrations] What QA Scenarios Needed? Questions To always Ask What Metrics do I need to Track the Feature? Should we Notify any of the teams beforehand?
  68. 68. Linkedin Medium Twitter Questions? Catch me on hello@magdoub.com
  69. 69. Thanks Top References *From Intercom’s: Scaling a product Team *Rework by 37 signals *Getting Real by 37 signals *Spotify’s: How we do work

×