Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Introduction to Product Development

Introduction to Product Development

Avatar for Jorge Suárez

Jorge Suárez

May 05, 2016

Other Decks in Technology

Transcript

  1. What’s my role? I oversee the development of products from

    idea to implementation. I’m the product CEO.
  2. What does that mean? I’m in charge answering this questions:

    What is the problem? Who has the problem? Do we want to solve the problem? What is the solution? How do we solve the problem?
  3. Business Analysis Customer Development Market Research UX Design Project Management

    What is the problem? Who has the problem? Do we want to solve the problem? What is the solution? How do we solve the problem? Insights Clustering User Interviews Stakeholder Mapping Customer Journey Personas Market Research Business Model Canvas KPIs Definition Validate Assumptions Sitemap or Workflow Paper Prototype Wireframe Use Cases Backlog Definition Roadmap Resource Planning
  4. Product Management User Experience Define Problem User Interviews Define Features

    User Stories Define Journey Workflow or Sitemap Define Experience Wireframe or Paper Prototype
  5. Minimum Viable Interview What are you trying to get done?

    Gather context How do you currently do this? Analyze current workflow What could be better about how you do this? Find opportunities
  6. 5 Whys Rule What are you trying to get done?

    Build a fence Why So I can plant a garden Why So I can grow my own food Why So I can save money in groceries Why User Story
  7. It’s all about the user. What the user wants to

    achieve? Define user stories What the user needs to do? Define requirements
  8. User Stories Format Persona + Need + Purpose Example As

    an user, I want to be able to search the users list to be able to find users by name. Requirements Use Case Search by name Use Case Description Search by name is the ability to find a person in the people list by their full name. Actor Persona Basic Flow • User inputs search criteria in search bar. • System searches people list for persons that matches the search criteria. • System shows a list of results. Alternate Flows No person have been added.
  9. Think of flows, not UI. What are the steps the

    user needs to take? Define customer journey What are the views this steps require? Define workflow What happens in each view? Define views
  10. The blueprint Design with blocks Keep it low-fi Don’t use

    color Always start on paper Organize elements by priority Label the components
  11. • Be nimble and agnostic. • Obsess over results, not

    process. • Start with real people – in their real context. • Listen and observe. Wants ≠ Needs. • Be user-centric. Let the user create the product. • Build to learn. Test the idea, not the execution. • Prototype early. Learn from failure. • Integrate quickly, in short build-and-learn-loops. • Keep it simple. Test one idea at a time. • Get involved. Don’t just code, fix problems.