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.

Transcript

1. PROJECTS ARE NOT PRODUCTS D. Keith Casey Jr keith@caseysoftware.com @CaseySoftware
2. WHO AM I?
3. WHO AM I?
4. WHO AM I? http://TheAPIDesignBook.com
5. AGENDA • Assumptions • What we do • Where things break • What we should do • What we should avoid @CaseySoftware
6. AGENDA • Assumptions • What we do • Where things break • What we should do • What we should avoid @CaseySoftware
7. ASSUMPTIONS • Technical Backgrounds • We write code for a living • We read tech websites & blogs • We see interesting problems all the time @CaseySoftware
8. ASSUMPTIONS (CONT) • Technical Backgrounds • We hate sales • We hate marketing • We hate everything but writing good code @CaseySoftware
9. AGENDA • Assumptions • What we do • Where things break • What we should do • What we should avoid @CaseySoftware
10. STEP 1 We get our code ready • Extensible architecture • Scrub out junk • Automation • Scalability & Security @CaseySoftware
11. STEP 2 We get a website ready • Product description • Screenshots • Feature list • Support & payment pages @CaseySoftware
12. STEP 3 And then we wait… @CaseySoftware
13. STEP 4 And then we make a ton of money! @CaseySoftware
14. AGENDA • Assumptions • What we do • Where things break • What we should do • What we should avoid @CaseySoftware
15. STEP 1 (REVIEW) We get our code ready • Extensible architecture • Scrub out junk • Automation • Scalability & Security @CaseySoftware
16. We get our code ready • Extensible architecture • Scrub out junk • Automation • Scalability & Security STEP 1 (REVIEW) @CaseySoftware
17. We get our code ready • Extensible architecture • Scrub out junk • Automation • Scalability & Security STEP 1 (REVIEW) @CaseySoftware
18. We get our code ready • Extensible architecture • Scrub out junk • Automation • Scalability & Security STEP 1 (REVIEW) @CaseySoftware
19. We get our code ready • Extensible architecture • Scrub out junk • Automation • Scalability & Security STEP 1 (REVIEW) @CaseySoftware
20. STEP 2 (REVIEW) We get a website ready • Product description • Screenshots • Feature list • Support email • Payment pages @CaseySoftware
21. STEP 2 (REVIEW) We get a website ready • Product description • Screenshots • Feature list • Support email • Payment pages @CaseySoftware
22. STEP 2 (REVIEW) We get a website ready • Product description • Screenshots • Feature list • Support email • Payment pages @CaseySoftware
23. STEP 2 (REVIEW) @CaseySoftware
24. We get a website ready • Product description • Screenshots • Feature list • Support email • Payment pages STEP 2 (REVIEW) @CaseySoftware
25. We get a website ready • Product description • Screenshots • Feature list • Support email • Payment pages STEP 2 (REVIEW) @CaseySoftware
26. We get a website ready • Product description • Screenshots • Feature list • Support email • Payment pages STEP 2 (REVIEW) @CaseySoftware
27. 10 tasks: probably wrong: 4 possibly wrong: 4 probably ok: 2 OUR SCORE SO FAR.. @CaseySoftware
28. And then we wait… STEP 3 (REVIEW) @CaseySoftware
29. STEP 4 (REVIEW) And then we make a ton of money! @CaseySoftware
30. AGENDA • Assumptions • What we do • Where things break • What we should do • What we should avoid @CaseySoftware
31. BUSINESS MODEL CANVAS @CaseySoftware
32. @CaseySoftware
33. Define your market • Who are they? • Where do they work? • What sites do they visit? • Groups, clubs, associations, memberships, etc? @CaseySoftware
34. @CaseySoftware
35. 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
36. @CaseySoftware
37. Define your approach • How to reach your market? • Which ways are effective? • How much does it cost? • How much is a customer worth? @CaseySoftware
38. @CaseySoftware
39. 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
40. AGENDA • Assumptions • What we do • Where things break • What we should do • What we should avoid @CaseySoftware
41. Hiding from customers @CaseySoftware
42. Feature lists @CaseySoftware
43. “WOULD” questions @CaseySoftware
44. RECAP • Assumptions • What we do • Where things break • What we should do • What we should avoid @CaseySoftware
45. What’s missing in this process? @CaseySoftware
46. Code. @CaseySoftware
47. PROJECTS ARE NOT PRODUCTS D. Keith Casey Jr keith@caseysoftware.com @CaseySoftware
48. Who am I? http://TheAPIDesignBook.com