O slideshow foi denunciado.
Seu SlideShare está sendo baixado. ×

Learn build measure building products customers love

Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Carregando em…3
×

Confira estes a seguir

1 de 104 Anúncio

Learn build measure building products customers love

Baixar para ler offline

An in depth introduction to building products with a focus on software. Slides are from the Product Management Bootcamp at General Assembly, Austin, Texas.
The focus is on the basics of learning, building and measuring as a cycle.

An in depth introduction to building products with a focus on software. Slides are from the Product Management Bootcamp at General Assembly, Austin, Texas.
The focus is on the basics of learning, building and measuring as a cycle.

Anúncio
Anúncio

Mais Conteúdo rRelacionado

Diapositivos para si (20)

Anúncio

Semelhante a Learn build measure building products customers love (20)

Mais recentes (20)

Anúncio

Learn build measure building products customers love

  1. 1. LEARN. BUILD. MEASURE. REPEAT…
  2. 2. AGENDA
  3. 3. AGENDA LEARN ‣ Market ‣ Customers BUILD ‣ What to build ‣ How to build MEASURE ‣ User Research ‣ Role of Metrics ‣ What to Measure BEING AN AWESOME PM ‣ Influencing ‣ Storytelling
  4. 4. INTRODUCTIONS
  5. 5. HELLO! ‣ PM | PM Coach | Startup Co-Founder Background: ‣ SaaS | QA | BA | Marketing | Advertising ‣ Launched two service businesses ‣ Building digital products; consumer & enterprise What I like: ‣ Understanding human behavior ‣ Building consumer products that a global footprint RAHUL PRUTHI HELLO!
  6. 6. HELLO ‣ Who you are, where you're from and what you do? ‣ What are two outcomes you hope to achieve for which you are spending $ on this bootcamp? ‣ What’s your one pet peeve about working in teams? ‣ Favorite Product or Website ‣ Favorite Vertical to build a product for (e.g. Travel, Retail, Social etc.) But…Tell this to the person next to you and they’ll share with the group
  7. 7. WHAT IS A PRODUCT?
  8. 8. GOOD VS. BAD PRODUCTS
  9. 9. HABITS ARE PROBLEMS WORTH SOLVING
  10. 10. WHAT IS A GOOD PRODUCT? source: https://www.linkedin.com/pulse/what-makes-truly-great-product-jeff-weiner
  11. 11. BUILD LET’S TRY THIS
  12. 12. WHAT IS PRODUCT MANAGEMENT
  13. 13. WHAT IS PRODUCT MANAGEMENT? The process of conceiving, planning, developing, testing, launching, delivering and withdrawing products for your team and company to your users
  14. 14. WHAT DOES A PRODUCT MANAGER DO
  15. 15. WHAT DOES A PRODUCT MANAGER DO? Stakeholders “Viability” Designing the Product “Usability” “Desirability” Building the product “Feasibility” Source: http://www.mindtheproduct.com/2011/10/what-exactly-is-a-product-manager/
  16. 16. WHAT A PRODUCT MANAGER IS? The Visionary Mini CEO Passionate Voice of the Customer Jack of All Trades The Influencer The Project Manager Operations Finance Sales Support Marketing
  17. 17. WHO IS A PRODUCT MANAGER if the product is a success, don’t expect to get the credit if the product is a failure, don’t expect to not get the credit
  18. 18. LEARN: MARKET
  19. 19. WHAT PROBLEM DO YOU WANT TO SOLVE?
  20. 20. CUSTOMERS + PRODUCT + THE MARKET
  21. 21. 1 2 3 4 5 6 7 8 9 Source:https://en.wikipedia.org/wiki/Alexander_Osterwalder
  22. 22. PRODUCT SOLUTION FIT “DOES THE PROBLEM EXIST”
  23. 23. PRODUCT SOLUTION FIT “DOES THE PROBLEM EXIST” PRODUCT MARKET FIT “IS MY PRODUCT/SOLUTION DESIRABLE”
  24. 24. PRODUCT / MARKET FIT THE MARKET GAP IN THE MARKET MARKET IN THE GAP
  25. 25. PRODUCT / MARKET FIT GET IN FRONT OF CUSTOMERS AND VALIDATE YOUR ASSUMPTIONS (MAKE SURE YOU VALIDATE ASSUMPTIONS BEFORE YOU START BUILDING) LISTEN TO YOUR CUSTOMERS – VALIDATION IS NOT A SALES PITCH MAKE SURE THE PROBLEM YOU’RE TACKLING IS IMPORTANT TO THE CUSTOMER – IF NOT, THEN PIVOT MAKE SURE THE PRODUCT REALLY SOLVES THE PROBLEM FINDING THE FIT
  26. 26. YOU ARE THE VOICE OF THE CUSTOMER
  27. 27. YOU ARE ‘NOT’ THE CUSTOMER
  28. 28. LEARN: UNDERSTANDING YOUR CUSTOMERS WHO ARE MY CUSTOMERS? WHAT ARE THEIR PAIN POINTS? LIST ALL FEATURES YOUR PRODUCT WILL HAVE HOW WILL CUSTOMERS FIND YOUR PRODUCT? WHY ARE CURRENT SOLUTIONS NOT ENOUGH? HOW WILL CUSTOMERS BENEFIT FROM MY PRODUCT?
  29. 29. BUILD LET’S TRY THIS
  30. 30. BUILD: ASSUMPTIONS & HYPOTHESIS STEP 1: WRITE DOWN YOUR HYPOTHESIS We believe that people like have a need for/problem doing We know we will have succeeded when , or which will contribute to [Customer Type] [needs/actions/behaviors] [measurable outcome] [observable outcome] [KPI’s/Metrics]
  31. 31. BUILD
  32. 32. THE MVP PHILOSOPHY THE LEAST AMOUNT OF WORK YOU CAN DO TO LEARN THE MOST OF SOMETHING.
  33. 33. MVP (EXPERIMENTATION + LEARNING)
  34. 34. THE MVP PHILOSOPHY • REDUCE RISK • MAXIMIZE SUCCESS • FASTER FEEDBACK • REDUCED OVERHEAD • MEASURABLE PROGRESS WHY MVP?
  35. 35. MVP (APPROACH + ATTITUDE) Source: fastmonkeys.com
  36. 36. MVP (APPROACH + ATTITUDE) Source: fastmonkeys.com
  37. 37. MVP (APPROACH + ATTITUDE)
  38. 38. FAMOUS MVPS
  39. 39. FAMOUS MVPS
  40. 40. FAMOUS MVPS
  41. 41. FAMOUS MVPS
  42. 42. FAMOUS MVPS
  43. 43. FAMOUS MVPS
  44. 44. MVP IN 5 STEPS 1. DECLARE YOUR ASSUMPTIONS AND RISKS 2. ORGANIZE THEM INTO TESTABLE HYPOTHESES 3. DETERMINE WHAT RESULTS WILL VALIDATE / INVALIDATE THE HYPOTHESES 4. PLAN AN MVP TO TEST YOUR HYPOTHESES 5. LAUNCH IT! BUILD: CREATING AN MVP
  45. 45. MVP (APPROACH + ATTITUDE) Source: fastmonkeys.com
  46. 46. WHAT IF YOUR HYPOTHESIS IS WRONG? PIVOT, LEARN, AND ITERATE. BUILD: CREATING AN MVP
  47. 47. BUILD: DESIGNING WIREFRAMES MOCKUPS PROTOTYPES
  48. 48. BUILD: DESIGNING A low fidelity representation of a design should clearly show: • The main groups of content (what?) • The structure of information (where?) • A description and basic visualization of the user – interface interaction (how?) WIREFRAMES Quick : Easy : Faster feedback loop
  49. 49. BUILD: DESIGNING MOCKUPS A middle to high fidelity, static, design representation. A visual design draft, or even the actual visual design. A well created mockup: • Represents the structure of information, visualizes the content and demonstrates the basic functionalities in a static way • Encourages people to actually review the visual side of the project Closer to the real thing : Qualitative feedback
  50. 50. BUILD: DESIGNING PROTOTYPES Often confused with a wireframe, it is a middle to high fidelity representation of the final product, which simulates user interface interaction. It should allow the user to: • Experience content and interactions with the interface • Test the main interactions in a way similar to the final product Interactive : Qualitative & Quantitative feedback
  51. 51. BUILD: WIREFRAMES VS. PROTOTYPES VS. MOCKUPS
  52. 52. BUILD: WIREFRAMES VS. PROTOTYPES VS. MOCKUPS
  53. 53. BUILD: WIREFRAMES VS. PROTOTYPES VS. MOCKUPS
  54. 54. BUILD LET’S TRY THIS
  55. 55. MEASURE
  56. 56. CUSTOMER TESTING
  57. 57. CUSTOMER DEVELOPMENT
  58. 58. ALPHA & BETA TESTING
  59. 59. MEASURE: USER RESEARCH & INTERVIEWS These are the questions we are trying to answer. • What do we need to know at this point in the design process? • What are the knowledge gaps we need to fill? source: https://www.smashingmagazine.com/2013/09/5-step-process-conducting-user-research/
  60. 60. MEASURE: USER RESEARCH & INTERVIEWS These are what we believe we already know. • What are our team’s assumptions? • What do we think we understand about our users, in terms of both their behaviors and our potential solutions to their needs?
  61. 61. MEASURE: USER RESEARCH & INTERVIEWS These address how we plan to fill the gaps in our knowledge. • Based on the time and people available, what methods should we select?
  62. 62. MEASURE: USER RESEARCH & INTERVIEWS Answer our research questions, and prove or disprove our hypotheses. Make sense of the data we’ve gathered to discover what opportunities and implications exist for our design efforts. source: https://www.smashingmagazine.com/2013/09/5-step-process-conducting-user-research/
  63. 63. BEST PRACTICES ON RUNNING THE INTERVIEW ‣ Let the person know why you are doing the interview ‣ Use the script as a guide not a bible ‣ Make the interviewee feel comfortable ‣ Keep it on track ‣ Invite your teammates to listen in & help you capture data. ‣ DO NOT ask any leading questions ‣ DO NOT interpret ‣ Leave all bias aside ‣ Avoid using ‘why’ - Rather use phrases such as ‘what made you do that’
  64. 64. WHERE TO FIND PEOPLE
  65. 65. LET’S INTERVIEW!
  66. 66. Step 1: Pick one idea (2 mins) Step 2: Think of what information you would need from your potential customers (5 mins) Step 3: Three to four questions for the interview to validate your hypothesis (6 mins) Photo sharing app Restaurant reservation app Your pick! Interview Prep The Interview Step 1: Pick the interviewer & observer Step 2: Each person interviews once Step 3: Share the qualitative feedback on your hypothesis
  67. 67. METRICS
  68. 68. IF YOU DON’T MEASURE IT, ITS AN ________?
  69. 69. IF YOU DON’T MEASURE IT, ITS AN OPINION?
  70. 70. IF YOU ARE NOT THE ‘HIPPO’ YOU NEED METRICS
  71. 71. TYPE OF METRICS
  72. 72. MEASURE: THE RIGHT METRICS • COMPARATIVE • UNDERSTANDABLE • A RATIO OR RATE • BEHAVIOR CHANGING
  73. 73. MEASURE: TYPE OF METRICS QUANTITIVE EXPLORATORY LEADING CORRELATED QUALITATIVE REPORTING LAGGING CAUSAL vs vs vs vs
  74. 74. TAKE MEASURES TO MEASURE THE METRICS ‣ What metrics should we measure? ‣ Possible examples ‣ Unique visitors ‣ Number of emails collected ‣ Number of downloads ‣ Facebook likes & followers Vanity Metrics
  75. 75. TAKE MEASURES TO MEASURE THE METRICS ‣ What metrics should tell us? ‣ Possible examples ‣ How do you gain or lose revenue? ‣ How do you gain or lose customers? ‣ What are the key functions and benefits that people are coming to you for? Actionable Metrics
  76. 76. TAKE MEASURES TO MEASURE THE METRICS ‣ What metrics should tell us? ‣ Possible examples ‣ Lifetime Value ‣ Total Revenue (Month, Quarter, Annual) ‣ Net Profit ‣ Average Order Value ‣ Number of Transactions ‣ Average Length of Subscription (for subscription business models) ‣ Where do your leads and customers come from? Social Media? Google? Paid traffic? (NOT visitors!) Actionable Metrics
  77. 77. TAKE MEASURES TO MEASURE THE METRICS ‣ Metrics should help us decide ‣ A/B Testing | Multivariate Testing ‣ Think of it as a funnel ‣ Measure in Cohorts ‣ Execute in form of campaigns Actionable Metrics
  78. 78. WHAT METRICS WOULD YOU TRACK?
  79. 79. MEASURE: CUSTOMER ACQUISITION FUNNEL
  80. 80. MEASURE: PIRATE METRICS ACQUISITION ACTIVATION RETENTION REFERRAL REVENUE
  81. 81. BEING AN AWESOME PM
  82. 82. BE WILLING TO START A MOVEMENT
  83. 83. THE ART OF STORYTELLING
  84. 84. GOALS EXPERIENCE GAP INITIATIVES FEATURES STORIES
  85. 85. FEATURE—STORY + ACCEPTANCE CRITERIA ‣ “As a” user/role ‣ “I want to” or “I need to” do this ‣ “because” it will help me achieve this ‣ and “I will know this when” **Acceptance criteria** e.g. pivotal tracker
  86. 86. WOW’ING THE INTERVIEWER
  87. 87. BRINGING IT ALL TOGETHER…
  88. 88. ‣ Body Level One ‣ Body Level Two ‣ Body Level Three ‣ Body Level Four ‣ Body Level Five ‣ Body Level One ‣ Body Level Two ‣ Body Level Three ‣ Body Level Four ‣ Body Level Five GOOD READS & RESOURCES ‣ Body Level One ‣ Body Level Two ‣ Body Level Three ‣ Body Level Four ‣ Body Level Five BOOKSHELF ‣ Body Level One ‣ Body Level Two ‣ Body Level Three ‣ Body Level Four ‣ Body Level Five ‣ The Hard Thing About Hard Things: Building a Business When There Are No Easy Answers ‣ Inspired: How To Create Products Customers Love ‣ How to Win Friends and Influence People ‣ The Four Steps to the Epiphany ‣ The Design of Everyday Things ‣ How Google Works ‣ Cracking the PM Interview ‣ The Innovator's Dilemma ‣ Running Lean
  89. 89. ‣ Body Level One ‣ Body Level Two ‣ Body Level Three ‣ Body Level Four ‣ Body Level Five ‣ Body Level One ‣ Body Level Two ‣ Body Level Three ‣ Body Level Four ‣ Body Level Five GOOD READS & RESOURCES ‣ Body Level One ‣ Body Level Two ‣ Body Level Three ‣ Body Level Four ‣ Body Level Five ONLINE ‣ Body Level One ‣ Body Level Two ‣ Body Level Three ‣ Body Level Four ‣ Body Level Five ‣ Good Product Manager/Bad Product Manager ‣ How to get startup ideas ‣ Leading Cross-functional Teams ‣ How to Work With Software Engineers ‣ We are Product Managers ‣ What distinguishes the Top 1% of Product Managers from the Top 10%? ‣ How to Work with Designers ‣ Top Hacks from a PM Behind Two of Tech's Hottest Products ‣ The Art of Decision Making as a Product Manager ‣ What are the best ways to prioritize a list of product features? ‣ Product Prioritization at Pandora ‣ How to Avoid Delusional Thinking in Start-up Growth Strategy ‣ The Lego Block Exercise ‣ Top Hacks from a PM Behind Two of Tech's Hottest Products ‣ Working Backwards ‣ Design for Continuous Experimentation
  90. 90. ‣ Body Level One ‣ Body Level Two ‣ Body Level Three ‣ Body Level Four ‣ Body Level Five ‣ Body Level One ‣ Body Level Two ‣ Body Level Three ‣ Body Level Four ‣ Body Level Five THANKS! KEEP IN TOUCH ‣ Body Level One ‣ Body Level Two ‣ Body Level Three ‣ Body Level Four ‣ Body Level Five NAME ‣ Body Level One ‣ Body Level Two ‣ Body Level Three ‣ Body Level Four ‣ Body Level Five ‣ rahulpruthi@gmail.com ‣ @rahulpruthi ‣ www.linkedin/in/rahulpruthi

Notas do Editor

  • learn: about customer, about the market
    Build: what to build, how to build, about the processes of building better
    measure: importance of data, what to measure, how to measure, how to use metrics to influence product decisions

  • But, you won’t be doing this for yourself, but you have to learn this about another person here and talk about them.
  • Q1. What is a product? examples & definition.
    First of all, lets not define products only as a website or a mobile app. Websites and apps are not the only things someone or you will want to build. May be you like hardware and you want to make a wearable product like a fitbit, or you want to build the next best toaster.
    “Anything that a person will use, consume or experience is a product.”
  • The common theme between all of these products are
    they are solving a problem, probably better than others
    they give you a good experience along with it.
  • Other examples of bad products:
    https://www.givenchy.com/en/maison-17/all?p=featured
    http://www.domperignon.com/image/eoy2015/
    yahoo shopping
  • A highly used products in many parts of Asia/South Asia. In public halls etc, they have no idea from where to turn the lights on. The problem with current switches is that they have no mapping.
  • We as humans love problem solving, no matter how smart or how dumb, we love solving stuff- it boosts are ego and we feel good.
    As PM’s if we start observing around us, we’ll find humans giving in to problems in the form of habits. Habits are what are worth solving for. Take products- from smart suitcase, to TILE that helps you find your stuff, to COIN that puts all credit cards in one.
  • 1. Delivers on a singular value proposition in a world-class way

    Above all else, great products have a clearly defined sense of purpose, deliver value in a singularly focused way, and do so as well or better than any other product in the marketplace. Google presents a canonical example.

    When first introduced in 1998, many questioned why Google would even bother with search. Alta Vista had already come to define the genre and for the most part, people thought the search problem was essentially solved. However, through its singular focus (a search box offered on an otherwise blank page), a game-changing approach towards search relevancy called Page Rank, and an audacious goal to index the entire web, Google not only surpassed Alta Vista as the clear category leader, it went on to fundamentally change the way society organized and accessed the world's information. It would eventually become one of the most valuable companies in the world.

    Not every company needs to be as renowned as Google in order to fulfill a singular value proposition in a world-class way. Lesser-known products are more than capable of doing the same. Take Headspace for example, an app exclusively focused on how to meditate.

    For years, I was interested in learning meditation, but could never find the time or inclination. I finally made the point of asking a number of respected friends with long-standing meditation practices how they would suggest getting started. Each mentioned a different book, but all of them recommended Headspace. I'm now meditating daily, and having used the app for months, the reason behind the universal acclaim for the product is obvious: Headspace focuses on one thing and does that one thing extremely well.

    2. Simple, intuitive, and anticipates needs

    Waze is a mapping app that combines the best of driving directions and the collective intelligence of drivers to provide real-time updates regarding the most efficient way to get from point A to point B. It's extremely simple and intuitive to use: Just type in your destination, pick a route, and you're off. As good as that experience has always been for me (can't count the number of times it's shaved 10-15 minutes off of what would otherwise have been an hour-long trip), it was a simple, anticipatory feature that took my appreciation of the product to another level.

    Leaving the office one night before beginning my regular commute home, I opened up the app to see what traffic looked like. Repeating an almost daily use case, I was about to select my destination, when up popped the question: "Are you on your way home?" I immediately thought to myself "Yes, I am on my way home, and that's pretty cool." This wasn't rocket science: The app was relying on the consistency of previous inputs during that particular time of day to make an educated guess on where I was going. In doing so, Waze not only saved me a few keystrokes, it demonstrated an understanding of my needs and made an indelible impression as a quality product that's lasted to this day.

    3. Exceeds expectations

    Zappos: wow - shipping + prank- order pizza- and they ordered it— customer service
    WOWing the customer

    4. Emotionally resonates

    One of the first things we did today- we talked about our favorite product and when we explain our favorite product- we talked about how it made us feel. Once completed, each person was asked to stand up to explain their answer. The point of the exercise was for everyone on the team to see how much enthusiasm and passion people conveyed when talking about a great product experience.

    When it came time for one of the more laconic execs on the team to stand up, he excitedly began talking about his Tesla Model S, and remarked it was like "driving the future." I replied, "You've got to be kidding me," and held up the piece of paper I had written my response on. It said, "Tesla Model S: Driving the future."

    We had both cited the same product and described the exact same feeling, despite having never talked to one another about it, and Tesla never explicitly marketing itself that way. Turns out, the company doesn't need to. That's simply the way customers feel when driving a Tesla.

    5. Changes the user's life for the better

    In ways large and small, great products change their customers' lives for the better. Every product mentioned here does that. Yet, perhaps the clearest manifestation of this dynamic for me is the one product that enables all of the other product experiences I've written about thus far: The Apple iPhone 6+ (yes, there's even an app for the Tesla).

    The iPhone makes things more convenient and productive in countless ways. It provides services that inform, entertain, educate, and inspire. To a large extent, it's become more than a product: It's an extension of who I am. It's essentially become the control panel for my life.
  • exercise: good vs. bad products
  • Process: it should be and is repeatable.
    Team & company- As a PM, you are the glue, you are the person and you are the one that people will look at, you will lead things and influence. That’s pretty awesome
    Users: Make sure they are at the center. Think- Amazon 10 principles—> work backwards + customer obsession.
    So, its
    about working upstream (conceiving is w/ stakeholders and business)
    about working downstream (marketing, logistics etc)
    about working side ways (qa, dev etc)
  • Tactical vs. Strategic product manager
    %age of time spent on day to day features vs looking ahead and client stuff
  • You is a business strategy AND technical role.
    q: do you have to be technical. you don’t have to be- but it helps to understand— just like its easy when you know the other person’s language- same with teams.
  • YOU ARE:
    The mini CEO
    The visionary- pushing the limits
    Passionate- you need to be excited, vocal and orchestrating this ensemble of team members
    Voice of the customer
    jack of all trades
    an influencer W/O authority
    somewhat of a project manager (if the company doesn't have one)
    if its no one’s job- its the PM’s job- because you are responsible for success or failure

    Sound tough?
    Sure it’s a tough job but it’s just about the most fun you can have with your clothes on – certainly the most fun you’re going to get paid to do. You get to define the very essence of a product, design solutions to your customers’ problems, work with everyone in the business and play a very large part in your business’s success. We’re the unsung heroes of the tech world – or at least we’d like to think so…
  • Pair up exercise
  • You might have a hypothesis as to who your customers are, you might have a hypothesis as to what they like, don’t like, where they shop, how they would find your product, what they would like, what their pain points are, what features they are looking for, what marketing material they read, or ignore or are they looking for your product online, in the app store, or on a shelf at walmart—- those are ALL hypothesis and opinions- which you or your team came up w/ in a ROOM. And the same goes for your understanding of the market.
    You thoughts and understanding of the market, the competition, the feature set, the demand- shouldn’t be discounted- but they are nothing other than a hypothesis and more so, opinions. For any product, you want to validate these hypothesis.
    lets start w/ coming up w/ these hypothesis (business model canvas)
    then we’ll build them (mvp)
    then we’ll measure & test them (user research & metrics)
  • As a PM, you should be thinking about the end to end of what would make your product successful.
    Read more at:
    http://www.businessmodelgeneration.com/downloads/businessmodelgeneration_preview.pdf
  • This is a theme which we should get used to: “Talk to customers, get feedback”
  • More people are willing to talk and give feedback about our product. Even when you do not win a sale, are turned down for venture funding or when a customer leaves you, talking to these people give immense insights. Especially for new products, people get excited to give input. I can’t express enough the importance of customer validation. Do it before you even write a single line of production code. Once you know your concept is sound, and people will use (and pay for) your product, you can start to build it.
    Related: The four steps to customer discovery http://neverstop.co/start-launching/the-four-steps-to-customer-discovery/
  • image by fastmonkeys.com
  • image by fastmonkeys.com
  • image: General Assembly
  • General Assembly
  • image by fastmonkeys.com
  • General Assembly
  • Read more at:
    http://www.creativebloq.com/web-design/jargon-wireframes-mockups-prototypes-51514898?page=1
    http://designmodo.com/wireframing-prototyping-mockuping/
  • Pair-up UX= wireframing exercise
  • By using demographic analysis and additional information such as what type of phone I carry or what grocery store I shop at, you’ll be able to tell *what* I do, but user research will expose *why* I do what I do, which is far more valuable.
  • Remember the hypothesis? use that in the interview prep
    We believe that people like
    have a need for/problem doing
    We know we will have succeeded when , or
    which will contribute to
  • Hippo: Highest Paid Person’s Opinion
  • metrics- report progress + guide decision making + key insights
    its so easy to track so much, now we have to prioritize what is worth tracking
    Related:
    http://onstartups.com/tabid/3339/bid/96738/Measuring-What-Matters-How-To-Pick-A-Good-Metric.aspx
    https://blog.kissmetrics.com/qualitative-quantitative-analytics/
  • Who likes data? me-me-me-me-me-me
    Who likes a lot of data? me-me
    Who likes data that you can infer and take action on? me-me-me me-me-me me-me-me me-me-me
    Who likes data that doesn’t tell you much other than numbers? no-one

    It all comes down to one thing and one thing only: Does your data help you take action and make a decision.

    Related: https://blog.kissmetrics.com/vainest-metrics/
  • Pair-up exercise
    What would you track and classify them as qualitative, quant etc?
  • credit: Dave McClure
  • This is related to “growth hacking”
    http://jrom.net/metrics-for-pirates
  • Innovation through observation
    the art of prioritization and saying no- many times directly
  • linked to a ted talk.
  • Start w/ assumptions
    Keep a customer centric approach
    talk about user research
    talking about testing and validation
    communication is key to a PM’s success
    Respect for developers/engineers should come naturally
    Including your team (UX + Dev) early on for them to learn about the customer is a huge plus
  • credit: http://theleanstartup.com/principles
  • image credit: http://www.cyclosys.com/Practices/MethodologiesFramework

×