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

The Incredible Fine Balance between a Project and a Product

Harish Pillay
November 05, 2016

The Incredible Fine Balance between a Project and a Product

Talk at FUDCon APAC 2016 in Phnom Pehn, Cambodia

Harish Pillay

November 05, 2016
Tweet

More Decks by Harish Pillay

Other Decks in Technology

Transcript

  1. The Incredibly Fine Balance between a Project and a Product

    Harish Pillay @harishpillay [email protected] [email protected] FUDCon APAC November 5, 2016 Phnom Pehn, Cambodia https://speakerdeck.com/harishpillay/the-incredible-fine-balance-between-a-project-and-a-product
  2. Characteristics of Projects • Idealism to solve a problem •

    No constraints – should it have a product roadmap?
  3. Characteristics of Projects • Idealism to solve a problem •

    No constraints – should it have a product roadmap? • No pain, no gain
  4. Characteristics of Projects • Idealism to solve a problem •

    No constraints – should it have a product roadmap? • No pain, no gain • Ask forgiveness, not permission
  5. Characteristics of Projects • Idealism to solve a problem •

    No constraints – should it have a product roadmap? • No pain, no gain • Ask forgiveness, not permission • Permissionless innovation
  6. Characteristics of Projects • Idealism to solve a problem •

    No constraints – should it have a product roadmap? • No pain, no gain • Ask forgiveness, not permission • Permissionless innovation • Risk taking – no Product Requirements Document
  7. Characteristics of Projects • Idealism to solve a problem •

    No constraints – should it have a product roadmap? • No pain, no gain • Ask forgiveness, not permission • Permissionless innovation • Risk taking – no Product Requirements Document • Fail fast, fail early – learn, grow and evolve
  8. Characteristics of Projects • Idealism to solve a problem •

    No constraints – should it have a product roadmap? • No pain, no gain • Ask forgiveness, not permission • Permissionless innovation • Risk taking – no Product Requirements Document • Fail fast, fail early – learn, grow and evolve • What else do you think a project has?
  9. Characteristics of Products • Reduce risk – both yours and

    your customers • Constrained in that it needs to meet the customer requirements
  10. Characteristics of Products • Reduce risk – both yours and

    your customers • Constrained in that it needs to meet the customer requirements • UX/UI finesse
  11. Characteristics of Products • Reduce risk – both yours and

    your customers • Constrained in that it needs to meet the customer requirements • UX/UI finesse • Scalability is important: how would you help the evolution of the product?
  12. Characteristics of Products • Reduce risk – both yours and

    your customers • Constrained in that it needs to meet the customer requirements • UX/UI finesse • Scalability is important: how would you help the evolution of the product? • Branding: project name <> product name
  13. Characteristics of Products • Reduce risk – both yours and

    your customers • Constrained in that it needs to meet the customer requirements • UX/UI finesse • Scalability is important: how would you help the evolution of the product? • Branding: project name <> product name • What else do you think a product has?
  14. What about People • Project people have a different motivation

    compared with Product people • The motivations of being in a project team is significantly different than being a product team.
  15. What about People • Project people have a different motivation

    compared with Product people • The motivations of being in a project team is significantly different than being a product team. • There may be overlaps, but it is few and far between