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

Projects are not Products (2017 Rev)

Projects are not Products (2017 Rev)

If you build it, they will come.. well no, not really. Not even close.

As developers, too often we believe the best tech wins. We want to believe customers care about clean code, the most features, and our architecture. It turns out, no one cares.

When we’re building products, we need to understand the problem we’re solving, who we’re solving it for, and how to reach them. In this session, we'll review concrete steps and discuss how to turn your project into a product.

Keith Casey

August 09, 2017
Tweet

More Decks by Keith Casey

Other Decks in Technology

Transcript

  1. AGENDA • Assumptions • What we do • Where things

    break • What we should do • What we should avoid @CaseySoftware
  2. AGENDA • Assumptions • What we do • Where things

    break • What we should do • What we should avoid @CaseySoftware
  3. ASSUMPTIONS • Technical Backgrounds • We write code for a

    living • We read tech websites & blogs • We see interesting problems all the time @CaseySoftware
  4. ASSUMPTIONS (CONT) • Technical Backgrounds • We hate sales •

    We hate marketing • We hate everything but writing good code @CaseySoftware
  5. AGENDA • Assumptions • What we do • Where things

    break • What we should do • What we should avoid @CaseySoftware
  6. STEP 1 We get our code ready • Extensible architecture

    • Scrub out junk • Automation • Scalability & Security @CaseySoftware
  7. STEP 2 We get a website ready • Product description

    • Screenshots • Feature list • Support & payment pages @CaseySoftware
  8. AGENDA • Assumptions • What we do • Where things

    break • What we should do • What we should avoid @CaseySoftware
  9. STEP 1 (REVIEW) We get our code ready • Extensible

    architecture • Scrub out junk • Automation • Scalability & Security @CaseySoftware
  10. We get our code ready • Extensible architecture • Scrub

    out junk • Automation • Scalability & Security STEP 1 (REVIEW) @CaseySoftware
  11. We get our code ready • Extensible architecture • Scrub

    out junk • Automation • Scalability & Security STEP 1 (REVIEW) @CaseySoftware
  12. We get our code ready • Extensible architecture • Scrub

    out junk • Automation • Scalability & Security STEP 1 (REVIEW) @CaseySoftware
  13. We get our code ready • Extensible architecture • Scrub

    out junk • Automation • Scalability & Security STEP 1 (REVIEW) @CaseySoftware
  14. STEP 2 (REVIEW) We get a website ready • Product

    description • Screenshots • Feature list • Support email • Payment pages @CaseySoftware
  15. STEP 2 (REVIEW) We get a website ready • Product

    description • Screenshots • Feature list • Support email • Payment pages @CaseySoftware
  16. STEP 2 (REVIEW) We get a website ready • Product

    description • Screenshots • Feature list • Support email • Payment pages @CaseySoftware
  17. We get a website ready • Product description • Screenshots

    • Feature list • Support email • Payment pages STEP 2 (REVIEW) @CaseySoftware
  18. We get a website ready • Product description • Screenshots

    • Feature list • Support email • Payment pages STEP 2 (REVIEW) @CaseySoftware
  19. We get a website ready • Product description • Screenshots

    • Feature list • Support email • Payment pages STEP 2 (REVIEW) @CaseySoftware
  20. AGENDA • Assumptions • What we do • Where things

    break • What we should do • What we should avoid @CaseySoftware
  21. Define your market • Who are they? • Where do

    they work? • What sites do they visit? • Groups, clubs, associations, memberships, etc? @CaseySoftware
  22. Define your value • Why are you valuable? • How

    much time, money, stress, risk do you save them? • How much money do you make them? @CaseySoftware
  23. Define your approach • How to reach your market? •

    Which ways are effective? • How much does it cost? • How much is a customer worth? @CaseySoftware
  24. Define their pain • How much time, money, stress, risk

    do you save them? • What did it “cost” last time? • How can you take advantage of that? @CaseySoftware
  25. AGENDA • Assumptions • What we do • Where things

    break • What we should do • What we should avoid @CaseySoftware
  26. RECAP • Assumptions • What we do • Where things

    break • What we should do • What we should avoid @CaseySoftware