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

building great music products: a beginner's guide for experts

2b89ba3ef5a3d20078678a6eef138fcc?s=47 lily szajnberg
February 20, 2015

building great music products: a beginner's guide for experts

2b89ba3ef5a3d20078678a6eef138fcc?s=128

lily szajnberg

February 20, 2015
Tweet

Transcript

  1. building great music products: a beginner’s guide for experts

  2. about me •interactive designer (digital and physical) •singer, saxophonist, beatboxer

    (acapella nerd) introduction
  3. about me •built products in education, science, health, and music

    for half of a decade ? ? introduction
  4. warning •music is a crowded & tricky space to build

    in introduction
  5. warning •music is a crowded & tricky space to build

    in •many constraints that are not your user’s problem introduction
  6. the basics to building •start (no really, stop talking and

    just start) overview
  7. the basics to building •start (no really, stop talking and

    just start) •build overview
  8. the basics to building •start (no really, stop talking and

    just start) •build •iterate overview
  9. the basics to building •start (no really, stop talking and

    just start) •build •iterate •move on overview
  10. •ask yourself what you want and then work backwards start

    what?
  11. •something that solves a definable problem or thrills and delights

    start what?
  12. what? •definable problem: start •i want a way to pick

    a drink that goes well with what i’m listening to.
  13. what? •definable problem: start •i want a guide to know

    if my dress is too short.
  14. what? •thrills & delights: start •i want a JARULE song

    auto generated based on how thug and emotional i am feeling.
  15. what? •thrills & delights: start •i want rob thomas to

    tell me when it’s 3am.
  16. who? •“don’t see the world as a market, but rather

    a place that people live in — you are designing for people, not machines.” -red burns start
  17. who? •“don’t see the world as a market, but rather

    a place that people live in — you are designing for people, not machines.” -red burns start •who are you designing for?
  18. who? •“don’t see the world as a market, but rather

    a place that people live in — you are designing for people, not machines.” -red burns start •who are you designing for? •test with real people, often, and early
  19. •“aka: do you give a Shit + can you get

    others to give a Shit.” - dave mcclure start why?
  20. •“aka: do you give a Shit + can you get

    others to give a Shit.” - dave mcclure start why? •do you give a Shit = is this something you deeply care about?
  21. •“aka: do you give a Shit + can you get

    others to give a Shit.” - dave mcclure start why? •do you give a Shit = is this something you deeply care about? •can you get others to give a Shit = is this something others deeply care about?
  22. start why? •building things is difficult, time-consuming, and expensive. •definable

    goal = north star •fuel = care
  23. start how? •“the biggest danger is not ignorance, but the

    illusion of knowledge.” -red burns
  24. start how? •understand your landscape

  25. start how? •understand your landscape •who else is doing something

    similar?
  26. start how? •understand your landscape •who else is doing something

    similar? •have they been successful? failed? why?
  27. start how? •what looks easy, is hard.

  28. build K.I.S.S.

  29. build K.I.S.S. •Keep It Simple, Stupid

  30. build K.I.S.S. •the issues are usually not technical

  31. build dream big, build small •have enough self-confidence to try

    new things
  32. build dream big, build small •have enough self-confidence to try

    new things •have enough self doubt to question
  33. build dream big, build small •have enough self-confidence to try

    new things •have enough self doubt to question •have enough self determination to keep building
  34. build use existing tools •existing framework: bootstrap + ruby +

    sinatra + heroku
  35. build use existing tools •existing framework: bootstrap + ruby +

    sinatra + heroku •existing prototyping: uxpin, omnigraffle, photoshop, post-its
  36. build use existing tools •existing framework: bootstrap + ruby +

    sinatra + heroku •existing prototyping: uxpin, omnigraffle, photoshop, post-its •existing code: github (fork it!)
  37. build use existing tools •existing framework: bootstrap + ruby +

    sinatra + heroku •existing prototyping: uxpin, omnigraffle, photoshop, post-its •existing code: github (fork it!) •existing people: recruit someone who’s done this
  38. build use existing data •no one wants to dine at

    an empty restaurant -clay shirky
  39. build use existing data •you’ll need data to fill the

    empty space of a new product
  40. build use existing data •mtv artists / cmt artists •viacom

    owns lots of data / information •we source lots of data for our artist pages
  41. build use existing data •echonest, amg, spotify, wikipedia, twitter, facebook

    (to name a few)
  42. build use existing data •curation! •echonest, amg, spotify, wikipedia, twitter,

    facebook (to name a few)
  43. build don’t wait, curate •wikipedia: asked professors to write articles

  44. build •wikipedia: asked professors to write articles •imdb: database created

    from writing down info from the credits don’t wait, curate
  45. build •wikipedia: asked professors to write articles •imdb: database created

    from writing down info from the credits •netflix: asked filmmakers to tag films with adjectives don’t wait, curate
  46. build •wikipedia: asked professors to write articles •imdb: database created

    from writing down info from the credits •netflix: asked filmmakers to tag films with adjectives •spotify/beats: partners with curators for playlists don’t wait, curate
  47. iterate •there is a constant juggling between the inherent contradictions

    of a management imperative of efficiency and the human reality of ambiguity and uncertainty prioritize
  48. iterate •there is a constant juggling between the inherent contradictions

    of a management imperative of efficiency and the human reality of ambiguity and uncertainty prioritize •read: shit will go wrong, scope will change, and users will poke holes in your beautiful precious product
  49. iterate •there is a constant juggling between the inherent contradictions

    of a management imperative of efficiency and the human reality of ambiguity and uncertainty prioritize •read: shit will go wrong, scope will change, and users will poke holes in your beautiful precious product •be ok with taking risks, making mistakes, and letting go
  50. move on keep reinventing •stay fresh •think outside the box

    •timing is key…try again (friendster, anyone?)
  51. application product basics + mtv artists & cmt artists •making

    $, paying $
  52. application product basics + mtv artists & cmt artists •making

    $, paying $ •(we already do these)
  53. application product basics + mtv artists & cmt artists •move

    on:
  54. application product basics + mtv artists & cmt artists •move

    on: •stay fresh (responsive)
  55. application product basics + mtv artists & cmt artists •move

    on: •stay fresh (responsive) •think outside the box (artists can edit)
  56. application product basics + mtv artists & cmt artists •move

    on: •stay fresh (responsive) •think outside the box (artists can edit) •timing is key…try again (not our first rodeo)
  57. application product basics + mtv artists & cmt artists •start

  58. application product basics + mtv artists & cmt artists •start

    •what: a place for fans and artists to connect. •what strengths do we have that we can offer to artists? (eyeballs, tv, opportunities, highlights)
  59. application product basics + mtv artists & cmt artists •start

    •what: a place for fans and artists to connect. •who: mtv, vh1, cmt audiences
  60. application product basics + mtv artists & cmt artists •start

    •what: a place for fans and artists to connect. •who: mtv, vh1, cmt audiences •why: because we are a global music brand
  61. application product basics + mtv artists & cmt artists •start

    •what: a place for fans and artists to connect. •who: mtv, vh1, cmt audiences •why: because we are a global music brand •how: reinvent what we have + let artists help
  62. application product basics + mtv artists & cmt artists •build

    •dream big, build small: agile/lean dev
  63. application product basics + mtv artists & cmt artists •build

    •dream big, build small: agile/lean dev •use existing tools/data: topspin, echonest
  64. application product basics + mtv artists & cmt artists •build

    •dream big, build small: agile/lean dev •use existing tools/data: topspin, echonest •curate: production team
  65. application product basics + mtv artists & cmt artists •iterate

    •built our own artist tools
  66. application product basics + mtv artists & cmt artists •iterate

    •built our own artist tools •album premieres
  67. application product basics + mtv artists & cmt artists •iterate

    •built our own artist tools •album premieres •partnered with spotify coming soon.
  68. recap music is messy •users don’t care how they get

    content, they will go to the first place they can find it
  69. recap music is messy •users don’t care how they get

    content, they will go to the first place they can find it •curation is king
  70. recap music is messy •users don’t care how they get

    content, they will go to the first place they can find it •curation is king •solutions can come from strange places
  71. recap music is messy •users don’t care how they get

    content, they will go to the first place they can find it •curation is king •solutions can come from strange places •art has always been valued for less than it should
  72. recap want to know the future?

  73. recap want to know the future? •ask a kid

  74. thanks! get in touch •@lilyszajnberg • •lily.szajnberg@mtvstaff.com