Basic outline of a talk by the same title

Building great products - workshop

Building Great Products
=======================

1. Intro
    a. talk
    b. me
2. Vision realized
    a. "Like Facebook" already failed
    b. it's your baby
    c. target customer
        1. why do they need it
        2. are others "passionate" or just agreeing
        3. not too broad
            a. too complex will not be used, KISS
        4. Ask how would they solve the problem?
    d. don't compromise the end game, but plan the little battles well
3. Make plans
    a. ticket system
    b. time management (Agile, Waterfall)
4. Gather requirements
    a. Talk with developers
    b. Developers will create what they "think" you mean if requirements are sparse
    c. Full requirements ensures your vision becomes their vision
    d. Build domain language – define names and meanings that business and developers stick to
5. timelines
    a. Hurry, but don't rush
    b. imaginary deadlines kill, make them real
    c. tweak feature set to time available, not the other way around
6. developers
    a. offshore, OK but need effective management in place
    b. Local,
        1. same timezone, or close
        2. speak the same "language" (refer to meaning != language)
        3. similar values
    c. Staffing companies, comes with certain guarantees and sometimes shortfalls
    d. diverse
        1. less = limited ideas
    e. Let them be professionals
        1. sometimes "no" is the best answer
    f. Ask, "do you write tests?"
        1. If "no" let them "go"
    g. You get what you pay for. No, really!
        1. Offshore is NOT cheaper over the course of a project
6. Staffing
a. agencies
b. user groups
c. conferences
d. job sites
e. referrals 
7. architecture
    a. API first
    b. mobile separate
    c. responsive site
    d. PHP, Javascript, Ruby (tool for the job)
    e. more modern than current (6 months from now it will be “normal”)
8. testing
    a. taking time to create/add tests saves timelines
    b. it is part of the job, or should be, for developers
9. Measure
    a. who is using it
    b. how are they using it (usability study)
    c. why are they using it
    d. conversion
    e. roi
10. Funding
    a. find the right partners
    b. don't accept money from someone you don't like
    c. focus should benefit you, not them. They will make money in any way.